🌐 IPv4 to IPv6 Converter

IPv4 Address Input

Example IPv4 Addresses

{{ example.ip }} {{ example.description }}

IPv4 Address Information

Address: {{ result.originalIPv4 }}
Class: {{ result.info.addressClass }}
Type: {{ result.info.type }}
{{ result.info.description }}

IPv6 Representations

IPv4-mapped IPv6 (Recommended)
{{ result.ipv4Mapped }}
IPv4-mapped IPv6 (Dotted Notation)
{{ result.ipv4MappedDotted }}
IPv4-mapped IPv6 (Expanded)
{{ result.ipv4MappedExpanded }}
IPv4-compatible IPv6 (Deprecated)
{{ result.ipv4Compatible }}
6to4 Tunnel Address
{{ result.sixToFour }}
6to4 Tunnel: Not applicable for private/loopback addresses

Technical Details

Hexadecimal: {{ result.hexadecimal }}
Binary: {{ result.binary }}
🌐

Enter an IPv4 address to see its IPv6 representations

⚠️

ℹ️ About IPv4 to IPv6 Converter

Convert a dotted-decimal IPv4 address into the IPv6 forms commonly seen in dual-stack logs, socket APIs, migration notes, and legacy transition plans. The converter shows the original 32-bit IPv4 value as an IPv4-mapped IPv6 address, a deprecated IPv4-compatible form, and a 6to4 prefix when the source address is suitable for that legacy format.

Formats this converter shows

  • IPv4-mapped IPv6: ::ffff:192.0.2.33 or the expanded 0000:0000:0000:0000:0000:ffff:c000:0221 form. This is the useful representation for IPv4 traffic handled by IPv6-aware software.
  • IPv4-compatible IPv6: ::192.0.2.33. This historic syntax is deprecated; keep it for reading older documentation or configuration examples, not for new designs.
  • 6to4 prefix: a public IPv4 address can be embedded after 2002:, such as 198.51.100.14 becoming 2002:c633:640e::/48.
  • Hex and binary: the same IPv4 address is also shown as raw hexadecimal and bit-level output for firewall rules, packet analysis, and debugging.

Practical uses

  • Check how an IPv4 address appears in IPv6 socket logs, access logs, ACLs, or SIEM queries.
  • Prepare migration notes for applications that accept IPv4-mapped IPv6 addresses.
  • Compare dotted notation with fully expanded hexadecimal notation when troubleshooting parser behavior.
  • Document legacy 6to4 examples without hand-converting the IPv4 octets to hexadecimal.

Limitations to keep in mind

  • This is address representation, not packet translation. It does not configure NAT64, DNS64, tunnels, routes, or AAAA records.
  • Private, loopback, link-local, multicast, and other non-public IPv4 ranges are not valid 6to4 deployment sources even though they can still be written as IPv4-mapped IPv6 addresses.
  • 6to4 is a legacy transition mechanism. Modern IPv6 deployments should prefer native IPv6, managed tunnels, or documented translation architectures instead of relying on automatic 6to4 relays.
  • Examples use documentation IPv4 ranges so they are safe to copy into notes without referencing a live host.

Standards and source references

  • RFC 791 defines IPv4, while RFC 8200 defines the current IPv6 protocol specification.
  • RFC 4291 covers IPv6 text notation and IPv6 addresses with embedded IPv4 addresses.
  • RFC 3056 defines 6to4 addressing; RFC 7526 deprecates the 6to4 anycast relay-router prefix.
  • RFC 1918 documents private IPv4 ranges, RFC 5737 reserves IPv4 example blocks, and RFC 6052 describes IPv4/IPv6 translator prefixes such as 64:ff9b::/96.

API Usage Example:

POST /api/tools/networking/ipv4-to-ipv6
Content-Type: application/json

{
    "ipv4": "192.168.1.1"
}
Ready