Convert IPv4 addresses between dotted decimal, binary octets, 32-bit binary, hexadecimal, and unsigned integer formats. Use it when checking subnet math, reading packet captures, or documenting network ranges.
Dotted decimal
Binary octets
Hex and integer
Local browser math
Conversion result
IPv4 breakdown
Address192.168.1.25
Dotted decimal
192.168.1.25
Binary octets
11000000.10101000.00000001.00011001
32-bit binary
11000000101010000000000100011001
Hexadecimal
0xC0A80119
Unsigned integer
3232235801
Octets
192 | 168 | 1 | 25
Address range
Private RFC1918 range
Subnet hint
Commonly seen in private LANs.
Common examples
Quick IPv4 conversions
Use these examples to sanity-check private ranges, public DNS addresses, loopback, and link-local addresses without retyping them.
How IPv4 to binary conversion works
An IPv4 address is a 32-bit number. People usually write it as four decimal octets, like 192.168.1.25, because that is easier to read than one long binary value. Each octet is a number from 0 to 255, and each one can be represented by exactly eight binary bits.
To convert the address, convert each decimal octet separately and pad each binary group to eight digits. The octet 192 becomes 11000000, 168 becomes 10101000, 1 becomes 00000001, and 25 becomes 00011001. Joined together, those four groups form the full 32-bit address.
Why binary octets matter for subnetting
Subnetting is easier to understand when you can see which bits belong to the network portion and which bits belong to hosts. A subnet mask marks network bits with 1s and host bits with 0s. Comparing the binary address to the binary mask shows where a network boundary falls.
This is especially useful when a subnet is not on a clean dotted-decimal boundary, such as /26, /27, or /29. Binary groups make it clear why a /26 block increments by 64 addresses, while a /29 block increments by 8 addresses.
Decimal, hexadecimal, and integer IPv4 formats
Most network dashboards show dotted decimal addresses, but logs, APIs, packet tools, and firewall exports sometimes expose the same address as hexadecimal or an unsigned integer. These formats all describe the same 32-bit value; they simply package the bits differently.
Hexadecimal is compact because each hex digit represents four bits. That means an IPv4 address can be written as eight hex digits. Unsigned integer form stores the full 32-bit value as one number, which is common in databases and low-level tooling.
Common IPv4 conversion mistakes
The most common mistake is dropping leading zeroes in binary. Each IPv4 octet must stay eight bits wide, so 1 is not written as 1 inside an IPv4 binary octet; it is written as 00000001. Without padding, the groups no longer line up with subnet masks.
Another common mistake is mixing decimal and binary separators. A dotted binary IPv4 address should contain four binary octets. If you paste one 32-bit binary string instead, the converter can still read it, but it will display the grouped version so the boundaries are visible again.
