What Is File Decryption?
File decryption is the reverse of encryption. It takes an encrypted file — which appears as random, unreadable bytes — and, using the correct key (derived from a password), restores it to its original readable form. Without the password, the process is mathematically infeasible. With the password, it happens in milliseconds. This asymmetry is what makes encryption such a powerful privacy tool.
Every day, millions of people decrypt files: a doctor opening a patient's encrypted medical record, a lawyer receiving a signed contract, a journalist receiving a leaked document, a business owner restoring a backup. Decryption is not an exotic technique used only by hackers. It is a fundamental operation of modern digital life, and it needs to be as simple as clicking a button.
This tool makes decryption just that simple. Upload your .enc file, enter the password, and download the original. Behind the scenes, the tool performs a cryptographic operation that is identical in every way to what banks, governments, and secure messaging apps do — except that it runs entirely in your browser, and no data ever touches a server.
How AES-256-GCM Decryption Works
AES-256-GCM is a symmetric cipher, which means the same key that encrypted the file is used to decrypt it. That key is not stored anywhere — it is derived from your password at the moment you click "Decrypt File", and it exists only in your browser's memory for a few milliseconds before being used to decrypt the file. Then it is discarded.
Here is the exact sequence of operations that happen when you decrypt a file:
- Read the file header. The tool reads the first 33 bytes of the file to identify the format and extract the salt, nonce, and version byte.
- Derive the key. Your password is combined with the salt using PBKDF2-HMAC-SHA256 with 200,000 iterations. This produces the 256-bit AES key.
- Attempt decryption. The ciphertext is passed to AES-256-GCM along with the key, nonce, and auth tag. The GCM tag is verified first — if any byte of the file has been changed, decryption fails immediately.
- Verify the result. If GCM authentication succeeds, the plaintext is returned. If it fails, the tool shows a generic error.
- Download. The browser creates a Blob and downloads the restored file with the original name.
The entire process is deterministic: the same file with the same password will always decrypt to the same result. This is why you can decrypt your file years from now, as long as you still have the password and the file has not been corrupted.
Why GCM Prevents Silent Corruption
One of the most important properties of GCM decryption is integrity verification. When AES-GCM encrypts data, it produces two outputs: the ciphertext and a 128-bit authentication tag. When you decrypt, GCM recomputes the tag from the ciphertext and compares it with the stored tag. If they do not match, decryption refuses to output anything.
This means that if your encrypted file has been corrupted — by a bad disk sector, a failed download, or an attacker trying to modify the ciphertext — you will know immediately. You will not silently receive garbled plaintext. This is a critical property for files that must be reliable (like backups and contracts) as well as for files that must be secure (like source documents).
Where Does the Password Come From?
The password you used to encrypt the file is the only password that will decrypt it. There is no "master password", no recovery code, and no backdoor. If you encrypted the file yourself, you set the password. If someone sent you an encrypted file, they should have shared the password with you through a separate, secure channel (Signal, a password manager, a phone call).
This separation of channels is intentional. If someone sends you the file and the password in the same email, and that email is intercepted, the attacker has both pieces. By keeping the file and password separate — file via one channel, password via another — you force an attacker to compromise two independent systems to reach your data.
If you do not have the password, there is no way to decrypt the file. Cryptographic security relies on this. Any website or service that claims to "recover" an AES-256-GCM encrypted file without the password is lying or running a scam.
Why Browser-Side Decryption Is Safer
The traditional approach for online decryption tools is to upload the encrypted file to a server, decrypt it there, and send the result back. This creates a window in which the decrypted file — and the password you typed — exist on someone else's machine. Even if the service is honest today, the data may be retained in logs, backups, or memory. If the service is compromised tomorrow, your data is at risk.
This tool eliminates that risk entirely. The encrypted file is read into your browser's memory. The password is read into your browser's memory. Decryption is performed by your browser using the Web Crypto API — a native, browser-vendor-implemented cryptographic library. The decrypted result is downloaded directly to your device. The server is never involved in the decryption itself.
This design also makes the tool work offline. Save the HTML page to your desktop, open it without a network connection, and you can decrypt files without any internet. This is essential for air-gapped environments, offline laptops, and situations where you simply do not trust the network.
Common Decryption Errors and What They Mean
| Error | Cause | Solution |
|---|---|---|
| "Wrong password" | Password does not match the one used to encrypt | Try again, check caps lock, verify in a password manager |
| "File is not a valid encrypted file" | File does not start with FENC | You may have uploaded the wrong file |
| "File is too small or corrupted" | File is shorter than the minimum header | Re-download the original encrypted file |
| "Unsupported version" | File was encrypted by a newer version | Use the same version of the tool that encrypted it |
| "Authentication failed" | GCM tag mismatch — file was modified | Restore the file from a known-good copy |
Note that "wrong password" and "authentication failed" produce the same error in GCM, deliberately. If the tool told you which one it was, an attacker could use that information to distinguish between a password guess that partially worked and one that did not — this is a subtle but real security property.
What to Do If You Forgot the Password
If you have genuinely forgotten the password, there is no path forward. This is not a limitation of the tool — it is a property of the cryptographic design. AES-256-GCM with a strong password is not brute-forceable. Even with a supercomputer, testing every possible password would take longer than the age of the universe for any reasonable password length and complexity.
Before giving up, try these things:
- Check your password manager. Most people store their encryption passwords there.
- Check your email. If you emailed yourself the password (a bad idea, but common), it is in your sent folder.
- Check written notes. Look in notebooks, sticky notes, or wherever you might have written it.
- Try variations. Maybe you added a number at the end, changed case, or used a similar phrase.
- Look for a text file. If you used the "Download" button when encrypting, a text file with the password may be in your Downloads folder.
If none of these work, the file is unrecoverable. Learn from the experience: in the future, always store the password in a password manager, keep a backup of the original file, and consider using a passphrase rather than a random string.
Decrypting Files from Different Sources
Files encrypted with this site
Files created by the companion File Encryption tool use a documented, self-describing format. This decryption tool reads that format automatically — just upload the file and enter the password.
Files encrypted with other tools
This tool only supports the FENC format. Files encrypted with GPG, age, 7-Zip AES-256, OpenSSL default format, or any other tool require the corresponding decryption tool. Use the tool that matches the encryption method.
Files with a different extension
If the file does not end in .enc, you can still try to decrypt it. The tool inspects the file's magic bytes, not its name. If it starts with FENC, it will decrypt. If it does not, the tool will report an error.
Security Best Practices After Decryption
Once you have decrypted a file, you now have two files: the original encrypted file and the decrypted plaintext. Both deserve care.
- Delete the decrypted file when you are done. The whole point of encryption is to protect the plaintext; if you leave copies lying around, the protection is gone.
- Use a secure delete (like
shredon Linux orsrmon macOS) rather than a simple delete, so the plaintext cannot be recovered from disk. - Keep the encrypted file as the master copy. If you need to share the file again, send the encrypted version, not the plaintext.
- Never email the decrypted file. Email is not encrypted end-to-end by default. If you must share the plaintext, use an encrypted channel (Signal, PGP, a secure file sharing service).
- Verify the file before sharing it. Compare a hash (SHA-256) of the decrypted file with a hash the sender can provide. If they match, the file is intact.
Decrypting Without This Tool
The FENC format used by this site is documented in the companion encryption page. If you ever need to decrypt a file without access to this website, you can do so with a small script. Here is the outline:
- Read the file bytes and verify it starts with
FENC. - Extract the version byte, salt (16 bytes), nonce (12 bytes), and ciphertext (rest of the file).
- Derive the 32-byte key from your password and the salt using PBKDF2-HMAC-SHA256 with 200,000 iterations.
- Use AES-256-GCM to decrypt the ciphertext with the key and nonce.
- Verify the GCM tag, then write the plaintext to a new file.
Every major programming language has libraries for this: Python's cryptography package, Node.js's built-in crypto, PHP's openssl_decrypt, Java's javax.crypto, Go's crypto/aes. The format is simple enough that you can implement it in an afternoon if you ever need to.
Why Decryption Is Safe Even Though It Looks Scary
Some users hesitate to use online decryption tools because they worry the tool might "see" their decrypted data. This is a reasonable concern — many tools do exactly that. But this tool is different, and the difference is architectural: the decryption happens in your browser, using the same JavaScript engine that renders every other page. There is no server component that receives the file. You can verify this yourself:
- Open your browser's Developer Tools (F12).
- Go to the Network tab.
- Clear the list, then decrypt a file.
- Watch the requests — you will see only the initial page load. No file upload, no password POST, no decrypted file download request.
If you want even more verification, disconnect your internet before clicking "Decrypt File". The decryption will still work — because the file and password never left your machine.
Security Guarantees
| Property | Guarantee |
|---|---|
| Confidentiality | AES-256-GCM with 256-bit key — unbreakable by brute force |
| Integrity | 128-bit GCM auth tag — any tampering detected before output |
| Key derivation | PBKDF2-HMAC-SHA256 with 200,000 iterations |
| Randomness | CSPRNG (crypto.getRandomValues) for salt and nonce (used at encryption time) |
| Server exposure | None — file and password never leave your browser |
| Password storage | None — the password exists only in your browser's memory |
| File storage | None — the decrypted file is generated locally and downloaded directly |
| Standards | NIST FIPS 197 (AES), NIST SP 800-38D (GCM), RFC 8018 (PBKDF2) |
Frequently Asked Questions
Is my file uploaded to your server?
Do you store my password?
What if I enter the wrong password?
Can I recover my file if I forget the password?
What file types can I decrypt?
FENC format used by this site. That includes any type: documents, images, videos, archives, code, keys, backups.Can I decrypt files made by other tools?
Why is there a password generator on a decrypt page?
Is AES-256-GCM safe from tampering?
Does this work offline?
Is Web Crypto API secure?
What happens if the encrypted file is corrupted?
Does this work on mobile?
Is this tool free?
Related Tools You Might Find Useful
Encryption and decryption are only part of the privacy toolkit. Here are some other tools on this site that pair well with file decryption:
External Resources and Further Reading
If you want to go deeper into the cryptography and standards behind this tool, here are some authoritative resources:
- NIST FIPS 197 — the official specification for AES
- NIST SP 800-38D — the specification for GCM mode
- RFC 8018 — the specification for PBKDF2
- MDN Web Crypto API — Mozilla's documentation
- OWASP Cryptographic Storage Cheat Sheet — best practices
- GnuPG — PGP-compatible encryption