Graphite

Use the Layers panel and node graph as interchangeable views of one document structure

Graphite does not treat traditional layer editing and node-based editing as separate modes with unrelated data. Users can work entirely with canvas tools and the Layers panel, switch into the node graph to edit the underlying processing steps, or move between both throughout a project. Canvas interactions modify nodes behind the scenes, so a WYSIWYG result can later be opened up procedurally, while a complex node network can still be presented as an ordinary layer in the editing workflow.

Sources: [1][2]

Build reusable procedural graphics from Graphene DAGs and nested subgraphs

Graphene represents artwork as node networks connected as directed acyclic graphs. Groups of nodes can be encapsulated into subgraphs and reused as parent nodes, letting larger processing ideas become reusable building blocks rather than one-off filter chains. The root artwork graph follows the same underlying model as any subgraph and can import external data such as images or time values, process them, and export the result to the canvas. This makes nondestructive booleans, procedural patterns, and generative vector artwork part of the document's editable construction history rather than baked output.

Sources: [3][2]

Run the Rust editor backend as WebAssembly in the browser behind a Svelte interface

Graphite's current frontend is a Svelte and TypeScript web application, while the editor backend is written in Rust and compiled to WebAssembly. The backend is the source of truth for editor state and receives interactions from frontend widgets through generated bindings. This means the core editing engine runs in the browser instead of relying on a conventional server-side editing service. The current roadmap also marks offline caching and installable PWA support as completed work, reinforcing the project's goal of combining web distribution with a more local editing experience.

Sources: [4][2]

For 2D creators who want Illustrator-like interaction with the procedural control associated with Blender or Houdini

Graphite is especially interesting for logos, icons, illustration, posters, patterns, and procedural artwork where the ability to adjust parameters later or reuse a processing setup matters. Because the conventional layer and tool interface remains available, users do not have to author every document directly in a node graph. It is less suited today to users whose primary requirement is a mature Photoshop-class raster workflow, and more suited to people who value nondestructive construction, generative workflows, and the project's planned vector/raster convergence.

Sources: [1][2]

The product is still alpha and vector-first, with document format, raster workflows, and desktop releases still maturing

The official features page describes the current alpha as a vector-art and graphic-design tool with only a limited experimental raster toolset. A stable document format, improved imaging data model, brush and stylus work, and later desktop release candidates are still in progress, while items such as PDF export, GPU-accelerated raster rendering, and broader SVG filter support remain on the roadmap. It should therefore be evaluated for the vector and procedural capabilities that exist today rather than assumed to have the maturity or format compatibility of long-established commercial DCC applications.

Unless a repository path states otherwise, Graphite source code is dual-licensed under the user's choice of MIT License or Apache License 2.0. That is permissive for commercial and derivative use under the respective notice requirements, but any files with their own license declarations should be reviewed separately.

Sources: [2][5][6]