When a Trace Becomes a Transmission Line
Every trace is a transmission line at some frequency. The critical length threshold tells you whether your particular trace at your particular edge rate needs controlled impedance or not. The answer depends on two numbers and a judgment call.
Contents
The question that actually matters
Every trace is a transmission line. That's physics. The useful question isn't whether it is one — it's whether it behaves like one at the frequencies your signal carries.
A trace behaves like a transmission line when it's long enough for the signal to see a different impedance at the far end before the launch is finished. At that point reflections happen, and if you haven't terminated the line, those reflections ring.
Below the critical length, the trace is electrically short. The far end charges before the edge finishes transitioning, the whole thing looks like a lumped capacitor, and controlled impedance buys you nothing.
Two numbers
The propagation delay of a trace in FR4 is roughly 6.4 ns/m (about 170 ps/inch for inner layers, 140 ps/inch for outer). Multiply by length and you get the one-way flight time .
The rise time is whatever the driver produces — not the clock period, not the data rate, the edge.
The ratio decides everything:
- — trace is electrically short. No termination needed. The 20% rule: reflected energy is under 20% of the incident edge, which for most digital logic is below the noise margin.
- — trace is electrically long. Terminate it. Without termination, the first reflection arrives before the edge settles, and it adds to (or subtracts from) the signal. Two reflections later you're ringing.
- Between 3 and 5 — depends on your noise budget and how much margin you have.
These thresholds come from Bogatin's analysis of the step response of a lossless line: at the reflected step is 20% of the incident (the "20% rule"), and at the round-trip reflection arrives during the transition, making it impossible to separate from the signal.
An example that surprises people
Take a 100 MHz clock. Period is 10 ns. "Slow," right?
But the driver is modern CMOS with a 300 ps rise time. The one-way delay of a 5 cm (2 inch) trace in FR4 is about 340 ps.
That's deep into transmission-line territory. A 2-inch trace at 100 MHz needs controlled impedance and termination — not because 100 MHz is fast, but because 300 ps edges are fast.
Now take the same 100 MHz clock from a part with a 3 ns edge. Same trace:
Electrically short. Route it however you like.
The clock frequency told you nothing. The edge rate told you everything.
The judgment call
The 20% threshold at is conservative for most logic. LVCMOS with 400 mV of noise margin can absorb a 20% reflection on a 3.3 V swing without flinching. LVDS with 100 mV of differential noise budget cannot.
So there's a judgment embedded in the number:
- High noise margin (GPIO, LED, reset): or even is fine. Don't terminate, don't control impedance, save the effort.
- Tight noise margin (DDR strobe, SerDes, LVDS): or higher. Terminate everything.
- Somewhere in between: Use as the default and tighten where the datasheet tells you to.
The point is that "critical length" isn't a physical constant. It's a design threshold that encodes your tolerance for reflections.
Propagation velocity isn't one number
I said 6.4 ns/m but that's an inner-layer average in FR4 at . The actual velocity depends on the effective permittivity, which depends on the geometry:
- Stripline: . Field is entirely in dielectric, so you use the bulk value.
- Microstrip: . Part of the field is in air, so and the trace is faster.
- Coplanar waveguide: Somewhere between, depending on the filling factor.
On Rogers 4350B () an inner-layer trace is about 10% faster than FR4. That means your critical length is 10% longer — the same trace that needed termination on FR4 might be fine on Rogers.
For length matching between layers, this velocity difference is what you're compensating for. Two traces matched in millimetres but routed on different layers can be mismatched in picoseconds.
Common mistakes
Using the clock period instead of the rise time. The period tells you the repetition rate. The rise time tells you the bandwidth. A 25 MHz clock with 500 ps edges has a knee frequency of 1 GHz and needs transmission-line treatment on anything longer than about 1.5 cm. Using the datasheet typical rise time. Datasheets quote typical. Fast-corner silicon at low temperature with a light load can be 2-3x faster. Design to the fast corner. Ignoring the return path. A trace with a slot in its reference plane has a longer effective path — the return current detours around the slot. The physical length says "short" but the electrical length says "long," and the electrical length is what matters. Confusing delay with period. A trace becomes critical when approaches , not when approaches the clock period. A trace that's one wavelength long at the fundamental is already 6-10x past the critical length for a typical edge.What to actually do
- Find the rise time. Datasheet fast corner, not typical.
- Measure or calculate the trace delay. Inner layer FR4 at 170 ps/inch is close enough for a first pass.
- Compute the ratio. If it's above 5, you're done. If it's below 3, terminate.
- In the grey zone, check your noise budget.
The critical trace length calculator does this for you and gives both the conservative () and permissive () thresholds, plus the one-way delay and the knee frequency for your geometry.
- Microstrip: . Part of the field is in air, so and the trace is faster.
Related Articles
Broadside-Coupled Pairs: Half the Width, One Big Risk
Stacking a differential pair on adjacent layers halves the routing width, which is why flex circuits use it everywhere. The impedance maths is clean. The failure mode is layer-to-layer registration.
Aug 16, 2026
Signal Integrity0.35 or 0.5? Two Constants, Two Different Questions
The 0.35 in the rise-time-bandwidth rule isn't a fudge factor — it's ln(9)/2π exactly. The 0.5 knee frequency answers a completely different question. Mixing them up over-specifies your amplifier or under-models your channel.
Aug 16, 2026
Signal IntegrityPDN Impedance: Taming Resonances With Genetic Algorithm
A 1.0 V / 30 A FPGA power rail needs flat impedance from 100 kHz to 1 GHz. Cavity resonances between the power and ground planes create impedance spikes that.
Mar 4, 2026