IPv4 to IPv6 Converter
IPv4 to IPv6 Converter. Enter an IPv4 Address and click Convert to IPv6 in this IPv4 to IPv6 converter to get its mapped, compatible and 6to4 forms.
Input IPv4 Address
IPv6 Representations
IPv6 Address Format Types
| Type | Format | Usage |
|---|---|---|
| IPv4-Mapped | ::ffff:a.b.c.d | Dual-stack applications |
| 6to4 | 2002:xxyy:zzww::/48 | Automatic tunneling |
| IPv4-Compatible | ::a.b.c.d | Deprecated (RFC 4291) |
Enter any IPv4 address to instantly convert it into multiple IPv6 representations including IPv4-mapped, IPv4-compatible, and 6to4 tunnel formats. Get ready-to-use IPv6 addresses with full expanded and compressed forms — essential for dual-stack migration and transition planning.
An IPv4 to IPv6 Converter takes any IPv4 host you already know and reshapes it into valid IPv6 notation in a single step, giving you instant, dual-format results without doing the hexadecimal math by hand. Whether you're testing a dual-stack network, documenting a migration plan, or just curious what your host looks like under the newer standard, converting between the two formats takes seconds once you understand the notations involved. This guide walks through how the conversion works, why it matters, and how to read the output.
How to Convert an IPv4 to IPv6 Address
An IPv4 to IPv6 conversion is a matter of translating four decimal octets into their hexadecimal equivalents and slotting them into one of two accepted formats. Enter any valid address in dotted-decimal form into the tool above, and it will turn your IPv4 input into both 6to4 notation and IPv4-mapped notation automatically, showing you the expanded and shortened forms side by side. Behind the scenes, the tool splits that value into its four octets, converts each one from decimal to hex, and pairs the results into the two-byte groups IPv6 addressing expects.
- Split the IPv4 address into its four decimal octets (for example, 192.168.1.1 becomes 192, 168, 1, and 1).
- Convert each octet to a two-digit hex value (192 → c0, 168 → a8, 1 → 01, 1 → 01).
- Group the hex pairs into two four-character blocks (c0a8 and 0101).
- Insert the blocks into either the 6to4 template or the IPv4-mapped template to get the final result.
Reading the IPv6 Expanded Form
Expanded form writes out all eight groups of the 128-bit result in full, with no shortcuts. For 192.168.1.1, the fully expanded IPv4-mapped output reads:
$$0000:0000:0000:0000:0000:\text{ffff}:c0a8:0101$$
Expanded form is useful when you need an unambiguous, copy-paste-safe value for configuration files, firewall rules, or documentation where shorthand could be misread.
Reading the IPv6 Shortened Form
Shortened form (sometimes called IPv6 compressed form) collapses consecutive groups of zeroes into a double colon (::), used at most once per result. The same value above compresses to ::ffff:c0a8:0101, or equivalently ::ffff:192.168.1.1 using the dotted-decimal shortcut for the final 32 bits. Most operating systems and routers display results this way by default, so it's worth recognizing both representations.
Why Use an IPv4 to IPv6 Converter?
As the IPv6 rollout continues, network engineers, sysadmins, and hobbyists all run into situations where an IPv4 host needs to be represented on an IPv6 network, or vice versa. Manually working out hex from decimal octets and assembling the correct format is tedious and error-prone, and a single transposed digit can point traffic at the wrong host. An online lookup tool removes that risk, and it's also a fast way to sanity-check output from scripts, firewall configs, or CGNAT logs that mix formats.
IPv4 Exhaustion and the Push Toward IPv6 Migration
IPv4 exhaustion is the underlying reason this conversion exists at all: the 32-bit space caps out at roughly 4.3 billion unique addresses, and that supply has been effectively depleted for years given the number of connected devices in use today. IPv6 migration solves the scarcity problem outright, offering a 128-bit space large enough that running out isn't a realistic concern again. But because IPv6 isn't backward compatible with IPv4 at the protocol level, most networks run both stacks side by side during the transition, which is exactly where this kind of conversion becomes a practical, everyday need rather than a theoretical exercise.
IPv4 to IPv6 Translation: 6to4 Notation Explained
There are two distinct transition mechanisms behind this translation process, and they solve different problems, so the tool above generates both from the same input.
IPv4-Mapped Notation vs 6to4 Notation
6to4 notation is designed for tunnelling: it lets an IPv6 packet carry an embedded IPv4 payload so that traffic between hosts can cross an IPv4-only network segment. It always starts with the fixed prefix 2002::/16, followed by the hex-encoded value. IPv4-mapped notation solves the opposite problem — representing an IPv4-only host inside an IPv6 space on a dual-stack network — and always starts with 80 zero bits followed by ffff, per the formula below:
$$\text{IPv4-mapped} = \texttt{::ffff:} \; (w.x.y.z)_{16}$$
For 192.168.1.1, that formula resolves to 2002:c0a8:0101:: in 6to4 form and ::ffff:c0a8:0101 in IPv4-mapped form — two different results built from the same source, each valid for a different transition mechanism.
IPv4 to IPv6 Mapping: IPv4-Mapped Address Format Explained
The IPv4-mapped format exists specifically so that dual-stack systems, which run both protocols simultaneously, can represent an IPv4-only endpoint using pure IPv6 syntax. Sockets, routing tables, and logging tools that only understand IPv6 addressing can still reference that host this way, without needing a separate code path for legacy traffic.
NAT64 and Dual-Stack Networks
On networks that aren't fully dual-stack, NAT64 does the same job at the network layer instead of the application layer: it's a stateful translation service that lets IPv6-only clients reach IPv4-only destinations by mapping through a dedicated prefix, typically paired with DNS64 to synthesize the necessary records automatically. Full dual-stack deployment avoids needing that translation layer at all, since both protocol stacks are already reachable natively, but it costs more in management overhead — which is why most large networks run a mix of dual-stack, NAT64, and IPv4-mapped addressing depending on the segment.
IPv4 vs IPv6: Understanding the IP Address Converter Results
Once you have a result in hand, it helps to know what actually changed and why. The two protocols differ in far more than length — everything from header structure to how fragmentation is handled shifts between them.
IPv4 vs IPv6 Format Comparison
| Feature | IPv4 | IPv6 |
|---|---|---|
| Length | 32-bit | 128-bit |
| Notation | Decimal, dot-separated (192.168.1.1) | Hexadecimal, colon-separated (::ffff:c0a8:0101) |
| Total unique values | ~4.3 billion | ~340 undecillion |
| Header size | 20–60 bytes | Fixed 40 bytes |
| Checksum field | Present | Removed (handled at other layers) |
| Fragmentation | Sender and routers | Sender only |
| Configuration | Manual or DHCP | Auto-configuration or DHCPv6 |
| NAT requirement | Common, due to scarcity | Generally unnecessary |
Internet Protocol Basics: IPv4 vs IPv6
Internet Protocol is the routing layer that every device on a network relies on to send and receive data, and IPv4 and IPv6 are simply two versions of that same underlying standard. An IPv4 host like 8.8.8.8 is identified using four decimal octets; the equivalent IPv6 representation of that same conceptual host uses eight hexadecimal groups instead, carrying far more information and leaving room for internet connectivity to keep scaling for decades. Neither format is inherently "better" for a given task — they're complementary notations for the same identification problem, and converting between them is what keeps IPv4-only and IPv6-only systems able to communicate during the long transition period.
Where This Conversion Fits Into Broader Networking
Address translation rarely happens in isolation — it's one piece of how modern networking infrastructure keeps IPv4 and IPv6 traffic interoperable across cloud networking platforms, VPN tunnels, and IoT deployments that now outnumber traditional endpoints many times over. A cloud provider spinning up new public-facing infrastructure today typically assigns each host both an IPv4 address and an IPv6 address, and a VPN gateway bridging a legacy office network to a modern cloud environment often needs exactly the kind of translation between hosts that this tool performs. Cybersecurity and network security teams care about this too: firewall rules, intrusion-detection systems inspecting packets, and access-control lists all need to recognize a host under both notations, or traffic can slip past a filter that only supports one address family.
- Dual-stack cloud infrastructure that must expose the same host on both protocols
- VPN and gateway configurations bridging IPv4-only and IPv6-only segments
- IoT fleets that rely on IPv6's larger address space as device counts grow
- Network security tooling that inspects traffic and packets across both formats
- Documentation and support tickets that need an unambiguous, valid address on record
Subnetting Basics: CIDR and Subnet Calculators
Once you've converted a host, the next step for most network engineers is figuring out where it sits within a subnet. IPv4 and IPv6 both use CIDR notation to define a network's size — for example /24 on an IPv4 network or /64 on an IPv6 network — and a dedicated subnet calculator can work out the resulting range once you know the base address and prefix length. Public addresses, private ranges, and the gateway address for a segment all follow directly from that CIDR value, whichever protocol version you're working in.
Understanding both notations pays off well beyond a single lookup: it makes firewall rules, DNS records, and CGNAT logs readable regardless of which stack generated them, and it means an IPv4 to IPv6 converter becomes less of a novelty and more of an everyday utility for anyone who touches network infrastructure.
Related Network Tools
Explore these related tools for subnet calculation and IP address management.
Additional networking calculators for IP address planning and network analysis.
Comments & Feedback
Share your experience or ask questions about this tool