redzilla
All tools
Cabling

Patch Panel Planner

Enter the network drops, panel density (24/48 ports) and growth reserve and I compute the panels needed, the ports and the rack space (U), including cable managers.

Outlets or keystones to terminate on the panel (one per network drop).

Extra ports for future growth. Typical 25 %.

Ports per panel. 48p panels save U but crowd the cabling.

24p is usually 1U; 48p comes in 1U or 2U depending on model.

Horizontal manager or comb under each panel to dress the patch cords.

Examples
redzilla.cl — patch-panel
 
Ports used

Panels
Rack space
panels + managers
Ports installed
Free ports
installed − drops
Panels
Rack U
Ports
Free

Comparison by density

DensityPanelsPortsFreeRack U

The selected density is highlighted · U computed with the current height and manager.

How it is computed · patch panel sizing

1. The reserve is added to the drops: ports = ceil(drops × (1 + reserve/100)). With 96 drops and 25 %, 96 × 1.25 = 120 target ports.

2. Panels come from the density: panels = ceil(ports / density). With 48p panels, ceil(120 / 48) = 3 panels.

3. Ports actually installed are panels × density and free ports are installed − drops (spare capacity available today).

4. Rack space adds the panel height plus its manager: U = panels × (Upanel + Umanager). With 3 panels of 1U and 1U of manager each, 3 × (1 + 1) = 6U.

5. The reserve is a design recommendation: growing later costs more than leaving spare ports today. Adjust it to the site's expected growth.

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

How it works

The calculator sizes the patch panels and rack space for a number of network drops. It first applies the growth reserve: ports = ceil(drops × (1 + reserve/100)), with 25 % as the typical design value; it then derives the panels with panels = ceil(ports / density) for 24- or 48-port panels, and from there the ports actually installed (panels × density) and the spare ones.

Rack space is computed as U = panels × (panel_U + manager_U), adding the panel height (1U or 2U) and the optional 1U horizontal cable manager under each panel, a practice recommended by TIA-568/TIA-569 to dress the patch cords and preserve bend radius. The tool also shows the port occupancy percentage (with a warning above 90 %) and a comparison table between 24- and 48-port densities for the same scenario.

Example: 96 network drops with a 25 % reserve

  1. Target ports: ceil(96 × 1.25) = 120 ports.
  2. With 48-port panels: ceil(120 / 48) = 3 panels → 144 installed ports.
  3. Spare ports today: 144 − 96 = 48 (66.7 % occupancy).
  4. Rack: 3 panels of 1U plus 1U of cable manager each → 3 × (1 + 1) = 6U.

Frequently asked questions

How many patch panels do I need for 100 network drops?
With the typical 25 % reserve the target is 125 ports: that means 3 panels of 48 ports (144 installed) or 6 panels of 24 (144 installed). In the rack, with a 1U manager per panel, the 48p option takes 6U and the 24p option takes 12U: high density saves half the space.
What growth reserve should I leave in a patch panel?
Between 20 % and 30 % is standard for new designs; the calculator defaults to 25 %. Adding ports later means buying panels, re-pulling cable and often reorganizing the rack, so leaving spare ports from day one is almost always cheaper than expanding on the fly.
Which is better: 24-port or 48-port panels?
48-port panels double the density and save rack units, but they concentrate twice as many cables per U, making dressing and maintenance harder. 24-port panels give more working room and easier fault handling. In space-constrained racks the 48p wins; if rack space is plentiful, the 24p is easier to manage.
Why add a cable manager for every panel?
The 1U horizontal manager under each panel routes the patch cords to the sides, preserves the cable bend radius and keeps ports accessible without stressing the terminations. TIA-569 practices recommend it; skipping it saves rack units but usually ends in a messy rack that is hard to work on.
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 →