Hex to decimal
Turn hex into decimal, with binary and octal too. Huge and signed values work.
Collect & share
Schedule & staff
Business
Monitor & alerts
Security & dev
Switch numbers between hex, decimal and binary, see text as bytes, tidy JSON.
Result
Result
Result
Result
Result
Type a number, some text or a block of JSON and the converted result shows up as you type. Numbers appear in decimal, hex, binary and octal side by side, text becomes bytes in the encoding you pick, and JSON can be tidied, checked or rewritten as CSV, YAML or XML. There is no account or fee.
Number bases: decimal, hex, binary, octal or any base from 2 to 36, with two's complement, IEEE 754 floats and hex colours.
Turn hex into decimal, with binary and octal too. Huge and signed values work.
Convert decimal numbers to hex. Negatives can show as 8 to 64-bit patterns.
Paste ones and zeros to get the decimal value. Group bits with _ if you like.
Turn decimal numbers into binary, padded to 8, 16, 32 or 64 bits when you want.
Expand each hex digit into four bits. Long values like hashes work too.
Group bits by four from the right and read each group as one hex digit.
Convert octal to decimal, binary and hex and back. Handy for modes like 755.
Text: bytes in UTF-8, UTF-16, EUC-KR or ASCII, Unicode code points, Base64, URL encoding, HTML entities and escapes.
Encode text to Base64 or decode it back, with a URL-safe option and UTF-8.
Turn text into hex bytes in UTF-8, UTF-16, EUC-KR or ASCII, spaced as you like.
Decode hex bytes back into readable text in UTF-8, UTF-16, EUC-KR or ASCII.
Write text as ones and zeros, one 8-bit byte per group, in UTF-8 or ASCII.
All 128 ASCII codes in decimal, hex, octal and binary, with control code names.
JSON: format, minify, find errors by line and column, browse as a tree, sort keys, and convert to CSV, YAML, XML or a query string.
Pretty-print, minify and check JSON. Errors show the line, column and reason.
Turn a JSON array into CSV for Excel, or CSV into JSON. Nested keys become a.b.
Computer circuits work with two states, on and off, so every value inside a machine is binary. Counting with only 0 and 1 is usually traced to a paper by Leibniz in the 1703 volume of the Royal Academy of Sciences in Paris. Hex packs those bits four at a time into one digit, which is why memory addresses, colour codes (#FF8800) and hash values are written in hex whenever a person has to read raw bytes.
Text only fits in a computer once every character has a number. ASCII, set by the American Standards Association in 1963, numbered English letters, digits and signs from 0 to 127. Unicode 1.0 in 1991 began gathering the world's scripts into one table, and UTF-8, devised in September 1992 by Ken Thompson and Rob Pike at Bell Labs, writes those numbers as bytes and is now the default for web pages and JSON. Base64 and JSON are agreements for passing bytes and data around as plain text.
| Name | Where and when it started | Who defines it now | Used mostly for |
|---|---|---|---|
| Binary | Leibniz paper (1703 volume) | Plain maths notation, no owner | Machine code, bit flags, network masks |
| Hex | Spread through computing as a short way to write bytes | Plain maths notation, no owner | Memory addresses, colour codes, hashes, byte dumps |
| ASCII | American Standards Association X3.4 (1963) | ANSI, last edition X3.4-1986 | English text, control codes, source code |
| Unicode | Unicode Consortium, version 1.0 (1991) | Unicode Consortium, now 18.0 (September 2026) | Numbers for every script, from Hangul to emoji |
| UTF-8 | Ken Thompson and Rob Pike, Bell Labs (1992) | IETF RFC 3629 (2003) | Web pages, JSON, Linux file names |
| Base64 | PEM secure mail (1987), then MIME (1992) | IETF RFC 4648 (2006) | Mail attachments, data: URLs, JWT tokens |
| JSON | Douglas Crockford, RFC 4627 (2006) | ECMA-404 and IETF RFC 8259 (2017) | Web API responses, config files, logs |
New to this? Start with decimal to binary, then use the text tools to see how many bytes the same words take in UTF-8 and in EUC-KR. For API responses, tidy them with the JSON formatter, and see how each language reads JSON in the coding lessons. Decimal to binary Text to hex JSON formatter Learn to code
No. Every converter here is free and works without an account.
Numbers up to 10,000 characters, text up to about one million characters, and JSON files up to 10 MB.
Yes. Copy link puts your value after the # in the address, so whoever opens the link starts with the same input.
Only when there is no prefix. 0x or # is read as hex, 0b as binary and 0o as octal. Anything else uses the base you selected.