Get the recipient's public key.
Obtain their age1… recipient or SSH public key — or just their GitHub username if they publish keys there.
The point of encrypting to a recipient is that the channel no longer matters. Encrypt to their key, then send the .age over email, chat, or a shared drive — only they can open it.
Obtain their age1… recipient or SSH public key — or just their GitHub username if they publish keys there.
In AgePony, add their key as a recipient and encrypt the file. Choose armored output if you will paste it into a message, binary if you will attach a file.
Because the file is encrypted to the recipient, the transport does not need to be secure. Email, chat, cloud storage — all fine. Anyone intercepting it sees only ciphertext.
The recipient opens the .age in AgePony or with the age CLI using their private identity.
If they need to be sure the file is from you and unmodified, also sign it and send the .sig. They verify with your public key.
Yes — the file is encrypted end to end before it leaves your device. Email only carries ciphertext.
Sign when the recipient needs to confirm authorship and integrity, such as for releases or important documents.
They cannot open it unless you encrypted to their key. Encrypt only to the intended recipient's key.
Yes — add every recipient's key so each can decrypt independently.
Free file encryption for iOS and Android. No accounts, no tracking, no servers.