Converting IP Addresses Between Decimal, Hex, and Binary: When and Why

Most engineers can read 192.168.1.1 in their sleep but freeze when the same address shows up as 3232235777 in a database column or 0xC0A80101 in a packet capture. They are the same value — an IPv4 address is simply a 32-bit unsigned integer that humans prefer to read as four dotted octets. Once that clicks, converting between representations stops being a party trick and becomes a routine part of the job.

This is a quick tour of the four forms, when each one shows up, and how to move between them without doubting your math.

The four forms of one number

Take 192.168.1.1:

• Dotted-decimal: 192.168.1.1 — what people read.
• Decimal integer: 3232235777 — (192 × 2^24) + (168 × 2^16) + (1 × 2^8) + 1.
• Hexadecimal: 0xC0A80101 — the same integer in base 16, two hex digits per octet.
• Binary: 11000000.10101000.00000001.00000001 — base 2, eight bits per octet.

Every one of those describes the identical address. The IP Address Converter takes any of them and prints all the others at once, so you never have to chain two one-way tools together.

When you actually need each form

Integer — for storage and range queries. A lot of schemas store IPv4 as an unsigned INT rather than a string: it is four bytes instead of fifteen, and range checks become plain integer comparisons (WHERE ip BETWEEN x AND y). Convert to the integer to insert, and back to dotted to display.

Hex — for packet captures and low-level logs. tcpdump, firewall counters, and binary protocol fields routinely render addresses in hex. Being able to glance at 08080808 and recognize 8.8.8.8 saves a context switch.

Binary — for subnet reasoning. Masks and the network/host boundary only become obvious in binary. If you are studying for Network+ or CCNA, converting by hand and checking yourself is the fastest way to build the intuition. The companion IP Addressing Guide walks through the underlying bit math.

The two gotchas that bite people

Leading zeros can mean octal. In the classic C inet_aton family (and some libraries), an octet written 010 is interpreted as octal — the value 8, not 10. Strip leading zeros before trusting a hand-typed address, and be suspicious of any tool that silently accepts them.

Signed vs unsigned integers. Any address above 127.255.255.255 has the top bit set, so a 32-bit signed integer column shows it as a negative number. The standard IP integer is unsigned; if a database hands you a negative value, add 4294967296 to recover the real number.

A typical workflow

Say an alert references the host 3475931033. Drop it into the IP Address Converter to get 207.55.x.x, work out the enclosing network with the CIDR / IP Converter, then attribute it with IP Lookup and confirm ownership with WHOIS Lookup. Four representations, one underlying number, no guesswork.

IP math feels like trivia until the day a log hands you an integer and a clock is running. Knowing that every form is the same 32 bits — and having a converter that shows them side by side — turns that moment into a five-second lookup instead of a detour.