Explainers · 2026-07-11 · Patreon guide

Patreon for FPV drone creators: tiers, PID tuning documentation, iOS rates, and the Apple Tax in 2026

FPV drone Patreons retain patrons because the YouTube video shows the flight but not the .diff file: a Betaflight tune that produces locked-in freestyle behavior on a specific 5-inch quad is a configuration file that a patron can paste into the CLI in 30 seconds — but without the tune file and the build documentation that contextualizes it, the patron cannot extract the useful knowledge from watching the flight footage alone. The FPV audience has a high desktop-use component (Betaflight Configurator, blackbox log analysis, hardware research), which keeps iOS rates below the action-sport average and moderates Apple Tax exposure compared to pure-lifestyle creator niches.

The FPV drone creator subtypes

FPV racing drone technical educators: PID tuning, motor selection, and ESC firmware

FPV racing drone technical educators are the most technically demanding creator type in the FPV space, documenting the flight controller configuration, hardware selection reasoning, and filtering approach that transforms a raw build into a precisely controllable racing machine. Their audience is the intermediate-to-advanced FPV pilot who understands that a bad tune is the most common cause of poor flight performance and who wants documented configuration files rather than generic advice.

PID tuning is the core technical subject. The Betaflight PID controller consists of three terms for each axis (roll, pitch, and yaw). The P term (proportional) produces a correction force proportional to the current error — the difference between the commanded rotation rate and the measured rotation rate. Too high a P term causes oscillation; too low causes sluggish response. The I term (integral) accumulates error over time and corrects for sustained bias — wind drift, motor imbalance, frame flex — that the P term alone cannot correct. Anti-windup limiting prevents the I term from accumulating during conditions where the motor cannot physically respond (throttle cutoff during a flip). The D term (derivative) damps the response to prevent overshoot from the P term correction; it acts on the rate of change of error, not the error itself. Dterm must be filtered because it amplifies high-frequency noise in the gyroscope signal. The RPM filter uses bidirectional DSHOT telemetry to measure each motor’s actual RPM and compute the motor harmonic frequencies (fundamental frequency = motor RPM × motor pole count ÷ 2, expressed in Hz) dynamically, applying notch filters at each harmonic to remove motor-generated vibration from the gyro signal without affecting control bandwidth. Dterm low-pass filter frequency (LPF) sets the cutoff below which all frequencies pass; higher cutoff preserves D term responsiveness but requires adequate RPM filter performance for noise rejection.

Motor selection documentation: the Kv rating (RPM per volt) determines the mechanical advantage tradeoff between torque and speed for a given propeller diameter. For a 5-inch 3-blade racing propeller, a 2306 2450 Kv motor on 4S battery produces a high top-end RPM suitable for gates and straightlines; a 2306 1700 Kv motor on 6S battery produces higher torque at lower RPM for a different throttle response character. Stator volume (stator diameter mm × stator height mm × π/4, expressed in mm³) is a proxy for motor power output capacity; a 2306 stator has 25 mm diameter and 6 mm height, giving approximately 2,945 mm³. Document for each featured build: motor brand and model, stator specification (diameter × height), Kv rating, battery cell count (4S or 6S), and the propeller specification (brand, diameter inches, pitch inches, blade count) that the tune was developed with. Changing propeller specification without re-tuning affects motor harmonic frequencies and may require RPM filter recalibration.

ESC firmware documentation: BLHeli_32 is the dominant closed-source ESC firmware for high-performance FPV; AM32 is the open-source alternative with similar features. Document: firmware version, DSHOT protocol selection (DSHOT600 is standard for high-frequency setups; DSHOT300 for longer wire runs or older F4 flight controllers with limited processing bandwidth), bidirectional DSHOT status (required for RPM filter telemetry), motor timing advance setting, and demag compensation setting. The ESC configuration affects motor efficiency and heat characteristics; a high-timing-advance setting on a low-inductance motor can reduce efficiency and increase heat.

Propeller selection is the third axis of technical documentation. Pitch is the theoretical vertical advance per revolution in inches — a 5.1 × 4.8 propeller advances 4.8 inches per revolution at zero slip. Higher pitch increases top speed but reduces efficiency at low throttle. Diameter determines the disc area and thus the static thrust capacity at a given power. The efficiency tradeoff is real: larger diameter at lower pitch is more efficient (lower disc loading) but less agile; smaller diameter at higher pitch is more responsive and generates less drag in forward flight but requires more power. APC propellers are common in testing for their consistent quality; HQProp 5.1 × 4.8 (5-inch diameter, 4.8-inch pitch) are popular for freestyle; Gemfan Hurricane props are common in racing.

Tier structure: Workshop ($7–10/month, flight video early access, Discord with channels by frame size — 3-inch, 5-inch, 7-inch — and discipline), Tune Files ($18–28/month, monthly Betaflight .diff tune file download with complete build documentation — the core retention tier), Blackbox Review ($45–65/month capped 6–8, patron uploads a Betaflight blackbox log and receives documented tune analysis with specific adjustment recommendations).

FPV freestyle and cinematic creators: line documentation, LUTs, and tune file sharing

FPV freestyle creators make artistic flight content — flowing line sequences through architectural environments, forests, or skateparks — and cinematic FPV creators shoot production-quality aerial footage for commercial and creative purposes. Their Patreon value proposition is less technical than the racing subtype but more varied: tune files contextualized by flying style, color grade LUT files for the specific camera system featured, line documentation for specific locations, and equipment configuration guides for the camera and video transmission systems used.

Line documentation for freestyle flight is analogous to the route documentation a trail runner might share: a GPS overlay showing the flight trajectory through a location, the throttle curve recording (the throttle input trace exported from a Betaflight blackbox log, showing the characteristic low-throttle-during-flow / high-throttle-during-power-moves pattern of a skilled freestyle line), camera angle settings (the camera tilt angle from horizontal in degrees, which determines the visual horizon line in the footage and the natural flight speed for the framing), and one or two notes on the specific challenges of the location (a section where tight clearances required a specific approach angle, a moment where the creator deliberately desaturated throttle to hold a gap exit). This documentation has low replicability — the patron cannot fly the same line in the same location — but high aspirational value: it shows the craft decision-making behind what looks like pure instinct in the footage.

Color grade LUT files are the most broadly applicable deliverable for cinematic FPV creators. A LUT (look-up table) is a color transformation file in .CUBE format (DaVinci Resolve standard) that maps the flat or log color profile from a camera sensor to a finished color grade. Document for each LUT release: the source camera and recording profile (GoPro Hero with Flat color profile, Caddx Volta in Vivid or Flat mode, DJI O3 Air Unit in D-Log M, RunCam Split 4K), the intended output (a specific visual aesthetic described in 1–2 sentences), the lighting conditions the LUT was calibrated for (overcast diffuse light vs direct sun vs golden hour), and any exposure adjustments required before applying the LUT (the LUT assumes a specific exposure range; underexposed footage will have incorrect shadow behavior after the LUT is applied).

Tune file sharing for freestyle uses the same Betaflight .diff format as the racing subtype, but the documentation emphasis is different. Freestyle tunes are optimized for different behavior than racing tunes: more D term for propwash suppression during hard stops and direction reversals, lower P term response aggressiveness for smoother flow, and I term settings tuned for the characteristic weight and inertia of the specific build. Document: whether the tune is optimized for props-in or props-out orientation, the specific flying style it was developed for (technical flow vs power freestyle vs cinematic smooth), and the battery weight that was used during development (a heavier or lighter battery changes the quad’s inertia and requires different PID settings for the same feel).

Equipment configuration documentation covers the video transmission system selection: DJI O3 Air Unit documentation (link mode, distance vs latency vs resolution tradeoffs — 1080p/100fps mode vs 1080p/60fps mode vs 810p/120fps mode, the link budget in dBm at various distances), analog VTX system documentation (transmitter power in mW, antenna polarization, frequency band and channel selection for multi-pilot flying), and RunCam Split configuration (recording resolution, stabilization on/off, color profile selection). The DJI O3 latency vs analog VTX latency comparison (∼30–40 ms for O3 vs ∼14 ms for analog under typical conditions) is a technical documentation point that patrons use in hardware selection decisions.

Tier structure: Cinematic ($8–12/month, early video access, LUT file download pack per month, Discord), Full Config ($20–30/month, monthly LUT pack plus .diff tune file with build documentation and line notes for each featured location), Film Consult ($50–75/month capped 5–8, patron submits raw footage and receives color grade notes and equipment configuration feedback).

FPV fixed-wing and long-range creators: ArduPlane, wing design, and VTOL

Fixed-wing FPV creators occupy a smaller but highly engaged niche focused on long-distance autonomous or semi-autonomous flight using fixed-wing aircraft running ArduPlane or similar autopilot firmware. Their audience is the technically sophisticated pilot who is building toward kilometer-range cross-country flights, autonomous waypoint navigation, or VTOL (vertical take-off and landing) hybrid aircraft capable of hovering at departure and destination while covering ground efficiently in forward flight. The documentation depth required is the highest of the three FPV subtypes.

ArduPlane autopilot configuration is the core documentation subject. ArduPlane runs on flight controllers supported by the MAVLink protocol and is configured via Mission Planner or QGroundControl ground station software. The complete parameter set for a fixed-wing build is exported as a .param file, which can be loaded into another aircraft with equivalent hardware — but without documentation of which parameters were changed from defaults and why, the file is opaque. Document the attitude controller PID values (ROLLCONTROLLER and PITCHCONTROLLER P, I, and D terms, which determine how aggressively the autopilot corrects pitch and roll attitude error), the airspeed limits (ARSPD_FBW_MIN: the minimum airspeed in m/s at which the autopilot maintains control — set this too low and the wing stalls in stabilized modes; ARSPD_FBW_MAX: the maximum allowable airspeed for the specific wing), and the navigation controller parameters (WP_RADIUS for waypoint acceptance radius in meters, LOITER_RADIUS for loiter orbit radius). The PIDFLC (PID with feedforward and limit compensation) attitude control loop in ArduPlane also includes the L1 navigation controller for lateral track following, which has a single tuning parameter: L1_PERIOD, the look-ahead period in seconds that determines how aggressively the aircraft tracks a straight-line route.

Wing design documentation: aspect ratio AR = b² ÷ S, where b is the wingspan in meters and S is the wing area in square meters. High AR wings (AR > 8) are efficient for long-range cruise but have poor roll rate and are structurally demanding; low AR wings (AR < 5) are agile and structurally simpler but less efficient. Clark Y airfoil (a classic flat-bottom section with moderate camber) produces good lift at low Reynolds numbers (the Re range of most FPV wings, Re = 100,000–500,000 based on chord length and airspeed) and is easy to hand-build. NACA 4412 (4% max camber at 40% chord, 12% thickness) is a symmetrically proportioned cambered section with documented Cl/Cd polars: at the typical cruise angle of attack (3–5°), NACA 4412 produces approximately Cl = 0.8 and Cd = 0.016, giving a lift-to-drag ratio of 50 in clean configuration. Document wing airfoil selection, chord length, span, aspect ratio, construction material (EPO foam, balsa-and-fiberglass, carbon fiber), and CG location as percentage of mean aerodynamic chord (MAC) — typically 25–33% MAC for neutral stability.

Long-range radio link documentation: ExpressLRS (ELRS) 2.4 GHz uses frequency-hopping spread spectrum (FHSS) and is the dominant long-range RC link in FPV. Link budget calculation in dBm: transmitter output power (dBm) + transmitter antenna gain (dBi) − free-space path loss (dB at the specific distance and frequency) + receiver antenna gain (dBi) = received signal level (dBm), which must exceed the receiver sensitivity by at least 10 dB for reliable link. At 1 km range at 2.4 GHz, free-space path loss is approximately 100 dB; a 100 mW (20 dBm) transmitter with a 3 dBi antenna and a −112 dBm sensitivity receiver has approximately 35 dB of link margin — adequate for reliable control. 915 MHz link systems have ∼10 dB lower free-space path loss at the same distance, yielding longer practical range but requiring larger antennas and more regulatory compliance overhead. Document the ELRS packet rate (250 Hz, 150 Hz, or 50 Hz — higher rates give lower latency but reduce range at a given transmitter power), the telemetry ratio (the fraction of packets used for downlink telemetry vs uplink commands), and the operating frequency and power limits for the jurisdiction.

VTOL transition documentation for tilt-rotor or fixed-tilt hybrid aircraft: the hover-to-forward-flight transition requires a specific airspeed schedule (the minimum airspeed at which the wing generates enough lift to support the aircraft without rotor thrust, minus a safety margin, defines the transition completion threshold). Document the transition altitude AGL, the transition forward airspeed schedule (VTOL_TRANS_DECEL and VTOL_FW_MIN_THROTTLE parameters in ArduPlane VTOL), and any observed transition behavior (pitch authority during transition, the airspeed at which the autopilot committed to wing-borne flight).

Tier structure: Long Range ($10–15/month, flight video early access, mission planning posts, Discord with channels by autopilot firmware and airframe type), Param Files ($22–35/month, ArduPlane .param file export per build with complete documentation — changed parameters from defaults, wing design specifications, radio link budget calculation), Build Review ($55–80/month capped 4–6, patron submits build specifications and receives documented review of wing design, autopilot configuration, and radio link budget).

Tune file and configuration documentation mechanics

The document that accompanies every Betaflight .diff tune file should be structured in four sections: (1) the build specification (every hardware component relevant to the tune — flight controller model and firmware version, motor model and Kv, propeller brand and specification, battery cell count and capacity, total flying weight); (2) the PID values explicitly listed for all three axes, even though they are also in the .diff file — a patron reading the documentation post before downloading should be able to compare the P/I/D values to their own current tune without opening the Betaflight Configurator; (3) the filter configuration (RPM filter enabled/disabled with motor pole count, Dterm LPF cutoff frequency, gyro LPF type and cutoff frequency if changed from default); and (4) the flying-style context (what specific behavior this tune optimizes for, what the creator noticed it improved or required tradeoff on, and which motor or propeller substitutions are likely to require re-tuning).

This four-section structure applies to all downloadable configuration deliverables across FPV creator subtypes: ArduPlane .param files need the airframe specification, changed-parameter list with rationale, link budget calculation, and flight test notes; VTOL configuration files need the additional transition-schedule documentation section. LUT files need the source profile, target aesthetic, calibration lighting, and exposure adjustment notes. The common principle: the downloadable file is useful; the documentation makes it educational.

For freestyle and cinematic creators, the location-specific nature of line documentation creates a unique retention mechanism: the patron who has followed 12 months of line documentation posts has built a referenced library of flight locations, approaches, and creative decisions that forms a coherent body of work — not just isolated tune files. This makes long-term patrons more likely to stay subscribed than patrons who joined for a single download.

iOS rates and the Apple Tax

FPV drone creator iOS rates are below the action-sport and maker average because the FPV audience has a substantial desktop computing component. Betaflight Configurator runs on desktop; blackbox log analysis (Blackbox Explorer) runs on desktop; hardware research and purchasing for flight controllers, ESCs, motors, frames, and video transmission systems is heavily desktop-based. YouTube FPV drone content: 48–68% iOS — racing-focused and tuning-focused content sees the lower end of this range (48–58% iOS) while more visual freestyle and cinematic content sees higher iOS rates (58–68%). Instagram FPV: 68–78% iOS. TikTok FPV: 72–82% iOS.

Frequently asked questions

Related: Patreon for technology creators · Patreon for electronics creators · Patreon for 3D printing creators · How the Apple Tax works · All explainers