Graphite

Key features

• Hybrid layer and node editing Work with ordinary layers while a procedural node graph records each operation, so adjustments remain editable instead of destructive. Canvas edits rewrite the underlying nodes, which means beginners can stay in the layer view while technical users open the graph and tune the actual logic.[1][2]

• Shape, Pen, and Path vector tools Build illustrations from primitives plus freeform Pen and Path tools for organic curves, styled with colors and gradients. Vector illustration is the manual's stated current core competency, so this is the most dependable part of the editor today.[1]

• Parametric procedural nodes Drive artwork with nodes that expose numeric parameters, such as a Circular Repeat that turns one shape into radial patterns. Changing a number re-renders the result, which suits generative exploration far better than manual duplication.[1][2]

• Resolution-independent raster rendering Raster output renders from the procedural document rather than fixed pixels, keeping exports crisp at any scale. Designs stay sharp whether they end up as icons or large-format prints.[1]

• Experimental raster compositing Import images from disk and apply nondestructive color effects while the artwork stays re-editable. Treat this as a preview of the compositing direction, not a finished photo workflow.[1][2]

• PNG, JPG, and SVG export Save finished work in three common formats with a scale factor and artwork, selection, or artboard bounds. SVG output matters most here: it keeps vector work portable into other tools when a project outgrows the alpha.[1]

• No-account browser editor plus desktop app Launch the hosted editor without signing in, or use the maintained native desktop application that the core team staffs with a dedicated engineer. Trying it costs nothing but a click.[1][2]

• Free builds with creator-owned artwork Use and redistribute builds commercially at no cost under dual MIT or Apache-2.0 licensing at the licensee's choice, and keep full ownership of what you make. Funding runs on voluntary donations, so there is no paid tier quietly gating features.[1][2][3]

Who will love it

• Illustrators curious about parametric design: tuning a numeric parameter instead of redrawing is rewarded directly by the node graph, and the layer view keeps the learning curve gradual.[1][2][3]

• Generative-art prototypers on a zero budget: procedural nodes, free commercial builds, and no-account browser access require no signup, payment, or installation, so discarded experiments cost nothing.[1][2][3]

• Open source contributors who write Rust: the codebase, contributor call, and dual MIT/Apache-2.0 licensing speak to developers who want to shape an editor, and the donation model sustains a community project through voluntary gifts rather than license fees.[1][2][3]

Who should avoid it

• Production teams shipping client work: alpha status with expected breaking changes makes Graphite a poor foundation for deadlines today, since a file built this month may behave differently after the next update.[1]

• Photo editors and digital painters: raster compositing is growing but the brush tool is an acknowledged limited prototype, not a painting station, so pixel-level retouching belongs elsewhere for now.[1]

• Teams needing collaboration and handoff: there is no documented multi-user editing, commenting, or developer-inspect pipeline comparable to mature design tools, which rules out shared design-system work.[1][2]

Alternatives and compatibility