Decrypt a PGP message locally in your browser with your private key and passphrase. The original file comes back. No upload.
Running locally on your device ...
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
If you have received a PGP-encrypted file - usually with the extension .asc or .gpg - then it is addressed to your public key and can only be opened with your private key. This tool does exactly that: from the unreadable message the exact original file is reconstructed, byte for byte identical to what the sender encrypted. The content was protected the whole way and only becomes readable here, locally on your device.
Paste your private key into the field and enter the passphrase you protected it with. The passphrase unlocks the key strictly here in the browser - it does not decrypt the message directly, it makes the private key usable. Then you drop the received .asc or .gpg file and get the decrypted original file to download, with its original name minus the PGP extension.
Everything runs locally through the bundled OpenPGP library (openpgp.js 6.3.1, following the OpenPGP RFC 9580 standard); neither the key nor the passphrase nor the message is sent anywhere. If the passphrase is wrong, the message belongs to a different key, or it was altered in transit, you get an honest error message instead of a half-decrypted or wrong file.
| Input formats | ASC, GPG, PGP |
|---|---|
| Batch processing | No |
| Processing | Locally in your browser (JavaScript) |
| File upload | None |
Limitations: You need the matching private key and its passphrase - this is not a cracking tool and does not recover lost keys or passphrases. Messages encrypted to a different key cannot be opened and are honestly rejected. Signatures are not verified: the tool only decrypts and does not establish who created the message; an embedded signature is flagged as unverified in the result.
No. The key, passphrase and message stay entirely local in the browser and are not sent or stored.
The private key cannot be unlocked and you get an honest error message. A wrong file is never produced.
Yes, byte for byte identical. OpenPGP additionally protects the encrypted message against later modification: if it was altered in transit, decryption fails instead of returning altered content. It does not establish who created the message - that would require a verified signature.
Yes, as long as they are encrypted to your key. The tool reads standard OpenPGP messages in both ASCII-armor and binary form.
No. That would require the sender's public key, which this tool does not ask for. If the message contains a signature, the result explicitly notes that it was left unverified. If you need to establish origin, verify it additionally with GnuPG or another OpenPGP program.