Number and encoding conversion
Hex Converters
Every hex conversion tool on the site, from decimal and binary through to text and Base64.
Choosing the right one
Twelve converters, but only two questions behind them, and knowing which you are asking saves a step.
Number conversion treats your input as a single quantity and rewrites it in another base. Use these when the value is a number: an address, a size, a register contents, an error code.
Encoding conversion treats your input as a sequence of bytes and reinterprets what those bytes mean. Use these when the value is data: a string, a payload, a token.
The distinction matters. 48656C6C6F as a number is 310,939,249,775. As bytes it is
the word “Hello”. Both readings are correct; only one is what you wanted.
Picking by what you are holding
| What you have | What it probably is | Start with |
|---|---|---|
| Two hex digits | One byte — a character or a color channel | Hex to decimal |
| Six digits after a # | An RGB color | Hex to RGB |
| Eight digits | A 32-bit value, address or register | Hex to binary |
| Twelve digits with colons | A MAC address | Hex to decimal |
| Thirty-two digits | A UUID or MD5 digest | Hex to text |
| Sixty-four digits | A SHA-256 hash | Hex to Base64 |
| Digits and letters ending in = | Base64, not hex | Base64 to hex |
Counting characters is the quickest identification method there is, because hex length maps directly onto bit width: every two digits is one byte.
What every converter here does the same way
- Converts as you type, with no button and no server round trip.
- Uses exact integer arithmetic, so a 64-character hash converts without rounding. Tools built on floating point lose accuracy above about nine quadrillion.
- Tolerates real input —
0x,#,$,\x, spaces, commas, colons and hyphens are all stripped for you. - Reports bad characters rather than silently dropping them, so a mis-pasted value gets caught instead of quietly changing your answer.
- Shows the nibble view, so you can check the working rather than trusting it.