Version 1.9
What this converter does
Number System Converter translates values among hexadecimal, decimal, and binary representations. These systems write the same underlying number with different symbols and place values. The tool is useful when reading software logs, register maps, color values, bit masks, network data, or documentation that uses a base other than everyday decimal.
Understanding the bases
Decimal is base 10 and uses digits 0–9. Binary is base 2 and uses only 0 and 1. Hexadecimal is base 16 and adds A–F for values ten through fifteen. One hexadecimal digit represents four binary bits, which makes hexadecimal a compact way to display machine-oriented values.
Example
Decimal 255 equals binary 11111111 and hexadecimal FF. In binary it is eight one-bits; in hexadecimal those bits are grouped into two four-bit values, each equal to F. Prefixes such as 0x for hexadecimal or 0b for binary are common in programming documentation but may not be part of the numeric value itself.
Limits and interpretation
Large inputs may exceed the exact integer range supported by ordinary browser numbers. Signed integers, two’s-complement values, floating-point data, character encodings, and byte order require additional context that a base conversion alone cannot infer. Confirm the expected bit width and data type before interpreting a hardware register or serialized value.
Common questions
Are hexadecimal letters case-sensitive? No; A–F and a–f represent the same digit values. Why do some values begin with zeros? Leading zeros often show a required bit or byte width even though they do not change an unsigned numeric value. Can text always be converted directly? Text first needs a character encoding such as UTF-8 or ASCII. Without that encoding context, a hexadecimal byte sequence does not have one guaranteed textual interpretation. Preserve leading zeros when a protocol specifies a fixed field width.
Related tools: Normalization & Statistics, QR Cards, and Date Calculator.