How to Choose a Subnet Size

Picking a CIDR prefix is a balance between four factors: the number of hosts you need today, the headroom for growth, the size of the broadcast domain you can tolerate, and the address space you have to spend. This guide gives concrete rules for each. For sizing VLANs interactively, use the VLAN sizing calculator; for DHCP pools, the DHCP scope calculator.

Built by a network engineerCalculations run locally in your browserNo signup requiredNetwork information is not transmitted to our servers

The four inputs

FactorQuestion
Current hostsHow many endpoints will be on this segment now?
Growth headroomHow many will be added in 2–3 years? (Rule: 30–50%.)
Broadcast toleranceHow much broadcast/multicast traffic is acceptable?
Address budgetAre you in RFC 1918 (abundant) or public space (scarce)?

The sizing formula

  1. Take current hosts and add growth headroom: need = current × 1.5.
  2. Add infrastructure overhead (gateway, switches, reserved): ~5–10 addresses.
  3. Find the smallest prefix where 2^h − 2 ≥ need.
  4. Check the broadcast domain — if it exceeds ~500 hosts, consider splitting.

Prefix selection table

PrefixUsable hostsBest for
/312Point-to-point router links (RFC 3021)
/302P2P links on older gear
/296Small server cluster, HA pair + VIPs
/2814Management VLAN, small DMZ
/2730Small office, IoT, printer VLAN
/2662Medium VLAN, department segment
/25126Large user VLAN
/24254Standard access VLAN
/23510Large/wireless VLAN (watch broadcasts)
/221022Guest wireless, carefully segmented

Worked example: a 180-user office

Current: 180 hosts. With 50% growth: 270. Plus infrastructure: ~280. The smallest prefix with 2^h − 2 ≥ 280 is /23 (510 usable). But a /23 broadcast domain for 280 hosts is excessive. Better: split into two /24s (VLAN 10, VLAN 20) of 254 each — cleaner, smaller broadcast domains, and room to grow.

Option A: 192.168.10.0/23   (510 usable, one big broadcast domain)
Option B: 192.168.10.0/24 + 192.168.11.0/24  (254 each, two VLANs) ← recommended

Broadcast domain guidance

Hosts per VLANBroadcast loadRecommendation
≤ 250LowSingle /24, no concern
250–500Moderate/23 acceptable, monitor broadcasts
500–1000HighSplit into multiple VLANs
> 1000Very highAvoid; segment aggressively

Special-purpose sizing

Point-to-point links

Use /31 (RFC 3021) on modern gear for zero waste; /30 on older gear. See How /31 Networks Work.

Loopback addresses

Use /32 — one address per router loopback. A /24 of 127.x or a slice of your management block gives 256 loopbacks.

Management VLANs

Typically /28 (14 hosts) or /27 (30) — switch management IPs, OOB, IPMI. Keep it small and restricted.

Server segments

Start at /24 and grow to /23 only if needed. Servers generate more broadcast/multicast traffic than users (mDNS, clustering heartbeats), so keep domains tight.

Address budget considerations

In RFC 1918 space, addresses are effectively free — size generously. With public IP space, every address counts, so size tightly and use VLSM (VLSM Explained) to avoid waste.

Configuration example

! Two-VLAN design for a 180-user office
interface Vlan10
 description Users - floor 1
 ip address 192.168.10.1 255.255.255.0
!
interface Vlan20
 description Users - floor 2
 ip address 192.168.11.1 255.255.255.0
!
ip dhcp pool FLOOR1
 network 192.168.10.0 255.255.255.0
 default-router 192.168.10.1
ip dhcp pool FLOOR2
 network 192.168.11.0 255.255.255.0
 default-router 192.168.11.1

Related guides

Technically Reviewed By

Senior Enterprise Network Engineer — 25+ years of IT and network infrastructure experience, including enterprise Cisco switching, routing, wireless, firewalls, VPN, network access control, SD-WAN, and large-scale network operations.

Last reviewed: 2026-09-02

Calculations are performed using standards-based formulas and verified against known reference values. All computation runs client-side in your browser.