Decimal to IP Converter

About this tool

Decimal to IP is the reverse of IP to Decimal - it converts an unsigned 32-bit integer back into standard IPv4 dotted-decimal notation. Databases, security tools, and analytics platforms frequently store IP addresses as integers for efficiency. When you are reading those systems' output, you need a fast way to get back to a human-readable address. This tool does that in one step.

Real example

Input: 3232235777

The tool extracts each octet by bit-shifting:
3232235777 >>> 24 = 192
(3232235777 >>> 16) & 255 = 168
(3232235777 >>> 8) & 255 = 1
3232235777 & 255 = 1
Result: 192.168.1.1

A few useful reference values: 0 = 0.0.0.0, 2130706433 = 127.0.0.1 (localhost), 3232235520 = 192.168.1.0, 4294967295 = 255.255.255.255.

Common use cases

• Database exports: MySQL's INET_ATON() and PostgreSQL's integer IP storage formats produce decimal integers. When querying raw values from these tables, convert them here to verify you are looking at the right address.
• SIEM and firewall log analysis: Many SIEM exports include integer-formatted IPs in raw event data. Paste the number here to immediately read the address without writing a conversion function.
• Incident response: When reviewing large log volumes, integer IPs appear frequently. Having a fast converter avoids mental arithmetic during time-sensitive investigations.
• Validating parser output: If you have written custom IP parsing code, convert the integer output here to verify the dotted-decimal result is correct.

How it works

The decimal integer is treated as an unsigned 32-bit value. Each octet is extracted by right-shifting and masking: the first octet is bits 31-24 (value >>> 24), the second is bits 23-16 ((value >>> 16) & 255), the third is bits 15-8 ((value >>> 8) & 255), and the fourth is bits 7-0 (value & 255). The four values are joined with dots.

Common mistakes

• Negative signed integers: In signed 32-bit representation, addresses above 127.255.255.255 appear as negative numbers. If your source is a signed integer, you need to add 2³² (4,294,967,296) to it before converting. For example, -1062731775 + 4294967296 = 3232235521 = 192.168.1.1 (roughly).
• Octet concatenation confusion: 3232235777 is not 192+168+1+1 concatenated as a string. The conversion involves bit shifting - simple string joining of the octets produces a completely different number.
• Out-of-range values: Valid inputs are 0 to 4,294,967,295. Values above this represent addresses outside the IPv4 space and are not valid.

FAQ

What is 2130706433 in dotted notation
127.0.0.1 - the loopback address (localhost). This is a common value to recognize when reviewing logs.

How do I convert an IP to a decimal integer
Use the IP to Decimal tool - the reverse of this converter.

Does this handle negative numbers
No. Enter the unsigned equivalent (add 4,294,967,296 to negative signed values first). This tool only accepts values in the 0-4,294,967,295 range.

What is the valid range
0 (= 0.0.0.0) through 4,294,967,295 (= 255.255.255.255).

Why decimal IP representation exists

Every IPv4 address is fundamentally a 32-bit unsigned integer. The dotted-decimal notation — four octets separated by dots — is a human-readable convention layered on top of that integer. Routers, operating systems, and network APIs work with the 32-bit value internally. Dotted notation exists purely for readability; the underlying math is always integer arithmetic.

When you see a decimal IP in a database column, a log parser, or a binary protocol field, you are looking at the raw integer form. Many older systems stored IPs as INT UNSIGNED in MySQL or as a 4-byte field in binary protocols (including parts of DHCP and older BGP implementations) rather than as text. Converting back to dotted notation is the first step to making those values meaningful during investigation or debugging.

How the conversion works

To convert a decimal integer to dotted-quad notation, repeatedly extract 8-bit chunks from right to left. Given the integer N:

• Octet 4 (rightmost) = N mod 256; N = floor(N / 256)
• Octet 3 = N mod 256; N = floor(N / 256)
• Octet 2 = N mod 256; N = floor(N / 256)
• Octet 1 (leftmost) = N

Equivalently, you can use bitwise operations: octet 1 is (N >>> 24) & 0xFF, octet 2 is (N >>> 16) & 0xFF, octet 3 is (N >>> 8) & 0xFF, octet 4 is N & 0xFF. This is exactly what this tool does in your browser using JavaScript's bitwise operators — no server involved.

Common decimal IP values worth recognizing

2130706433 — 127.0.0.1 (localhost loopback). Frequently appears in application logs when services communicate internally.

3232235520 to 3232301055 — 192.168.0.0/16 range. Private LAN addresses defined by RFC 1918, common in home and office networks.

167772160 to 184549375 — 10.0.0.0/8 range. The largest RFC 1918 private block, widely used in cloud VPCs (AWS, GCP, Azure default VPCs often start at 10.0.0.0).

4294967295 — 255.255.255.255, the limited broadcast address. A packet sent to this address is broadcast to all hosts on the local network segment.

0 — 0.0.0.0. Depending on context, represents "all interfaces" (bind address), "unspecified" (DHCP before assignment), or "default route" in routing tables.

For the reverse operation, use the IP to Decimal converter. For hexadecimal representation of the same address, see IP to Hex. If you are working with subnet ranges, the CIDR IP Converter shows the full address range for any prefix length.