How to Get Support or Contribute to Betaflight
Updated
Betaflight's own site points to two support paths and one contribution path: community channels (a Facebook group of over 30,000 members, a growing Discord server, and third-party YouTube resources) for help, and GitHub for source code and contributions. The project is open source with a review system, and the team states it is always looking for talented contributors. Use the community channels when you have a setup or tuning question; go to GitHub when you want to read, report against, or change the code itself.
Community support channels
The Betaflight site describes the user community as "active and helpful" and names these places to get help:
- Facebook group — over 30,000 members, per the site.
- Discord server — described as growing.
- YouTube — "considerable support resources" made by third parties, not by the Betaflight team.
Because the YouTube material is third-party, treat it as informal guidance rather than official documentation. For anything that affects flight safety, cross-check against the official wiki and firmware resources linked from the site.
What each channel is good for
| Channel | Best for | Note from the site |
|---|---|---|
| Facebook group | Quick questions, build photos, community troubleshooting | 30,000+ members |
| Discord | Real-time back-and-forth | Growing server |
| YouTube (third party) | Walkthroughs and visual setup guides | Made by third parties |
| Betaflight Wiki | Reference material | Listed under the site's main navigation |
Contributing to the project
Betaflight is open source, so you can read the source and contribute on GitHub. The site states the team maintains "a robust review system in order to maintain clean code" and is "always looking for talented contributors."
That means contributions go through review rather than being merged directly — expect feedback and iteration on anything you submit. The site does not publish a contribution guide, coding standard, or issue template on the page summarized here, so check the repository itself for the current process before starting work.
A practical order of operations
- Read the source on GitHub to understand the area you want to touch.
- Check whether the problem or feature is already being discussed before opening anything new.
- Prepare a focused change rather than a broad rewrite — the review system is set up to keep code clean.
- Submit and respond to review feedback.
Related resources on the site
The site's navigation also lists Firmware, Download, Stats, Sponsors, Blog, and Apps, with Blackbox Explorer and the Betaflight App called out separately. If your goal is installing or updating rather than contributing, those download and firmware pages are the relevant entry points, not the community channels.
Hardware questions
If your question is whether a specific flight controller works, the site points to Targets under Support and to the Betaflight Partner program, which provides hardware manufacturer recommendations from the development team. That is a more reliable route than asking in a general community group, where answers vary by build.
What the site does not tell you
The page summarized here does not list response times, whether Discord or Facebook requires an account, or any cost associated with support or contribution. Nothing in the provided material indicates paid support tiers or fees, but absence of pricing information is not confirmation that everything is free — verify on the individual platforms if that matters to you.