Why does it say the file was not produced here?

Every file this site encrypts begins with a specific eight-byte marker. Without it, the tool stops rather than attempting to interpret a layout it does not understand. Encrypted output from other software uses different containers and is not interchangeable.

It refuses even though I am sure of the password.

Then the file has changed since it was sealed. Re-download it from wherever it was stored, since a truncated or partially synced copy is the usual culprit, and check that no tool in the path tried to be helpful by decompressing or re-encoding it.

Why did I get a .bin file back?

Because the original extension was dropped when it was encrypted. The contents are intact and correct; only the name lost its type. Rename it to the right extension and it will open normally.

Can several files share one password?

Yes, and they can be decrypted together in one pass. Each file still has its own random salt and initialisation vector, so reusing a password across files does not weaken any of them.

Decrypt File

Open a .enc file made here and check it hasn't been altered.

Everything runs inside your browser. Your files never leave your device.

Drop your files here

.enc · they stay on this device

Ask about Decrypt File

Questions about what this tool does, which option to pick, or what it can and cannot handle.

The question you type here is sent to an AI provider to be answered — your files and whatever you put in the tool above are not, and the assistant cannot see them. Answers are generated and can be wrong. The tool itself is not guessing: it runs deterministic code on your device.

About the Decrypt File

The counterpart to the file encryption tool. Give it a “.enc” file produced here and the password it was sealed with, and it returns the original bytes under the original name.

Everything needed to derive the key again lives in the file's own header: the sixteen-byte random salt, the iteration count, and which hash the derivation used. Nothing about the settings on this page affects the outcome, which is deliberate — a file encrypted with one set of parameters must remain openable when the page's defaults have moved on. The figures reported alongside your result are the ones the file itself specified.

Filenames are restored by removing the “.enc” suffix, so “contract.pdf.enc” becomes “contract.pdf” again. When the original extension was not preserved at encryption time, the result is handed back as a plain “.bin”. That is not the tool being unhelpful — it genuinely does not know what the bytes are, and guessing a file type from content it cannot inspect would be a fabrication. Rename it yourself once you know.

The most useful property of this page is the one that reports failure. Because AES-GCM checks an authentication tag over the entire file before releasing any of it, a successful decryption is proof that not one byte has changed since the file was sealed. Storage corruption, a truncated download, an interfering proxy, deliberate tampering: all of them produce a refusal rather than a quietly damaged document. A tool that returned something anyway would be worse than useless for anything you actually needed to trust.

How to use it

1Drop in the .enc files you want to open. Several at once is fine if they share a password.
2Enter the password they were encrypted with.
3Press the button. The wait is the key derivation running the same number of rounds that were used to seal the file.
4Download the restored files. The summary confirms the derivation settings that were read from the file itself.

Questions

Why does it say the file was not produced here?: Every file this site encrypts begins with a specific eight-byte marker. Without it, the tool stops rather than attempting to interpret a layout it does not understand. Encrypted output from other software uses different containers and is not interchangeable.
It refuses even though I am sure of the password.: Then the file has changed since it was sealed. Re-download it from wherever it was stored, since a truncated or partially synced copy is the usual culprit, and check that no tool in the path tried to be helpful by decompressing or re-encoding it.
Why did I get a .bin file back?: Because the original extension was dropped when it was encrypted. The contents are intact and correct; only the name lost its type. Rename it to the right extension and it will open normally.
Can several files share one password?: Yes, and they can be decrypted together in one pass. Each file still has its own random salt and initialisation vector, so reusing a password across files does not weaken any of them.