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

Base64url alphabet

03

The URL-safe alphabet changes two symbols without changing the six-bit grouping.

Related RFCs and changes

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

DIAGRAM§ 5 ↗
RFC 4648 · § 5EXAMPLE
3 / 3
Base64url alphabetThe URL-safe alphabet changes two symbols without changing the six-bit grouping.Base64url alphabetAlphabet indices 62 and 63-_Base64urlPadding omission requires the consuming profile
03
Apply the profile

Padding behavior comes from the consuming protocol, not the alphabet name alone.

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

Base64url uses - and _ instead of + and /.

  • Base64url uses - and _ instead of + and /.
  • It is distinct from standard Base64.
  • Omitting padding requires an explicit profile or an implicitly known data length as described in §5.
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 ↗