Traffic Signal Cycle Length Calculator
Size a signalized intersection the way a US traffic engineer does. Enter your peak-hour volumes and phasing, and get the optimum cycle length, per-phase green splits, degree of saturation, and a MUTCD pedestrian check, using both Webster’s method and the FHWA critical-lane approach.
Intersection Timing Tool
Fill in the change intervals, saturation-flow conditions, and each phase’s critical volume. Everything updates in one click.
Enter your intersection data and press Calculate. Your optimum cycle length, green splits, and saturation check will appear here.
Cycle composition by phase
Intersection timing basics for a busy US junction
Every time you sit at a red light in Phoenix, Columbus, or Charlotte, a small piece of math is deciding how long you wait. That math is the signal cycle length: the total number of seconds it takes a traffic light to run through every movement once and return to where it started. Green for the main street, then yellow, then a moment of all-red, then green for the cross street, and around again. Add up all of those seconds and you have the cycle.
Get the cycle right and traffic breathes. Cars clear the intersection before the queue spills back into the last block, buses keep their schedule, and the folks waiting to cross on foot get a fair shake. Get it wrong and everything backs up. Too short, and the queued cars never fully clear before the light turns red again, so the line grows every cycle until it chokes the corridor. Too long, and side streets and pedestrians sit forever while the main street runs mostly empty green. There is a sweet spot, and this calculator finds it.
The words engineers actually use
Before the numbers make sense, a handful of plain-English definitions help. None of this is complicated once you see it on a real corner.
- Phase. One protected green interval for a group of movements that can safely go together. A simple crossroads has two phases: north-south, then east-west. Add protected left turns and you climb to three, four, or more.
- Cycle length (C). The full loop of all phases in seconds. If your cycle is 90 seconds, the light shows you the same color at the same point every 90 seconds.
- Saturation flow rate (s). The most cars a single lane could push through the green if the light just stayed green and a full queue kept moving. In the United States the base figure is roughly 1,900 vehicles per hour of green per lane, before you knock it down for narrow lanes, grades, and trucks.
- Flow ratio (y). Demand divided by saturation flow for a phase, or v/s. It answers a simple question: what fraction of a full green does this movement actually need? A y of 0.35 means the movement needs about 35 percent of a saturated green to clear.
- Lost time (L). The seconds in each cycle that no one really uses. Drivers react slowly when the light turns green (start-up lost time) and the all-red clearance at the end of a phase is unavoidable overhead. Lost time is paid once per cycle no matter how short the cycle is.
- Degree of saturation (X, or v/c). How close a movement runs to its own capacity. Below about 0.85 you have breathing room. At 1.0 the movement is maxed out and queues start carrying over.
Notice how the yellow and all-red change interval ties directly into this. Those clearance seconds are part of your lost time, so the length of your yellow feeds straight into the cycle math. If you have not set your change interval yet, size it first, then bring the numbers here.
Why longer is not automatically better
A common gut reaction is that a longer cycle moves more cars, so just crank it up. It is half true. A longer cycle does spend a smaller fraction of its time on lost-time overhead, so raw throughput inches up. But every extra second of cycle is an extra second that somebody else waits at a red light. Average delay follows a flat-bottomed U-shaped curve: it drops as you lengthen the cycle toward the optimum, bottoms out, then climbs again as the cycle grows too long. F.V. Webster mapped that curve back in the late 1950s, and the shape has held up for more than sixty years of US practice. The lesson baked into this tool is simple: when you are unsure, err a little long rather than short, because the penalty for a slightly short cycle is much steeper than the penalty for a slightly long one.
Who actually uses this math
This is not just an exam exercise. City and county traffic engineers reach for these formulas every time a new development opens, a road gets restriped, or residents complain about backups at a corner. Consultants use them on preliminary design before the detailed modeling begins. Students preparing for the transportation portion of the Fundamentals of Engineering and Professional Engineering exams practice this exact procedure, because it shows up on the test. Even a public works technician sizing a temporary signal for a work zone needs a defensible starting cycle. If you touch a signalized intersection in the United States in any capacity, the cycle length calculation is the doorway into the whole problem.
What ties all of those users together is a shared need for numbers they can trust and defend. When a resident asks why their side street sits red so long, or when a plan review board questions a submittal, an engineer needs to point at accepted methods and standard values, not a hunch. That is why this calculator leans entirely on published US sources, the Federal Highway Administration, the Highway Capacity Manual, and the MUTCD, rather than a proprietary black box. You can see every input, understand every adjustment, and explain the result to anyone who asks.
Reading the intersection before you read the numbers
The quality of your answer depends entirely on the quality of your inputs, and the most important input is the critical volume for each phase. Spend time getting that right. Pull turning-movement counts for the design hour, identify the busiest lane in each phase, and be honest about heavy vehicles and lane widths. A cycle built on careful counts will hold up in the field. A cycle built on rounded guesses will send you back for a second visit. The formulas are the easy part; the observation is where good signal timing is really made.
One last habit worth building: always write down your assumptions alongside your result. Note the design hour you used, the saturation flow you assumed, the walk speed, and the method. Six months later, when someone questions the timing or demand shifts, that short record turns a mystery back into a clear, defensible decision you can update in minutes rather than rebuild from scratch.
How this tool runs the numbers
The calculator gives you two proven US methods. They start from the same inputs but answer slightly different questions, and it is worth knowing which one you are looking at.
Method 1: Webster’s optimum cycle
Webster’s formula finds the cycle that produces the least total vehicle delay at an isolated, pre-timed signal. It is the classic taught in every US transportation course and it sits under the Highway Capacity Manual procedure. The formula is:
C₀ = (1.5 × L + 5) ÷ (1 − Y)
C₀ is the optimum cycle in seconds. L is total lost time per cycle. Y is the sum of the critical flow ratios across all phases. As Y creeps toward 1.0, that denominator shrinks toward zero and the cycle shoots up, which is the math telling you the intersection is running out of room.
The tool computes each phase’s flow ratio from your volume and its adjusted saturation flow, adds them into Y, then plugs L and Y into the formula. It rounds the raw answer up to the nearest 5 seconds, the way US agencies do for corridor coordination.
Method 2: FHWA critical-lane volume
The FHWA Signal Timing Manual and the HCM also give a method built around critical lane volumes and a target degree of saturation. Instead of chasing minimum delay, it sizes the cycle so the intersection runs at a v/c you choose, say 0.90. The form is:
C = L ÷ (1 − V⁵ ÷ (RS × target v/c))
V⁵ is the sum of the critical lane volumes. RS is a reference sum flow, 1,710 vehicles per hour adjusted by your peak-hour factor and an area-type factor (0.90 in a central business district, 1.00 elsewhere). This method shines when you are managing a saturated corridor and want a specific reserve rather than pure least-delay.
Splitting the green fairly
Once the cycle is set, the leftover green (cycle minus lost time) gets divided among the phases in proportion to their flow ratios. A phase carrying twice the flow ratio of its neighbor gets twice the effective green. The tool then converts effective green into the displayed green you would actually program into the controller, and reports each phase’s own degree of saturation so you can spot the one movement that is about to fail while the others coast.
The pedestrian safety net
Vehicles are only half the story. The MUTCD sets a minimum walk interval of 7 seconds and a pedestrian clearance based on a walking speed of 3.5 feet per second. If you enter a crosswalk length, the tool checks whether the shortest served phase actually gives people enough time to get across. When it does not, you get a clear red flag, because a cycle that clears cars but strands pedestrians is not a finished design.
Where timing meets corridor coordination
A single intersection almost never lives alone. Drive down any major arterial in Denver, Nashville, or Sacramento and you are moving through a string of signals that talk to each other. When those lights share a common cycle and their greens are offset just right, you get a green wave: leave one light and arrive at the next just as it turns green. Traffic engineers call that progression, and it is one of the biggest levers for reducing delay on a busy road without pouring a single yard of new concrete.
Here is the catch. Progression only works if every signal in the group runs the same background cycle length. That is why the number this calculator gives you for an isolated intersection is a starting point, not always the final answer. If the intersection you are timing sits inside a coordinated system, the corridor already has a cycle, often the longest optimum among its members, and your signal has to fall in line. You still run the math here to understand your intersection’s true demand, then you compare it to the corridor value. If your optimum is shorter, no problem, you inherit the longer corridor cycle and simply run a little more green than the bare minimum. If your optimum is longer than the corridor cycle, that is a red flag that your intersection is the bottleneck, and you may need to rethink phasing or geometry rather than force everyone else to slow down.
The half-cycle trick
Sometimes a light intersection in the middle of a coordinated corridor can run at half the corridor cycle, serving twice as often while still lining up with the green wave. A minor cross street that only needs 30 seconds does not have to sit through a full 120 second corridor cycle if it can cleanly double up at 60. The calculator helps you spot these candidates: when a signal’s optimum comes back far shorter than its neighbors, it may be a half-cycle candidate, which cuts side-street delay dramatically.
Peak, off-peak, and the case for time-of-day plans
Demand is not one number. The morning rush, the midday lull, the evening peak, and the quiet overnight hours each want a different cycle. A 110 second cycle that is perfect at 5:30 in the afternoon is pure punishment at 10 at night, when a driver on the side street stares at a red light with no cross traffic in sight. Good practice is to run this calculator for each demand period, then load several time-of-day plans into the controller so the signal breathes with the day. Running one fat cycle around the clock is one of the most common and most avoidable sources of complaint calls a city gets.
Common timing mistakes and how to dodge them
After enough retiming projects, the same handful of errors show up again and again. Knowing them ahead of time saves you a return trip to the intersection.
Mistaking volume for the critical lane
The math cares about the critical lane volume, not the total approach volume. If an approach has three through lanes carrying 1,500 vehicles per hour combined, the number that drives the phase is roughly 500 per lane, not 1,500. Feeding the full approach volume into a single-lane assumption inflates the flow ratio, balloons the cycle, and wastes green on a phase that did not need it. The tool asks for lane count precisely so it can find the true per-lane critical volume.
Forgetting that trucks are not cars
A loaded delivery truck accelerates from a standstill far slower than a sedan and takes up more room in the queue. US practice counts each heavy vehicle as roughly two passenger cars. On a corridor with a distribution center or a lot of transit, ignoring the heavy-vehicle share quietly overstates your real capacity and leaves you short on green. Enter an honest heavy-vehicle percentage and the calculator knocks the saturation flow down accordingly.
Letting Webster run wild
When an intersection is genuinely saturated, Webster’s formula happily returns a 200 or even 300 second cycle that no real agency would ever deploy. Chasing that number is a trap. Beyond a sum of flow ratios of about 0.5, the formula overstates the cycle, and past a v/c of 1.0 the whole premise breaks. A very long cycle does not add capacity, it just makes everyone wait longer for the same throughput. When you see the tool’s advisory, treat it as a nudge to fix the intersection physically, not to keep stretching the clock.
Treating pedestrians as an afterthought
It is easy to size the vehicle greens, feel done, and forget the crosswalks. But a cycle that clears cars while stranding a person halfway across the street is not just poor service, it is a safety problem and a liability. Always run the pedestrian check, and where older adults, children, or wheelchair users cross regularly, drop the walk speed below 3.5 feet per second as the MUTCD allows. The extra clearance seconds are cheap insurance.
Ignoring the field
Every formula in this tool rests on assumed values that a real count might contradict. Maybe your saturation flow is 1,750 rather than 1,900 because of a tight curve on the approach. Maybe a nearby driveway steals capacity you did not model. The numbers get you 90 percent of the way, but a few hours watching the intersection during the peak will tell you the rest. The best engineers pair the math with their own eyes.
Reference values used across US intersection design
These are the working numbers behind the calculator. They line up with the FHWA Signal Timing Manual, the Highway Capacity Manual, and the MUTCD. Keep them handy when you sanity-check a result.
Typical saturation flow adjustments
| Condition | Effect on saturation flow | Notes |
|---|---|---|
| Base rate | 1,900 vphgpl | US standard per lane before adjustment |
| Narrow 10 ft lane | Reduces flow | fw drops below 1.0 for lanes under 12 ft |
| Wide 13 ft lane | Slight increase | fw rises modestly, capped near 1.10 |
| Upgrade approach | Reduces flow | Vehicles accelerate slower uphill |
| Heavy vehicles | Reduces flow | Each truck or bus counts as two cars |
| Protected left | About 5% lower | Turning paths run slower than through |
| Right turn | About 15% lower | Slower turning and pedestrian conflicts |
Change interval and lost time defaults
| Element | Common US value | Source |
|---|---|---|
| Yellow change interval | 3.0 to 5.0 s | Speed-based, ITE kinematic equation |
| All-red clearance | 1.0 to 3.0 s | Intersection width and speed |
| Start-up lost time | 2.0 s per phase | Driver reaction at green |
| Usable yellow | About 2.0 s | Moving vehicles use part of yellow |
| Minimum walk interval | 7 s | MUTCD 4I.06 |
| Pedestrian walk speed | 3.5 ft/s | MUTCD 4I.06 |
Reading the degree of saturation
| v/c range | What it means | Action |
|---|---|---|
| Below 0.85 | Comfortable reserve | Cycle is healthy, room to grow |
| 0.85 to 0.95 | Approaching capacity | Watch the critical phase closely |
| 0.95 to 1.00 | Near saturation | Consider added lanes or phasing |
| Above 1.00 | Over capacity | No fixed cycle can serve demand |
Three worked examples from real US intersections
Numbers click into place when you watch them move through a real corner. Here are three, sized the way you would tackle them on the job.
Example 1: A four-phase arterial in Columbus, Ohio
A city engineer is retiming a four-phase intersection where a busy arterial meets a collector. The two through movements carry 520 and 430 vehicles per hour on their critical lanes, and the two protected left phases carry 300 and 260. Yellow is 4 seconds, all-red is 2, and start-up lost time is 2 seconds per phase.
The tool flags a Webster advisory here because Y sits above 0.5. The engineer switches to the FHWA method with a 0.90 target and confirms the shorter cycle still holds the reserve she wants, then locks in 80 seconds to match the neighboring signals on the corridor.
Example 2: A simple two-phase crossing in Boise, Idaho
A quiet residential crossroads has just two phases. The main street carries 610 vehicles per hour on its critical lane and the side street carries 240. Lanes are a standard 12 feet, the grade is flat, and heavy vehicles are only 2 percent. Yellow is 4 seconds and all-red is 1.5.
Because Y is below 0.5, Webster is right at home and no advisory appears. The engineer adds a crosswalk length of 48 feet, and the pedestrian check confirms the main street green comfortably covers the 7 second walk plus roughly 14 seconds of clearance.
Example 3: A saturated downtown grid signal in Austin, Texas
Downtown, a three-phase signal is pushing hard against its limits during the evening peak. Critical lane volumes are 700, 560, and 420 vehicles per hour, lanes are a tight 11 feet, and heavy vehicles from delivery trucks run 6 percent. The engineer chooses the FHWA method with a target v/c of 0.92 and marks the area as a central business district.
The tool warns that the intersection is close to saturation and that one phase carries a v/c near 0.98. That single red number tells the engineer exactly where to add a lane or steal green from a lighter phase, rather than guessing across the whole intersection.
Field-tested tips from working traffic engineers
Round up, never down
When the raw optimum lands between two five-second marks, take the higher one. The delay curve is flat on the long side and steep on the short side, so a slightly generous cycle protects you against a demand surge.
Match the corridor cycle
An isolated optimum means little if the signal sits on a coordinated arterial. Neighboring lights usually share one background cycle so green bands can flow. Size the signal here, then snap it to the corridor value.
Chase the critical phase
Do not average your way to a fix. Look at the one phase whose degree of saturation is highest. That single movement usually drives your delay, your queue spillback, and your complaint calls.
Respect the pedestrians first
Run the crosswalk check before you finalize anything. If a phase cannot clear a walker at 3.5 feet per second, the vehicle math is moot. Lengthen the phase or the cycle until the walk plus clearance fits.
Measure saturation flow when you can
The 1,900 base is a strong default, but a field count on your own approach beats any table. Local driver behavior, sight lines, and land use all nudge the real number up or down.
Keep long cycles honest
If your result pushes past 150 seconds, pause. Long cycles pile delay on side streets and pedestrians. Often the smarter move is added lanes, tighter phasing, or splitting a heavy left rather than a longer clock.
Quick reference for intersection timing
| Item | Rule of thumb |
|---|---|
| Webster formula | C₀ = (1.5L + 5) / (1 − Y) |
| Typical two-phase cycle | Roughly 40 to 60 s |
| Typical four-phase cycle | Roughly 80 to 120 s |
| Practical US maximum | 150 to 180 s |
| Base saturation flow | 1,900 vphgpl |
| Start-up lost time | 2 s per phase |
| Design degree of saturation | 0.85 to 0.95 |
| Walk interval minimum | 7 s |
| Walk speed for clearance | 3.5 ft/s |
| Round cycle to | Nearest 5 s, upward |
Timing questions drivers and engineers ask
What is a good cycle length for a typical US intersection?
It depends on how many phases you run and how busy each one is. A simple two-phase crossing often lands between 40 and 60 seconds. A four-phase arterial with protected lefts usually sits between 80 and 120 seconds. Most US agencies try to keep cycles at or below 150 to 180 seconds, because longer cycles pile delay onto side streets and pedestrians. This tool gives you the optimum for your exact volumes rather than a one-size number.
What is the difference between Webster and the FHWA method?
Webster’s method finds the cycle that produces the least total delay at an isolated signal. The FHWA critical-lane method sizes the cycle to hit a target degree of saturation that you pick, such as 0.90. Webster is the classic least-delay answer, while the FHWA approach is handy for saturated corridors where you want a specific reserve. When traffic is heavy, Webster tends to run long, so comparing both is smart practice.
Why does Webster’s formula overestimate at high volumes?
Webster was calibrated on random, uncoordinated arrivals. As the sum of flow ratios climbs past about 0.5, the denominator in the formula shrinks fast and the cycle balloons, sometimes to unrealistic lengths. Peer-reviewed studies confirm the overshoot beyond a volume-to-capacity of roughly 0.5. That is why the calculator posts an advisory when your Y is high and suggests checking the FHWA method or a shorter coordinated cycle.
What is lost time and why does it matter so much?
Lost time is the seconds each cycle that no traffic really uses. It comes from start-up delay when drivers react to the green and from the all-red clearance at the end of each phase. Because lost time is paid once per cycle regardless of cycle length, a very short cycle spends a large fraction of itself on overhead, which starves the greens. That is the core reason cycles cannot shrink indefinitely.
What saturation flow rate should I use?
The US base is about 1,900 vehicles per hour of green per lane. From there you adjust down for narrow lanes, upgrades, heavy vehicles, and turning movements. The calculator applies those adjustments automatically from your inputs. If you have a field count on your own approach, use it, because local conditions can move the real number meaningfully.
How is the green time split between phases?
After the cycle is set, the leftover green, which is cycle minus total lost time, gets shared among phases in proportion to their flow ratios. A phase with twice the flow ratio of another receives twice the effective green. The tool converts effective green into the displayed green you would program into the controller and shows each phase’s own degree of saturation.
What is degree of saturation, or v/c?
Degree of saturation is demand divided by capacity for a movement. Below 0.85 you have comfortable reserve. Between 0.85 and 0.95 you are approaching capacity. At 1.0 the movement is maxed and queues carry over from cycle to cycle. The calculator reports both an overall value and a per-phase value so you can spot the one movement that is close to failing.
Does this include a pedestrian timing check?
Yes. If you enter a crosswalk length, the tool checks the MUTCD minimum walk interval of 7 seconds plus a clearance based on a walking speed of 3.5 feet per second. It then compares that requirement to the shortest served phase and flags any phase that does not give people enough time to cross. You can lower the walk speed for crossings used by older or disabled pedestrians.
How many phases should my intersection have?
The fewer the better, as long as safety holds. A basic crossroads needs two phases. Add a protected left turn and you need a third or fourth. Every extra phase adds its own lost time, which drives the cycle up. Engineers often test whether a permitted left or a leading pedestrian interval can avoid an extra protected phase before committing to it.
Why round the cycle to the nearest 5 seconds?
Controllers and coordination plans work in tidy increments, and neighboring signals along a corridor usually share a common background cycle so their greens line up into progression bands. Rounding to the nearest 5 seconds, upward, keeps your signal compatible with that corridor and gives a small delay cushion.
What is the peak-hour factor and when do I change it?
The peak-hour factor captures how evenly traffic arrives within the peak hour. A value near 1.0 means steady flow, while a lower value like 0.85 means the demand is concentrated in a sharp fifteen-minute burst. The FHWA method uses it to keep the cycle honest against those bursts. Use a local count if you have one, otherwise 0.90 to 0.92 is a reasonable urban default.
Can I use this for an actuated or adaptive signal?
The math here is for pre-timed, fixed-cycle operation, which is also the planning baseline for actuated signals. Actuated controllers vary the green in real time based on detection, and adaptive systems adjust the whole plan on the fly. Use this tool to set sensible maximums and a background cycle, then let the controller flex within those bounds.
What happens if my intersection is over capacity?
When the sum of flow ratios reaches or exceeds 1.0, the denominator in the cycle formula goes to zero or negative, and no fixed cycle can clear the queues each cycle. The calculator stops and tells you plainly. The real fixes are physical or operational: add a lane, restripe, revise the phasing, or reduce a turning conflict. A longer cycle alone will not rescue a truly saturated intersection.
How does the yellow interval feed into this?
Yellow plus all-red make up the change interval, and part of that time is lost time in the cycle math. A longer yellow, often needed on higher-speed approaches, raises your lost time and nudges the cycle up. Size your change interval first with a dedicated tool, then bring the yellow and all-red values here so the cycle reflects them accurately.
Is a 120 second cycle too long?
Not necessarily. Busy four-phase arterials and downtown grids often run 100 to 120 seconds during peaks, and that can be perfectly appropriate. It becomes a problem when the length is driven by an over-inflated Webster estimate rather than real demand, or when pedestrians and side streets pay an unfair delay penalty. If the tool caps your result at 180 seconds, treat that as a signal to rethink phasing or geometry.
What US standards does this calculator follow?
It draws on the FHWA Traffic Signal Timing Manual, the Highway Capacity Manual approach to critical lane volumes and degree of saturation, and MUTCD pedestrian timing rules for the walk interval and 3.5 feet per second clearance. Saturation flow uses the US base of 1,900 vehicles per hour of green per lane. Always confirm final timing against your own agency policy.
Is this tool a substitute for a licensed traffic engineer?
No. It is a fast, accurate planning-level tool that follows accepted US methods, ideal for study, preliminary design, and sanity checks. Final signal timing that goes into the field must be reviewed, sealed, and approved by a licensed professional engineer under your jurisdiction’s standards. Field conditions, coordination, and safety judgment all matter beyond the formulas.
Related calculators to pair with this one
Legal disclaimer and editorial transparency
This traffic signal cycle length calculator is provided for educational, study, and preliminary planning purposes only. It applies widely accepted United States methods, including Webster’s optimum cycle formula, the FHWA and Highway Capacity Manual critical-lane approach, and MUTCD pedestrian timing rules, using a base saturation flow of 1,900 vehicles per hour of green per lane. Results are planning-level estimates and are not sealed engineering deliverables.
Actual signal timing that is deployed in the field must be designed, reviewed, and approved by a licensed professional engineer in accordance with your local, state, and federal standards, along with field-measured saturation flow, corridor coordination plans, detection layout, and current agency policy. USCalculators does not assume liability for decisions made from these estimates. Always verify against the authoritative sources: the FHWA Traffic Signal Timing Manual, the Manual on Uniform Traffic Control Devices, and your jurisdiction’s traffic engineering manual.
Editorial transparency: Our methods and constants are drawn from public US government and standards sources, including the Federal Highway Administration and the MUTCD. Formulas were verified against published textbook examples during development. We update our tools as federal guidance evolves. If you spot an issue, we welcome corrections so we can keep the math accurate and trustworthy.