IPv4 Address Converter
How to use this IPv4 address converter
- Type any IPv4 address (like 192.168.1.1).
- See it instantly as a 32-bit decimal number, binary, hex, and IPv6-mapped notation.
- Useful for low-level networking, firewall rules, or understanding IPv6 transition.
What is an IPv4-mapped IPv6 address?
It's a way to represent an IPv4 address within the IPv6 address space, using the format ::ffff:a.b.c.d, allowing IPv6-only systems to communicate with IPv4 hosts during the ongoing transition between the two standards.
Why convert an IP to a single decimal number?
Databases and some networking code store IP addresses as a single 32-bit integer for efficient range comparisons and storage, instead of the human-readable dotted format.
What does the binary format tell me?
It shows exactly which bits are set, which is useful for understanding subnet masks and manually verifying subnet calculations bit by bit.
Why dotted-decimal is a human convenience, not how computers store the address
An IPv4 address is, underneath the familiar dotted notation, just a single 32-bit unsigned integer — the four-number, dot-separated format most people recognize is purely a human-readability layer added on top of that raw number, splitting it into four 8-bit bytes because reading four small numbers is easier than reading one large one. Networking equipment, routing tables, and low-level code frequently work with the raw 32-bit integer directly rather than the dotted string, which is exactly why this converter's decimal, binary, and hex outputs aren't just alternate formats for display — they're closer to how the address is actually represented and processed at the protocol level.
Why the same address can appear in surprising alternate decimal forms
Because an IPv4 address is fundamentally one 32-bit number, most operating systems and browsers will actually accept and correctly interpret unusual, non-standard-looking numeric forms of an address — a full 32-bit decimal integer typed directly (like http://3232235777), or even a mix of fewer than four dot-separated numbers, can resolve to a valid IP address in many contexts. This isn't just a curiosity: it's a real, historically used obfuscation technique, where a malicious link disguises a suspicious IP address as an unfamiliar-looking large number specifically so it doesn't visually register as an IP address to someone glancing at a link before clicking it. Recognizing that a large, unfamiliar number in a URL could be an obfuscated IP address is a genuinely useful piece of security awareness.
IPv4-mapped IPv6 addresses are one specific coexistence mechanism, not the only one
The ::ffff:a.b.c.d format this tool generates is a specific, standardized way to represent an IPv4 address as an IPv6 address, used mainly so that software built around IPv6 sockets can still communicate with IPv4-only endpoints without needing entirely separate code paths for each address family. It's worth knowing this is just one of several distinct IPv4/IPv6 coexistence mechanisms that have existed at different points during the ongoing, decades-long transition between the two standards — NAT64 and 6to4 tunneling, for instance, solve related but different interoperability problems using different techniques. IPv4-mapped addresses specifically address dual-stack software compatibility, not network-level translation or tunneling.
Why hex representation matters for low-level network work
Hexadecimal shows up constantly in contexts one level below typical network configuration — raw packet captures (the kind this site's TCP capture viewer displays), certain firewall and access control list configurations on specific hardware, and low-level debugging output all frequently represent addresses in hex rather than dotted decimal, since hex maps cleanly onto the underlying bytes without the arithmetic conversion dotted decimal requires. Being able to quickly convert between the dotted address you recognize and its hex representation is a practical skill specifically for reading raw packet data or vendor-specific configuration syntax that expects addresses in that format.
Limitations of this tool
This converter translates a single IPv4 address between decimal, binary, hexadecimal, and IPv6-mapped notation — it doesn't perform any subnet or CIDR range math (this site's separate IPv4 Subnet Calculator handles that), doesn't validate whether an address is actually reachable or properly routed anywhere, and only generates the IPv4-mapped IPv6 representation of an IPv4 address rather than working with native IPv6 addresses directly. Use it for straightforward format conversion and understanding how one specific address is represented across these notations, not as a subnetting or network diagnostic tool.