Calculate the network prefix of an IPv6 address
An IPv6 address plus a prefix length defines which leading bits belong to the network. This calculator keeps the prefix bits, clears the remaining host/interface bits, and returns the normalized network in both compressed and expanded notation.
For example, 2001:db8:1234:5678::abcd/64 belongs to 2001:db8:1234:5678::/64. Review the IPv6 guide if you want a broader explanation of prefix planning and address types.
How to use the IPv6 prefix calculator
Enter a valid IPv6 address and a prefix length from 0 through 128. Press Calculate prefix and the tool applies the bit boundary directly to the 128-bit value. The result is shown in compact form for normal documentation and expanded form for detailed inspection.
If your source address is difficult to read, normalize it first with the IPv6 compress/expand tool.
Example: calculating a /64
With 2001:db8:1234:5678:abcd:ef01:2345:6789/64, the first four 16-bit groups are inside the prefix and the remaining 64 bits are cleared. The resulting network is 2001:db8:1234:5678::/64.
The same operation works at nibble-aligned and non-nibble-aligned boundaries because the calculator works on the underlying bits, not on textual group boundaries.
Prefix length versus IPv4 subnet masks
IPv4 often expresses the same boundary as either CIDR or dotted decimal, such as /24 and 255.255.255.0. IPv6 almost always uses prefix length directly. A /48 fixes 48 leading bits, a /56 fixes 56, and a /64 fixes 64.
The prefix length describes a bit boundary; it does not imply a particular topology, VLAN count or host-allocation policy by itself.
Why /64 is common but not universal
/64 is the standard size for many IPv6 LAN segments and is especially important for mechanisms such as SLAAC. However, larger allocation boundaries such as /48 or /56 are commonly delegated so they can be subdivided into many /64 networks. Other prefix lengths also exist for specific operational purposes.
Use the IPv6 subnet calculator when you need to divide a larger allocation into child prefixes rather than calculate only one network boundary.
Expanded output and bit verification
The expanded result can be useful when the prefix ends inside a hexadecimal group. Because every group is shown with four digits, you can see exactly where zeros begin after the network boundary. The compressed result is usually preferable for configuration and documentation.
Both outputs represent the same network value and are generated from the same 128-bit calculation.
A normalized prefix is particularly useful when comparing routing entries, documenting delegated space or checking whether two addresses are intended to sit inside the same network. The calculator does not infer routing policy or subnet purpose; it only applies the bit boundary you provide. That separation is deliberate: the mathematical network address should be predictable, while design decisions such as which VLAN or site receives the prefix remain part of your addressing plan.
Frequently asked questions
What prefix lengths are accepted?
Any integer from /0 through /128.
Does the calculator assign host addresses?
No. It only normalizes the network portion for the address and prefix you provide.
Is every IPv6 LAN required to use /64?
/64 is the normal choice for many LANs and SLAAC, but IPv6 also uses other prefix lengths for allocations and specialized links.
Can I enter a compressed IPv6 address?
Yes. The parser accepts normal compressed notation and calculates the same network as the expanded form.
Next step
Use this calculator to normalize one prefix, then move to IPv6 subnet planning when you need to derive many child networks from a delegated block.