Hex decode strips 0x prefixes, whitespace and colons from your text, then reads what remains two characters at a time as bytes. An odd number of hex digits after cleanup is refused, since every byte needs exactly two. An invalid two-character byte is named along with its offset, and valid UTF-8 output prints as text while anything else downloads as decoded.bin.
Questions
What formatting does it strip before decoding?
0x prefixes, whitespace and colons, so a value copied from a hex dump with byte separators still decodes.
What happens with an odd number of hex digits?
The tool refuses, since every byte needs exactly two digits.
What happens with an invalid byte?
The tool refuses, naming the two-character byte and its offset.
What does the output look like?
Valid UTF-8 text prints directly; anything else downloads as decoded.bin.
Can I use this from the command line?
Yes, the same code runs on the page, the CLI and MCP.
Related Dev tools
n→nBase64 encodeBase64 encode.Runs on each file you dropn→nBase64 decodeBase64 decode.Runs on each file you dropn→nBase64URL encodeBase64URL encode.Runs on each file you dropn→nBase64URL decodeBase64URL decode.Runs on each file you dropn→nBase32 encodeBase32 encode.Runs on each file you dropn→nBase32 decodeBase32 decode.Runs on each file you dropn→nBase45 encodeBase45 encode.Runs on each file you dropn→nBase45 decodeBase45 decode.Runs on each file you drop