IPv4 Integer Converter
Convert strict IPv4 addresses and unsigned 32-bit integers
Convert strict dotted-decimal IPv4 and integers 0β4294967295 in network byte order, with hex and binary output. Leading zeros, signs, exponents and hex input are rejected. Limit: 1 MiB, 1000 non-empty lines.
Addresses and networks are processed in this page. No network probes or input drafts; analytics contains fixed action names and counts only.
The full guide also includes pitfalls, worked examples, snippets, FAQs, and related tools for checking results or troubleshooting.
About this tool
Translate dotted-decimal IPv4 addresses into unsigned 32-bit integers, or turn decimal integers back into IPv4. The leftmost octet is the most significant byte: 192.0.2.1 corresponds to 3221225985, 0xC0000201 and binary 11000000.00000000.00000010.00000001. Auto mode treats a value containing a dot as an address and other values as integers; explicit modes catch the wrong input direction. Decimal integers must be 0β4294967295. Signs, exponents, hexadecimal input, empty octets and leading zeros are rejected instead of coerced. Lists are limited to 1000 non-empty lines and 1 MiB. Correct all invalid rows before exporting TSV. Conversion uses browser-local integer arithmetic and saves no drafts; it does not classify, locate or contact an address.
Failure Clinic (Common Pitfalls)
The same bytes produce a different database number
Cause: Signed storage and little-endian byte assembly differ from the unsigned network-byte-order convention used here.
Fix: Check the column type and the code that wrote it. Use a known vector such as 1.0.0.0 = 16777216 before migrating a whole table.
A loosely formatted octet becomes a different address
Cause: General Number conversion can interpret an empty segment as zero, 0xC0 as hexadecimal, or 1e2 as an exponent.
Fix: Repair the source to four decimal octets. This converter rejects those spellings and blocks export of a list with any invalid row.
Scenario Recipes
Check an unsigned database address
Goal: Confirm numeric storage and byte order
- Enter 192.0.2.1 and 3221225985 on separate lines in Auto-detect mode.
- Convert and confirm that both rows show address 192.0.2.1 and hex 0xC0000201.
- Compare the unsigned decimal column with the database field, then export TSV.
Result: Two equivalent rows demonstrate network byte order without a live database connection.
Production Snippets
Network byte order has a fixed numeric meaning
text
192.0.2.1
= 192 Γ 16777216 + 0 Γ 65536 + 2 Γ 256 + 1
= 3221225985
= 0xC0000201
0 -> 0.0.0.0
4294967295 -> 255.255.255.255
1e3 -> invalid integer syntaxFrequently Asked Questions
Which byte order is used?
Network byte order, with the first octet multiplied by 2^24, the second by 2^16, the third by 2^8 and the fourth added directly. 1.0.0.0 is 16777216, not 1.
Why is a database value negative?
Some databases store the same 32 bits as a signed integer. This tool accepts only unsigned decimal values. Verify the database schema before converting a negative value by adding 4294967296.
Are 1e3, 0xC0000201 or 001 accepted?
No. Integer input is strict unsigned decimal without exponents, signs or leading zeros. Hexadecimal and binary are output columns only.
How does automatic direction selection work?
A dot selects IPv4 parsing; otherwise the line is parsed as an integer. Choose an explicit mode when a list must contain only one input type. A malformed dot-containing number is not silently retried as a decimal.
What are the endpoint values?
0 maps to 0.0.0.0 and 4294967295 maps to 255.255.255.255. A value of 4294967296 is outside the 32-bit range and is rejected.
Can I process a log export without saving it?
Paste up to 1000 non-empty lines and 1 MiB. Inputs are processed locally without draft storage. Every invalid row must be corrected before the complete TSV can be copied or downloaded.
Keep browsing