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

Base64 bit groups

01

Three input bytes become four six-bit alphabet indices.

Related RFCs and changes

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

DIAGRAM§ 4 ↗
RFC 4648 · § 4EXAMPLE
3 / 3
Base64 bit groupsThree input bytes become four six-bit alphabet indices.Base64 bit groupsASCII: ManTWFu010011 010110 000101 10111024 input bits → four 6-bit alphabet indices
03
Look up symbols

Those indices encode as TWFu.

Protocol participantThreat or exceptionProtocol controlSimplified drawings · precise section references
WHAT CHANGED
RFC 3548RFC 4648 §13

This revision adds the Base32 extended-hex alphabet and test vectors, among other clarifications.

Read the updated RFC section ↗
KEY POINT

Base64 uses A–Z, a–z, 0–9, +, and /.

  • Base64 uses A–Z, a–z, 0–9, +, and /.
  • Padding completes a final partial quantum when required.
  • Encoding does not provide encryption or integrity.
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. Base64 bit groups
  2. Padding and pad bits
  3. Base64url alphabet
  4. Base32 and Base16
  5. Strictness and canonical form
RFC 9700 / CHAPTERS

Chapters

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

RFC status and corrections ↗