The Complete Guide to Number Base Conversion
Numbers are abstract — the value of “a dozen eggs” is the same regardless of how you write it — but their representation depends on the base you write them in. The decimal system (base 10) is the everyday default for humans, but computers built on binary switching elements use base 2 internally, programmers frequently encounter base 16 (hexadecimal) for memory addresses and colour values, base 8 (octal) for file permissions and legacy systems, and base 64 for transport-safe encodings. A number base converter is the tool that translates the same numeric value between these representations — essential when debugging memory dumps, decoding colour palettes, or reasoning across the humans-vs-machines boundary that runs through every technical field.
1. Why bases exist at all — the digits-vs-value question
A base (or radix) is the number of distinct digits used to represent numbers. Decimal uses 10 digits (0–9); binary uses 2 (0, 1); hexadecimal uses 16 (0–9, then A–F); base 64 uses 64 (capital letters, lowercase letters, digits, and two extra symbols). The choice of base is purely a question of display— the underlying value is the same — but it has profound practical consequences. Decimal is convenient for humans because it matches our ten-finger counting instinct and matches our currency, units, and common vocabulary. Binary is convenient for digital circuits because each digit is one on/off switch; hexadecimal is convenient for programmers because each hex digit packs exactly four binary digits, making binary values readable in shorthand; octal packs three binary digits, which once mattered for 12-bit and 36-bit machines.
2. Bases 2, 8, 10, 16 — the daily-driver bases
- Binary (base 2) — the representation computers actually use. Memory dumps, raw I/O registers, and digital logic are all natively binary.
- Octal (base 8) — Unix file permissions (
rwxr-xr-x=755), some legacy systems, and the occasional low-level config value. - Decimal (base 10) — the human baseline and the resting place of all final answers.
- Hexadecimal (base 16) — memory addresses (
0xDEADBEEF), colours (#FF5733), MAC addresses, cryptographic outputs, and察 any 4-bit-aligned binary data.
3. Bases 32 and 64 — transport-encoded representations
Bases above 16 appear in data-transport contexts. Base 32 packs 5 bits per character and is the alphabet that uses 0–9 and A–V (excluding ambiguous characters for safe manual transcription); it appears in some URL-safe encodings and in secret-key exchange. Base 64packs 6 bits per character and uses A–Z, a–z, 0–9, +, and / (or URL-safe equivalents). It is the encoding for binary attachments in email (MIME), for image inlines in HTML and CSS, for OAuth state tokens, and for any context where binary data must travel through a channel limited to printable ASCII. Converting between decimal and base 64 is not a typical end-user task, but it is occasionally exactly what you need when inspecting an encrypted token or decoding a data URL.
4. Why the maximum base matters — why not base 1000?
The largest base with practical use is base 64, because above that point the representation runs out of conveniently-typable ASCII characters and you start needing arbitrary symbols. Bases beyond 64 don’t appear in standard computing. Bases below 2 appear in some niche combinatorial work but are otherwise theoretical. The interesting bases for everyday work are exactly 2, 8, 10, 16, 32, and 64 — and a converter that supports all six covers the practical surface comprehensively. This tool handles all six, with custom base input for the rare cases outside the standard set.
5. Common mistakes — the silent corruption cases
Base conversion errors go silent at the worst moment: the number looks plausible in every base, so you do not notice until downstream code misinterprets it:
- Leading zeros stripped — converting
0755(octal, often file-permission notation) to decimal gives 493, but if interpreted as decimal it gives 755. The leading zero is the only signal that the value is octal. - Hex without the
0xprefix —FFlooks like text in many contexts;0xFFis unambiguous. Many printers and inspection tools omit the prefix and you can misread the output as decimal. - Mixed-case hexadecimal —
0xffand0xFFare the same value, but case-insensitive parsing is assumed only sometimes. When you copy a hex string from a colour palette expecting F–F uppercase and it has lowercase f–f, nothing breaks, but the difference matters in cryptographic contexts where the casing of a hash may be intentionally computed. - Base 64 with vs without padding — base 64 strings may or may not have the trailing
=padding. The decoder must accept both forms; the encoder usually emits padded form.
6. Fractional and negative values
Most base converters handle integer values; a smaller number handle fractions and negative numbers. Fractional values across non-power-of-two bases are not always exactly representable — 0.1 in decimal is a non-terminating binary, the famous foundation of floating-point error. For exact integer work, base conversion is exact; for fractional work, expect some representational drift depending on the precision chosen. This tool focuses on the integer-base-conversion surface; for fractional values, use the float-and-integer conversion utility instead.
7. Why this belongs in your browser
Base conversion is a tool you reach for many times a day during debugging, design, and review. A browser-based converter requires no install, no account, no upload — nothing about the numbers you convert is particularly sensitive, but the convenience of always-available conversion is real. There is no telemetry, no retention, no server-side processing. The numbers you convert exist in the page only as long as you are looking at them.
Conclusion
Number base conversion is the daily-workhorse tool of every programmer, hardware engineer, cryptographer, and digital designer. With support for the six practical bases (2, 8, 10, 16, 32, 64), custom base input for edge cases, both directions of conversion, and zero-upload browser-side execution, this tool handles the entire practical base-conversion surface in a single page. Pair it with the bit-shift inspector for binary-level work and the colour converter for hex-vs-decimal colour arithmetic.