How do I convert an IP address to an integer?

Multiply the first octet by 16777216, the second by 65536, the third by 256 and add the fourth. For 192.168.1.1 that is 3232235777. The converter does this exactly with BigInt and also shows the hex, hex byte and binary forms.

Why is my signed integer rejected?

IPv4 addresses are unsigned 32-bit values. Some languages and databases store them as signed int32, so 192.168.1.1 appears as -1062731519. That value is shown as a programming view, and signed input is refused with the unsigned value to use instead.

Is the address I type sent or stored?

No. Conversion runs entirely in your browser, nothing is resolved or looked up online, and addresses are not saved.

IPv4 Address Converter

Convert IPv4 between dotted, integer, hex and binary forms

Input

IPv4 address

Dotted decimal, unsigned integer, 0x hex or 32-bit binary.

Detected format:

Dotted decimal

Converted 192.168.1.1 from Dotted decimal.

Results

IPv4 notations

IPv4 address: 192.168.1.1
Unsigned integer: 3232235777
Hex: 0xC0A80101
Hex bytes: C0 A8 01 01
Binary: 11000000 10101000 00000001 00000001
Octets: 192 | 168 | 1 | 1

Programming views

Signed int32: -1062731519; Programming and database representation, not an IPv4 notation.
Reverse octets (little-endian integer): 16885952; The same four bytes read least significant first. Not an IPv4 notation.

All forms are in network byte order (big-endian): the most significant octet comes first. Swap byte order in the Endianness Converter

Address type

Type: Private
Private
Registry block: 192.168.0.0/16 (RFC 1918)

CIDR / Subnet CalculatorIPv4 and IPv6 subnet math, address types and subnet splitting IPv4 Range & CIDR CalculatorConvert IPv4 ranges to the minimal CIDR list, list their addresses, or expand a CIDR block IPv6 ParserExpand, compress and inspect any IPv6 address Endianness ConverterSwap byte order in 16, 32 or 64-bit words and read big-endian and little-endian values.Text ↔ Binary ConverterConvert text and binary bytes with UTF-8 or strict ASCII.

What the converter shows

Enter one IPv4 address as dotted decimal (192.168.1.1), an unsigned 32-bit integer (3232235777), 0x hex (0xC0A80101) or 32 binary digits. The format is detected automatically and every other form is shown with its own copy button: dotted decimal, unsigned integer, hex, hex bytes, binary grouped by octet and the four octets. The address type comes from the IANA special-purpose address registry, with the defining RFC.

Strict parsing

Legacy shorthand that operating systems read differently is rejected instead of guessed: short forms such as 127.1, octets with leading zeros such as 192.168.001.001 (often read as octal), octets above 255, integers above 4294967295 or with leading zeros, hex without the 0x prefix and binary that is not exactly 32 bits. Each error names the part to fix.

Byte order and signed integers

Every form is in network byte order (big-endian): the most significant octet comes first. Signed int32 is the two's-complement value some languages and databases store, and Reverse octets is the integer a little-endian host reads from the same four bytes; neither is an IPv4 notation, and signed input is not accepted. Use the Endianness Converter for general byte swapping.

Privacy and limits

Conversion runs entirely in your browser. Nothing is sent, resolved, pinged or saved, so addresses of internal networks stay on your device. The tool converts single IPv4 addresses; use the CIDR / Subnet Calculator for networks and the IPv6 Parser for IPv6 addresses.