About Hex to Decimal
Hex to decimal reads hexadecimal values and reports their decimal equivalents, so FF becomes 255 and 1000 becomes 4096. It is the conversion you need when a value arrives in hex — from a colour picker, a protocol document, a debugger — and has to be expressed as a number you can use in arithmetic.
Input is parsed as tokens separated by spaces, commas or line breaks, and each is converted independently, which means a whole column pasted from a specification converts in one pass. Both uppercase and lowercase digits are accepted, so nothing needs normalising first.
A useful habit when reading hex output: knowing that FF is 255 and FF FF is 65535 makes it obvious at a glance how many bytes a value occupies and whether it is in the range of a single byte, a 16-bit word, or something wider. That quick sanity check catches a great many off-by-one errors.
Values are read as whole numbers and that is the only interpretation available, so a string of hex digits is never grouped into bytes on your behalf — spacing the input the way you intend it to be read is left to you. There is no option to interpret the input as two's complement, and no signed or fixed-width representation is offered, so negative values are out of scope. The output is decimal figures only; the page will not also show the hexadecimal form it read, which means checking the tokens against their source is left to you. There is also no upper limit enforced on length, and past a certain size the precision of ordinary number handling is what applies.
How to use Hex to Decimal
- 1 Paste the hexadecimal values, separated by spaces, commas or line breaks.
- 2 Each is converted to its decimal equivalent immediately.
- 3 Uppercase and lowercase digits are both accepted.
Frequently asked questions
Does it matter if the hex is uppercase or lowercase?
No. FF and ff both mean 255 and are read identically, so you can paste values from any source — a spec that uses uppercase, a language that prints lowercase — without converting case first.
How can I tell how many bytes a hex value represents?
By its length. Two digits is one byte, four digits is two, eight digits is four. Knowing that FF is 255 and FF FF is 65535 gives you an instant read on whether a value fits in a byte, a 16-bit word, or needs more room.
What about a value with an 0x prefix?
The prefix is a notation used in source code to mark a literal as hexadecimal, not part of the value itself. Since the conversion scans for hexadecimal digits, keep it in mind if a prefixed value produces an unexpected result, and strip the prefix if needed.
Can I convert a long hex string from a hash?
It will convert, but the decimal form of a 256-bit hash is a 78-digit number with no practical use — hashes are compared as hex. Convert single values you intend to do arithmetic with, not digests.
Free, online, and private
Free to use
Hex to Decimal is completely free. There is no account to create, no login, and no hidden charge or usage limit.
Runs online in your browser
It is a free online tool that runs entirely in your browser. Nothing to download or install — open the page and start using it right away.
Your data stays private
All processing happens locally on your device. Your input is never uploaded, stored, or tracked, so it never leaves your browser.
How Hex to Decimal behaves in detail
These are the specifics of this implementation — the exact ranges, defaults and fixed settings you are working with.
| Parameter | Value |
|---|---|
| Tokenizer | split on runs of whitespace or commas |
| Digit parsing | parseInt with radix 16 |
| Prefix handling | a leading 0x is tolerated, since radix 16 already implies it |
| Letter case | both accepted — ff and FF both read as 255 |
| Output form | decimal integers joined by single spaces |
Compiled from the implementation of this tool and checked against it by itoolnet.
What Hex to Decimal does not do
Knowing the edges of a tool saves more time than another list of its features. These are the cases where it will not do what you might expect.
- Parsing stops at the first character outside the digit set, so 1fg or a quoted value is truncated to 1f and answered as 31 instead of being rejected. The output never shows that part of the token was ignored.
- Bytes are not the unit of this conversion. A group like e4 bd a0 becomes three separate decimal numbers, not a reassembled character, so it cannot stand in for a text decoder when the hex came from UTF-8 text.
- There is no zero padding and no alignment in the output, so the decimal values have varying widths and are separated only by spaces — predictable only if you keep the input tokens in the same order.
Tested and documented by itoolnet, the team that builds and maintains this site.