{
  "slug": "base64url",
  "term": "Base64url",
  "aliases": [
    "Base64 URL encoding",
    "URL-safe Base64"
  ],
  "definition": "Base64url is the RFC 4648 binary-to-text variant that uses minus and underscore instead of Base64's plus and slash symbols.",
  "note": "Alphabet: The changed symbols represent the same six-bit values; the input remains bytes, not Unicode characters. Padding is a separate protocol choice. Base64url does not universally mean that equals signs are forbidden. [base64-rfc]\n\nProfiles: JSON Web Signature specifies base64url without trailing equals signs, line breaks or whitespace. The signed representation is protocol-defined; do not normalize its text independently of signature verification rules. [base64-jws]\n\nDecoder labels: Node's base64 and base64url Buffer decoders both accept the other alphabet; its base64url encoder omits padding. Successful decoding therefore does not establish that an input used only URL-alphabet symbols. [base64-node]\n\nExample: Bytes 0xfb 0xff encode as +/8= in padded Base64 and -_8 in an unpadded URL profile. An exact-profile check also tests unused bits: -w encodes 0xfb canonically, while -x has nonzero unused bits. [base64-example]",
  "related": [
    "base64",
    "data-serialization"
  ],
  "status": "unknown",
  "advantages": [],
  "limitations": [],
  "supersedes": [],
  "supersededBy": [],
  "firstSeen": null,
  "lastSeen": null,
  "updated": "2026-11-21",
  "citations": [
    {
      "id": "base64-rfc",
      "title": "RFC 4648: Base-N encodings, sections 3-5 and 10",
      "url": "https://www.rfc-editor.org/rfc/rfc4648.html",
      "accessed": "2026-11-21"
    },
    {
      "id": "base64-jws",
      "title": "RFC 7515: JWS terminology, base64url encoding and signing input",
      "url": "https://www.rfc-editor.org/rfc/rfc7515.html#section-2",
      "accessed": "2026-11-21"
    },
    {
      "id": "base64-node",
      "title": "Node v24.22.2: Buffer binary-to-text encodings",
      "url": "https://nodejs.org/download/release/v24.22.2/docs/api/buffer.html#buffers-and-character-encodings",
      "accessed": "2026-11-21"
    },
    {
      "id": "base64-example",
      "title": "Hesela: Base64 checksum representations and native decoder observations",
      "url": "https://hesela.com/analyses/object-etags-checksums-conditional-writes/#base64-representation",
      "accessed": "2026-11-21"
    }
  ],
  "provenance": [
    "The example selects an unpadded URL profile. It is not a claim that every RFC 4648 application forbids padding.",
    "Native decoder acceptance is version-qualified and does not certify service-side acceptance or authentication."
  ]
}
