Convert IPv4 addresses to IPv6 mapped and compatible formats with detailed notation breakdown.
Starting with one dotted-decimal IPv4 address, this converter produces its IPv4-mapped and IPv4-compatible IPv6 representations. It translates the four octets into the final 32 bits, then shows how the mapped and compatible prefixes change the complete 128-bit address. The important distinction is that this is an address representation conversion, not an allocation of native IPv6 service. The compatible form is also a deprecated transition format, while mapped addresses remain useful when software represents an IPv4 node in an IPv6-sized address field.
A concrete input and expected output from the current implementation.
Input
192.0.2.1
Expected output
IPv4-mapped: ::ffff:192.0.2.1 (hex: ::ffff:c000:201) IPv4-compatible: ::192.0.2.1 (hex: ::c000:201)
The octets 192, 0, 2, and 1 become the hexadecimal bytes c0, 00, 02, and 01, forming the hextets c000:0201. IPv6 text may omit the leading zero in 0201, producing c000:201.
Each IPv4 octet represents one 8-bit value. Converting the four octets to hexadecimal produces four bytes, which combine into the last two 16-bit IPv6 groups. For 192.0.2.1, c0 00 and 02 01 become c000 and 0201. IPv6 leading-zero suppression permits the second group to appear as 201.
The mapped form places 80 zero bits and 16 one bits before the IPv4 value, yielding a prefix displayed as ::ffff:. The compatible form places 96 zero bits before that value, yielding :: followed directly by the embedded IPv4 portion. Mixed dotted-decimal and all-hexadecimal spellings can represent the same underlying 128 bits.
No. Embedding an IPv4 value in either notation does not assign an IPv6 address, publish an IPv6 route, or make an IPv4-only service reachable over IPv6. An IPv4-mapped address is principally a representation of an IPv4 node within IPv6 address syntax. Native IPv6 connectivity requires an independently assigned and routed IPv6 address.
Use the mapped result only where the receiving software or data format specifically expects an IPv4-mapped IPv6 address. The IPv4-compatible form was created for earlier transition mechanisms and is deprecated by the IPv6 addressing architecture. It may still be useful for interpreting legacy data, but it is not a general replacement for the mapped form.
The example and behavioral notes were checked against the browser implementation. Standards and primary references below define the relevant format, formula, or platform behavior.
Format, validate, and beautify JSON with syntax highlighting and error detection.
Encode text or files to Base64 and decode Base64 strings back to their original form.
Format and indent SQL queries for better readability across all major dialects.
Convert HTML markup into clean Markdown syntax with support for tables and lists.
Write Markdown and see the rendered HTML output in real time with live preview.
Visualize unified diffs and patch files with color-coded additions and deletions.