Encode or decode Base64 text for data URLs, API payloads, and config strings.
Encode or decode Unicode text locally in your browser.
Free tools that often go together. Everything runs in your browser.
Base64 is a way of representing binary data, like an image or a file, as plain text made up of letters, numbers, and a few symbols. It exists because some systems, such as email, JSON, and older APIs, are only designed to handle text safely and can corrupt raw binary bytes. Encoding data as Base64 lets it travel through those text-only channels intact. You'll commonly see it in data URLs embedded in CSS or HTML, API authentication headers, and JSON fields that carry file contents.
Developers embedding a small image directly into CSS or HTML as a data URL, API testers inspecting authentication tokens or payloads, and anyone decoding a Base64 string they found in a config file, log, or webhook to see what it actually says.
No. Base64 is encoding, not security. Anyone can decode it back to the original data with no key or password required, so it should never be relied on to protect sensitive information.
Yes. The tool encodes text as UTF-8 before converting it to Base64, so accented letters, emoji, and non-Latin scripts round-trip correctly.
The input probably contains invalid Base64 characters, is missing padding characters at the end, or decodes to bytes that aren't valid UTF-8 text.
No. Encoding and decoding use your browser's built in APIs on your device. Nothing is sent to Justools servers.
This minimal version handles pasted text only. Encoding actual files would need a tool that reads file bytes directly rather than a text box.
Processed locally in your browser. Your files are never uploaded to our servers.