logo

betaflight/betaflight-configurator

Cross platform configuration and management application for the Betaflight firmware

View on GitHub ↗Jump to charts ↓Open shareable report →

betaflight/betaflight-configurator has 3k+ stars and 1k+ forks on GitHub, is written in TypeScript, and was last pushed on Oct 16, 2026. Data as of . Signed-in members get hourly updates — create a free account.

Summary Information

Updated 1 hour ago
Type:ApplicationCategory(s):Embedded & IoTRobotics & Autonomous SystemsSystems, Hardware & HPC
Added to GitGenius on September 20th, 2026
Created on June 8th, 2016
Open Issues & Pull Requests: 71 (+0)
GitHub issues: Enabled
Number of forks: 1,150
Total Stargazers: 3,334 (+0)
Total Subscribers: 158 (+0)

Repository Insights (GitGenius)

Median issue/PR response: 4.6 hours
Mean response time: 49.0 days
90th percentile: 28.9 days
Tracked items: 306

Most active contributors

Sign in to see contributor activity.
Sign in

Related repositories by overlapping contributors

Maintainer activity

5 people did triage or write work on this repository in the last 12 months.

Counts unlabeled, assigned, unassigned, milestoned, demilestoned, locked, unlocked over the last 12 months. These are issue and pull request events that require triage or write permission. Commits and code review are not counted. labeled and renamed are excluded because GitHub issue forms record the issue author as the actor. Figures from October 18, 2026. This count is not comparable across projects: each project's automation decides which of these events a person emits. How this is counted.

How this project is maintained

About 3% of issues opened in the past year have never received a reply. 79% of open issues come from outside the core team, so the backlog reflects real-world use rather than internal planning. Work labelled "Inactive" is answered fastest, typically in about an hour, while "Feature Request" waits about 24 hours. 88% of issues opened in the past year have been closed, leaving a working backlog. Three people close 82% of everything that gets resolved.

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 25
New in 7 days: 4
Closed in 7 days: 5
Avg open age: 272 days
Stale 30+ days: 8
Stale 90+ days: 4

Recent activity

Opened in 7 days: 3
Closed in 7 days: 2
Comments in 7 days: 6
Events in 7 days: 12

Top labels

  • Template: Bug (95)
  • BUG (85)
  • Feature Request (54)
  • Inactive (42)
  • Template: Feature Request (28)
  • Cleanup (9)
  • enhancement (6)
  • Pinned (4)

Most active issues this week

Sign in to see which issues are moving.
Sign in
Explore full issue details

Detailed Description

Betaflight Configurator is a cross-platform configuration and management application for the Betaflight flight control firmware.

The tool addresses the need to configure and manage Betaflight firmware running on flight controllers without requiring command-line interaction or manual firmware editing. It provides a graphical interface that allows users to adjust flight parameters, calibrate sensors, update firmware, and monitor real-time telemetry from their aircraft. The application communicates directly with Betaflight-compatible flight controllers over serial connections, translating user input into firmware commands.

Betaflight Configurator is essential for anyone flying quadcopters or other aircraft using Betaflight firmware. It suits hobbyists and professionals who need intuitive access to flight controller settings without deep firmware knowledge. The tool is particularly valuable for users who want to tune PID values, configure motor outputs, manage receiver protocols, and perform pre-flight checks through a visual interface rather than text-based configuration files.

The project maintains steady development activity with regular commits addressing bug fixes, feature additions, and compatibility updates. The codebase receives ongoing refinement to support new Betaflight firmware versions and flight controller hardware. Community contributions are actively integrated, indicating responsive maintenance of pull requests and issues. The project demonstrates consistent engagement with its user base through issue resolution and feature requests.