IPv4 number converter
Convert IPv4 addresses to unsigned integers, hexadecimal and binary with editable bits.
How it works & useful details
How it works & limits
Convert a dotted-decimal IPv4 address to an unsigned 32-bit number and back. Octets are ordered from most to least significant (network byte order). Decimal values range from 0 to 4294967295.
Hexadecimal accepts up to eight digits, optionally prefixed with 0x. Binary accepts up to 32 bits, optionally prefixed with 0b. Signs, fractions, scientific notation and ambiguous IPv4 octets with leading zeros are rejected. Toggle any bit to explore the value.
Your working space
Explore the live view, then save copyable text and a downloadable file. Everything is calculated locally. Inputs are not stored; refreshing clears them.
These tools inspect address notation and ranges. They do not contact addresses, check availability or establish connectivity.
About this tool
IPv4 number converter translates an IPv4 address into its unsigned integer, hexadecimal, and binary representations, and lets you edit the bits directly. It is useful for database schemas that store addresses as integers and for bit-level debugging.
Conversion is exact across all 32 bits, so nothing is lost to sign handling. The bit editor shows how each octet maps to the underlying number.
How to use it
- Enter the IPv4 address or an integer value.
- Review the decimal, hexadecimal, and binary forms.
- Toggle or type individual bits if you need to adjust the value.
- Copy the representation you need.
Worked example
192.168.1.1 converts to the unsigned integer 3,232,235,777, hexadecimal 0xc0a80101, and binary 11000000 10101000 00000001 00000001. Each octet is one byte: 192 = 0xc0, 168 = 0xa8, 1 = 0x01, 1 = 0x01. The integer is 192 × 256³ + 168 × 256² + 1 × 256 + 1.
Converting back works the same way in reverse. 0x0a000001 is 10.0.0.1, and 4294967295, the largest 32-bit value, is 255.255.255.255.
Where numeric IPs appear
Databases often store IPv4 addresses as integers, because range checks become simple numeric comparisons and the column is smaller. GeoIP files, firewall exports, and packet captures may show addresses in hexadecimal or as raw integers. Converting them back to dotted notation makes logs readable.
Leading zeros are rejected on purpose. Some software reads 010.0.0.1 as octal, meaning 8.0.0.1, while others read it as decimal 10.0.0.1. That ambiguity has caused real security bugs in address filters. Toggling individual bits in the tool also shows how subnet masks work, since a /24 mask is simply the first 24 bits set to 1.
Frequently asked questions
Why does my database show an unexpected integer?
IPv4 as an integer is unsigned. Signed 32-bit storage or byte-order differences can make the same address appear negative or reversed.
Are octets with leading zeros accepted?
Standard dotted-quad notation is used; ambiguous leading-zero octets are rejected rather than interpreted as octal.
Does it support IPv6?
No. Use the IPv6 address converter for 128-bit addresses.
Which byte order is used?
Network byte order (big-endian): the first octet is the most significant byte. A little-endian system dump of the same address would show the bytes reversed.