🔢 Number Base Converter
Convert numbers from any base from 2 to 36 into six common bases. Real-time conversion with BigInt support for arbitrarily large numbers.
Last updated: November 8, 2026 · By the BoltQuickTools team
Reading one number in several bases at once
A hex value in a debugger, an octal file mode, a bitmask in binary: the same integer shows up in different notations, and converting by hand is error-prone. This page takes a whole number in any base from 2 to 36 and shows it in six common bases together.
Converting a value
- Choose the base of your input with the Input Base dropdown, a quick button (BIN, OCT, DEC, HEX, B32, B36), or the or custom (2-36) field.
- Type the value into Number Input. Results appear as you type. Spaces and underscores are ignored, so
1_000 000is fine. - Read the cards for binary, octal, decimal, hexadecimal, base 32 and base 36. Use Copy on any of them.
- Tick Show signed binary (two's complement, 8/16/32/64-bit) to see a negative number at each width it fits.
Converted values
Input 0xDEADBEEF with HEX selected:
| Card | Value shown |
|---|---|
| Binary | 0b1101 1110 1010 1101 1011 1110 1110 1111 |
| Octal | 0o33653337357 |
| Decimal | 3735928559 |
| Hexadecimal | 0xDE AD BE EF |
| Base 32 | 3farfnf |
| Base 36 | 1ps9wxb |
The line below the cards reads Bit length: 32 bits | Fits in: 32-bit unsigned.
Input -128 in decimal with the signed box ticked fills the binary card with:
8-bit: 1000 0000
16-bit: 1111 1111 1000 0000
32-bit: 1111 1111 1111 1111 1111 1111 1000 0000
64-bit: 1111 1111 1111 1111 1111 1111 1111 1111 1111 1111 1111 1111 1111 1111 1000 0000
Input rules and known problems
- Whole numbers only.
1.5stops withInvalid digit "." for base 10. A leading+is rejected too. Only-is accepted as a sign. - Prefixes are stripped only for the matching base.
0x10is an error in decimal. Worse,0b1010in HEX is valid hex digits, so it converts as0x0B1010and not as binary. - Base 32 here is a radix, not the encoding. Digits run 0 to 9 then a to v. RFC 4648 Base32, as seen in TOTP secrets, uses a different alphabet and encodes bytes. Base 36 follows the same digit order up to z.
- Custom bases apply to the input only. Output is always the six cards, so you cannot convert to base 7 here.
- Negative numbers are not valid machine notation. The cards show forms such as
0x-80, and Copy produces strings such as0b-10000000, which most languages will not parse. Without the signed box, binary is shown the same way, as a sign followed by the magnitude. - Copy on the binary card ignores the signed view. It copies the sign-and-magnitude form, not the two's complement shown. Select the line you want by hand.
- The signed box does nothing for positive input, and it will not read
FFas -1, since the input is always taken as unsigned unless it starts with-. - The bit info misreports negative numbers. For
-128it says at least 9 bits are needed, when 8 are enough, and for-200it says it fits in 8-bit when the two's complement list starts at 16. Rely on the widths listed in the binary card. - Very long input can lag. Values are BigInts with no size cap, and the whole number is reconverted on every keystroke.
For Unix file modes, the chmod calculator shows what each octal digit grants. To turn text into its binary bytes rather than convert a number, use the binary and text converter, and for looking at raw file bytes, the hex editor.
Questions about the output
Why does the binary card show extra leading zeros?
Binary is padded to groups of four and hex to pairs for reading. 5 displays as 0101. Copy gives the unpadded form, 0b101.
Can it handle numbers beyond 64 bits?
Yes. It uses BigInt, so a 77-bit value converts exactly. The two's complement view lists only 8, 16, 32 and 64 bits, so a negative number beyond 64 bits falls back to sign and magnitude.
Is letter case important in the input?
No. deadbeef and DEADBEEF are the same. Output is uppercase for hexadecimal and lowercase for bases 32 and 36.