This standards reference on Base64Encoding explains openpgp in plain language for developers and everyday users.
Everything important stays private: try the matching converter or tool in your browser — files and tokens are not uploaded.
Read the full English article below for code samples and edge cases, or switch language anytime from the menu. We keep expanding translations from real user feedback.
OpenPGP messages and keys are often sent as ASCII armor (RFC 4880): a cleartext block with headers, Base64 body (76-character lines), and a CRC-24 checksum line starting with =.
The Base64 alphabet matches standard RFC 4648 (+/ with = padding). The extras are framing and the CRC, not a different alphabet.
Versus MIME Base64
MIME (RFC 2045)
OpenPGP armor
Line length
≤ 76
≤ 76
Headers
MIME Content-Transfer-Encoding
BEGIN / END armor
Checksum
none
CRC-24 (=XXXX)
Developer tips
Never treat armored text as encryption by itself—the armor is packaging; OpenPGP encryption is separate.
Strip headers before feeding the body to a generic decoder, or use a tool that understands armor.
Our encoder/decoder supports the OpenPGP ASCII armor standard for body encode/decode workflows; use the detector if you are unsure which wrapping you have.
Najczęściej zadawane pytania
Does this page upload my data?
No. Articles are static. Linked tools run locally in your browser unless a feature explicitly needs a network relay.
Can I request a translation or a new tool?
Yes — use the private feedback form. We prioritize what users ask for across languages.
What is the fastest way to try openpgp?
Open the homepage Base64 converter or the related tools linked on this page and paste a sample.
Komentarze (0)
Pytania, pomysły lub błąd w „OpenPGP ASCII armor”? Zostaw komentarz, oceń narzędzie lub odpowiedz innym.
Brak komentarzy. Podziel się opinią jako pierwszy!