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

Base32 and Base16

04

Different group sizes create different alphabets and expansion ratios.

Related RFCs and changes

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

DIAGRAM§ 6 ↗
RFC 4648 · § 6EXAMPLE
3 / 3
Base32 and Base16Different group sizes create different alphabets and expansion ratios.Base32 and Base16Byte FF = 1111 11111111111100Base32 uses five-bit groups and its own rulesThe final group needs zero pad bits
03
Compare Base32

A different five-bit grouping needs its own alphabet and final-group rules.

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

Base32 maps five-bit groups to 32 symbols.

  • Base32 maps five-bit groups to 32 symbols.
  • Base32hex uses the extended-hex alphabet of §7.
  • Base16 maps each four-bit nibble to a hexadecimal character and needs no padding.
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 ↗