Decrypt one or more .gxenc files locally in your browser with your password and get the original files back. Nothing leaves your device. No upload.
Running locally on your device ...
0%
Your files never left your device
No. Everything runs in your browser - your file never leaves your device. How this is verifiable
A .gxenc file is the result of the "Encrypt file" tool: an encrypted container that holds the original file in unreadable form. This tool reverses that step - with the correct password the exact original file is reconstructed, byte for byte identical to its starting state. You can also drop several .gxenc files in one run; each one is decrypted individually.
Every container carries its own salt and initialisation vector inside it, so the matching key can be derived from your password again. If the password is wrong or a file was altered, the GCM check fails for that specific file and you get a clear error message instead of a broken file.
Here too everything happens strictly locally through the browser’s native Web Crypto interface; neither the encrypted files nor your password is sent anywhere. If you drop several files at once, the one password you enter applies to ALL files in that run - if they came from separate encryption runs with different passwords, decrypt them in separate runs. If a .gxenc file kept its original name during encryption, the decrypted file automatically gets its original name and extension back.
| Input formats | GXENC |
|---|---|
| Batch processing | Yes |
| Processing | Locally in your browser (JavaScript) |
| File upload | None |
Limitations: You need to know the password - this is not a cracking tool and does not recover forgotten passwords. With several files in one run, the same password is tried for all of them - files with a different password need their own run. It only reads .gxenc containers from the sibling "Encrypt file" tool; other encryption formats are honestly rejected.
No. Decryption and password stay entirely local in the browser - just like when encrypting.
GCM authentication fails and you get an honest error message. A half-decrypted or wrong file is never produced.
Yes, byte for byte identical. AES-GCM guarantees the content is unchanged.
Only .gxenc files from this tool and only with the correct password. It is not a password cracker.
Because encryption only appends ".gxenc" to the original name; decryption strips that suffix off again.
Yes. Drop several .gxenc files in one run; each is decrypted individually. Important: the one password you enter is then used for ALL files in that run.