Base64-decode a TSV
Decode a Base64 blob back to the TSV it came from. Line breaks, spaces, and stray whitespace in the input are ignored, so you can paste a wrapped MIME-style block or a value copied out of a JSON field without cleaning it up first. The encoding direction is TSV → Base64.
How to use
- Paste the Base64, wrapped or not.
- Check the decoded text on the right — if it's garbled, see below.
- Copy or download as a
.tsvfile.
When the output looks wrong
Garbled accents mean the original bytes weren't UTF-8 — the decode succeeded and the text was in a legacy encoding. Download the result and run it through convert encoding, which reads raw bytes and can decode Latin-1, Windows-1252, or UTF-16. An error about invalid characters usually means the input is URL-safe Base64 (using- and _ instead of + and /), or that it was truncated. Base64 length must be a multiple of four, padded with =; a copy that lost its trailing padding will fail.
Binary garbage means the encoded content wasn't text at all — a zip or an image, which this page can't usefully show.
After decoding
The result is text, not necessarily a valid TSV — nothing about Base64 guarantees the content's shape. Run the validator to check the column counts, or the viewer to see it as a table.
FAQ
Does it accept URL-safe Base64?
Not directly. Replace - with + and _ with / first — find and replace can do it, or paste into urltoolskit.org which handles that variant natively.
Is the padding required?
Yes — Base64 comes in four-character groups, and unpadded input fails. If your string lost its trailing =, add enough to make the length a multiple of four.
Can I decode something that isn't text?
The output will be shown as text whatever it was, which is meaningless for a binary payload. Use base64 -d > file on the command line for those.
Is anything sent to a server?
No — decoding happens in your browser. Which matters here, because people paste secrets into Base64 decoders more than they should.
Privacy
100% client-side. No upload. See the privacy policy.