does this pgp tool upload my message or keys?

when javascript runs, encryption happens entirely in your browser using openpgp.js and nothing leaves your device. with javascript blocked, a fallback mode encrypts on the server instead - it processes your input in memory for that single request and stores nothing, but the plaintext does travel to the server over an encrypted connection.

what do i need to encrypt a message?

only the recipient's public key. they decrypt it with their matching private key. nobody else - including this website - can read the encrypted output.

how do i know i'm encrypting to the right key?

ask the recipient to read out their key's fingerprint over a channel you already trust and match it against the key you pasted - a matching fingerprint proves the key is really theirs and rules out impostor keys.

what does "also sign" do?

it attaches your signature inside the encrypted package so the recipient can prove the message came from your key. signing needs your own private key and its passphrase.

home / tools / pgp encrypt

pgp

key generator encrypt decrypt sign verify armor cleaner fingerprint compare

tor & coins

onion status onion validator vanity onion bitcoin validator monero validator

everyday

passphrase sha-256 text diff base convert

pgp encrypt

scramble a message so that only one person can read it: the one whose public key you paste below. you need their public key (starts with -----BEGIN PGP PUBLIC KEY BLOCK-----) and your text. that's all.

paste the recipient's public key

this decides who can read the message - and who can't. get the block straight from the recipient (their website, a keyserver they point you to, or handed over in person), never from an unverified email. before sending anything sensitive, compare the key's fingerprint - the short checksum that identifies it - with its owner over a channel you already trust. encrypting to a look-alike key means an impostor holds the private half and reads everything you send. two keys look similar? check them in the fingerprint comparator.

a block starting with BEGIN PGP PRIVATE KEY BLOCK will technically work too, but that's almost always a mix-up - encrypt to the recipient's public key.

write your message

also prove it's me - sign with my private key

your private key

its passphrase

encrypt it

where should this run?

local · in your browser most private - nothing leaves your device. needs javascript. server · on our machine works without javascript. processed in memory during this one request - never stored or logged.

javascript is off: the local option is unavailable - your request runs on our server instead. it is processed in memory during this one request and never stored or logged.

privacy note

with javascript enabled, encryption happens entirely in your browser - your message and keys never leave your device. with javascript blocked, the same button submits this form and the encryption runs on our server instead: your input is processed in memory for that one request, then discarded - nothing is logged or stored - but the plaintext does cross the network to reach us. if that ever bothers you, enable javascript.

faq

is my message or my key uploaded?: not when javascript is on: everything runs inside your browser tab - open dev tools and watch the network panel stay quiet when you click encrypt. when javascript is blocked, the browser-mode can't work, so the form posts to the server and we encrypt there, in memory, keeping nothing. that server fallback only supports rsa keys.
how do i know i'm encrypting to the right key?: ask the recipient to read out their key's fingerprint over a channel you already trust (a voice call, or in person) and match it against the key you pasted - the fingerprint comparator does the diffing for you. a matching fingerprint proves the key is really theirs; skipping this check is exactly how impostor attacks happen.
what does "also sign" do?: it attaches your signature inside the encrypted package so the recipient can prove the message came from your key, not just from whoever knows their address. needs your private key + passphrase to do that.
i don't have a public key to encrypt to: then ask the recipient to send theirs, or use the key generator if you actually want to make your own pair first.
how long should my message be?: any length works. pgp encrypts text of any size into a similar-sized armored block.