IP Address to Decimal Converter

IPv4 addresses look like four small decimal numbers because dotted notation is made for people. The network field underneath is a fixed 32-bit value. When the same address moves into a database, packet trace, firewall export, or legacy API, those four octets may appear as one unsigned decimal integer, a hexadecimal word, a binary bit string, or a signed 32-bit value.

The dotted form 192.0.2.10 and the integer 3221225994 are not different addresses. They are two spellings of the same bits, read left to right in network byte order. That sounds like a small formatting detail until a log stores addresses as integers, a security rule expects dotted notation, or a troubleshooting note mixes public, private, and documentation ranges in the same list.

Decimal IPv4 conversion is most useful when the address must survive a boundary between human-readable network work and machine-oriented storage. A subnet planner may still think in CIDR blocks, but a database index may compare integer ranges. A packet field may show bytes, while a report needs a compact decimal column. The conversion does not change the address family or discover anything about reachability; it only makes the same 32 bits comparable in another notation.

The four numbers in dotted notation are byte positions, not separate labels. The first octet is the most significant byte, so changing it has a much larger effect on the decimal value than changing the fourth octet. Nearby-looking dotted addresses can be far apart as integers, and a byte-order reversal can produce a value that still looks valid while pointing to a different address.

Dotted decimal

The familiar a.b.c.d notation, where each octet is a decimal number from 0 through 255.

Unsigned decimal

One whole number from 0 through 4294967295, useful for storage, sorting, and range comparisons.

Network byte order

The left-to-right order used for normal IPv4 text and packet fields, with the first octet carrying the highest weight.

Decimal conversion does not prove that an address is assigned, public, reachable, or safe to route. Private-use space, loopback, documentation ranges, shared address space, multicast, reserved blocks, and limited broadcast addresses all have meanings that come from routing and protocol rules, not from arithmetic alone.

How to Use This Tool:

Use the converter when you have one IPv4 value from a log, database field, ACL note, packet capture, or code sample and need to compare its other notations from the same 32-bit address.

1. Enter one value in IPv4 value. Supported examples include 192.0.2.10, 3221225994, 0xC000020A, 11000000.00000000.00000010.00001010, and 0o30000001012.
2. Keep Input format on Auto detect for most pasted values. Select Dotted IPv4, Decimal integer, Hex integer, Binary bits, or Octal integer when the pasted text could be read more than one way.
3. Choose an Output focus for the value you expect to copy. The focused row and Copy focus button change, while Address Formats, Octet Ledger, Range Profile, Octet Weight Map, and JSON stay available.
4. Open Advanced if notation details matter. Binary grouping changes dotted, continuous, nibble, or byte-grouped binary output. Hex style changes prefixed, bare, or dotted byte display. Include API rows adds signed int32 and little-endian checks.
5. Fix any validation message before using the result. The input must resolve to exactly one IPv4 value, four octets must stay inside 0 to 255, and integer forms must fit the unsigned 32-bit range.
6. If several non-empty lines are pasted, the converter uses the first value and warns how many extra lines were ignored. Run separate conversions when each address needs its own range profile or export.

Interpreting Results:

The main output is Decimal integer, the unsigned 32-bit value for the parsed address. Use the matching Dotted IPv4 row as a quick sanity check before copying a decimal value into a ticket, SQL query, firewall comment, or code constant.

• Address Formats lists the same address as dotted IPv4, decimal, hexadecimal, binary, octal, IPv4-mapped IPv6, and optional compatibility views.
• Octet Ledger shows each octet's decimal value, binary bits, hex byte, weight, and contribution to the final integer.
• Range match names the first built-in IPv4 range that contains the address. Treat it as category context, not as a live lookup or route test.
• Routability hint separates special-purpose handling from a public unicast candidate. A public unicast candidate still needs allocation, DNS, route, and policy checks.
• Legacy class is historical. Class A, B, C, D, and E labels do not replace CIDR prefixes for modern subnet planning.
• Signed int32 view and Little-endian integer help compare legacy APIs, logs, and packed byte values. Use them only when the system you are checking stores addresses that way.

A useful troubleshooting pattern is to compare three signals together: dotted IPv4, decimal integer, and range match. If one of them feels wrong, inspect the octet ledger before assuming the other system is using the same byte order, signedness, or address category.

Technical Details:

An IPv4 address is a fixed-width 32-bit address field. Dotted decimal notation splits that field into four octets for readability. Decimal notation reads the same field as one unsigned integer, with the leftmost octet as the high-order byte.

Every accepted notation must reduce to those same four bytes. Hexadecimal, binary, and octal input forms are alternate numeric spellings, not separate address families. A valid decimal integer must fit inside 0 through 4294967295, which is 2^32 - 1.

Formula Core

The decimal value is the sum of four weighted octets.

For 192.0.2.10, the calculation is 192 x 16777216 + 0 x 65536 + 2 x 256 + 10, which equals 3221225994. The same bytes can be written as 0xC000020A in hexadecimal and 11000000.00000000.00000010.00001010 in binary octets.

Range and Compatibility Rules

IPv4 range labels depend on address reservations and CIDR blocks. The converter compares the unsigned decimal value against built-in ranges so an address such as 192.168.1.1 is not mistaken for ordinary public host space just because it has a valid numeric form.

Signed 32-bit output uses two's-complement interpretation. Values through 2147483647 stay positive, while larger unsigned IPv4 values appear negative after subtracting 4294967296. For example, 3232235777 becomes -1062731519 in a signed int32 view.

The IPv4-mapped IPv6 forms place the IPv4 address in the low 32 bits after the ::ffff: marker. For 192.0.2.10, the dotted mapped form is ::ffff:192.0.2.10 and the hex grouped form is ::ffff:C000:020A. Those strings are compatibility representations for mixed IPv4/IPv6 software; they do not prove that an IPv6 route exists.

Privacy Notes:

The conversion runs in the browser after the page loads. Turning one IPv4 value into decimal, hex, binary, range, chart, and JSON outputs does not require an address lookup service or an uploaded file.

The values you copy, export, screenshot, or share can still reveal internal networks. Review downloaded CSV, DOCX, chart image, JSON, and copied links before sending private or customer-specific addresses outside the intended audience.

Worked Examples:

Documentation address in a sample rule

Enter 192.0.2.10 with Input format set to Auto detect. The decimal integer is 3221225994, hexadecimal is 0xC000020A, and the range profile reports Documentation TEST-NET-1 (192.0.2.0/24). That range is useful for examples, not for production traffic.

Database value back to dotted IPv4

Enter 3232235777 and choose Decimal integer if you do not want auto detection to guess. The dotted IPv4 row becomes 192.168.1.1, the range profile reports Private-Use (192.168.0.0/16), and Include API rows shows the signed int32 view -1062731519.

Checking byte order in packed data

For 192.168.1.1, the normal unsigned decimal value is 3232235777. With API rows enabled, the little-endian integer is 16885952. A system showing the little-endian value is probably reading the same four bytes in reverse order rather than pointing at a nearby address.

Catching a multi-line paste

Paste 192.168.1.1 followed by 8.8.8.8 on the next line. The warning says the first value is used and one extra line is ignored. Run each address separately if you need separate address formats, range labels, chart rows, or exports.

FAQ:

Glossary:

IPv4

The 32-bit Internet Protocol address format commonly written as four dotted decimal octets.

Octet

An 8-bit byte of the IPv4 address, shown as one number from 0 through 255.

Unsigned 32-bit integer

A non-negative whole number from 0 through 4294967295.

CIDR

Classless Inter-Domain Routing notation, used to describe address ranges with slash prefixes such as 192.0.2.0/24.

Special-purpose address

An IPv4 block reserved for a defined use, such as private networking, documentation, loopback, benchmarking, multicast, or broadcast.

Two's complement

The common signed integer representation that makes 32-bit values above 2147483647 appear negative.

Little-endian

A byte-order view that reads the least significant byte first, useful when checking packed data or legacy storage.

IPv4-mapped IPv6

An IPv6 address form that stores an IPv4 address in the low 32 bits after the ::ffff: marker.

References:

• RFC 791: Internet Protocol, RFC Editor, September 1981.
• IPv4 Special-Purpose Address Space Registry, IANA.
• RFC 1918: Address Allocation for Private Internets, RFC Editor, February 1996.
• RFC 5737: IPv4 Address Blocks Reserved for Documentation, Internet Engineering Task Force, January 2010.
• RFC 4291: IP Version 6 Addressing Architecture, Internet Engineering Task Force, February 2006.