Plan networks with clear capacity and ranges fast. Model reserved space, growth, and subnets easily. Export results to CSV or PDF for documentation teams.
| Prefix | Subnet mask | Total addresses | Usable hosts | Typical use |
|---|---|---|---|---|
| /30 | 255.255.255.252 | 4 | 2 | Small routed links |
| /29 | 255.255.255.248 | 8 | 6 | Very small segments |
| /28 | 255.255.255.240 | 16 | 14 | Lab or small office |
| /24 | 255.255.255.0 | 256 | 254 | Typical LAN segment |
| /22 | 255.255.252.0 | 1,024 | 1,022 | Large LAN segment |
Network size is driven by address bits and prefix length. For IPv4, a /24 leaves 8 host bits, producing 2^(32−24)=256 addresses. For IPv6, a /64 leaves 64 bits, yielding 2^64 addresses, which is about 1.84×10^19. This calculator converts those relationships into totals, usable counts, and planning-friendly summaries.
In many routed IPv4 segments, two addresses are reserved for the network and broadcast. That makes a /24 provide 254 usable hosts, while a /28 provides 14. If you enter a base address, the tool derives the network boundary and shows first and last usable values. For point-to-point links, /31 can make both addresses usable, avoiding wasted space.
IPv6 does not run out of hosts in the same way, so engineers often standardize subnet boundaries for simplicity. A common practice is allocating /64 per LAN, then grouping sites under a larger block such as /56 or /48. Instead of listing every address, the calculator reports powers of two, approximate magnitude, and digit count so teams can compare prefix choices without losing scale.
Right-sizing begins with demand, then adds safety margin. If a VLAN needs 50 devices and you reserve 10 for infrastructure and growth, the requirement becomes 60 usable. The calculator selects the smallest power-of-two subnet meeting that target, then reports total and usable capacity. This mirrors procurement-style capacity planning where headroom reduces readdressing during expansion.
Multiple subnets should roll up cleanly for routing. If you need 4 equal /26 subnets, the aggregate is 4×64=256 addresses, which aligns with a /24 supernet. The tool estimates an optional supernet prefix so you can summarize routes, document allocations, and keep tables consistent across environments. This supports growth planning when additional subnets are expected later.
After sizing, validate implementation details: DHCP scope excludes reserved ranges, gateways and critical services are fixed, and security policies match the boundary. Use the results panel to capture the chosen prefix, mask, and computed ranges. The chart visualizes capacity tradeoffs at a glance, while CSV and PDF exports provide auditable documentation for change reviews and handoffs for your team.
Total addresses come from 2^(32−prefix). Usable hosts usually exclude the network and broadcast addresses, so usable equals total minus two for prefixes up to /30.
On point-to-point links, RFC-style behavior allows both addresses to be assigned because no broadcast is needed. That can save space compared with /30.
Many LAN designs standardize on /64 for compatibility and simplicity, but other prefixes can be valid for special cases. Follow your platform guidance and routing plan.
Reserved space is added to required hosts before choosing the smallest fitting subnet. This headroom supports gateways, services, and growth without frequent readdressing.
It is an optional aggregate block that can contain all planned equal-sized subnets. Using it can simplify route summaries and documentation, especially across multiple sites.
Yes. After a calculation, use the CSV or PDF buttons in the results panel to save the latest output for change tickets, audits, or handoffs.
Important Note: All the Calculators listed in this site are for educational purpose only and we do not guarentee the accuracy of results. Please do consult with other sources as well.