IP Converter
Convert IPv4 addresses between dotted decimal, binary, hexadecimal and 32-bit integer.
Input
Auto-detects dotted decimal, binary, hexadecimal and 32-bit integer.
Output
Type an IPv4 value in any supported format.
Understanding IPv4 address formats
An IPv4 address is fundamentally a 32-bit unsigned integer. The four formats this converter supports are simply different ways to write the same value — and every network engineer eventually encounters all of them.
Dotted decimal (192.168.1.1) is the everyday notation used in router configs, packet captures and documentation. Dotted binary (11000000.10101000.00000001.00000001) is what the CPU actually sees and is essential for understanding subnet masks, wildcard masks and bitwise ACL matching. Hexadecimal (0xC0A80101) appears in low-level protocol analysis, BGP communities, and some operating-system APIs. The 32-bit integer form (3232235777) is used by databases, spreadsheets, and older UNIX tools — inet_aton() and inet_ntoa() in C work with this value directly.
Converting between these formats by hand is error-prone. The binary IP to decimal conversion alone requires eight multiplications per octet. This IP to binary converter auto-detects the input format and outputs all four representations simultaneously, octet by octet, so you can focus on the network problem rather than the arithmetic.
The detection heuristic handles the most common edge cases: hex values with or without the 0x prefix, pure 32-bit integers, and mixed inputs. Once you have the dotted-decimal form, send it to the Subnet Calculator to compute prefix boundaries without leaving the workflow.
Common use cases
- ACL wildcard masks — verify that a binary wildcard mask correctly matches the intended host range.
- Protocol analysis — translate hex addresses from Wireshark or tcpdump into readable dotted-decimal form.
- Database queries — convert between integer-stored IPs and human-readable notation for SQL or scripting.
- CCNA binary practice — quickly check manual binary IP conversion exercises.
- Subnet boundary checks — confirm that two addresses share the same network bits in binary before writing a route.
100% in-browser. No data sent. Zero tracking.