Library / SDK
cinder/Cinder avatar
cinder/Cinder

Cinder: a C++ creative coding library built on CMake

Cinder is a community-developed, free and open source library for professional-quality creative coding in C++.

5,550 stars965 forksC++NOASSERTION

At a glance

What is it?
Cinder is a free, open source C++ library for creative coding, aimed at developers who want a native application rather than a browser sketch. The 0.9.4dev branch builds through CMake on macOS, Windows and Linux, and it needs a C++20 compiler.
Who is it for?
Cinder suits engineers who want native C++ performance, GPU rendering and a single codebase across macOS, Windows and Linux, and who are comfortable with CMake and a C++20 toolchain. It is the wrong choice if you want a scripting language, a browser runtime, or a project that ships frequent releases.
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?
Activity is slowing. The repository last received commits 8 months 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 14, 2026, and from our analysis. They are not legal advice.

From daily snapshots

Star history

  • cinder/Cinder5,550 ★ · +11
Star history
Repository2026-09-232026-11-14
cinder/Cinder5.5k5.6k

11 Stars in the last 52 days, measured from the daily GitHub snapshot. Compare with other projects

Editorial analysis

What Cinder solves, and who it is actually for

The README calls Cinder a peer-reviewed, free, open source C++ library for creative coding. That phrase describes the niche precisely. If you want to draw generative graphics, process images, or build an interactive installation, the usual options are a scripting environment or a game engine. Cinder sits in between: you write C++ and get a library, not a scene graph you have to fight.

The target reader is an engineer who already knows C++ and wants native performance on the desktop. The samples directory shows the shape of the work: BasicApp, CanvasUi, BezierPath, CameraPersp, CaptureBasic. These are small programs, not frameworks with an editor. There is no visual builder and no runtime scripting layer. You compile an application.

The licensing is permissive. The README states Cinder is released under the Modified BSD License, with COPYING in the repository root. That matters for commercial installations, though the repository metadata reports the licence as NOASSERTION, so read COPYING rather than trusting a badge.

How Cinder is put together: submodules, blocks and samples

Cinder is not a header-only library you drop into an existing tree. The README warns that it depends on a few submodules and gives a recursive clone as the simplest way to get them. The .gitmodules file at the top level confirms that dependency structure.

The repository layout separates concerns. include/ carries the public headers, src/ the implementation, blocks/ a set of add-on modules, samples/ the runnable examples, and proj/ the platform project files. The build itself is driven by a top-level CMakeLists.txt, so the primary path is CMake rather than a checked-in IDE project.

That structure has a consequence worth naming. Because the submodule content is pinned by commit rather than fetched at configure time, upgrading Cinder means updating submodules too. A plain git pull on the superproject leaves you with the old dependency revisions.

Installing Cinder and running a first sample

The README gives the recursive clone as the simplest route, and that flag is not optional. Without --recursive the submodules stay empty and the build will fail.

bash
git clone --recursive https://github.com/cinder/Cinder.git

The README also points to pre-packaged downloads at libcinder.org/download if you would rather not clone. After cloning, configure and build a debug tree from the repository root. The README gives exactly this pair of commands.

bash
cmake -B build
cmake --build build -j

For a release build, the README passes the build type at configure time and the config at build time.

bash
cmake -B build -DCMAKE_BUILD_TYPE=Release
cmake --build build --config Release -j

The README states this works on macOS, Windows and Linux, and that Cinder requires a C++20 compiler: Xcode 11.3.1+ on Mac, Visual C++ 2022+ on Windows. If your toolchain is older, the configure step is where you will find out. Once the library builds, samples/ holds runnable programs such as BasicApp and CanvasUi that you can open and build against the freshly compiled library. The README does not document a per-sample build command, so expect to read the sample's own project files or add it to the CMake tree.

Where Cinder gets in your way

The release history is the clearest limitation. v0.9.3 arrived on 2025-11-02, v0.9.2 on 2020-04-12, and v0.9.1 on 2017-03-31. Between 0.9.2 and 0.9.3 there is a gap of more than five years. The repository is not archived and the last push was on 2026-03-20, so work continues on master, but the tagged release cadence is slow. If your process depends on regular versioned drops with changelogs, plan around that.

There is also a toolchain floor. C++20 and Visual C++ 2022+ exclude older build servers, and the README does not describe a fallback. A team standardised on an older MSVC or an older Xcode cannot simply compile this branch.

The documentation is thin in places. The README points to guides and reference documentation on libcinder.org rather than in the repository, and it does not document rollback, a downgrade path between versions, or how the blocks/ add-ons are versioned against the core. If you need a library with an in-tree migration guide, this is not it.

Cinder against openFrameworks

openFrameworks is the closest comparison and the difference is philosophical rather than mechanical. Both are C++ creative coding libraries with a permissive licence and desktop targets, and both ship examples you compile rather than run in a browser.

The practical divergence is the build. Cinder's README presents a CMake workflow as the primary path, with a single set of configure and build commands that the README says work on macOS, Windows and Linux. openFrameworks has historically leaned on its own project generator and per-platform project files, which is friendlier if you like an IDE-centric loop and less friendly if you want your creative code to live inside an existing CMake build.

Cinder's blocks/ directory plays a similar role to openFrameworks addons, but the README does not describe a package manager for either core or blocks. In both cases you are managing source dependencies yourself. The choice comes down to which build integration fits the rest of your codebase, not to a feature checklist.

Maintenance, upgrades and the licence question

The default branch is master. The README labels the branch Cinder 0.9.4dev, so master is a development line rather than a frozen release. That is the version you get from a fresh clone.

Upgrade cost has two parts. First, submodules: because the README's clone is recursive, moving between revisions means updating submodule pointers, and the repository does not document a supported upgrade procedure. Second, the C++20 requirement means a compiler upgrade may be a prerequisite for a library upgrade.

On licensing, the README states the Modified BSD License and COPYING is the authoritative file. The repository metadata reports NOASSERTION, so a tool that reads licence metadata may not classify it. Modified BSD is permissive and generally allows commercial use with the copyright notice retained, but that is a description of the licence family, not legal advice. Have your own counsel read COPYING if the terms matter to your product.

Editorial conclusion

Cinder suits engineers who want native C++ performance, GPU rendering and a single codebase across macOS, Windows and Linux, and who are comfortable with CMake and a C++20 toolchain. It is the wrong choice if you want a scripting language, a browser runtime, or a project that ships frequent releases. Before committing, clone with --recursive, confirm your compiler meets the Xcode 11.3.1+ or Visual C++ 2022+ requirement, and read the Modified BSD terms in COPYING.

Frequently asked questions

What is Cinder in this context?

Cinder is a free, open source C++ library for creative coding, described in its repository description as community-developed and in its README as peer-reviewed. It targets native applications on macOS, Windows and Linux rather than a browser runtime.

How do I install Cinder?

The README gives a recursive git clone as the simplest way to get the library and its submodules, and also links to pre-packaged downloads at libcinder.org/download. After cloning, you configure and build with CMake from the repository root.

What compiler does Cinder require?

The README states Cinder requires a C++20 compiler: Xcode 11.3.1+ on macOS and Visual C++ 2022+ on Windows. It supports macOS, Windows and Linux.

What licence is Cinder released under?

The README says Cinder is released under the Modified BSD License, and the COPYING file in the repository root carries the terms. The repository metadata reports the licence as NOASSERTION, so read COPYING directly.

How often does Cinder release new versions?

The tagged releases are v0.9.3 on 2025-11-02, v0.9.2 on 2020-04-12 and v0.9.1 on 2017-03-31, so the interval between tags has been measured in years. The repository itself is not archived and the last push was on 2026-03-20.

Official sources

  1. cinder/Cinder on GitHub
  2. Issues
  3. Project website
  4. README
  5. Releases
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.

Add this badge to your README

markdown
[![Hysen Labs](https://hysenlabs.com/badge/cinder-cinder.svg)](https://hysenlabs.com/projects/cinder-cinder)

Star history chart for your README

markdown
[![Star history](https://hysenlabs.com/chart/cinder-cinder.svg)](https://hysenlabs.com/projects/cinder-cinder)

Was this useful?