IPv4 to IPv6 Converter Online — Free Tool to Convert IPv4 Addresses to IPv6

CodexFuse Team · 2026-10-31T15:54:19.325Z · 10 min read min read

Convert any IPv4 address to its IPv6-mapped, 6to4, and hex forms instantly with CodexFuse's free IPv4 to IPv6 converter — worked example included.

An IPv4 to IPv6 converter turns a familiar 32-bit IPv4 address, such as 203.0.113.45, into its IPv6 forms — most usefully the IPv6-mapped form ::ffff:203.0.113.45 — so dual-stack software, firewall rules, and migration documents can refer to the same host in IPv6 notation. It does not create a new address or change how packets route; it rewrites the same host identifier into IPv6 syntax.

If you are documenting a migration, configuring a dual-stack server, or simply trying to read an IPv6 log line that contains an old IPv4 host, that translation is the missing step. The rest of this guide shows exactly how the conversion works, walks through a real example end to end, and explains where the converted forms are useful — and where they are not.

How does an IPv4 address become an IPv6 address?

An IPv4 address becomes an IPv6 address by embedding its 32 bits inside a 128-bit IPv6 address, most commonly as an IPv6-mapped address in the form ::ffff: followed by the original IPv4 address. The first 80 bits are zero, the next 16 bits are all ones (ffff), and the final 32 bits are the IPv4 address itself, so ::ffff:203.0.113.45 is the same host as 203.0.113.45, written in IPv6 notation.

That construction matters because it is lossless and reversible for this one form. Nothing is guessed, rounded, or assigned: the four IPv4 octets are carried verbatim into the last 32 bits. Two other forms sometimes appear alongside it, and they are worth distinguishing before you use any of them.

The three forms you will see

• Mapped form (::ffff:): the safe, standard way to represent an IPv4 host on an IPv6 socket. Use this one for new work.
• 6to4 form (2002:): an older tunnelling notation that prefixes the IPv4 address in hex with 2002::/16. It was deprecated by RFC 7526 in 2015 and should not be used for new deployments.
• Hex form (::ffff:xxxx:xxxx): the same mapped address with the IPv4 octets written as two hexadecimal groups instead of dotted decimal. It is identical in meaning to the dotted mapped form.

The hex step itself is simple arithmetic. Each IPv4 octet becomes two hexadecimal digits: 203 becomes cb, 0 becomes 00, 113 becomes 71, and 45 becomes 2d. That is why 203.0.113.45 converts to ::ffff:cb00:712d in hex and to 2002:cb00:712d:: in 6to4 notation.

How do you use the CodexFuse IPv4 to IPv6 converter?

You use the CodexFuse IPv4 to IPv6 converter by entering an IPv4 address and clicking Convert, which instantly shows the mapped, 6to4, and hex forms side by side. The tool opens with 192.168.1.1 already entered, accepts any valid IPv4 address of four octets from 0 to 255, and lets you copy the mapped address with one click — all in your browser, with nothing to install.

The walkthrough below uses a worked example rather than the default address, so you can check every step yourself.

Worked example: converting a branch-office gateway

The scenario: A small logistics company runs a branch office behind a gateway at 203.0.113.45. Its new inventory system runs on a dual-stack server, and the migration document must list every gateway in IPv6 notation so the server team and the network team are reading the same list.

Step 1 — Enter the address: The network administrator opens the IPv4 to IPv6 converter and replaces the default with 203.0.113.45.

Step 2 — Convert: One click on Convert produces three outputs at once, with no separate step for each form.

Step 3 — Copy and paste: The administrator copies the mapped form, ::ffff:203.0.113.45, into the migration document and into the server's allowlist. Because the mapped form carries the original address verbatim, either team can recover 203.0.113.45 from it later without a lookup table.

Step 4 — Verify the reverse: As a sanity check, the team confirms the last 32 bits decode back to the gateway: cb is 203, 00 is 0, 71 is 113, and 2d is 45. If any octet mismatches, the address was mistyped — the tool's strict validation (four octets, each 0–255) catches entries such as 256, a missing octet, or letters with an "Enter a valid IPv4 address" message.

The outcome: The migration list is consistent, the allowlist matches the gateway, and nobody had to hand-convert hex under time pressure. Total time: under a minute, versus a manual conversion that invites exactly the kind of single-digit error that blocks a cutover.

When should you convert IPv4 to IPv6, and when should you not?

You should convert IPv4 to IPv6 when you need to represent an existing IPv4 host inside IPv6-only contexts: dual-stack application code, IPv6 socket APIs, firewall rules written in IPv6 notation, and migration inventories. In those places the mapped form is the correct, standard bridge between the two address families.

You should not convert when you actually need a new, native IPv6 address. A mapped address is not an IPv6 allocation, it does not come from your ISP's IPv6 block, and it will not give an IPv4-only host IPv6 connectivity. If your goal is to obtain real IPv6 addresses for servers or users, that is a provisioning task with your hosting provider or ISP — not a notation conversion.

Similarly, do not use the 6to4 form for anything new. It survives in the tool because legacy documents still contain it and engineers still need to read those documents, but RFC 7526 deprecated 6to4 in 2015, and modern networks should not rely on it.

Common mistakes to avoid

• Treating a mapped address as a new host: ::ffff:203.0.113.45 and 203.0.113.45 are the same host, not two machines. Counting both in an inventory double-counts.
• Copying the 6to4 form into new firewall rules: rules written against 2002: addresses will not match traffic arriving on the mapped form, and vice versa.
• Assuming private addresses behave differently: private addresses convert exactly like public ones. The tool converts 192.168.1.1 to ::ffff:192.168.1.1 and ::ffff:c0a8:0101 without any special handling, because the conversion is pure notation.
• Expecting a reverse conversion: there is no universal way to squeeze an arbitrary IPv6 address into IPv4. Only a mapped address contains an IPv4 address to recover.

How does this fit a wider network migration?

A notation converter is one small tool in a larger migration, and it helps most when paired with the checks around it. Before a cutover, verify the address you are converting is the right host, check its range and neighbours, and confirm it is not on a blocklist that would break the new service.

For those surrounding checks, CodexFuse's free network tools cover the same workflow: use the IP address lookup to confirm an address's version, class, and type before you convert it, the IP range calculator to turn a CIDR block into its full usable range, and the IP to binary converter when you need to see the same address at bit level for subnetting work. If a converted host will face the public internet, run it through the IP blacklist checker first — a clean conversion of a blocklisted address still will not deliver mail or pass reputation checks.

What are the honest limits of an IPv4 to IPv6 converter?

An IPv4 to IPv6 converter only rewrites notation; it cannot allocate IPv6 addresses, test connectivity, or migrate a network. It will not tell you whether an address is reachable, whether your ISP has assigned you an IPv6 prefix, or whether your firewall permits IPv6 traffic — those need live network checks, not arithmetic.

It also only converts in one direction. If you paste an IPv6 address into the IPv4 to IPv6 converter, it cannot produce an IPv4 equivalent, because 128 bits cannot fit into 32. The single exception is a mapped address, whose last 32 bits already are the IPv4 address — for example, ::ffff:8.8.8.8 contains 8.8.8.8, and ::ffff:0808:0808 is the same value in hex.

Finally, remember that the tool runs entirely in your browser and validates strictly. That is a strength for quick conversions — no account, no install, no waiting — but it also means there is no saved history and no bulk mode: large migration lists still need to be converted one address at a time, or scripted with your own tooling.

Frequently Asked Questions

What is an IPv4 to IPv6 converter?

An IPv4 to IPv6 converter is a free online tool that rewrites an IPv4 address into IPv6 notation, typically as an IPv6-mapped address such as ::ffff:203.0.113.45. It changes the notation, not the host, and it is used for dual-stack software, firewall rules, and migration documents.

How do I convert an IPv4 address to IPv6?

Enter the IPv4 address into the converter and click Convert. For 192.168.1.1 the tool shows the mapped form ::ffff:192.168.1.1, the 6to4 form 2002:c0a8:0101::, and the hex form ::ffff:c0a8:0101, and you can copy the mapped address with one click.

What is the difference between the mapped form and 6to4?

The mapped form (::ffff:) is the standard way to represent an IPv4 host on an IPv6 socket and is safe for new work. The 6to4 form (2002:) is an older tunnelling notation deprecated by RFC 7526 in 2015; it remains useful only for reading legacy documents.

Can I convert an IPv6 address back to IPv4?

No, there is no universal conversion back, because IPv6 addresses are 128 bits and IPv4 addresses are only 32 bits. The one exception is a mapped address: ::ffff:8.8.8.8 literally contains 8.8.8.8 in its final 32 bits.

Do private IPv4 addresses convert differently?

No. Private addresses convert exactly like public ones, because the conversion is pure notation. The tool converts 192.168.1.1 to ::ffff:192.168.1.1 just as it converts 8.8.8.8 to ::ffff:8.8.8.8.

Does converting an address give my server IPv6 connectivity?

No. Conversion only rewrites the label; real IPv6 connectivity still requires a dual-stack interface, an IPv6 route, and firewall rules that permit IPv6 traffic. If you need native IPv6 addresses, arrange them with your hosting provider or ISP.

Move the whole stack, not just the notation

Converting one address takes seconds. Running the infrastructure behind it — hosting that stays patched, business email that delivers, security that watches, backups that restore — takes constant attention when it is spread across vendors. That is the work CodexFuse takes off your plate: move your hosting, email, security, and backups to one fully managed platform on pay-as-you-go credits, with no subscriptions and no lock-in, and stop maintaining the plumbing yourself. Open CodexFuse, add credits, and migrate your first service today — the converter above stays free for the next address on your list.