Encode any file as Base64, Base32 or Hex text - fully local in your browser; the file never leaves 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
Encoding means turning arbitrary bytes into a form that survives being carried as plain text. Many systems - email, JSON, XML, configuration files, database fields - only tolerate printable characters and choke on raw binary. Base64 solves this by mapping every three bytes onto four harmless text characters; an image, a key or a small file becomes a string you can safely embed, copy and turn back again. The content is fully preserved, it is just written differently.
This tool offers three standard alphabets per RFC 4648. Base64 is the most compact and most common choice, for data URLs, embedded attachments or API fields. Base32 uses only uppercase letters and digits, which makes it case-insensitive and good when the text is typed by hand or read aloud (TOTP keys use it). Hex (base 16) writes each byte as two characters 0-9 a-f - longer than Base64, but immediately readable and the standard when you want to spot individual bytes, as with checksums.
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. The result appears as a text file you can download or copy; with the counterpart (decode) you get the original file back from it, byte for byte exactly.
| Output format | TXT |
|---|---|
| Batch processing | Yes |
| Processing | Locally in your browser (JavaScript) |
| File upload | None |
Limitations: Encoding is not encryption: anyone can turn the text back without a key - so it keeps nothing secret, it only makes binary data text-safe. Encoded text is also larger than the original (Base64 about a third more, Hex twice). For very large files the approach is impractical.
No. The encoding runs entirely locally in your browser; the file never leaves your device and is not stored.
No. It is just a reversible notation. Anyone who has the text can turn it back without a key. To protect data, use the encryption tool.
When in doubt, Base64 (most compact, most common). Base32 for case-insensitive, typeable values, Hex for reading byte by byte.
Yes. With the decode tool the text is turned back into the unchanged original file, byte for byte.