IP to Decimal Converter

What is IP to Decimal?

IP to Decimal converts an IPv4 or IPv6 address into its decimal number representation. This is useful for databases, low-level networking, and comparing or sorting IP ranges without dotted or colon formats.

How does the converter work?

• Enter IP Address: Type or paste the IP address into the input box at the top.
• Enable Auto Update (Optional): Keep Auto Update checked for instant results, or uncheck it if you prefer manual conversion.
• Convert the IP: Click the Convert button to process the entered IP.
• View Output: Check the Output box below to see the converted IP format or result.

Why convert IP to decimal?

Decimal IPs make it easy to compare ranges, store values in databases, and perform numeric operations. Network tools and security scripts often rely on decimal formats for sorting, filtering, and range checks.

• Range math: Quickly see if an IP falls within a CIDR block.
• Database storage: Store IPs as integers to improve indexing and comparisons.
• Automation: Scripts and firewalls can work directly with decimal values.

The formula behind IP to decimal conversion

An IPv4 address is four 8-bit octets written in dotted-quad notation. Converting it to a decimal integer means treating those four octets as a single 32-bit number, where each octet is weighted by its position:

decimal = (octet1 × 256³) + (octet2 × 256²) + (octet3 × 256) + octet4

Take 192.168.1.1 as a worked example. That expands to (192 × 16,777,216) + (168 × 65,536) + (1 × 256) + 1, which totals 3,232,235,777. Because every octet holds a value from 0 to 255, the full IPv4 space maps onto the integer range 0 through 4,294,967,295.

• Octet weights: 16,777,216, 65,536, 256 and 1, from left to right.
• Reversible: integer division and modulo by the same weights rebuild the dotted-quad address.
• Fixed width: every IPv4 address fits in exactly 4 bytes, which is why integer storage is so compact.

Common pitfalls when converting IP addresses

Most conversion errors come from input that looks valid but is not, or from storing the result in a column that cannot hold it. These are the cases worth checking before you trust a converted value:

• Octets above 255: 192.168.1.300 is not a valid IPv4 address, even though it parses as four numbers.
• Leading zeros: some libraries read 010 as octal, turning it into 8 rather than 10.
• Signed integer overflow: any address above 127.255.255.255 exceeds a signed 32-bit INT. Use an unsigned column, or a 64-bit type, to avoid negative values.
• IPv6 addresses: these are 128-bit, so they need a much larger numeric type than IPv4 and cannot be stored in the same 4-byte column.

Frequently Asked Questions

What is an IP to decimal converter used for?

It turns IPv4 or IPv6 addresses into their integer representation. This is helpful for IP range math, ACL comparisons, database storage, and networking scripts.

Does it support IPv6?

Yes. Compressed IPv6 (with ::) and embedded IPv4 are parsed into the correct 128-bit integer value.

Can I convert the decimal back to an IP?

You can use our Decimal to IP tool to reverse the conversion for both IPv4 and IPv6 integers.

Is my input stored or sent to a server?

No. The conversion runs locally in your browser; TestMu AI does not log your IP data.

Can I process multiple IPs at once?

Yes. Paste multiple lines and the tool will output each IP on its own line in decimal form, ready to copy or download.

What is the largest decimal value for an IPv4 address?

255.255.255.255 converts to 4,294,967,295, which is the highest value a 32-bit unsigned integer can hold. The lowest is 0.0.0.0, which converts to 0.

Should I store IP addresses as INT or BIGINT?

For IPv4, a 4-byte unsigned integer column such as MySQL INT UNSIGNED is enough and is the most storage-efficient option. A signed INT overflows above 2,147,483,647, so addresses starting at 128 and higher would wrap to negative numbers.