Text vs file mode
Text mode encodes and decodes UTF-8 strings for APIs and config snippets. File mode turns uploads into Base64 (or downloads decoded bytes) when you need Base64-to-file without a server.
Tool
Convert text and files to and from Base64, instantly, in your browser.
Decoded bytes will download with the name you enter.
Processed entirely in your browser, nothing is uploaded anywhere.
Encode or decode Base64 for text and files entirely in your browser, nothing is uploaded.
Base64 turns binary or text into an ASCII-safe string for JSON fields, data URLs, email attachments, and config files. Tokitool encodes and decodes in the tab: text mode for UTF-8 snippets, file mode when you need Base64 to downloadable bytes without a server round-trip.
Anyone can decode Base64. Do not treat it as a way to hide passwords or personal documents. If you need confidentiality, use real encryption. This tool is for transport and embedding formats, not secrecy.
= padding at the end of the string- / _) pasted into a standard Base64 decoderdata:…;base64, prefix left on the valueStrip the data-URL prefix if present, paste the full standard alphabet string, and try again. Pair with the JSON Formatter when a Base64 field sits inside JSON. Privacy model: private browser tools.
Text mode encodes and decodes UTF-8 strings for APIs and config snippets. File mode turns uploads into Base64 (or downloads decoded bytes) when you need Base64-to-file without a server.
Some transports replace + and / and drop padding. This tool sticks to standard Base64 so results match common libraries; adjust for URL-safe variants only if your API requires them.
Encoding happens locally. Useful for tokens, keys, or documents you should not paste into a third-party online converter.
No. Base64 is encoding, not encryption. Anyone can decode it. Use proper crypto if you need confidentiality.
Check for missing padding, URL-safe characters, or truncated strings. Paste the full standard Base64 value and try again.