Hex to file.

Hexadecimal, Base16, writes every byte as two digits from 0 to 9 and A to F. Each digit is four bits, so the mapping is direct: no grouping, no padding, no arithmetic. It is the way bytes are shown in debuggers, hash digests, colour values and memory dumps.

A byte is split into two nibbles of four bits, each written as one of 16 digits: 0x48 is 01001000, the H of ASCII, written 48. The output is exactly twice the size of the input. Upper and lower case mean the same thing; the decoder reads both, with or without spaces or 0x prefixes.

Hash digests (a SHA-256 is 64 hex digits), CSS colours (#FF5733), MAC addresses, memory addresses, cryptographic keys and IVs, file signatures (a PNG starts 89 50 4E 47), and every hex dump a developer reads.

Yes: digits and letters only, nothing to escape.

Twice the size of the bytes, the worst of the practical encodings, and the most readable: a byte is two digits and you can see them. Use it to show bytes to a person; use Base64 to carry them.

No. Hex is an encoding, not encryption: it changes how bytes are written, not who can read them, and anyone can decode it with no key. Encrypt first (AES, age, a library's sealed box) when the content needs protecting, then encode the ciphertext if it has to travel as text.

Paste the Hex into the input, or drop a text file that holds it. The tool decodes the bytes, says what they look like and how many there are, and shows the image when they are one. Check the file name, which is guessed from the bytes, and press Download.

From the first bytes. Most formats start with a signature, 89 50 4E 47 for PNG, %PDF for PDF, PK for ZIP, and the tool knows the common images, documents, archives, fonts and media, and tells text from the rest. It is a guess for the file name only; if you know what the bytes are, rename the file and it downloads under that name.

Usually the Hex was cut short or carries something extra. Copy the whole value, including its end; leave out quotes and commas from the surrounding code. If the status line says the bytes look like text when you expected an image, the value wasn't the file's Hex to begin with.

Nothing leaves your browser. The text is read into memory on your machine and the encoding is computed there, in plain JavaScript; the page makes no request with it. Load the page, go offline and it keeps working.

No. The "Hex to file" tool is free and opens without a sign-in, an account or an install.

Nothing. The "Hex to file" tool holds your input in the page's memory, so closing or reloading the tab clears it, and it saves nothing in this browser.

Yes: you can rename it before downloading. The default name is decoded plus the extension the format suggests, such as decoded.png.

When the bytes start like a PNG, JPEG, GIF, WebP, AVIF, ICO, BMP or SVG image, the page shows a preview before you download it. Other types show their size and the name of the format they start like.

The decoder takes digits 0 to 9 and a to f in either case, two to a byte, ignoring spaces and 0x prefixes.

Closest to the "Hex to file" tool: File to Hex, Hex decoder, Hex encoder, Binary to file. Each opens on its own page, free and in the browser.

The "Hex to file" tool is one of 32 in its group. The group's page, /tools/encoding, lists them all.

The tool is free. Its interface is built from shadcn.io's own components (Button, Input, Slider and the rest of the registry under /ui), which come in React, Vue, Svelte and Solid. Pro adds the blocks and templates for the product around it.