/24 vs /23: What's the Difference?

A /24 and a /23 differ by exactly one bit — the bit that decides whether the third octet belongs to the network or the host. That single bit doubles the address space and halves the number of subnets you can carve out of a larger block. This guide compares the two concretely so you can pick the right one. Verify any layout with the subnet calculator.

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

Side-by-side comparison

Property/24/23
Subnet mask255.255.255.0255.255.254.0
Prefix bits2423
Host bits89
Total addresses256512
Usable hosts254510
Networks per /16256128
Wildcard mask0.0.0.2550.0.1.255

Address layout

A /24: 192.168.1.0/24

Network:    192.168.1.0
First host: 192.168.1.1
Last host:  192.168.1.254
Broadcast: 192.168.1.255
Range:      192.168.1.0 – 192.168.1.255   (256 addresses)

A /23: 192.168.0.0/23

Network:    192.168.0.0
First host: 192.168.0.1
Last host:  192.168.1.254
Broadcast: 192.168.1.255
Range:      192.168.0.0 – 192.168.1.255   (512 addresses)

The /23 spans two third-octet values (0 and 1). The network address must be even — 192.168.0.0/23 is valid but 192.168.1.0/23 is not, because 1 is not a multiple of the block size (512).

The one-bit difference in binary

/24 mask: 11111111.11111111.11111111.00000000
/23 mask: 11111111.11111111.11111110.00000000
                                   ^
                          this bit moves from network to host

Moving one bit from the network to the host portion doubles the host space (2⁸ → 2⁹) and halves the number of available subnets within a fixed parent block.

When to use a /24

  • Small user VLANs — up to ~200 endpoints keeps ARP/broadcast traffic manageable.
  • Server segments — most racks fit comfortably in 254 addresses.
  • Point-to-point with room — when you want a /30 but keep a /24 for future growth.
  • Clean boundaries — a /24 aligns to one octet, which simplifies documentation and mental math.

When to use a /23

  • Large user VLANs — 300–500 hosts on one flat segment (watch broadcast traffic).
  • Wireless networks — client counts often exceed a /24, and roaming benefits from a larger pool.
  • Conserving a larger block — one /23 uses half the space of two /24s when you need 300 hosts.
  • DHCP pools with growth headroom — see the DHCP scope calculator.

The broadcast domain trade-off

The biggest downside of a /23 is not address count — it is broadcast domain size. ARP requests, DHCP broadcasts, mDNS, and NetBIOS traffic hit every host in the subnet. On a /23 with 500 active hosts, broadcast traffic can become a measurable load on access-layer switches. Rules of thumb:

VLAN sizeBroadcast loadTypical use
/24 (254 hosts)LowStandard access VLAN
/23 (510 hosts)ModerateLarge/wireless VLAN
/22 (1022 hosts)HighGuest wireless, careful design
/21 (2046 hosts)Very highAvoid unless segmented

Configuration comparison

/24 on a Cisco switch

interface Vlan10
 ip address 192.168.1.1 255.255.255.0

/23 on a Cisco switch

interface Vlan20
 ip address 192.168.0.1 255.255.254.0

DHCP scope for a /23

ip dhcp pool VLAN20
 network 192.168.0.0 255.255.254.0
 default-router 192.168.0.1
 dns-server 192.168.0.1
 lease 7

Merging two /24s into a /23

You can combine two adjacent /24s into a /23 only if the first network address is even-aligned. 192.168.0.0/24 and 192.168.1.0/24 merge cleanly into 192.168.0.0/23. But 192.168.1.0/24 and 192.168.2.0/24 cannot merge into a single /23 — they would need a /22.

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.