IP Address to Decimal Converter

An IPv4 address is a 32-bit number most people read as four dotted decimal octets, such as 192.0.2.10. Decimal conversion shows the same address as one unsigned integer from 0 through 4294967295. That form still appears in database rows, packet notes, access-control checks, legacy APIs, log fields, and low-level code where a single numeric value is easier to sort or compare than dotted notation.

The four octets are not four independent identifiers. They are byte positions in one 32-bit value, so the first octet carries far more weight than the last. 192.0.2.10 becomes 3221225994 because 192 is multiplied by 256^3, 0 by 256^2, 2 by 256, and 10 by 1.

Decimal address form is useful when two systems disagree about notation. One log might store 3232235777, another might show 192.168.1.1, and a packet note might prefer 0xC0A80101. They refer to the same 32 bits when the byte order and signedness are understood.

The numeric form does not say whether an address is assigned, reachable, safe to route, or owned by a given organization. Special-purpose ranges, private-use ranges, documentation ranges, multicast space, loopback, and broadcast addresses have routing meanings that must be checked separately from the arithmetic.

How to Use This Tool:

Start with one value from a log, database row, firewall note, or packet capture. The converter accepts one IPv4 value at a time and shows every supported representation from the same parsed 32-bit address.

1. Enter one value in IPv4 value. Valid examples include 192.0.2.10, 3221225994, 0xC000020A, 11000000.00000000.00000010.00001010, and 0o30000001012.
2. Leave Input format on Auto detect for normal pasted values. Choose Dotted IPv4, Decimal integer, Hex integer, Binary bits, or Octal integer when a bare value is ambiguous.
3. Set Output focus to the representation you plan to copy. This changes the highlighted row and Copy focus value while keeping Address Formats, Octet Ledger, Range Profile, Octet Weight Map, and JSON available.
4. Open Advanced when notation matters. Binary grouping changes dotted, continuous, nibble, or byte-grouped binary display. Hex style switches between prefixed, bare, and dotted byte output. Include API rows adds signed int32 and little-endian views.
5. Read any warning before copying. If several non-empty lines are pasted, the page uses only the first value and reports how many extra lines were ignored. If an octet, integer, or bit string is outside the accepted range, fix the input until the result panel returns.
6. Use Range Profile to check Range match, Routability hint, Legacy class, and Integer window before pasting the value into a ticket, ACL note, SQL query, or code comment.

Interpreting Results:

The main value to verify is Decimal integer. It is the unsigned 32-bit address value. If the dotted address is correct but the integer looks surprising, inspect Octet Ledger to see each octet's weight and contribution.

• Address Formats compares dotted IPv4, decimal, hexadecimal, binary, octal, dotted and hex IPv4-mapped IPv6, and optional legacy API views from the same address.
• Range match names the first built-in special-purpose block that contains the address. Treat that as address-category context, not a live reachability test.
• Routability hint separates special-purpose handling from a public unicast candidate. Public unicast candidate means no built-in special range matched; it does not prove allocation, ownership, DNS validity, or route advertisement.
• Legacy class is historical. Modern routing uses CIDR prefixes, so a Class A, B, C, D, or E label should not be used as a subnet size decision.
• Signed int32 view and Little-endian integer are compatibility checks. Use them only when the system you are comparing against stores addresses in that form.

For troubleshooting, compare two independent rows before trusting the copied value. A correct Dotted IPv4 plus a plausible Range match usually catches pasted decimal mistakes, byte-order reversals, and documentation-range addresses before they move into a change note.

Technical Details:

IPv4 carries a source address and destination address as 32-bit fields. Dotted decimal notation prints those 32 bits as four 8-bit octets in network byte order. Decimal notation treats the same four octets as one unsigned integer, with the leftmost octet as the most significant byte.

Valid dotted IPv4 input has exactly four decimal octets, each from 0 through 255. The resulting integer must fit the unsigned IPv4 window from 0 through 4294967295. Hexadecimal, binary, and octal inputs are alternate ways to spell the same 32 bits, not different address families.

Formula Core

The decimal value is weighted addition across the four octets.

For 192.0.2.10, the substitution is 192 x 16777216 + 0 x 65536 + 2 x 256 + 10, which gives 3221225994. The same value in hexadecimal is 0xC000020A, and the binary octets are 11000000.00000000.00000010.00001010.

Range and Compatibility Rules

Special-purpose range labels come from well-known IPv4 reservations. A match changes how the address should be discussed, but it does not run a lookup against routing tables, DNS, allocation registries, or firewall policy.

Signed 32-bit display uses two's-complement interpretation. Values above 2147483647 appear negative after subtracting 4294967296, so 3232235777 becomes -1062731519. Little-endian display reverses the byte order before reading the value as an integer, which helps diagnose packed data and older address storage.

The IPv4-mapped IPv6 form uses an IPv6 prefix with the IPv4 value in the low 32 bits. For 192.0.2.10, the canonical dotted mapped form is ::ffff:192.0.2.10, while the hex grouped view is ::ffff:C000:020A. Both are representations for APIs and mixed IPv4/IPv6 software, not proof that an IPv6 route exists.

Privacy Notes:

The conversion calculation runs in the browser after the page loads. It does not need an address lookup service, uploaded file, or account-specific query to turn one IPv4 value into its related numeric forms.

Copied rows, downloaded tables, chart images, JSON, DOCX exports, screenshots, and shared links can still reveal internal addresses. If a copied link includes the current values, remove sensitive addresses before sending it outside the intended audience.

Worked Examples:

Documentation address from a sample config

Enter 192.0.2.10 with Input format on Auto detect. Decimal integer becomes 3221225994, Hex integer becomes 0xC000020A, and Range match reports Documentation TEST-NET-1 (192.0.2.0/24). That range label means the address is appropriate for examples, not production traffic.

Database integer back to a private gateway

Enter 3232235777 and set Input format to Decimal integer if you want to avoid guessing. Dotted IPv4 becomes 192.168.1.1, Range match reports Private-Use (192.168.0.0/16), and the optional Signed int32 view is -1062731519. If another system shows the signed value, the addresses can still match once signedness is accounted for.

Finding a paste problem before export

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. If you meant to compare both addresses, run them one at a time; otherwise only the Address Formats, Range Profile, and exported rows for 192.168.1.1 should be trusted.

FAQ:

Glossary:

IPv4

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

Octet

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

Unsigned 32-bit integer

A whole number from 0 through 4294967295 with no negative values.

CIDR

Classless Inter-Domain Routing notation, used to describe address ranges with slash prefixes.

Special-purpose address

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

IPv4-mapped IPv6

An IPv6 representation that embeds the IPv4 value in the low 32 bits after the ::ffff: marker, commonly with the final 32 bits shown as dotted IPv4 text.

Signed int32

A 32-bit integer view where values above 2147483647 appear negative.

Little-endian

A byte-order view that reads the least significant byte first.

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.