How is 192.168.1.1 equal to 3232235777?

Each octet is one byte, so the address packs into 32 bits as 192×256³ + 168×256² + 1×256 + 1. That is 192×16777216 + 168×65536 + 256 + 1 = 3221225472 + 11010048 + 257 = 3232235777. The tool does exactly this packing, and reading the bytes back out the same way gives you 192.168.1.1 again.

Why do databases and apps store an IP as an integer?

One 32-bit integer column is smaller and faster to index than a 15-character string, and range queries become trivial: a whole subnet is just a contiguous integer range, so WHERE ip BETWEEN x AND y selects it. Geo-IP tables, rate limiters and firewall rules all lean on this. Convert the dotted address to the integer once, store that, and convert back only for display.

What is IP to binary good for?

Binary lays the 32 bits out so subnetting becomes visual. A /24 mask is 24 ones then 8 zeros, and the network part of 192.168.1.1 is the first 24 bits, 11000000.10101000.00000001, with the last octet free for hosts. Seeing 11000000.10101000.00000001.00000001 makes it obvious why 192.168.1.0/24 holds 192.168.1.0 through 192.168.1.255.

How do I turn an integer back into an IP address?

Switch to the number-to-IP direction and paste the value. The tool splits the 32-bit integer into four bytes from most significant to least: 3232235777 becomes 192, 168, 1, 1. It also accepts a hex value such as 0xC0A80101, which is the same number written base 16. Anything outside 0 to 4294967295 is rejected because it cannot fit in four octets.

Does this support IPv6 addresses?

No. This tool is IPv4 only, where the whole address is 32 bits and maps cleanly to a single integer up to 4294967295. IPv6 is 128 bits, so its integer form needs a big-number type and a different notation with colons and hex groups like 2001:db8::1. For IPv6 work use a dedicated tool; everything here assumes the four-octet dotted-quad format.

Why does an octet like 256 or a leading zero get rejected?

Each octet is a single byte, so the valid range is 0 to 255; 256 needs nine bits and cannot fit, so 256.1.1.1 is not a real address. Leading zeros such as 192.168.01.1 are refused on purpose because some systems read 01 as octal, which would silently change the value. Strip the zero and the tool accepts it.

Store IP addresses as a single integer column

You are designing a logins table and want to record the source IP per row. Instead of a 15-char VARCHAR, convert 203.0.113.42 to its integer and store one INT/BIGINT. Indexes get smaller, range filters over a whole subnet become a simple BETWEEN, and joins against a geo-IP table keyed by integer ranges run far faster than string comparisons.

Write a subnet range filter for analytics

A dashboard needs to count hits from 10.0.0.0/8. Convert the network address 10.0.0.0 and the broadcast 10.255.255.255 to integers, then query WHERE ip BETWEEN 167772160 AND 184549375. The two bounds come straight out of this tool, and the query reads cleanly without any CIDR math living inside the SQL.

Debug a value that came back as a raw integer

A log line or an API response handed you 3232235777 with no context. Paste it into the number-to-IP side and you instantly see 192.168.1.1, plus its binary and hex. No more squinting at a bare number wondering which host on the network it points at.

Teach or learn how subnetting maps to bits

Studying for a networking exam, you need to see why a /26 splits a /24 into four blocks. Convert addresses to dotted binary and watch the boundary bits move: the first 26 ones are the network, the trailing six bits give 64 hosts per block. Seeing the 1s and 0s line up makes masks click in a way decimal never does.

IP to Decimal Converter (IPv4 to Integer, Binary, Hex)

IPv4 dotted-quad to 32-bit integer, binary and hex, both directions, browser-only

Runs locally
Category Developer & DevOps
Best for Formatting, validating, shrinking, or inspecting code-adjacent text.

Direction:

IPv4 address

Examples:

Decimal (32-bit integer)

3232235777

Binary (dotted)

11000000.10101000.00000001.00000001

Hex

0xC0A80101

All conversion runs on plain JavaScript in your browser. Nothing about the address you enter is uploaded.

What this tool does

Free IP to decimal converter that turns an IPv4 dotted-quad address into a 32-bit integer, dotted binary and hexadecimal, and converts any of those back into an IP. Type 192.168.1.1 and read 3232235777, the binary 11000000.10101000.00000001.00000001, and 0xC0A80101 side by side, each with a one-click copy. Feed it a decimal like 3232235777 or a hex value like 0xC0A80101 and it rebuilds the address. Every octet is validated to 0-255 and every integer is range-checked to 0-4294967295, so a typo gives a clear error instead of a wrong answer. The math is the same packing databases, firewalls and routers use internally, which is why storing an IP as one integer column beats four bytes. Everything runs in your browser, the result rides in a shareable URL, and nothing you type is ever uploaded.

Tool details

Input: Text + Numbers; The page exposes text boxes, numeric controls, file pickers, or structured inputs depending on the tool.
Output: Live result + Copy; The result area focuses on usable output, with copy, download, or preview actions when supported.
Privacy: Browser-side processing; The main tool logic does not call an external API, so inputs normally stay in the current tab.
Save / share: Shareable URL state; Key settings are encoded in the URL so another person can reopen the same setup.
Performance budget: Initial JS <= 9 KB; No WASM budget is declared, keeping the tool quick to open on mobile.
Best fit: Developer & DevOps · Developer; Category and role tags drive related tools, internal links, and quick fit checks.

How to use

1. Input

Paste or drop your content into the tool panel.
2. Process

Click the button. All processing is local in your browser.
3. Copy / Download

Copy the result or download to disk in one click.

How IP to Decimal Converter fits into your work

Use it in the small gaps between coding, reviewing, debugging, and shipping.

Developer jobs

Formatting, validating, shrinking, or inspecting code-adjacent text.
Preparing snippets for documentation, tickets, commits, or handoff.
Checking a small payload quickly without switching tools.

Developer checks

Run irreversible transforms like minify or obfuscate on a copy.
Keep secrets out of pasted snippets unless the tool explicitly stays local.
Use your normal tests or linter before shipping transformed code.

Good next steps

These links move the current task into a more complete workflow.

Real-world use cases

Store IP addresses as a single integer column
You are designing a logins table and want to record the source IP per row. Instead of a 15-char VARCHAR, convert 203.0.113.42 to its integer and store one INT/BIGINT. Indexes get smaller, range filters over a whole subnet become a simple BETWEEN, and joins against a geo-IP table keyed by integer ranges run far faster than string comparisons.
Write a subnet range filter for analytics
A dashboard needs to count hits from 10.0.0.0/8. Convert the network address 10.0.0.0 and the broadcast 10.255.255.255 to integers, then query WHERE ip BETWEEN 167772160 AND 184549375. The two bounds come straight out of this tool, and the query reads cleanly without any CIDR math living inside the SQL.
Debug a value that came back as a raw integer
A log line or an API response handed you 3232235777 with no context. Paste it into the number-to-IP side and you instantly see 192.168.1.1, plus its binary and hex. No more squinting at a bare number wondering which host on the network it points at.
Teach or learn how subnetting maps to bits
Studying for a networking exam, you need to see why a /26 splits a /24 into four blocks. Convert addresses to dotted binary and watch the boundary bits move: the first 26 ones are the network, the trailing six bits give 64 hosts per block. Seeing the 1s and 0s line up makes masks click in a way decimal never does.

Common pitfalls

Reversing the byte order. The first octet is the most significant byte, so 1.2.3.4 is 16909060, not 67305985. If you build the integer little-endian by mistake, every address comes out wrong. Pack big-endian, first octet times 16777216 down to last octet times 1.
Leaving a leading zero in an octet. Writing 192.168.01.1 looks harmless, but some parsers read 01 as octal and quietly change the value, while strict ones reject it outright. Drop the zero; an octet is just 0 to 255 in plain decimal.
Overflowing a signed 32-bit integer. 255.255.255.255 is 4294967295, which is larger than the 2147483647 max of a signed INT. Store IPv4 integers in an unsigned 32-bit or a 64-bit column, or addresses above 127.x wrap to negative numbers.

Privacy

Every conversion here is plain JavaScript running inside your browser tab. The address, the integer, the binary and the hex never leave the page, and nothing you type is logged. The one caveat: the shareable URL encodes your input in the query string, so a link pasted into chat records that value in the recipient server's access log. Internal addresses are rarely secret, but if you would rather not leak one, use the copy button instead of the share link.

FAQ

Tool combos

Folks in your role tend to reach for these alongside this tool.

Developer

Browse all tools for this role

IP to Decimal Converter (IPv4 to Integer, Binary, Hex)

What this tool does

Tool details

How to use

1. Input

2. Process

3. Copy / Download

How IP to Decimal Converter fits into your work

Developer jobs

Developer checks

Good next steps

Real-world use cases

Store IP addresses as a single integer column

Write a subnet range filter for analytics

Debug a value that came back as a raw integer

Teach or learn how subnetting maps to bits

Common pitfalls

Privacy

FAQ

Unit Converter

Percentage Calculator

IP Subnet Calculator (CIDR)

Number Base Converter

IPv4 Address Normalizer

Scientific Notation Converter

AI Eval Planner

Apache Cheatsheet

API Key Generator

API Rate Limit Cheatsheet

ASCII Table Generator

ASCII Table Reference