Report clear bugs
Include your system, the version, the steps to repeat the problem and a log file. A well-written report saves maintainers hours.
Behind the familiar window of OBS Studio is a worldwide group of developers, translators, writers and plugin authors. This page maps the OBS Project: where it began, how decisions are made and where a newcomer can plug in.
People often say “OBS” when they mean the application, but the OBS Project is the effort around it. It covers the main source repository, the documentation, the translation work that makes the interface available in dozens of languages, the support forums and the release process that ships new versions to millions of desktops.
The work is organised like many open-source efforts: contributors propose changes, maintainers review them, and an accepted change lands in a later release. Nobody has to ask permission to read the code, report a problem or suggest an improvement.
Because the code is public, anyone can inspect what the program does, and security or privacy concerns can be checked rather than taken on trust. It also means the tool cannot be abruptly paywalled, and that the long tail of unusual capture needs gets handled by people who actually have them.
Dates are kept general; the project’s own pages hold the exact release history.
An original “Open Broadcaster Software” appeared in the early 2010s, aimed at giving ordinary people a no-cost way to stream from Windows.
A fresh codebase was written to be cross-platform and modular, adding macOS and Linux and a proper plugin interface.
As live video grew, the project gained hardware encoders, browser sources, Studio Mode and a larger contributor base.
Features that once needed add-ons, such as a WebSocket control server and virtual camera, became part of the standard program.
You do not need to write C++ to be useful.
Include your system, the version, the steps to repeat the problem and a log file. A well-written report saves maintainers hours.
Help your language stay current as new menus and options appear with each release.
Fix an unclear instruction, add a missing step, or write the guide you wish you had found on day one.
Build a source, filter or output, or beta-test one that is nearly ready and tell the author what broke.
Start with a small, well-scoped fix, follow the contribution rules, and expect honest review feedback.
Answer questions in community spaces. Patient support keeps newcomers from giving up.
Independent authors publish plugins for new capture methods, audio tools, transitions, scene automation and more. They are not part of the core program, so quality and upkeep vary.
Lua and Python scripting lets users automate scene changes, timers and overlays without compiling anything.
A built-in WebSocket server allows other apps, stream decks and web dashboards to drive scenes, sources and recording.
The project relies on voluntary donations and sponsorship rather than ads or a paid version, which keeps the main application free of tracking banners.
It is the open-source community that develops and maintains OBS Studio, including its code, documentation, translations and support spaces.
No. Translation, testing, documentation, support and bug reports are all valuable contributions.
OBS Studio is licensed under the GNU General Public License, which lets you use, study and share the software under the same terms.
Through voluntary donations and sponsorships from individuals and companies.
Yes, the license allows it, provided your derived work stays under compatible open terms.
Every release of the OBS Project is available to download for free. Pick your system and get started.