About this tool
What is the Base64 Encode/Decode?
Encode text, files, or images to Base64; decode Base64 back to its original form — all in your browser. Useful for embedding images in CSS data URLs, encoding API request bodies, decoding JWT tokens, or inspecting any Base64-encoded payload.
File and image data never leaves your device. The encoder handles UTF-8 multi-byte characters correctly (a common bug in lazy implementations).
FAQ · BASE64 ENCODE/DECODE
Questions about the Base64 Encode/Decode
Can I encode images and files, or just text?
Both. Drop any file (up to ~50 MB practical limit) and get its Base64 encoding. Useful for embedding small images directly in CSS via data: URLs, or for inspecting binary payloads in API debugging.
Is my data uploaded?
No. Encoding and decoding both happen entirely in your browser using the FileReader and btoa/atob APIs. Sensitive data (tokens, internal files) stays on your device.
Does it handle UTF-8 text correctly?
Yes. We use TextEncoder/TextDecoder which handle multi-byte characters correctly — emoji, CJK, accented characters all round-trip cleanly. Naive btoa() implementations corrupt these.