Base64 to TXT Converter
Paste the Base64 and get a .txt file back. Use this page when you want the decoded content saved as a file; when you only want to read it on screen, the text decoder is quicker.
Processed as you paste — no button to press (Ctrl+Enter converts now / Esc clears)
Drop a file here, or — Ctrl+V a screenshot works too
Any file type · 100 MB maximum
Paste, drag and drop, or Ctrl+V a screenshot
Saving to .txt vs decoding to text
Both decode the same bytes; they differ in what you get. The text decoder shows the result inline for reading and copying. This page hands back a downloadable file, which is what you want when the payload is a log, a CSV or a config that needs to be opened elsewhere.
Not every Base64 payload is text
If the decoded bytes are an image, a PDF or an archive, saving them as .txt produces a file that no editor can render meaningfully. Check the detected type reported by the tool before saving: if it is not text, the matching page — PDF, image — is the right destination.
Two reasons decoded text becomes mojibake
- A legacy character set — the producer used GBK, Shift_JIS or Windows-1252 rather than UTF-8
- A corrupted copy — an intermediary altered the string, so the bytes no longer represent the original text
Frequently asked questions
Can I specify a legacy encoding such as GBK?
The decoder follows UTF-8, the overwhelmingly common choice and the standard for modern APIs. Bytes encoded in a legacy code page decode without error but render as symbols, which is your signal to convert with the correct set before decoding.
Will line breaks in the result be preserved?
Yes. Newlines carried inside the payload are decoded as-is, so logs and CSV rows keep their structure.
How large a payload is supported?
Up to 100 MB, with larger payloads processed on a background thread so the page stays responsive.