Twitchy quad: what causes it and what helps
A twitchy FPV quad, or one that wobbles in the air, can have very different causes, and each one needs a different fix. This guide helps you figure out which one it is. The facts come from the Betaflight documentation and source code; fpvrates measures the rates part for free on your own blackbox log, the recording your quad makes in flight. You switch it on in the Betaflight App (how to).
The self test
Fly one pack and pay attention to when the twitching happens. That already narrows the cause down a lot:
- It shakes, buzzes or wobbles even when you don’t move the sticks.not the rates
That’s not the rates: with the stick centered they ask for no rotation. Check the props first (nicks, cracks, tight), then motors and screws. If that doesn’t help, it’s PIDs and filters; there are tools like FPVtune and PIDtoolbox for that.
- Small stick movements turn into big swings, you keep correcting back and forth.fpvrates helps
Typical of rates that are too sensitive around center, or of a curve that suddenly gets steep in the middle of your normal flying. That’s exactly what fpvrates measures in your log, and it suggests a curve that fits your stick. If it jerks mainly on fast stick moves, feedforward can play a part too.
- Flips and rolls are too slow or too wild for you.fpvrates helps
That’s the rotation rate at full stick, “max” in Betaflight. With the Tuning Pass you tell the result whether the speed is too slow or too fast, and the suggested rates adjust it.
- It jumps up when you add throttle, holding height is hard.free check shows it
That’s the throttle curve and the throttle settings, not the rates. The free check shows your throttle curve and where your throttle sits in flight; there are no suggested settings for it yet.
- You fly in angle mode: the quad levels itself.acro first
Then the self-leveling mostly decides how it reacts, and fpvrates can’t measure what you need on the stick. Learn acro in an FPV simulator (which sims work and how to carry over your rates: guide Rates in the simulator) and come back with an acro log.
Twitchy mainly when you steer? Then measure it on your log: the free check shows how your rates fit your stick. No account, the file stays with you.
No log yet? See a real example · Turn on logging, with pictures
For your next flying day
- Betaflight App, Blackbox tab: logging device onboard flash or SD card, logging rate 1 kHz
- RC Commands, Setpoint and Gyro on, then “Save and reboot”
- Fly 3 to 5 packs of normal acro
- Then get the log off the quad and drop it into the free check
1. The rates: the center is too sensitive
The rates set how fast the quad rotates at which stick position. Since Betaflight 4.3 the docs say: “Starting from 4.3, Actual Rates will be the new Betaflight default.” With Actual rates the first value is called centerSensitivity in the source code: in the formula in rc.c the rotation rate rises at center stick by exactly this value. If it is high, even a small thumb movement becomes a fast rotation, and you keep correcting back and forth.
The docs on the new defaults show how big the difference can be: “the new defaults are softer in the center (center sensitivity of 70, compared to about 200 in Betaflight's old defaults), and more responsive further out.” You can see which rates your quad runs in the Betaflight App under PID Tuning → Rate Profile Settings, or in the free check.
There is a second rates cause: a curve that suddenly gets steep in the middle of your normal flying. Turns and gaps fly smoothly until you push a bit further and the quad suddenly reacts much more strongly. Expo moves this rise outwards: in the formula, more expo gives weight to the part that only grows close to full stick.
What helps: don’t copy other pilots’ rates, measure how you use your stick. That is exactly what fpvrates does: the free check shows you how much stick travel stays unused and how much more strongly your quad reacts at the end of your normal flying than in the center. More in Setting up Betaflight rates and Actual Rates explained.
2. Feedforward: jerks on fast stick movements
Feedforward makes the quad respond faster to stick movements. The docs: “The faster the sticks are moving, the more FeedForward we get.” That makes it direct, but there is a downside: “However, it accentuates even the tiniest of RC inputs, and can make for twitchy flight and jerkiness in HD video.” The docs say this about older versions: since Betaflight 4.3, built-in jitter reduction strongly attenuates feedforward on slow stick moves (default factor 7). On fast, jerky inputs feedforward stays a candidate.
For beginners in angle mode the docs have their own tip: “If you're a beginner and you find Level too twitchy, reduce the feedforward value in the PIDs.” That tip comes from the Betaflight 4.3 tuning notes. In 2026.6.2 the feedforward value in PID Tuning no longer acts in angle mode: according to the source code (pid.c) a separate value applies there, angle_feedforward. The app has no field for it, only the CLI does.
Important: don’t change feedforward and rates at the same time, otherwise you don’t know what made the difference. fpvrates measures the rates curve; feedforward is not part of the suggested rates. Every feedforward setting with its default, and how feedforward ties into your rates: Understanding Betaflight feedforward.
3. Radio and sticks: a restless signal
Your stick movement does not reach the flight controller as a smooth line. The docs: “Since RC data comes into the flight controller in 'packets', we actually get a series of sudden steps coming in.” Betaflight smooths these steps with RC smoothing. About old gimbals and shaky thumbs the docs say: “high level RC smoothing (auto smoothing of 90 or higher) will attenuate the erratic behavior of old gimbals or 'thumb shake'.”
What helps: in the Betaflight App, check in the Receiver tab whether the bars stay still when you let go of the sticks. If they jump, the twitching comes before the rates, from the radio or the radio link.
4. Shaking without stick input: props, motors, PIDs
If the quad shakes, buzzes or wobbles although you don’t move the sticks, it is not the rates. In acro mode they ask for no rotation with the stick centered: in the formula in rc.c stick 0 gives exactly 0 °/s, whatever values are set.
For random wobbles in HD footage, the docs name typical mechanical causes: “Usually the frame is too soft or flexy, or it is being shaken by slightly out of balance props or worn bearings.” And: “bent props make the motors really hot really quickly”. Very hot motors after a short flight are a warning sign.
If the mechanics are fine, it is about PIDs and filters. A PID guide in the Betaflight docs puts it like this: “If P is too high, the quadcopter becomes too sensitive and tends to over-correct, eventually it will cause overshoots, and you will have high frequency oscillations.”
What helps: change the props first (nicks, cracks, tight), then check motors and screws. For PIDs and filters there are tools like FPVtune and PIDtoolbox. fpvrates deliberately does no PID tuning. If single motors twitch or stutter, go on with section 7.
5. Throttle: it jumps up or sinks
If the quad jumps up when you add throttle and holding height is hard, that is the throttle curve and the throttle settings, not the rates. From Betaflight 2025.12 the throttle curve is built around a hover point: thr_mid is the stick position, thr_hover the throttle at that point, thr_expo flattens the curve there. On top of that there is throttle boost, per the docs: “Transiently boosts throttle with faster throttle inputs, providing a more immediate throttle response.”
What helps: the free check shows your throttle curve from the log and where your throttle really sits in flight. There are no suggested throttle settings yet.
6. Angle mode: the quad levels itself
In angle mode you don’t command a rotation rate but an angle. The docs: “In this auto-leveled mode the roll and pitch channels control the angle between the relevant axis and the vertical, achieving leveled flight just by leaving the sticks centered.” In acro mode, on the other hand: “the multicopter does not level on its own if you center the pitch and roll sticks on the radio.”
The rates still matter a bit in angle mode. The source code (pid.c) says: “We now use Acro Rates, transformed into the range +/- 1, to provide setpoints”. So the shape of your curve helps decide how far the quad tilts at which stick position, the max does not. How fast it rotates is decided by the self-leveling. That is why fpvrates can’t measure from angle flights what you need on the stick.
What helps: the feedforward tip from section 2. And acro as the next step: practice in an FPV simulator with your radio, then fly three to five packs of acro with the real quad and drop the log into the free check.
7. Motors twitching: ESC protocol, DShot and the motor test
If single motors twitch or stutter, for example when arming or while hovering, look at the ESCs and motors. In the Betaflight App (2026.6.2) everything you need is in the “Motors” tab, in the “ESC/Motor Features” box:
- “ESC/Motor protocol”. The docs: “DShot is standard for modern builds and provides the best flight performance and features.” About older protocols such as PWM, Oneshot or Multishot they say: “Analog protocols require two-point calibration, are susceptible to noise, and can only provide telemetry over an additional serial connection.” The app itself warns: after changing the protocol, remove the props before connecting a battery for the first time, because a protocol your ESCs don’t support can spin the motors up right away.
- “Bidirectional DShot” and “Motor poles”. With Bidirectional DShot every ESC reports its RPM back to the flight controller. The RPM filter needs that, and according to the app it only works if “Motor poles” is right as well: the number of magnets on the motor bell.
- Motor test without props. The docs: “Always remove props before connecting a battery and testing motors.” Then switch on “I understand the risks …” in the same tab and spin up each motor on its own with its slider. With Bidirectional DShot each motor shows its RPM (“RPM:”) and the error rate of the telemetry (“Err:”). The docs on the error rate (called “E” there): “Will show errors if the ESC is not powered. A powered ESC should show 0% or very close to 0% errors. Error rates of 1% or more usually indicate a hardware problem.”
- ESC firmware. About BLHeli_32 the docs say: “Stuck motors, hot motors and unexpected behavior have been observed in BLHeli_32 releases after 32.7.”
What helps: the mechanics from section 4 first (props, bearings, screws), then protocol, Bidirectional DShot and the motor test as above. The free check on fpvrates measures the rates, not ESCs and motors. If the quad won’t arm at all, the guide Quad won’t arm: all arming flags explains what each flag means and how to fix it.
How to measure it on your log
You don’t have to guess whether it’s your rates. Switch on logging in the Betaflight App, fly three to five packs of acro and drop the log into the free check. Without an account it shows you how you use your stick, how much stick travel stays unused, how evenly your curve rises and where your throttle sits. How to get the log is in Setting up and reading out the blackbox log.
Last updated: Nov 13, 2026