OpenToonz: a Ghibli-derived 2D animation suite you install from the official site

What OpenToonz is, and which animators it fits

OpenToonz is a 2D animation application published by DWANGO. The README states that it is based on Toonz Studio Ghibli Version, originally developed by Digital Video, Inc. in Italy and customized by Studio Ghibli over years of production. That lineage is the pitch: a codebase that spent its early life inside a working animation studio, later released under an open licence.

The people it fits are 2D animators and small studios that want a desktop production toolchain they can install and run locally. The README frames the project as a full-featured creation tool, and the repository layout backs that up: a large C++ application under toonz/, a plugins/ directory, a stuff/ directory for brushes and assets, and a thirdparty/ directory for bundled dependencies. This is not a lightweight sketch tool. It is a production package with a long build system behind it.

The README is explicit that only two places are official: opentoonz.github.io and the GitHub repository itself. It warns that there are no other official mirrors or partner sites. If you find a download elsewhere, the project does not vouch for it.

The Toonz codebase and how the source tree is organized

The architecture visible from the repository is a native C++ application with platform-specific build paths. The top level holds appveyor.yml and a ci-scripts/ directory, and the README links continuous integration badges for Windows, macOS and Linux, so the project builds and checks the same codebase on three platforms. A BSD build document also exists, which is uncommon for animation software and worth noting if you run a BSD workstation.

The main application code lives under toonz/. Supporting material is split between plugins/, stuff/ and thirdparty/. That split matters when you audit the project: the README's licensing section treats those directories differently from the rest of the tree, so the boundary between first-party code and bundled dependencies is a real line in the repository, not a formality.

Translation is handled outside the repository, through Weblate, and the README links a translation status badge. Localized READMEs exist for Japanese and Simplified Chinese under doc/. If your team works in another language, the translation workflow is the Weblate instance rather than pull requests against source strings.

Installing OpenToonz from the official site

The README does not give a package manager command. It says to download and install OpenToonz from the latest installer at the project site. That is the supported path for most users, and it is the one the project wants you to take, given the warning about unofficial mirrors.

Older versions and unstable nightly builds are published on the GitHub releases page. A nightly build dated 2026-09-21 and a v1.8.0 release dated 2026-06-19 both appear in the release list, so you can choose between a stable tag and a rolling build.

If you prefer to build, the README links separate documents for each platform. The commands below are the documented entry points, not a script the README provides; open the matching document for the actual build steps.

# Windows
doc/how_to_build_win.md

# macOS
doc/how_to_build_macosx.md

# Linux
doc/how_to_build_linux.md

# BSD
doc/how_to_build_bsd.md

There is also a stylesheet build step documented separately in doc/how_to_stylesheet.md. If you change interface styling, that document is where the project says to look.

A first real use is to open the application and start a scene, then draw and time a short sequence with the toolset the installer ships. The README does not walk through that workflow; it points to the separate documentation repository at opentoonz/opentoonz_docs for general documentation. Read that before assuming a feature exists.

Where OpenToonz stops being the right tool

The README describes a desktop installer and source builds for Windows, macOS, Linux and BSD. It documents no mobile client, no hosted editor and no browser version. Anyone searching for an Android or iPad build will not find one in this material, and the project's own text gives no indication that one is planned.

Licensing is the second boundary, and it is easy to miss. The README says files outside thirdparty and stuff/library/mypaint brushes are based on the Modified BSD License, and that under that licence the software may be used or changed freely for business or personal use. For the two excluded directories it does not grant the same terms: it directs you to the READMEs or source code in thirdparty, and to stuff/library/mypaint brushes/Licenses.txt. If you redistribute a build or ship assets from those directories, the licence question is not answered by LICENSE.txt alone.

Build cost is the third. This is a C++ application with per-platform build documents and a separate stylesheet build. The README does not describe a one-command build. Teams without C++ build experience on their target platform should treat the installer as the only realistic route.

OpenToonz versus Synfig Studio and other open 2D options

The obvious alternative in the same category is Synfig Studio, another open-source 2D animation program. The difference in approach is provenance and scope. OpenToonz descends from a commercial studio pipeline, Toonz, that was customized at Studio Ghibli, and the repository reflects that history with a large C++ codebase, a plugins directory and bundled thirdparty dependencies. Synfig comes from a community project rather than a studio pipeline, and its feature set and file formats differ accordingly.

The practical consequence is migration cost. A studio moving from a commercial Toonz-derived pipeline will find familiar concepts in OpenToonz, because the README ties the project directly to that lineage. A studio moving from a vector-tween tool will not, because the underlying model is different. Neither is a drop-in replacement for the other, and the README does not claim compatibility with any other package's project files.

For teams that only need simple frame-by-frame drawing, a lighter tool may be less work than installing and learning a full production suite. OpenToonz's size is the price of its scope.

Maintenance, releases and what upgrading actually costs

The repository is not archived, and its last push was on 2026-09-20. Releases are active: a nightly build dated 2026-09-21, v1.8.0 dated 2026-06-19, and a release candidate dated 2026-05-29. The README also links a development checklist and an AI-assisted development checklist, both marked as drafts, which suggests the project is documenting its own contribution process rather than freezing it.

Upgrade cost depends on which channel you pick. Stable tags such as v1.8.0 are the conservative choice. Nightly builds are published continuously and the README itself calls them unstable, so a nightly is a testing channel, not a production one. If you rely on a nightly for a feature, you inherit the risk that the next one changes it.

On licence implications, the Modified BSD terms in LICENSE.txt cover files outside thirdparty and stuff/library/mypaint brushes, and the README states that this permits business and personal use and modification. It does not resolve the two excluded directories. Treat that as an audit item for your own legal review rather than something the README settles.

Contributors who cannot write C++ still have a documented route: the README links steps for testing individual pull requests before they are merged. That is a concrete way to help without touching the build.

Editorial conclusion

OpenToonz suits 2D animators and small studios that need a full production toolchain and can accept installer-based distribution from opentoonz.github.io. It is the wrong choice if you need a hosted, browser-based editor or a mobile app, since the README points only to the desktop installer and the repository's build documents. Before committing a production, verify the exact licence of any file you pull from thirdparty or stuff/library/mypaint brushes, because the Modified BSD licence that covers the rest of the tree does not automatically cover those directories.

Frequently asked questions

Official sources

1. Issues
2. opentoonz/opentoonz on GitHub
3. Project website
4. README
5. Releases