Visual RFC.
ALL RFCs / RFC 2045
Read the RFC ↗
RFC 2045 / MECHANISM GUIDE

Base64 body encoding

04

Base64 converts body octets into a restricted alphabet suitable for mail transport.

Related RFCs and changes

“Updates” changes part of an earlier RFC. “Obsoletes” replaces it. This list shows selected related documents.

DIAGRAM§ 6.8 ↗
RFC 2045 · § 6.8EXAMPLE
3 / 3
Base64 body encodingBase64 converts body octets into a restricted alphabet suitable for mail transport.Base64 body encodingTWFuBase64: TWFuMIME wraps encoded lines at at most 76 characters
03
Wrap for MIME transport

Use the MIME line-length rules, distinct from generic no-wrap Base64 profiles.

Protocol participantThreat or exceptionProtocol controlSimplified drawings · precise section references
KEY POINT

Three bytes become four encoded characters.

  • Three bytes become four encoded characters.
  • MIME encoded lines must not exceed 76 characters.
  • Base64 adds no confidentiality or authenticity.
DETAILS

Examples are illustrative. Consult the linked RFC and its errata for implementation details.

Read the RFC section ↗

Diagrams simplify the RFC. Read the linked sections for complete requirements.

Privacy
All chapters in this RFC
  1. MIME entity headers
  2. Content type and charset
  3. Quoted-printable bytes
  4. Base64 body encoding
  5. Canonical form and safety
RFC 9700 / CHAPTERS

Chapters

For full details, tables, algorithms, and exceptions, read the original RFC.

RFC status and corrections ↗