IPv6 Netmask & Subnet Calculator
Enter an IPv6 prefix length to calculate the netmask. Add an IPv6 address to calculate the network range for that subnet.
Supports compressed addresses (::), full notation, and IPv4-mapped endings (example: ::ffff:192.168.1.10).
What is an IPv6 netmask?
In IPv6, we usually describe subnets with a prefix length such as /64, /56, or /48. While people still say “netmask,” IPv6 networking uses prefix notation much more often than dotted masks used in IPv4.
A prefix length tells you how many bits are fixed as the network portion. IPv6 addresses are 128 bits total, so the remaining bits are host/interface bits.
- /64 means 64 network bits + 64 host bits.
- /48 means 48 network bits + 80 host bits.
- /128 means a single host address (all bits fixed).
How this IPv6 calculator helps
This calculator gives practical values you often need during network planning, troubleshooting, and documentation:
- Expanded and compressed IPv6 netmask from prefix length
- Normalized form of the input IPv6 address
- Calculated network address for a given address and prefix
- Last address in the subnet range
- Total number of addresses in that subnet
If you provide only a prefix (without an address), it still calculates the netmask and subnet size.
Quick IPv6 subnet examples
/64 (most common LAN subnet)
A /64 is the standard for most end-user or server LAN segments. It leaves 64 bits for interface identifiers, which is important for SLAAC and other standard IPv6 behaviors.
/56 (typical ISP delegation)
Many ISPs delegate a /56 to residential customers. That gives 256 separate /64 subnets to use internally.
/48 (larger site allocation)
Organizations often receive /48 blocks, enabling 65,536 individual /64 subnets—great for hierarchical design across buildings, departments, or services.
Common mistakes to avoid
- Treating IPv6 like IPv4: IPv6 subnet sizing logic is different; /64 is a norm, not “waste.”
- Using non-/64 LANs without a reason: Some features and assumptions break outside /64 on typical host networks.
- Inconsistent compression: Always document canonical/compressed format clearly to reduce errors.
- Forgetting prefix boundaries: Hex nibble boundaries (/4 increments) are easier to read and manage operationally.
Best practices for IPv6 address planning
1) Design for growth
Use structured subnet assignments so you can add segments later without painful renumbering.
2) Keep documentation clean
Record delegated blocks, routed prefixes, VLAN mappings, and DNS conventions in one authoritative place.
3) Standardize naming and prefix allocations
Predictable patterns save time during incidents and simplify automation.
4) Validate before deployment
Run calculations ahead of changes to confirm boundaries, routes, and ACL matches before touching production.
Final thoughts
IPv6 looks intimidating at first, but once you think in prefixes and hexadecimal blocks, subnetting becomes straightforward. Use this IPv6 netmask calculator whenever you need accurate prefix-to-mask conversion and quick network boundary checks.