Dotted-decimal, decimal, hex, octal, binary; IPv6 expand & compress; IPv4↔IPv6 mapping; CIDR↔range. 100% local.
| Input | Type | Decimal | Hex | Binary | Note |
|---|
Dotted-decimal, unsigned decimal, signed int32, hex, segmented hex, octal, segmented octal, segmented binary, full 32-bit binary — all update as you type.
Lower case, no leading zeros, only the longest run of zero groups compressed, single zero group never compressed — the standard form professionals expect.
IPv4-mapped, IPv4-compatible, 6to4 and NAT64 at once, plus a custom /96 prefix; paste an IPv6 back and it reverses automatically.
A subnet calculator only expands a CIDR into a network; this tool does the reverse — splits any range into the fewest CIDR blocks that tile it exactly.
It extracts the address from URLs, ports, brackets, zone ids and full-width characters, and tells you clearly what was removed — no silent changes.
Everything runs in your browser. IP addresses are never sent to a server, and the tool works offline.
Paste any form into the top box: dotted-decimal, decimal integer, 0x hex, octal, binary, CIDR or range — or click an example.
The nine forms appear live; the badge by the input shows what was detected, and flags ambiguity so you can switch manually.
Need IPv4↔IPv6 mapping or CIDR↔range? Open the matching tab. Large lists go to "Bulk".
Every result has its own copy button; bulk output copies as TSV straight into Excel / WPS.
Turn a dotted IP into a 32-bit integer or hex for databases, firewall rules and code constants.
Logs often store integer or hex IPs; convert back to dotted-decimal for troubleshooting.
Verify CIDRs, split ranges, double-check network boundaries before deploying.
Map IPv4 into IPv6, do 6to4 / NAT64 translation, compare compressed and expanded forms.
One address per line, compute type and bases, export TSV for a spreadsheet or system import.
Visually explore multiple representations, IPv6 normalization and CIDR boundary splitting.
Yes — just a different notation. IPv4 is a 32-bit unsigned integer; dotted-decimal splits it into four 8-bit segments. The unsigned decimal shown here is that number itself.
An IPv4 as a whole octal value is at most 32 bits = 11 octal digits (e.g. 192.168.1.1 → 30052000401). Segmented octal pads each segment to 4 digits with a leading 0 (0300.0250.0001.0001); both are common conventions.
IPv6 is 128 bits in 8 groups. To shorten it, a run of all-zero groups is compressed with ::, but only one run is compressed and a single zero group is never compressed. This tool outputs the canonical form per RFC 5952.
History created several mappings: the common ::ffff:192.168.1.1 (IPv4-mapped); the deprecated ::192.168.1.1 (IPv4-compatible); 2002:c0a8:101:: (6to4) and 64:ff9b::192.168.1.1 (NAT64). They have different meanings — don't mix them up.
Because a CIDR block size must be a power of two aligned to a boundary. An irregular range cannot be covered by one CIDR, so the tool greedily splits it into the fewest blocks that tile the range exactly — something a subnet calculator can't do.
| Range / address | Type | Meaning |
|---|---|---|
0.0.0.0/8 | This network | "Current network"; host bits all zero is not a normal source address |
10.0.0.0/8 | Private A | LAN only, not publicly routable |
100.64.0.0/10 | Carrier-grade NAT | CGNAT, for ISP address sharing |
127.0.0.0/8 | Loopback | Points to this host; 127.0.0.1 is the common one |
169.254.0.0/16 | Link-local | Auto private address when DHCP fails |
172.16.0.0/12 | Private B | LAN, covers 172.16–172.31 |
192.0.2.0/24 | Documentation | TEST-NET-1, docs and examples only |
192.168.0.0/16 | Private C | Most home routers |
198.18.0.0/15 | Benchmarking | Network device testing |
198.51.100.0/24 | Documentation | TEST-NET-2 |
203.0.113.0/24 | Documentation | TEST-NET-3 |
224.0.0.0/4 | Multicast | One-to-many; 224.0.0.1 is all hosts |
240.0.0.0/4 | Reserved | Unassigned |
255.255.255.255 | Limited broadcast | Local segment only, not routable |
| Address / prefix | Type | Meaning |
|---|---|---|
::/128 | Unspecified | IPv6 equivalent of 0.0.0.0 |
::1/128 | Loopback | IPv6 equivalent of 127.0.0.1 |
::/0 | Default route | IPv6 equivalent of 0.0.0.0/0 |
::ffff:0:0/96 | IPv4-mapped | Represents IPv4 in IPv6; most common |
::/96 | IPv4-compatible | Deprecated |
64:ff9b::/96 | NAT64 | IPv6↔IPv4 translation prefix |
2001:db8::/32 | Documentation | Docs and examples only |
2002::/16 | 6to4 | Carries IPv6 over IPv4 |
fc00::/7 | Unique local | IPv6 private (fc00 and fd00) |
fe80::/10 | Link-local | Auto-configured, local link only |
ff00::/8 | Multicast | One-to-many |
Paste an IP address, integer, CIDR or address range into the top box and the nine representations appear instantly. The three tabs below add IPv4↔IPv6 mapping, CIDR↔range conversion, and bulk conversion for up to 1000 rows. Every result has its own copy button.
Many systems (databases, firewalls, scripts, C inet_addr, Java int) store IPs as a 32-bit integer. Turning 192.168.1.1 into 3232235777, or back, is one of the most common tasks in network programming, log analysis and rule configuration.
IPv6 is 128 bits in 8 groups. The compressed form (e.g. 2001:db8::1) is just shorter; expanded it is 2001:0db8:0000:0000:0000:0000:0000:0001 and they are identical. This tool normalizes strictly per RFC 5952: lower case, no leading zeros, only the longest run of zero groups compressed, and a single zero group is never compressed. Showing the canonical form does not mean your address was changed.
When a value is all 0/1 and at least 8 digits long, auto-detection prefers binary (binary 11000000 = 192). If you want decimal, switch the format dropdown on the right from "Auto" to "Decimal"; the badge will clearly state you chose the format.
::ffff:0:0/96 is the IPv4-mapped address (most common, e.g. ::ffff:192.168.1.1); ::/96 is the deprecated IPv4-compatible form; 2002::/16 is 6to4; 64:ff9b::/96 is NAT64. You can also supply a custom /96 prefix and embed the IPv4. Paste an IPv6 address back and it auto-detects which mapping it belongs to and recovers the IPv4.
CIDR block size must be a power of two aligned to a boundary. An irregular range (e.g. 192.168.1.5-192.168.1.10) cannot be covered by a single CIDR, so the tool splits it into the minimum number of CIDR blocks (here 4) that exactly tile the original range — no gaps, no overlap.
No. All conversion happens locally in your browser; IP addresses are never sent anywhere and are never recorded. The tool also works fully offline.