File Conversion Tools

Convert Base64 and text encodings or generate SHA file hashes privately in your browser. No upload or external API.

3 tools

File Conversion Tools works on a local file's bytes, never its meaning: re-package it as Base64, re-save its text in another character encoding, or fingerprint it with a hash. The Base64 File Encoder & Decoder turns a file into Base64 or a data: URL and back. The Text File Encoding Converter re-saves a text file between UTF-8, UTF-16 and two legacy single-byte encodings. The File Hash Generator computes SHA digests so you can compare a download against a published checksum. Each file is read and processed in the browser and is never uploaded.

Which tool should I use?

Use the Base64 File Encoder & Decoder to embed a small file in code or a data: URL, or to turn a Base64 blob back into a downloadable file; it is for files, whereas the Developer Tools Base64 tool is for a text string.
Use the Text File Encoding Converter for text files only, and pick the correct source encoding yourself — without a byte-order mark it is not detected.
Use the File Hash Generator to confirm a downloaded file matches a published checksum; it also offers legacy SHA-1, unlike the text SHA tool in Developer Tools.

Limitations and things to know

File-size ceilings differ by tool: 5 MB for Base64 encoding, 2 MB for the encoding converter, 25 MB for hashing.
Converting a text file to Windows-1252 or ISO-8859-1 is lossy — any character outside that set is replaced with a question mark. Files that look binary are rejected.
There is no character-set auto-detection: without a BOM, the source encoding you select is trusted as-is.
Base64 decoding accepts only the standard alphabet, and decoded content is offered as a download with no preview and no malware check.
A matching hash confirms two files have identical bytes; it is not proof that a file is safe, authentic or unmodified by its publisher.