IP Address to Hex / Binary / Integer Converter

One address, three equivalent representations

192.168.0.1 converts to hex 0xc0a80001, binary 11000000101010000000000000000001, and unsigned 32-bit integer 3232235521 -- three different ways of writing the exact same 32-bit value.

Each octet of the dotted-decimal address maps directly to 8 bits: 192 = 11000000, 168 = 10101000, 0 = 00000000, 1 = 00000001, concatenated into the full 32-bit binary string, then reinterpreted as hex (2 hex digits per octet) or as one large unsigned integer.

The integer form (3232235521) is how IP addresses are actually stored and compared in many databases and low-level networking code -- converting between dotted-decimal and this integer form is a common need when working directly with IP range storage or bitwise operations.

Where the octet-as-decimal rule matters

IPv4 only. Leading zeros in octets are treated as decimal, not octal. An octet like '010' is interpreted here as decimal 10, not as octal 8 -- some older systems and libraries historically treated a leading zero in an IP octet as an octal prefix, which could silently produce a different address than intended. This tool always reads octets as plain decimal.

This is IPv4-specific 32-bit math -- IPv6 addresses are 128 bits and use a completely different hex-grouped notation (eight groups of four hex digits) that doesn't map onto this dotted-decimal-to-32-bit conversion.

Each of the four octets must be a valid decimal value from 0 to 255 for the conversion to produce a meaningful result, since any octet outside that range isn't representable in a single byte.

Related IP and address-range tools

For the subnet, broadcast, and usable-host range that this same address belongs to, the IP Subnet & CIDR Calculator handles that calculation.

If you're inspecting request headers from a server that logged this address, the HTTP Header Parser is a related debugging tool.

Frequently Asked Questions (FAQ)