Decode Base64, Base32 or Hex text back to the original file - fully local in your browser; the data never leaves your device.
Running locally on your device ...
Running locally on your device ...
0%
Your files never left your device
No. Everything runs in your browser - your file never leaves your device. How this is verifiable
Decoding is the way back: encoded text becomes the original bytes again. If someone sent you a file as a Base64 string, a key arrived in Base32, or a value sits as a hex sequence in a configuration, this tool recovers the real file from it - exactly the bytes that were there before encoding. You can download the result as a file and use it normally.
You choose which alphabet the text is in: Base64, Base32 or Hex (all per RFC 4648, respectively base 16). The tool is lenient toward line breaks and spaces, which copying often introduces, and toward missing or present padding at the end. The only thing that matters is choosing the right format - reading Base64 text as Hex yields no meaningful content.
The conversion runs entirely locally in your browser via a tiny pure-JavaScript routine - nothing is uploaded, nothing is stored, and no foreign library is loaded from a CDN. If the text contains characters that do not belong to the chosen alphabet, the tool reports that honestly rather than producing a wrong file.
| Output format | BIN |
|---|---|
| Batch processing | Yes |
| Processing | Locally in your browser (JavaScript) |
| File upload | None |
Limitations: You must pick the right input format - the tool does not guess it. If the format is wrong or the text contains invalid characters, you get an honest error instead of a broken file. Any recovered file name is only a guess from the text file name; you assign the final name when saving.
| Format | Character set | Size overhead | Typical use |
|---|---|---|---|
| Base64 | A-Z, a-z, 0-9, +, / | +33% | data URLs, embedded attachments, API fields |
| Base32 | A-Z, 2-7 | +60% | typeable/readable-aloud values (e.g. TOTP keys) |
| Hex | 0-9, a-f | +100% | reading byte by byte, e.g. checksums |
No. Decoding runs entirely locally in your browser; the data never leaves your device and is not stored.
The tool reports an honest error (invalid characters) instead of producing a meaningless file. Then pick the right format.
No. Spaces and line breaks are ignored, as are missing or present padding characters at the end.
With the encode tool: it turns any file into Base64, Base32 or Hex text. This tool is the way back.
Encode to Base64 · Calculate an HMAC · Decode URL · IBAN Validator · NIK decoder · PAN validator · Check a personnummer · Check a PESEL number · TC Kimlik No validator · Chat Export Analyzer (WhatsApp)