Pick a direction
Text to Base64, Base64 back to text, the URL-safe alphabet without padding, or percent-encoding for query strings and links.
Free tools · Data
Base64, URL-safe Base64 and percent-encoding both directions, converted as you type — computed on your device, never uploaded.
Encode · decode · convert
Base64, URL-safe Base64 and percent-encoding both directions, converted as you type. Your text never leaves this page.
Converted text appears here with byte counts.
How it works
The same byte-table arithmetic behind every auth header and data URI, running here without accounts or uploads.
Text to Base64, Base64 back to text, the URL-safe alphabet without padding, or percent-encoding for query strings and links.
Conversion runs on every keystroke with byte counts on both sides — or load the per-operation sample to see the shape instantly.
Take tokens, data URIs and encoded parameters straight into configs, headers and tickets.
Questions
If you manage servers by hand, see the engineering services behind this tools series.
No. Encoding and decoding run entirely in your browser over explicit byte tables — the page makes no network requests with your data. You can verify this in your browser's developer tools or disconnect from the network after the page loads.
Standard Base64 uses + and / with = padding, which break URLs and filenames. Base64URL swaps in - and _ and drops the padding. Tokens and JWT parts use the URL-safe form; email attachments and data URIs usually use standard.
Yes — text is encoded as UTF-8 first, so any Unicode survives the round trip. Decoding bytes that are not valid UTF-8 fails with a clear error instead of mojibake.
No. It is an encoding anyone can reverse — it hides nothing. Never treat Base64 output as protected; encrypt first if secrecy matters.
Usually stray characters, a truncated copy-paste, or padding in the middle. Whitespace is ignored, both +// and -_ spellings are accepted, but anything outside the alphabet is rejected with an explanation.