How This IP Address Converter Works
Paste an IP address, a decimal integer, or a hex value, and this ip address converter, doubling as an ip to hex converter and ip to binary converter in the same pass, auto-detects what format you gave it, decimal, hex (0x-prefixed), binary (dotted), IPv6 (colon-containing), or IPv4 dot-decimal, then converts it to every other relevant representation at once. For IPv4 input, it returns dot-decimal, decimal integer, hex, hex-bytes, binary, and octal together with private-range, loopback, and link-local flags. For IPv6 input, it works as an ipv6 expand compress tool, returning both expanded and compressed notation, the raw hex representation, and loopback/link-local/multicast flags. Force a specific interpretation with the mode selector when auto-detection would be ambiguous, a bare decimal number and a hex value can look similar depending on formatting.
IPv4 to Decimal, Hex, and Binary Explained
Every IPv4 address is really just a 32-bit number, dot-decimal notation (192.168.1.1) is simply that number split into four 8-bit bytes for readability. An ip to decimal converter reading works by combining those four bytes back into a single integer: 192.168.1.1 becomes 3232235777. The same number reinterpreted in hex is 0xC0A80101, and in binary it's four 8-bit groups: 11000000.10101000.00000001.00000001. A decimal to ip converter runs the same process in reverse, splitting a decimal integer like 3232235777 back into its four dot-decimal bytes.
IPv6 Expanded vs Compressed Notation
IPv6 addresses have two equally valid ways to write the same address. Expanded notation always shows all eight 16-bit groups in full, ::1 (the IPv6 loopback address) expands to 0000:0000:0000:0000:0000:0000:0000:0001. Compressed notation uses :: once to replace the single longest run of consecutive all-zero groups, which is why ipv6 compressed notation tools matter, hand-writing the compression rule correctly (longest run, only once, leading zeros within a group also dropped) is easy to get subtly wrong. One current limitation worth knowing: this tool doesn't yet support IPv4-mapped IPv6 addresses (the ::ffff:192.168.1.1 style notation embedding an IPv4 address inside an IPv6 one), so an ipv4 to ipv6 converter use case involving that specific embedded format isn't covered here yet.
Private, Loopback, and Link-Local Ranges
Answering is this ip private without doing CIDR math by hand is one of the more common reasons to reach for an IP converter. This tool checks IPv4 input against the standard cidr private ip ranges, 10.0.0.0/8, 172.16.0.0/12, and 192.168.0.0/16, plus loopback (127.0.0.0/8) and link-local (169.254.0.0/16) ranges. For IPv6, it flags the loopback address (::1), link-local addresses (starting fe80::), and multicast addresses (starting ff).
| Range | IP version | What it means |
|---|---|---|
| 10.0.0.0/8 | IPv4 | Class A private range |
| 172.16.0.0/12 | IPv4 | Class B private range |
| 192.168.0.0/16 | IPv4 | Class C private range |
| 127.0.0.0/8 | IPv4 | Loopback (localhost) |
| fe80::/10 | IPv6 | Link-local |
| ff00::/8 | IPv6 | Multicast |
What This Tool Doesn't Do
This converter doesn't support IPv4-mapped IPv6 addresses yet, a currently unsupported input format rather than an oversight in the output. It also doesn't do IP geolocation, ISP lookup, or ASN information, that's a separate lookup tool on this site (IP Address & Geolocation Lookup), this one is purely a format converter with no external data or network requests involved. It doesn't validate whether an address is actually routable, assigned, or in active use, and it doesn't perform broader CIDR or subnet range calculations beyond flagging the handful of well-known private, loopback, link-local, and multicast ranges.