You plug in a board full of peripherals — GPS, VTX control, camera OSD, blackbox, ELRS receiver, LED strip — and suddenly the F4 flight controller chokes. UART conflicts, CPU warnings in Betaflight, dropped blackbox frames. The processor matters more than most builders realize. Here’s which one you need and why.
The Three Tiers: What Each Processor Actually Means
F4 (STM32F405)
The F4 runs at 168MHz with a single FPU. It’s been the baseline since 2017 and still ships on budget 20×20 stacks and AIOs. At 4K PID loop with bidirectional DShot and RPM filtering, an F4 sits at 40-55% CPU load — workable but tight. Add GPS rescue, LED strip, and blackbox logging at 2K, and you’re nudging 70%. The board doesn’t crash, but you’ll see the “CPU load” warning in the OSD on punch-outs when the gyro data spikes.
The real limitation is UART count. Most F4 boards ship with 3-4 usable UARTs after subtracting the one hardwired to the OSD chip and another to the USB port. GPS + SmartAudio VTX + serial RX = all of them consumed. No room for a compass, telemetry, or camera control.
F7 (STM32F722 or F745)
The F7 is the current sweet spot. 216MHz clock, double-precision FPU, more flash. At 8K PID loop with bidirectional DShot, RPM filtering, GPS, blackbox, and every peripheral enabled, an F7 runs at 25-40% CPU. 5-7 usable UARTs on most boards mean you stop worrying about conflicts.
The jump from F4 to F7 removes the peripheral ceiling. If you’re building a GPS-equipped long-range quad, a cinematic rig with camera control, or anything that needs more than 3 peripherals, the F7 is the minimum.
H7 (STM32H743)
480MHz dual-core. The H7 is overkill for Betaflight in 2026 — the firmware doesn’t utilize the second core. But it runs the full feature set at 8-15% CPU and handles future Betaflight features without breaking a sweat. More importantly, many H7 boards ship with 6-8 UARTs, integrated barometers, dual gyro support, and onboard blackbox flash.
If you build quads that push peripheral limits — dual GPS, dual camera switching, CAN bus ESCs, onboard logging — the H7 buys peace of mind. For 90% of pilots, the F7 is already more than enough.
The UART and Peripheral Reality Check
The spec sheet says “6 UARTs” — but how many are actually free? Here’s what a typical 2026 build consumes:
- UART1: Serial RX (ELRS/Crossfire receiver)
- UART2: VTX SmartAudio or IRC Tramp control
- UART3: GPS module
- UART4: Camera control (Runcam Device protocol)
- UART5: ESC telemetry (on boards without dedicated ESC telemetry pad)
- UART6: Free (rare on F4 boards)
On an F4 board with 4 UARTs, you’re already using soft-serial for the receiver or sacrificing SmartAudio. On an F7/H7 with 6+ UARTs, you have spare capacity for future add-ons.
| Feature | F4 (STM32F405) | F7 (STM32F722) | H7 (STM32H743) |
|---|---|---|---|
| Clock Speed | 168 MHz | 216 MHz | 480 MHz |
| Typical CPU at 8K/DSHOT600+RPM | 60-75% (drops frames) | 25-40% | 8-15% |
| Usable UARTs | 3-4 | 5-6 | 6-8 |
| Bidirectional DShot | Supported, tight CPU | Supported, comfortable | Supported, trivial |
| GPS Rescue + All Peripherals | Borderline | Comfortable | Overkill |
| Onboard Blackbox Flash | Rare | Common on premium boards | Standard |
| Dual Gyro Support | No | Some boards | Common |
| Typical Price (30×30 stack) | $35-50 | $55-80 | $70-100 |
| Best For | Budget 5″ freestyle, whoops | GPS builds, cinematic rigs | Long-range, future-proof builds |
Common Mistakes & How to Avoid Them
Mistake 1: Buying an F4 for a GPS long-range build
The F4 can run GPS rescue, but the CPU load at 8K PID loop with RPM filtering, GPS, blackbox, and SmartAudio hits 70-80%. Under heavy stick input, the gyro data rate spikes and the PID loop stutters — which means your GPS rescue might not arm when you need it. Fix: For any build with GPS rescue as a primary safety feature, use F7 minimum.
Mistake 2: Thinking “more MHz = better tune”
A quad on an H7 doesn’t fly better than one on an F7 with identical settings. Betaflight’s PID loop runs at the configured rate regardless of processor headroom. The extra clock cycles just sit idle. Fix: Spend on UART count and board quality (gyro type, voltage regulation), not raw MHz.
Mistake 3: Not checking which UARTs are inversion-capable
SBUS and some serial protocols require hardware inversion. On many F4 boards, only UART1 has a dedicated inverter. If you wire an SBUS receiver to UART3, it won’t talk. F7 and H7 handle inversion in software on any UART — another reason to go F7 if you’re mixing peripherals. Fix: Check the board’s pinout diagram before soldering. If using F4 with SBUS, wire to the dedicated SBUS pad, not a generic UART RX.
Mistake 4: Confusing flash size with performance
The H743 has more onboard flash memory. This matters for blackbox logging — but not for flight performance. A 512KB blackbox log on an F7 takes longer to download but flies identically. Fix: Evaluate based on UART count and peripheral support, not flash specs.
⚠️ Regulatory Notice: Flight controllers with advanced features like GPS rescue, dual compass, and autonomous return-to-home should be operated in accordance with the latest 2026 drone regulations. Always verify local requirements for autonomous flight features, visual line of sight (VLOS) rules, and remote ID compliance. Regulations vary significantly between the FAA (US), EASA (EU), CAA (UK), CAAC (China), and other authorities.
The processor you choose directly affects how well RPM filtering runs — see our Betaflight RPM filter setup guide for the full picture. When pairing your FC with a receiver, our Crossfire vs ExpressLRS comparison covers which protocol each processor handles best.
If you’re shopping for a flight controller that handles every peripheral without compromise, the SpeedyBee F7 V3 stack ships with 6 UARTs, Bluetooth configuration, and onboard blackbox — the board we reach for on 90% of 5-inch builds.