You move the stick, the quad responds — but there’s a measurable delay between your thumb and the motor output. That delay is the PID loop’s reaction time, and Feed Forward bridges it by predicting what you’re about to do. Set it too high and the quad overshoots every input. Set it too low and your racing lines feel sluggish. Here’s how Feed Forward actually works and how to tune it for your flying style.
How to Tune Betaflight Feed Forward
Feed Forward sits parallel to the PID controller. While the P-term reacts to an error that already happened, Feed Forward looks at your stick movement velocity (rate of change of the setpoint) and applies motor output preemptively. It’s not correcting an error — it’s anticipating one. This makes it fundamentally different from every other tuning parameter in Betaflight.
Step 1: Understand What Feed Forward Actually Changes
Feed Forward has three gain sliders — one per axis (roll, pitch, yaw). Each slider is a multiplier on the stick movement velocity. At zero, you get pure PID response. At 255, Feed Forward completely dominates — the motors follow your stick directly regardless of what the PID loop thinks.
In practice, Feed Forward values above 150 on roll/pitch feel twitchy and unpredictable. Most racers run between 80-120 on roll and pitch, and 60-80 on yaw. Freestyle pilots often run lower (50-80) because they want the PID loop to smooth out their inputs for cinematic flow.
What happens if you set FF too high: The quad overshoots every stick input. A 90-degree roll becomes 110 degrees, and you have to manually correct back. It feels like the quad is “ahead of you” — you finish the stick movement but the quad keeps rotating for another few degrees. In racing, this means you’re constantly over-correcting through gates.
What happens if you set FF too low: The quad feels “disconnected” from your stick. There’s a perceptible lag between thumb and motor — maybe only 30-50ms, but that’s enough to miss a tight gate entry. The PID loop has to build up error before it reacts, and Feed Forward should have filled that gap.
Step 2: Find Your Baseline Feed Forward Values
Start with Betaflight defaults (FF = 90 on roll/pitch, 0 on yaw in some versions) and make one change at a time:
- Fly a few packs with FF at defaults. Pay attention to how quickly the quad responds to snap inputs — a quick 90-degree roll, a sharp pitch-up to avoid a branch. Note whether it feels crisp or sluggish.
- Increase roll FF by 10 points. Fly the same maneuvers. If the roll feels sharper without overshoot, keep going. If you notice overshoot (the quad keeps rolling after you center the stick), back off by 5.
- Repeat for pitch. Pitch often needs slightly less FF than roll because the moment of inertia is different on most frames.
- Yaw FF is the last slider to touch. Yaw gains need to be lower because yaw authority is entirely torque-based — there’s no aerodynamic damping like on roll and pitch. Start at 60 and work up.
Step 3: Balance Feed Forward with PID P-Gain
Feed Forward and P-gain both produce motor output in response to stick movement, but they interact differently:
- P-gain adds output based on error magnitude — the difference between where the quad is and where you told it to be. P responds to both stick inputs and external disturbances (wind, prop wash).
- Feed Forward adds output based on setpoint velocity — only the stick movement, completely ignoring what the quad is actually doing.
If you increase Feed Forward substantially, you can often reduce P-gain slightly because FF is handling the “stick response” part of the work that P used to do. This reduces oscillation risk from P-gain while maintaining or improving stick feel.
Feed Forward Interaction Reference Table
| Parameter | Default Range | Racer Sweet Spot | Freestyle Sweet Spot | Effect if Over-Tuned |
|---|---|---|---|---|
| Roll FF | 90-100 | 100-130 | 60-90 | Overshoot on snaps, constant micro-corrections |
| Pitch FF | 90-100 | 90-120 | 60-90 | Pitch bounce on sharp stops, altitude instability |
| Yaw FF | 0-60 | 60-90 | 40-60 | Yaw overshoot, “drifting” feel during coordinated turns |
| Roll P-Gain | Frame-dependent | Slightly lower with high FF | Standard with moderate FF | Oscillation on hard stops — reduce FF first, then P |
| Pitch P-Gain | Frame-dependent | Slightly lower with high FF | Standard with moderate FF | Prop wash oscillation — reduce FF before touching P |
What Most Pilots Get Wrong About Feed Forward
Mistake 1: Treating Feed Forward as “Free Responsiveness”
Feed Forward lets you increase stick response without adding P-term oscillation. But it’s not free — high FF reduces the PID loop’s ability to reject external disturbances. When FF dominates, the quad responds to your stick but ignores wind gusts, prop wash, and frame vibrations more.
Consequence: The quad feels amazing in calm conditions on the bench test. Then you fly through your own prop wash in a split-S and the quad oscillates violently because the PID loop’s correction authority has been crowded out by FF.
Fix: Test FF changes in turbulent conditions — fly through your own wake, punch out through prop wash, and do aggressive split-S entries. If the quad oscillates where it didn’t before, reduce FF, not P — the FF is drowning out the PID correction.
Mistake 2: Copying Pro Racers’ Feed Forward Values
Professional racers run high FF because they have the thumb precision to handle it. They’ve done thousands of laps and developed muscle memory for the exact amount of stick correction needed after each input. Copy their values without their practice and the quad will feel uncontrollably twitchy.
Consequence: You overcorrect on every turn, your lines get worse, and you blame the tune when it’s your thumb that needs to catch up.
Fix: Tune FF for your current skill level, not for where you want to be. Increase FF by 10 points per month as your precision improves. It’s a progression parameter, not a destination.
Mistake 3: Ignoring FF on Yaw Entirely
Many Betaflight versions ship with yaw FF at zero. Pilots leave it there because “yaw is different.” But yaw is the axis most limited by stick-to-motor latency — it has zero aerodynamic damping and the slowest natural response. A small amount of yaw FF (50-70) makes slaloms and coordinated turns dramatically more responsive without the penalty of increased yaw P (which causes yaw twitches).
Consequence: Your yaw feels sluggish in technical sections where you need quick direction changes. You compensate by over-yawing and then correcting, wasting energy and looking sloppy on the track.
Fix: Set yaw FF to 60 as a starting point. Fly a slalom course. If you overshoot the exit of each gate, reduce by 10. If the yaw feels disconnected from your thumb, increase by 10.
⚠️ Regulatory Notice: Feed Forward tuning changes your drone’s flight characteristics. All test flights and tuning sessions should be conducted in accordance with the latest 2026 drone regulations in your country or region. Always verify local laws regarding flight altitude, no-fly zones, remote ID requirements, and registration before flying. Regulations vary significantly between the FAA (US), EASA (EU), CAA (UK), CAAC (China), and other authorities. Tuning sessions should be performed in designated flying areas with proper safety protocols.
Feed Forward tuning builds on your existing PID foundation. Our Betaflight PID tuning guide covers the P, I, D fundamentals that Feed Forward supplements. For stick feel optimization, the rates configuration guide covers RC Rate, Super Rate, and Expo — all of which interact with FF. And RPM filtering setup reduces noise in the PID loop, making FF tuning cleaner and more predictable.
Feed Forward shines with a flight controller that has low gyro noise and clean signal processing. The SpeedyBee F405 V4 stack runs an ICM-42688-P gyro with hardware filtering that keeps noise floor below detectable levels even at high FF gain — available at the uavmodel store for pilots dialing in their race tune.