How to Contribute to Processing or Use Community-Contributed Libraries and Tools
Processing's core software is extended by libraries and tools contributed through the community, and the project maintains lists of both online. If you want to use community extensions, start with the Contributed Libraries and Contributed Tools lists. If you want to contribute, the main path is GitHub, where the project publishes instructions for downloading the code, building from source, reporting and tracking bugs, and creating libraries and tools.
Using community-contributed libraries and tools
The Processing website states that the core software "is augmented by libraries and tools contributed through the community," and that a list of Contributed Libraries and Contributed Tools is posted online. Those two lists are the entry point for finding extensions rather than writing functionality yourself.
A practical way to work:
- Identify what your sketch needs that core Processing doesn't provide (for example, a specific file format, hardware interface, or visualization technique).
- Check the Contributed Libraries list for a library that covers it.
- Check the Contributed Tools list if what you need is a tool around the environment rather than code you call from a sketch.
- Install and test against a small example before committing to it in a larger project.
The site describes these community extensions as "a bright future for the project" and says the contributions "can't be underestimated" — so the lists are treated as a first-class part of the ecosystem, not an afterthought.
Contributing to Processing development
To contribute to Processing development, the site directs you to Processing on GitHub, where you can read instructions for:
- Downloading the code
- Building from the source
- Reporting and tracking bugs
- Creating libraries and tools
That covers two distinct kinds of contribution: improving the core software itself, and publishing your own library or tool for others to use. If your goal is the latter, the "creating libraries and tools" instructions are the relevant starting point; if your goal is fixing or extending core behavior, the download/build and bug-tracking paths are.
What else the community offers
Beyond libraries and tools, the site points to several places to see what others are making and to get help:
| Resource | What it's for |
|---|---|
| Forum | Sharing and learning; the site's suggested place for questions |
| OpenProcessing | Processing creative applications |
| Processing Subreddit | Community discussion |
| Vimeo | Video of community work |
| Studio Sketchpad | Sketch sharing |
| GitHub | Code, source builds, bug reports, library and tool creation |
The site also notes that a group of diverse books has been written to help people with different goals and skill levels, and that Processing turns 25 in 2026, with a celebration in October organized through local community events. If Processing has been part of your work, teaching, or creative practice, the site suggests planning a Processing Community Day (PCD) in your city — another form of contribution that isn't code.
Choosing your path
- Just want to use extensions: go to the Contributed Libraries and Contributed Tools lists, pick what fits, and test it in a small sketch first.
- Want to publish your own extension: follow the "creating libraries and tools" instructions on GitHub.
- Want to improve core Processing: use the GitHub instructions for downloading the code and building from source, and use the bug-reporting and tracking process for issues.
- Want to contribute without code: the Forum, community showcases, and local Processing Community Day events are the documented routes.
One caveat worth stating plainly: the site describes the software as free and open source, but it does not publish pricing or account requirements for the contributed libraries and tools themselves. Check each library's or tool's own page before assuming how it is licensed or distributed.