THE NUMORIX GUIDE
How to use the Number Base Converter
Last reviewed September 14, 2026
What this calculator does
Parse the input in the selected base into a decimal integer, then format that integer simultaneously in binary (base 2), octal (8), hexadecimal (16), and base 36.
Formula and method
Parse the input in the selected base into a decimal integer, then format that integer simultaneously in binary (base 2), octal (8), hexadecimal (16), and base 36.
Variables and inputs
Number defaults to 255 and Input Base to 10. The selector offers bases 2 through 12, 16, 20, and 36; there is no destination-base selector because all four outputs are fixed.
Worked example
For 255 in base 10: decimal = 255; binary = 11111111; octal = 377; hexadecimal = FF; base 36 = 73 because 7*36+3 = 255.
How to interpret the result
The four strings are different encodings of one nonnegative integer, useful for comparing human-readable and computer-oriented representations.
Common mistakes to avoid
Validate digits against the selected input base, especially letters in bases above 10. Do not assume base 36's A-Z mapping is decimal alphabet order without checking that A represents 10.
Assumptions and limitations
The engine uses parseInt and Number, so invalid suffixes may be tolerated and large integers are not arbitrary precision. Negative values are not specially formatted.
Practical use and checks
The Advanced Base Converter presents one nonnegative integer in decimal, binary, octal, hexadecimal, and base 36 at the same time. Enter 255 with input base 10 as a check; the outputs should be 255, 11111111, 377, FF, and 73 respectively. The final value is easy to verify because 7 x 36 + 3 equals 255. This side-by-side view is useful when translating a bit mask, a compact identifier, or a value between programming and classroom notation. Validate the source digits before trusting the result. For base 16, F is valid and represents 15; for base 2, any digit other than 0 or 1 is invalid even if a permissive parser accepts part of the text. The converter changes representation, not meaning, and does not preserve fixed-width leading zeros unless you add them for the target application. It uses parseInt and JavaScript Number, so malformed suffixes may be tolerated and large integers can lose exactness. Negative values and fractional bases are outside the intended nonnegative-integer model. It also does not address signed binary interpretation, two's complement, byte order, encoding, or overflow width. When moving a value into code or hardware documentation, record the base, width, and sign convention rather than copying the string alone.