Expanded hextets
Compressed input such as 2001:db8::1 is expanded into eight four-digit hextets before binary conversion.
Input Rules
Enter a full or compressed IPv6 address. The converter expands :: notation, normalizes leading zeroes, and accepts IPv4-mapped suffixes such as ::ffff:192.0.2.128.
Hextets
0
Bit Count
0
Compressed
-
IPv4 Suffix
-
Validation
Binary Groups
-
Expanded IPv6
-
Compressed Input
-
Continuous Binary
-
Hextet Breakdown
| # | Hextet | Decimal | Binary |
|---|---|---|---|
| No conversion yet. | |||
Report
-
IPv6 conversion
This IPv6 to Binary converter expands a full or compressed IPv6 address into eight hextets, then converts each 16-bit hextet into grouped binary and one continuous 128-bit value. It helps developers, DevOps engineers, network students, QA teams and support staff inspect zero compression, leading zeroes and hextet boundaries before reading protocol notes, subnet examples or packet-level output. The conversion runs locally, accepts valid IPv6 notation including IPv4-mapped suffixes, and shows expanded IPv6, grouped binary, continuous binary and a hextet-by-hextet breakdown.
Compressed input such as 2001:db8::1 is expanded into eight four-digit hextets before binary conversion.
Review colon-separated 16-bit binary groups for readability, or copy the continuous 128-bit value when a single binary string is needed.
The parser checks hextet count, invalid characters, duplicate :: markers, empty hextets and malformed IPv4-mapped suffixes.
2001:db8::8a2e:370:7334.See how eight 16-bit hextets form one 128-bit IPv6 address, especially when learning zero compression and leading-zero normalization.
Use the grouped bits to reason about prefix boundaries in documentation. This page does not calculate IPv6 subnet ranges.
Compare expanded hextets and binary groups with packet captures, protocol examples or low-level implementation notes.
Use IP to Binary for dotted IPv4 addresses and this page for 128-bit IPv6 notation.
Use an IPv6 address with eight hextets or one valid :: compression marker. Hex digits, colons and an optional IPv4-mapped suffix are accepted.
2001:db8::1 expands to 2001:0db8:0000:0000:0000:0000:0000:0001, then becomes eight 16-bit binary groups.
More than one ::, empty hextets without compression, too many groups, invalid hex characters or malformed IPv4 suffixes are rejected.
This page performs local IPv6 numeric representation only. It does not convert plain IPv4 addresses, calculate IPv6 subnet ranges, resolve hostnames, run DNS lookups, check ownership, geolocate addresses, ping hosts, scan ports or confirm uptime. IPv4-mapped suffixes are normalized only when they appear inside valid IPv6 notation. Because the conversion runs in browser JavaScript, the address does not need to be sent to a server to produce expanded hextets, grouped binary or continuous 128-bit output.
It accepts one IPv6 address in full or compressed notation. The address must expand to eight 16-bit hextets, and only one :: compression marker is allowed.
Expanded output shows all eight IPv6 hextets with four hexadecimal digits each, so compressed zero groups and leading zeroes are visible before binary conversion.
Grouped binary shows each IPv6 hextet as a 16-bit binary group separated by colons. This keeps the result aligned with the eight hextets of the original address.
Continuous output joins all eight 16-bit groups into one 128-bit value. It is useful for education, protocol notes and manual subnet reasoning, but this page does not calculate IPv6 subnets.
No. It is an IPv6 converter. It can normalize an IPv4-mapped suffix inside IPv6 notation, but plain IPv4 addresses belong in the IPv4 binary converter.
No. The conversion runs locally in your browser. It does not perform DNS lookup, geolocation, ownership lookup, ping, port checks or uptime testing.