A studio's own animation pipeline became public software

The process wall

Production software that a studio refines over decades of real work usually stays locked inside that studio, because it embeds years of specific pipeline decisions nobody outside has reason to document. Toonz, originally built in Italy by Digital Video S.p.A. and then customised by Studio Ghibli across many productions, was exactly that kind of tool. The wall it crossed on 18 March 2016, when the OpenToonz project's public code repository was created, was releasing that internal tool to anyone.

What the documents show

The OpenToonz project page states that Toonz was 'first used for some cuts of Princess Mononoke' and went on to be used in 'almost all of the works by Studio Ghibli,' with further customisation after Arrietty/The Secret World of Arrietty, and that Dwango 'launched the OpenToonz project in cooperation with Digital Video and Studio Ghibli.' The project's own repository, whose README describes the software as based on 'Toonz Studio Ghibli Version, originally developed in Italy by Digital Video, Inc., and customized by Studio Ghibli over many years of production,' was created on 18 March 2016, the date that marks the software's public release. Both documents state the source code is available under a Modified New BSD Licence, usable for commercial or non-commercial projects free of charge.

Authorship and limitation

The mechanism worth naming precisely is that a software licence and a copyright in finished footage are two separate things: the BSD terms cover the program's source code, not any drawing, character design or film Studio Ghibli made while using it. Neither document states that any Ghibli artwork, footage or character asset ships inside the repository or is licensed by it. That distinction matters directly for a pipeline like this one now that AI-assisted in-betweening or generated frames can be piped through it: an open licence on the tool says nothing about the rights status of whatever a user draws, imports or generates while running it.

What survives

A maker can rely on the BSD terms directly for the software itself, and on the documented lineage, Digital Video to Ghibli to Dwango's public release, for how the tool reached its current form. Editorially, treating an open pipeline's licence as covering the content moving through it is the mistake most worth avoiding as generated frames enter tools like this one.

• Check the Modified BSD Licence text directly before assuming what a commercial project may do with the software.
• Keep the software's open licence separate from the copyright status of any footage, drawing or generated frame produced inside it.
• Look at the repository's own history for how community plugins have extended, rather than replaced, the original Ghibli-refined pipeline.

The record here is a tooling history, not a film-rights one, and reading it as anything more risks assuming an openness that neither document actually grants.