Every IPv4 address is a 32-bit number; we just usually write it as four base-10 octets separated by dots because that is easier to memorise. This converter shows you the same address in all the other bases routers, libraries and packet captures actually use: per-octet binary (the form you need when sketching out a subnet mask), 0x-prefixed hex, colon-separated hex, the full 32-bit unsigned decimal, and per-octet octal.
Conversion is deterministic — there is no API call and no rounding. The binary representation always pads each octet to eight digits so that bit positions line up vertically with a CIDR mask, which is the whole point of looking at an address in binary. Validation is strict: anything outside 0–255 or missing a dot is rejected up front rather than producing a garbled output.
Each IPv4 octet is exactly 8 bits, so 1 must be shown as 00000001, not 1. The padding makes subnet-mask alignment possible — you can stack the address above a /24 mask and see the network/host split at a glance.
It is the address as a single unsigned integer, MSB-first. MySQL's INET_ATON, PostgreSQL's inet, and many log formats store IPs this way for compact indexing and range queries. 192.168.1.1 becomes 3232235777.
0xC0A80101 is the C-style numeric literal you would pass to a syscall. C0:A8:01:01 is the colon-separated form some firewall logs and packet captures use because it mirrors MAC notation.
Not on this page — it is one-way (IPv4 → other bases). For the reverse, paste 32 binary digits into the Binary to IP tool, which reassembles them into four octets.
Explore the full suite of Networking tools and 290+ other free utilities at Chunky Munster.