Convert Hex to IP

An IPv4 address is 32 bits = 4 octets (bytes). The hex representation packs those 4 octets into 8 hex digits – each octet becomes 2 hex digits. So 0xC0A80001 splits into C0, A8, 00, 01 → 192, 168, 0, 1 → 192.168.0.1. The tool just does this split and decimal conversion.

Because IPv4 addresses are stored differently in different memory contexts. Network byte order (big-endian) is how they appear in packets and most tooling – the leftmost octet is the most significant. But if you dump the same address from a little-endian CPU register or struct, the bytes appear reversed. 0xC0A80001 as little-endian bytes decodes to 1.0.168.192 (same physical bytes, different octet order).

All the common ones: period (C0.A8.01.01), colon (C0:A8:01:01), underscore (C0_A8_01_01), space (C0 A8 01 01), or none (C0A80001). Leading 0x is also stripped. Case-insensitive – Ab and AB and aB all work.

All the standard IPv4 categories: Loopback (127.0.0.0/8), Private (RFC 1918: 10/8, 172.16/12, 192.168/16), Link-local (169.254.0.0/16), Shared (RFC 6598 CGN: 100.64/10), Multicast (224.0.0.0/4), Limited broadcast (255.255.255.255), Reserved (0/8 and 240/4), and Public for everything else.

No – IPv6 addresses are 128 bits (32 hex digits) and use a different format (2001:db8::1). This tool is IPv4-only. Use a dedicated hex-to-IPv6 tool if you’re working with 32-digit hex values representing IPv6 addresses.

You get an error: “hex must be exactly 8 digits for IPv4 (got N)”. Unlike hex numbers in general, an IPv4 address has a fixed 32-bit width – there’s no such thing as a “6-bit IP” or a “10-bit IP”. The tool enforces the 8-digit (32-bit) requirement strictly.

After processing, the stats row tells you how many of the converted IPs fall into non-public ranges (private RFC 1918, loopback, link-local, shared CGN) versus how many are public. Useful when you’re scanning a hex dump for suspicious external addresses versus internal traffic.

No. All conversion happens in your browser’s JavaScript engine – no network requests fire during processing, and no server stores or logs your hex values. You can verify with your browser’s Network tab. The tool works offline after the initial page load.

Use our “IP to Hex” converter. Each octet becomes 2 hex digits: 192 → C0, 168 → A8, 0 → 00, 1 → 01 → concatenated to 0xC0A80001. The round trip is lossless in either byte order.

Common use cases: reading IP addresses from binary packet captures in a hex editor, decoding IP values stored in 32-bit integer columns in databases, reverse-engineering proprietary network protocols, parsing firewall log hex dumps, or converting values from embedded-system APIs that expose IPv4 as raw hex rather than dotted form.