redzilla
All tools
IP Addressing

IPv6 Planner

Enter your assigned IPv6 prefix (e.g. /48 or /56) and the target subnet size (typically /64). I compute how many subnets fit, the subnet bits, a suggested hierarchy and example prefixes. Fully local.

Format address/prefix, e.g. 2001:db8::/48. This is the block your ISP or RIR assigns you.

The standard is /64 per LAN/VLAN (SLAAC autoconfig). Split on nibbles (/48 /52 /56 /60 /64) for hex-readable prefixes.

redzilla.cl — ipv6-plan
 
Subnets
Bits
/64
Assigned prefix
source block
Target subnets
/— blocks
Subnet bits
nibble-aligned
Total /64s
/64 networks in the block

Suggested hierarchy

LevelPrefixCountBitsHolds

Classic rule: /48 per site/56 per building (256 per site) → /64 per VLAN (256 per building). The nibble (4 bits) keeps every level readable in hexadecimal.

Example subnets
#PrefixCompressed

Subnets are numbered by incrementing the subnet field of the prefix. With nibble alignment, each hex digit of the prefix maps to a level of the hierarchy, so 2001:db8:0:0000, 0001, 0002… read at a glance.

Runs locally in your browser · no sign-up · nothing leaves your browser

How it works

The planner takes the IPv6 prefix your ISP or RIR assigned you (for example 2001:db8::/48) and a target subnet size (typically /64) and works out the whole plan: how many subnets fit (2^(target − assigned)), how many subnet bits you use, how many /64s the block contains in total and the first example prefixes, already numbered and compressed per RFC 5952.

It also suggests the classic IPv6 addressing hierarchy: /48 per site → /56 per building → /64 per VLAN, with 256 blocks at each step. The tool warns when the subnet bits are not a multiple of 4, because splitting on nibble boundaries (/48, /52, /56, /60, /64) makes every level of the plan correspond to a full hexadecimal digit, so prefixes can be read at a glance.

Example: splitting 2001:db8::/48 into /64 subnets

  1. Subnet bits: 64 − 48 = 16, a multiple of 4, so the plan is nibble-aligned.
  2. Available subnets: 2^16 = 65,536 /64 blocks, one per VLAN or segment.
  3. Subnets are numbered by incrementing the subnet field: 2001:db8::/64, 2001:db8:0:1::/64, 2001:db8:0:2::/64
  4. With the suggested hierarchy, that /48 also supports 256 /56 buildings with 256 /64 VLANs each.

Frequently asked questions

How many /64 subnets come out of a /48, a /56 and a /60?
A /48 yields 2^16 = 65,536 /64 subnets; a /56 yields 2^8 = 256; and a /60 yields 2^4 = 16. The formula is 2 to the power of (64 minus the assigned prefix). Even the smallest residential delegation leaves plenty of subnets to separate guest, IoT and management networks.
What does nibble alignment mean and why does it matter?
A nibble is 4 bits, that is, one hexadecimal digit. If you split in steps that are multiples of 4 (/48 → /52 → /56 → /60 → /64), each level of the hierarchy occupies whole hex digits and prefixes read directly: 2001:db8:0:0000, 0001, 0002… With intermediate cuts (for example /50) the boundaries fall mid-digit and the plan becomes error-prone. It also simplifies delegating reverse DNS zones under ip6.arpa.
Can I use subnets smaller than /64 to save addresses?
In IPv6 you neither need to nor should: there is no address scarcity and SLAAC requires a /64 on every LAN. The recommended practice (RFC 6177) is to assign generous blocks (/48 or /56) and give one /64 per VLAN. The tool flags targets more specific than /64 as a special case.
Does the planner send my prefix to any server?
No. All the math runs in your browser using 128-bit arithmetic (BigInt), so you can plan with your organization real prefixes without exposing them.
Was this tool useful?
Disclaimer We take great care to keep every tool accurate and review it thoroughly; even so, we can't guarantee it is free of errors or take responsibility for how the results are used. We recommend double-checking anything critical.
Found an error? Let us know →