Skip to content
Encoding
Base64
Boundary
Text or bytes
Runtime
Browser

Encode bytes as standard Base64 or Base64url

Select standard Base64 or Base64url and retain or omit its canonical padding deliberately.

Local processingNo sign-upNo files or upload

Encode Base64

Limited to 512 KiB of bytes and 1 MiB of encoded text.

Tool Swim does not upload, fetch, save, log, convert files, or create presets from these values.

Selected Base64 representation

Decoder reports keep lowercase hexadecimal authoritative.

What this tool proves

Explicit byte-to-text semantics

Standard Base64 uses + and / while Base64url replaces them with - and _. They are separate profiles, not interchangeable spellings.

URL-safe alphabet and percent encoding are separate concerns

Standard Base64 uses + and / while Base64url replaces them with - and _. They are separate profiles, not interchangeable spellings.

Three source bytes become four symbols. The unpadded option removes only terminal equals signs and never changes the alphabet implicitly.

Bytes stay explicit, private, and bounded

Encoder text is converted with UTF-8 only after malformed surrogate pairs are rejected. Hex mode accepts exact byte pairs without 0x, spaces, or separators. Decoder hex is authoritative; a text preview appears only when the bytes are valid UTF-8.

The work starts only when you submit the form. Source text, byte values, and results stay in the current browser tab; Tool Swim does not upload them, log their content, save presets, or call a developer API.

Base16, Base32, Base64, and Base85 allow at most 512 KiB of source or decoded bytes and 1 MiB of encoded text. Bitcoin Base58 is limited to 4,096 bytes or 5,600 characters because generic radix conversion is quadratic.

Primary references

Questions and answers

Related Base Encoding tools