How computers see IP addresses 

If you type  192.168.1.1   into your browser. Your computer will not see those four numbers separated by dots. It sees one big integer: 3232235521

192.168.1.1  after conversion look 3232235521 not a rocket science.. It’s simple math. And once you understand it, you will look at IP

addresses differently.

I run SubnetLab. I built the IPv4 to decimal converter because I got tired of doing this calculation by hand. Let me show you how computers really see your network.

The dotted‑decimal lie (what you see vs. what the machine sees)

An IPv4 address like 192.168.1.1 is called dotted‑decimal notation. It was designed for humans. Routers, switches, and your operating system do not use dots.

They use a 32‑bit unsigned integer.

That’s a fancy way of saying a single whole number between 0    & 4,294,967,295.

Every device on a network, your phone, a DNS server, and an Amazon router, converts the dotted IP into this integer before making any routing decision.

“The decimal representation is what the kernel passes to the routing table. Dots are just a convenience layer.”
— Kazim Ali, founder of SubnetLab

The math: breaking down 192.168.1.1

An IPv4 address has four parts. Each part is called an octet. Octet means eight bits.

One octet can be any number from  0 to 255. That’s 2⁸ possibilities.

Here is the conversion formula:

(octet1 × 256³)  + (octet2 × 256²) +  (octet3 × 256¹) +  (octet4 × 256⁰)

That’s the integer your computer actually works with.

Why does this matter for network programming?

If you write code that talks to sockets, pings a server, or builds a firewall rule, you often need the decimal form.

Example (Python):
The Ip address module lets you convert back and forth. But under the hood, it uses the same math.

Example (JavaScript):
Bitwise operators(<<,>>>) do the conversion in one line. That’s what our SubnetLab tool does – no backend, just your browser doing the math.

Why programmers care:
Storing IPs as integers in a database is faster and uses less space than storing strings. A 192.168.1.1 string takes 15 bytes. The integer 3,232,235,521takes 4 bytes.

I tested this on a MySQL table with 10 million rows. Integer lookup was 3x faster.

The rules behind the conversion RFC 791

The math is not random. It comes from RFC 791—the document that defined the Internet Protocol back in 1981.

That standard says: an IPv4 address is a 32‑bit number. The dotted notation is just for people. Every router, switch, and ARP request uses the integer form.

IANA (the organization that hands out IP blocks) also uses decimal representation internally when managing address space.

So when you convert 8.8.8.8,

(Google’s DNS) to decimal, you get 134744072. That’s how Google’s own servers see their IP before answering your ping.

Real‑world examples you can try right now

Open your command prompt& Ping 192.168.1.1  Your computer converts it to 3232235521

. Your computer converts it to 3232235521 before sending the packet.

Now try traceroute. Same thing. Every hop along the path is stored as an integer in the packet header.

One more: Open Wireshark and capture some traffic. Look at the IP header. You won’t see dots. You’ll see hex values. Those hex values translate directly to the decimal integer.

“”I once spent two hours debugging a firewall because I typed the decimal IP wrong. That’s when I built SubnetLab’s converter – to stop making that mistake.””

How CIDR and subnet masks relate to decimal IPs

A subnet mask like  255.255.255.0

255.255.255.0 in decimal represntation looks like 4294967040

CIDR notation(/24)  just tells you how many leading bits are 1. Your router converts both the IP and the mask to integers, then does a bitwise AND to decide if a destination is local or remote.

So when you use our converter, you are not just doing a party trick. You are seeing exactly what your router sees before it forwards your traffic.

Try the tool yourself

Instead of doing the math manually every time, use the SubnetLab IPv4 to decimal converter.

• No installation

• No ads

• Works offline (JavaScript only)

• Shows the integer with or without commas

Click here to convert any IPv4 address in one second →

Summary 

The conversion is always:

(octet1 × 256³) + (octet2 × 256²) + (octet3 × 256¹) + (octet4 × 256⁰)

That’s it. No magic. No AI. Just math your router does billions of times per second.

Founder’s note:
“I built SubnetLab because networking tutorials either oversimplify or overload you with jargon. The decimal IP conversion is a perfect example – easy to learn, useful to know, and a pain to calculate by hand. So I automated it.”
— Kazim Ali, SubnetLab

Ready to convert? Try the free IPv4 to decimal tool here →