Is 900 FPM always acceptable for a trunk duct, or does it depend on the specific building?

The commonly cited 600-900 FPM residential trunk range is a general guideline, and specific noise-sensitivity requirements (a recording studio, a quiet office, a hospital patient room) may call for targeting the lower end of this range or even below it, while a less noise-sensitive application (a garage, an industrial space) might reasonably tolerate velocities somewhat above the typical residential guideline.

Does higher duct velocity always mean higher energy cost?

Generally yes — higher velocity for the same airflow means higher static pressure, and the blower has to do more work (consume more electrical power) to push air against that higher pressure, which is a genuine, ongoing operating cost consequence of an undersized duct design, not just a one-time noise annoyance.

Why does low velocity cause air to "dump" at a register instead of just delivering less noticeable airflow?

Air leaving a register relies on its own momentum and the register's throw design to project across and mix with the room air rather than simply falling straight down under gravity/buoyancy effects — insufficient velocity means insufficient momentum to achieve that proper throw and mixing, producing localized drafts or cold/hot spots near the register even when the total delivered airflow volume is technically adequate.

Engineering·6 min read·August 14, 2026

🔊 Duct Velocity: The Real Tradeoff Behind Sizing Decisions

Why duct velocity is the practical consequence that actually governs sizing decisions — connecting noise, static pressure, and airflow throw to the friction-rate design target.

By EngineersUniverse Editorial Team

Engineering Editorial & Technical Review Team

Published August 14, 2026

Why Velocity Is the Practical Consequence, Not the Design Target

The equal friction method, covered in the companion article, sizes ducts to a target friction rate — but velocity is the practical, physically felt consequence of that sizing decision, and it's velocity (not friction rate directly) that a building occupant experiences as duct noise or a technician evaluates as delivered airflow quality at a register. Understanding the tradeoffs velocity governs is what makes friction-rate-based sizing decisions meaningful in practice, rather than an abstract number disconnected from real system performance.

What Happens When a Duct Is Undersized (Velocity Too High)

A duct sized smaller than its friction-rate target would suggest — whether from an explicit undersizing decision or a field installation error — forces the same airflow through a smaller cross-sectional area, directly increasing velocity. Higher velocity has several compounding negative effects: increased static pressure (making the blower work harder, potentially beyond its rated capability), increased noise (air moving faster through ductwork and past register grilles generates more audible turbulence and whistling), and increased energy consumption (a blower working against higher static pressure consumes more electrical power for the same delivered airflow).

What Happens When a Duct Is Oversized (Velocity Too Low)

An oversized duct — larger than the friction-rate target requires — produces lower velocity, which sounds like it should be unconditionally good (quieter, lower pressure drop), but it carries its own real costs: wasted material and installation cost (larger ductwork costs more and takes more physical space, a real constraint in tight mechanical spaces or ceiling cavities), and reduced register "throw" — the distance conditioned air travels from a register before losing momentum and mixing with room air. Airflow that's moving too slowly at the register can "dump" straight down near the register rather than properly mixing across the room, producing uneven temperature distribution even though the total airflow delivered is technically correct.

Why Trunk and Branch Ducts Target Different Velocity Ranges

Trunk ducts (the main supply runs carrying combined airflow toward multiple branches) commonly target a higher velocity range (roughly 600-900 FPM for residential systems) than branch ducts (roughly 400-700 FPM) feeding individual rooms — this reflects both a practical sizing consideration (trunk ducts often run through spaces less sensitive to noise, like unconditioned attics or basements, while branches terminate near occupied spaces where noise matters more directly) and the different functional roles these sections play in the overall system. This differentiated target — not one single velocity number for the entire system — is exactly why this site's Duct Sizing Calculator lets a user select "trunk" or "branch" duct classification, applying a different target velocity range to each.

Why the Right Design Point Is a Genuine Balance, Not a Simple Maximum or Minimum

Neither "as low a velocity as possible" nor "as high a velocity as fits the friction rate" is the right universal goal — the practical design target sits within an established acceptable range (the commonly cited 600-900 FPM trunk / 400-700 FPM branch figures for residential work) that balances noise, energy efficiency, material cost, and proper register throw simultaneously. A calculated velocity outside this range — whether too high or too low — is a genuine design signal worth acting on, not a minor cosmetic concern, which is why this site's calculator explicitly flags velocity as "too low," "acceptable," or "too high" rather than only reporting the raw calculated number without interpretation.

What to Do When a Calculated Duct Size Produces an Out-of-Range Velocity

When a calculation shows velocity outside the acceptable range for the selected friction rate and duct classification, the practical responses are: adjusting the design friction rate (a higher friction rate target, within the range the air handler's static pressure budget can support, generally raises resulting velocity for a fixed size, or vice versa), manually stepping the duct size up or down from the calculated ideal to the next practical standard size, or in some cases revisiting the underlying airflow requirement itself (checking whether the CFM value used is actually correct for that specific duct run, since an error there propagates directly into an apparently problematic velocity result that's actually a symptom of a different upstream input error).

Topics covered

duct velocity noiseHVAC duct sizing tradeoffsduct airflow throwFPM velocity guidelines HVAC