Base64 & URL Encoder
Runs on your device. Nothing is sent.Everything happens on your own device. Nothing you type or upload is ever sent anywhere.
Text
Result
The result will appear here
Encode or decode Base64 and URL-encoded strings, or convert a file to Base64, entirely in your browser.
Base64 turns arbitrary binary data into plain ASCII text using 64 printable characters, which is why it shows up wherever binary data needs to travel through a text-only channel - embedding an image directly in CSS or HTML, attaching a file to an email, or encoding a token inside a JWT. URL encoding (percent-encoding) is a different, unrelated scheme that escapes characters a URL can't contain literally, like spaces and ampersands, so they survive being placed in a query string. This tool converts text or files in either direction for both, entirely in your browser - nothing is uploaded anywhere.
Frequently asked questions
Is Base64 encryption?
No. Base64 is an encoding, not encryption - anyone can decode it instantly with no key or password required, this tool included. It only changes the representation of data so it can safely pass through systems that expect text, not binary. Never use it to hide anything sensitive.
Why does Base64-encoded text end with = signs?
Base64 works in 3-byte chunks, each turned into 4 output characters. When the input isn't a multiple of 3 bytes, = characters pad the last chunk out to a full 4 characters. The URL-safe variant typically drops this padding since decoders can usually infer it from the string's length.
What's the difference between the standard and URL-safe alphabets?
Standard Base64 uses + and / as two of its 64 characters, but both have special meaning inside a URL (space and path separator, respectively), so a standard Base64 string can break when placed directly in a URL or filename. The URL-safe variant substitutes - and _ for those two characters instead, which is why it's the format used inside JWTs and similar tokens.
Why does decoding sometimes show binary data instead of text?
Base64 can encode literally any bytes, not just text - an image, a font file, an executable. When the decoded bytes don't form valid UTF-8 text, this tool can't display them as a readable string, but you can still download them as a file to recover the original binary content.
Why is Base64-encoded output around a third bigger than the original?
Base64 maps every 3 input bytes to 4 output characters, so the encoded result is always about 4/3 (roughly 33%) larger than the source, whether you're encoding a snippet of text or a whole file. That overhead is the price of representing arbitrary binary data with only 64 printable characters - it's normal and doesn't mean anything went wrong.
Do I need to turn on 'URL-safe alphabet' before decoding a URL-safe Base64 string?
No - decoding always works whether the string uses the standard alphabet or the URL-safe one. Behind the scenes, this tool converts - and _ back to + and /, and restores any missing = padding automatically, so you can paste either variant straight into decode mode. The checkbox only matters for encoding, since it controls which alphabet the output uses.
For developers: open this page with a `q` parameter in the URL - e.g. gizke.com/base64?q=hello world - and that value is pre-filled automatically. Most visitors won't need this; it's meant for linking directly to a ready-to-use example.