Developer & Tech
IP Address Format Converter
Enter your details
Runs in your browser
How to use it
Using the ip address format converter
- 01
Enter the address
Standard dotted quad, e.g. 10.0.0.1.
- 02
Pick a representation
Binary for teaching, hex for packet dumps, integer for databases that store IPs as numbers.
Good to know
Where each format appears
Integer form shows up in IP geolocation CSVs and database columns; hex appears in Wireshark and protocol documentation; binary is how netmasks actually behave. Translating between them makes subnet math and packet analysis far less opaque.
Unsigned 32-bit range
The packed integer spans 0 (0.0.0.0) to 4,294,967,295 (255.255.255.255). Sorting or comparing IPs numerically works correctly only once they are converted to this form.
How it's calculated
The math behind this calculator
int = o₁·2²⁴ + o₂·2¹⁶ + o₃·2⁸ + o₄Each octet contributes eight bits. The converter packs them into one unsigned 32-bit integer, renders that integer in your chosen base, and shows every other representation as cross-check rows so conversions verify themselves.
Assumptions & limitations
- Input must be strict dotted decimal with octets 0–255.
- Hex output uses uppercase pairs; octal pads each octet to three digits.
Worked example
192.168.1.1 packs to integer 3232235777, binary 11000000.10101000.00000001.00000001 and hex C0.A8.01.01.
FAQ
Frequently asked questions
- Why store IPs as integers?
- They sort correctly, index compactly and compare cheaply. Most databases offer inet helpers over either representation.
- Is 192.168.001.001 valid input?
- Leading zeros are accepted by some tools but rejected here; enter plain decimal octets from 0–255 to avoid ambiguity.
- Does this handle IPv6?
- Not currently; IPv6 needs 128-bit packing and its own notation rules.
Keep exploring