convert

PGP Armor

Wrap binary into OpenPGP ASCII armor with a CRC-24 checksum (or unwrap an existing armored block back to bytes + headers). Doesn't encrypt or sign — that's pgp-encrypt / pgp-sign. This tool only handles the armoring envelope.

Loading…

About PGP Armor

PGP Armor wraps raw binary into OpenPGP ASCII armor with a CRC-24 checksum, or unwraps an existing armored block back into bytes plus its headers. It handles only the armoring envelope, the BEGIN/END text wrapper that lets binary keys and messages travel safely through email and chat. It does not encrypt or sign anything (that's pgp-encrypt and pgp-sign), and everything runs locally in your browser.

Category
convert
Input
Accepts: */*.
Output
Outputs: text/plain.
Cost
Free, runs in your browser
Memory
low
Privacy: PGP Armor runs entirely on your device. Files you provide never leave your browser — no uploads, no server, no tracking. The page works offline once loaded.

Common uses

  • Convert a binary GPG export into a pasteable ASCII-armored block for an email or wiki
  • Decode an armored PGP message back to its raw bytes to inspect the underlying packets
  • Verify the CRC-24 checksum on an armored block someone sent you before processing it
  • Read the armor headers (Version, Comment) off a key block without a full PGP toolchain
  • Re-armor binary key material that arrived as an attachment so it can be shared as text
  • Round-trip a file through armor and back to confirm it survives copy-paste intact

Frequently asked questions

Does this encrypt or sign my data?

No. PGP Armor only adds or removes the ASCII-armor envelope and CRC-24 checksum. Use pgp-encrypt to encrypt or pgp-sign to sign.

What can I feed it?

Any file, since it accepts all types. In the armor direction it wraps the bytes; in the unwrap direction it reads an armored text block back to bytes and headers.

What standard does it follow?

OpenPGP ASCII armor as described in RFC 4880, including the CRC-24 checksum line.

Is my key material uploaded anywhere?

No. Armoring and de-armoring happen entirely in your browser, so sensitive bytes never leave your device.

Why is the checksum important?

The CRC-24 catches corruption introduced when a block is copied, pasted, or line-wrapped, so a tampered or truncated block can be spotted.

Keywords

  • pgp
  • armor
  • ascii-armor
  • encode
  • decode
  • crc24
  • rfc4880

Try next