Base64 Encoder & Decoder
Encodes text to Base64, or decodes Base64 back to the original text. Common for query parameters, Authorization headers and temporarily hiding plain text.
Encode and decode Base64 online — URL-safe base64url, padding options, binary-safe text, with RFC 4648 and atob()/btoa() notes. Free, in your browser.
Steps and notes
What is Base64 Encoder & Decoder — Padding, URL-Safe, Binary-Safe?
Base64 is an encoding that represents data using 64 printable ASCII characters, so payloads can travel through text-only channels: email (MIME), data URLs, HTTP Basic credentials and JSON fields. It maps every 3 bytes to 4 characters and pads the tail with = when the input is not a multiple of 3 bytes.
- Enter the text on the left
- The encoded result appears on the right immediately
- To decode, flip the direction and paste the Base64 into the left side
- Base64 is encoding, not encryption — anyone can reverse it, so never use it to store passwords
Frequently asked questions
- Is Base64 encryption?
- No. It is a reversible encoding with no secret key — anyone can decode it. Never use it to protect passwords or tokens; use real encryption or hashing for that.
- Why does the result end with one or two = signs?
- Base64 processes input in 3-byte groups. When the last group is incomplete, = characters pad the output to a multiple of 4. The padding carries no data and can stay as it is.
- Why does my Base64 break inside a URL?
- The standard alphabet uses + and /, which have special meanings in URLs. Switch on the URL-safe option when decoding such values, and percent-encode the string before putting it into a query parameter.
Category: Converter
JWT tools workflow
JWT Decoder & Parser — Inspect Header, Payload and Expiration → Base64 Encoder & Decoder — Padding, URL-Safe, Binary-Safe → Date Converter — Formats, Time Zones and ISO 8601 → Unix Timestamp Converter — Epoch to Date, Seconds vs Milliseconds