openFrameworks: the gap between the nightly you download and the stable you build
openFrameworks is a community-developed cross platform toolkit for creative coding in C++.
At a glance
- What is it?
- openFrameworks ships two different products from one repository, master and stable, and the gap between them is wider than the version numbers suggest. A git clone is also not a working copy: it carries no libraries and no project files.
- Who is it for?
- Take the packaged nightly or stable release if you want to draw something this week, and only work from the git repository if you are prepared to fetch per-platform libraries and generate project files yourself. Before committing to a version, decide whether you can live with the stable branch still pointing at 0.12.1 from 2025-05-02 while master moves, and remember that a project you move up or down a directory will break its relative paths.
- Can I use it commercially?
- Check first. The repository uses a licence we do not classify automatically, so read its LICENSE file before any commercial use.
- Is it still maintained?
- Yes. The repository last received commits 2 days ago.
- What is it written in?
- Mainly C++, according to GitHub's language statistics.
Answers come from the project's GitHub data, last synced on November 13, 2026, and from our analysis. They are not legal advice.
Star history
- openframeworks/openFrameworks10,465 ★ · +39
| Repository | 2026-09-16 | 2026-11-13 |
|---|---|---|
| openframeworks/openFrameworks | 10.4k | 10.5k |
39 Stars in the last 58 days, measured from the daily GitHub snapshot. Compare with other projects
Editorial analysis
Master and stable ship two different products
The build status section is split by branch, and each branch has its own download destination. Master contains the newest, most recently updated code and is packaged into the Nightly Builds section of openframeworks.cc/download, while the stable branch carries the code for the last stable release and is packaged into the downloads area at the same site. The release list makes the distance concrete: 0.12.1 was published on 2025-05-02, 0.12.1-RC1 on 2025-04-16, and the nightly release was published on 2026-11-03, while the repository itself last received a push on 2026-11-02. That means the last stable version is well over a year older than the ongoing work, and anyone who wants the recent fixes is effectively choosing nightly over stable. The link at the top of the README goes straight to the nightly release specifically to avoid submodule cloning, which is the same problem the developer section raises later.
The Git clone carries no libraries and no project files
Two of the differences between the git repository and a release are stated outright. First, there are no external dependencies in the repository, and you download them with the download_libs.sh script that sits in each platform folder inside scripts. Second, the repository has no project files for the examples, because they are generated automatically for each release using a tool in apps/projectGenerator/. The examples themselves are large: the top level of examples/ carries 3d, android, communication, computer_vision, events, gl, gles, graphics, gui, input_output, ios, math, shader, sound, strings, templates, threads, tvOS, utils, video and windowing, alongside its own README and .gitignore. None of those directories is buildable on arrival. The practical sequence is fixed: clone, run the per-platform downloader, then generate project files.
Self-contained releases break when you move a project one level
OF releases are designed to be self-contained, and that design choice produces a common error. Because each release is self-contained, there is extensive use of local file paths such as ../../../ throughout the tree. The README names the mistake directly: taking a project and moving it a level below or above where it used to be compared to the root of OF breaks links such as ../../../libs. The same self-containment also means you cannot mix different releases of OF together, so each one, 0.8.0 and 0.8.1 for instance, has to stay in its own place on disk. Projects may generally work from release to release, but that is explicitly not guaranteed. For anyone sharing work this is the practical edge: a project that compiled on your machine is tied to the directory depth and the release it was built against, so version control and machine setup have to move together.
The Project Generator hides bulk work behind Advanced Options
New projects come from a GUI tool, and the projectGenerator folder is only present in packaged releases, which is one of the listed differences between the two. Regenerating the examples is a two-step interaction in that tool rather than a plain menu item: you enable Advanced Options in the settings tab, then use Update Multiple to update the projects for the examples folder path in the repository. The generator itself is a submodule inside the OF repository, and the two commands given for setting it up are:
git submodule init
git submodule updateBoth run while you are inside the openFrameworks repository. Per-platform detail and the Project Generator documentation sit behind docs/table_of_contents.md.
Six build targets are listed, and the Android row is commented out
The build status grid covers Windows MSYS2, Windows Visual Studio, Linux 64 and Arm, Emscripten, macos, and iOS and tvOS, with a CI badge for master and one for stable on every row. An Android Arm7 row exists in that grid as well, but it is commented out in the README's markup, so no build status is published for Android even though examples/android is one of the example directories in the repository. Read that as what it is rather than as a verdict: Android example code is present and its status is simply not reported. Emscripten is the row worth noting separately, since it is the compile-to-web path and it is tracked in the same grid as the native targets. Per-platform setup instructions are not in the README itself, they are linked from openframeworks.cc/download, and the docs folder holds platform notes such as osx.md.
export exists on some systems only, which decides where your DLLs land
The folder layout does more than organise files, it encodes where compiled output belongs. addons holds functionality that is not part of the core, libs holds the libraries OF uses including the openFrameworks core itself, apps is where your own projects go, and examples holds the projects that show you how to use OF. Then there is export, described as being for DLLs and dylibs that need to be put in each compiled project, and the same sentence marks it as present on some systems. The remaining folders are scripts, which holds the templates and small per-platform automation scripts, and other. Docs and community channels are separate: docs carries usage and per-platform notes, the forum and Slack handle questions, and a developer mailing list exists for work on the future of OF.
Semantic Versioning only becomes strict at 1.0.0
openFrameworks uses Semantic Versioning, and the README attaches a condition to that claim: strict adherence will only come into effect at version 1.0.0. Until then the version numbers describe intent without guaranteeing it, and with stable still sitting on 0.12.1 from 2025-05-02 while master moves on, you should not assume a master build is a superset of the stable one in any ordered sense. Licensing is the other thing to check before you build anything on this. The license field in the repository metadata reads NOASSERTION, meaning no standard identifier is asserted, while the tree does contain a LICENSE.md file and the README describes the project as free software. Read LICENSE.md directly for the terms rather than inferring them from the README's phrasing or from what similar creative coding toolkits use.
Editorial conclusion
Take the packaged nightly or stable release if you want to draw something this week, and only work from the git repository if you are prepared to fetch per-platform libraries and generate project files yourself. Before committing to a version, decide whether you can live with the stable branch still pointing at 0.12.1 from 2025-05-02 while master moves, and remember that a project you move up or down a directory will break its relative paths. If you plan to ship, read LICENSE.md, because the repository metadata asserts no standard license identifier.
Frequently asked questions
how to install openframeworks
Grab the Nightly Release, which is linked to avoid submodule cloning, or follow the setup guides for different platforms at openframeworks.cc/download. Platform builds are packaged per platform rather than as one download.
what is openframeworks
openFrameworks is a community-developed cross platform toolkit for creative coding in C++. It ships graphics, sound, video, computer vision, gui, threads and other areas as examples and addons around a C++ core.
is openframeworks dead
The repository last received a push on 2026-11-02 and a nightly release was published on 2026-11-03. The stable branch still corresponds to release 0.12.1 from 2025-05-02, so the active work lives on master rather than in a stable release.
openframeworks alternatives
The README does not name alternatives to openFrameworks. It points to per-platform setup guides at openframeworks.cc/download and to the documentation index at docs/table_of_contents.md, and the forum at forum.openframeworks.cc for questions.
Official sources
Add this badge to your README
If you maintain this project, the badge below links readers to this analysis and shows its maintenance status from the daily GitHub snapshot. Paste the markdown into your README; add ?metric=license or ?metric=stars to the image URL for a different field.
[](https://hysenlabs.com/projects/openframeworks-openframeworks)Star history chart for your README
[](https://hysenlabs.com/projects/openframeworks-openframeworks)Was this useful?