IPv4 to IPv6 Converter

The transition from IPv4 to IPv6 is one of the longest-running infrastructure migrations in internet history. Even though IPv6 was introduced in 1998, IPv4 addresses still dominate everyday traffic, which means networking professionals routinely need to express the same address in both formats. An IPv4 to IPv6 converter translates a 32-bit IPv4 address into the 128-bit IPv6 representations that dual-stack systems, tunneling protocols, and mixed-environment logs expect to see. Whether you are debugging a connection, reading server logs that suddenly show ::ffff: prefixes, or planning a migration, knowing how to convert between the two formats is a foundational networking skill. For background on why the transition is happening at all, see our companion article on IPv4 vs. IPv6.

Understanding IPv4-Mapped IPv6 Addresses

The most common conversion you will encounter is the IPv4-mapped IPv6 address, defined in RFC 4291. The format embeds a full IPv4 address inside an IPv6 address by prefixing it with ::ffff: — for example, 192.0.2.1 becomes ::ffff:192.0.2.1. This format exists specifically so that IPv6-only software can still communicate with IPv4 endpoints when the underlying network is dual-stack. When a Linux server logs a connection from an IPv4 client on a socket bound to IPv6, the source address often appears in this mapped form. Recognizing it as “really just an IPv4 address” is the difference between a confused engineer and a productive debugging session.

6to4 Tunneling and Address Embedding

Another conversion you may need is the 6to4 prefix, which embeds an IPv4 address inside the special 2002::/16 IPv6 range. The format is 2002:XXXX:YYYY::/48 where XXXX:YYYY is the IPv4 address rewritten as two 16-bit hex groups. So 192.0.2.1 (hex c000:0201) becomes 2002:c000:0201::/48. This prefix was historically used to allow IPv6 packets to traverse an IPv4-only network by encapsulating them. Native IPv6 connectivity has largely replaced this tunneling approach today, but you will still see 6to4 addresses in older configurations and archived documentation. The tool above generates the correct prefix automatically so you can verify what range a 6to4 tunnel allocates.

The Hex Math Behind the Conversion

Converting an IPv4 address to its hex representation is straightforward once you understand that an IPv4 octet is just an 8-bit number. Each octet (0 to 255) corresponds to exactly two hex digits (00 to FF). The address 192.0.2.1 works out to:

• 192 → c0
• 0 → 00
• 2 → 02
• 1 → 01

Grouped as 16-bit blocks (which is how IPv6 is structured), this becomes c000:0201. That is the same 32 bits, written in two different formats. The IPv4-mapped IPv6 form simply pads this with the ::ffff: prefix, while the 6to4 form drops it inside the 2002::/16 allocation. If you want to see the same conversion happen in binary, our IP Binary Converter shows the bit-level breakdown.

When You’ll See These Conversions

There are several practical scenarios where an IPv4 to IPv6 converter is useful:

• Reading dual-stack logs: Servers running on IPv6 sockets often record IPv4 client connections in the mapped ::ffff: format. Knowing how to read these saves time when investigating incidents.
• Configuring firewalls: Modern firewalls and access control lists frequently need both IPv4 and IPv6 rules. Converting addresses up front avoids inconsistent rule sets.
• Planning IPv6 migrations: When mapping out an IPv4 to IPv6 transition, knowing the canonical IPv6 representation of each existing IPv4 allocation is the first step toward parallel addressing.
• Working with cloud and CDN providers: Some providers expose interfaces that accept either format. Converting between them lets you confirm the same endpoint is being referenced in dashboards, logs, and API responses.

Related Tools & Resources

Use this converter alongside our other free networking tools: inspect domain records with the DNS lookup, identify hardware via the MAC Address Lookup, or calculate prefix details with the Subnet Calculator. For deeper background, our guides on public vs. private IP addresses and IP address formats provide additional context for the conversion math.