mrkeyoor.com_
Tue 01 Sept 17:20 UTC
Webevaluationupdated 01 Sept 2026

Graphite review

Graphite is a browser-based 2D graphics editor that combines familiar layers and canvas tools with a visual node graph. Its current alpha is mainly for vector art and graphic design, while raster editing remains limited and experimental.

trackingstars / 7d
Verdict

Our Graphite dependency step installed 559 packages in 46 seconds, but both build and tests exceeded 900 seconds while Rust was still compiling. Use the hosted alpha to explore procedural vector work, especially if switching between layers and nodes solves a real design problem. Keep production files in a proven editor until Graphite's document format, exports, raster tools, and release packaging move beyond their current alpha constraints.

We ran it

Lab card: what happened when we ran GraphiteScreenshot of Graphite (graphite.art)
Install✓ · 46s559 packages
Build✗ timed out · 900s
Tests✗ timed out · 900sran, no count parsed
Repo1046 files~206,883 lines of source · 14.6 MB · 10 CI workflows

Answers from our run

Does Graphite build from source?

Dependencies installed in 46 seconds (559 packages), and the build failed. We cloned commit be0f6a8 into a clean Debian container with 3 CPUs and no project-specific setup.

Do Graphite's tests pass?

We could not finish them: the suite was still running after 15 minutes in our container.

Who should not use Graphite?

Production studios that need a stable document format or a 1.0 support promise: both remain roadmap items.

What are the alternatives to Graphite?

Inkscape, Krita, Penpot. Our Graphite dependency step installed 559 packages in 46 seconds, but both build and tests exceeded 900 seconds while Rust was still compiling.

Setup2/5Install took 46 seconds; build and tests each exceeded 900 seconds
Docs4/5Clear alpha scope, roadmap, project setup, and contributor guide
Community5/527,032 stars with September 1 pushes and active issue work
Maturity2/5Alpha editor with open document, export, and packaging gaps

Who it’s for

Vector artists curious about editing the same document through layers or procedural nodes.
Designers who can trial an alpha web editor without making it their only production tool.
Graphics programmers who want a large Rust and WebAssembly codebase to contribute to.
Creative coders exploring nondestructive, parameter-driven artwork and animation.

Who it’s NOT for

Production studios that need a stable document format or a 1.0 support promise: both remain roadmap items.
Print and interchange workflows requiring CMYK, spot colors, ICC profiles, PDF, EPS, AI, or PSD import: the feature page places those capabilities on later roadmap stages.
Raster painters expecting a Krita-class toolset today: Graphite calls its current raster editing limited and experimental.
Distribution maintainers who require signed, versioned release artifacts: issue 4227 says the moving latest-stable tag is hard to package, and GitHub returned no latest release.
Contributors seeking a quick compile cycle: our build and test commands each exceeded 900 seconds.

Setup reality

Our sandbox installed 559 packages in 46 seconds. The build timed out after 900 seconds, and tests separately timed out after 900 seconds. The test log was still compiling Rust dependencies and local crates such as graphene-std and document-format; it showed no assertion failure or cause beyond unfinished compilation.

Source development needs current stable Rust, current LTS Node.js, and Git. The official path is cargo run, which checks tool versions and starts a browser dev server. Using the hosted alpha needs no account for a first trial.

The 14.6 MB checkout has no Dockerfile and no tests directory, although it has 10 CI workflow files. Desktop distribution and stable release packaging remain unsettled, so contributors should expect a large native and web toolchain rather than a small web project.

The alpha gives one document a layer view and a node view

Graphite's current alpha is a 2D vector editor with a procedural engine underneath. The layer panel and node graph are two views of the same document structure, so a designer can use ordinary canvas tools, edit nodes directly, or move between both. That is the reason to try Graphite. It brings parameter-driven construction into a workflow that does not force every user to begin by programming a graph.

The repository has grown well beyond a drawing demo: our checkout contained 1,046 files and roughly 206,883 lines of source. Its node engine handles the operations behind interactive tools, while the browser interface exposes layers, properties, and the canvas. Nondestructive edits keep earlier construction steps available. This approach suits patterns, repeated geometry, and art that needs controlled variations more naturally than a stack of permanently altered pixels.

What happened when we ran it

Our sandbox installed 559 packages in 46 seconds at commit be0f6a8. The checkout occupied 14.6 MB before those packages and ran inside an unprivileged container with 3 CPUs and 12 GB of RAM. The repository has 10 CI workflow files. It has no Dockerfile and no tests directory, although the detected Rust commands did begin a substantial compile.

The build did not finish within 900 seconds. A separate test command also timed out at 900 seconds. Its final lines showed Rust compiling diff, color, yansi, pretty_assertions, and env_logger, followed by local packages including math-parser, raster-nodes, graph-craft, graphene-std, document-graph-storage, and document-format. No assertion failed in the visible tail. Both results are compile timeouts, so neither step passed.

A 46-second dependency step led to two 900-second timeouts

Graphite's source guide asks for the latest stable Rust, the current Node.js LTS, and Git. From the repository root, cargo run checks versions and starts a development server at port 8080 with file watching for Rust and frontend changes. Contributors also use Cargo for checking, linting, and formatting, while the frontend directory has npm commands for code checks and fixes. The setup is documented clearly; the compile cost remains the practical barrier.

Our 12 GB sandbox did not run out of memory and the log did not name a missing system package. It simply remained in compilation when each 900-second allowance ended. The evidence supports a narrow conclusion: a clean build and test cycle on this 3-CPU machine takes longer than our 15-minute cap. Developers should budget a warm build cache and avoid treating a first source checkout like a quick frontend install.

Raster editing is experimental and print support is later work

The official feature page describes the current raster toolset as limited and experimental. Graphite can combine vector and raster content and redraw procedural artwork at the current viewing resolution, but its broader selection tools, adjustments, filters, effects, raw photo processing, and painting behavior remain assigned to later roadmap stages. The README also names photo editing, digital painting, desktop publishing, and VFX as future competencies rather than current finished modules.

Version 1.0, a stable document format, desktop releases, PDF export, and local-font access appear in the Alpha 5 roadmap. CMYK, spot colors, ICC profiles, and import for PDF, EPS, AI, DXF, PSD, and TIFF sit farther out. Those labels matter. Graphite is credible for procedural vector experiments now; the roadmap does not make it ready for a print shop, an archive workflow, or an Adobe-file interchange requirement.

Open reports reach saved documents and exported text

Issue 4432 on unreadable saved documents says a NaN value can be serialized as null and then fail to load. The report says affected users must edit the JSON manually to recover the document and suggests checking for NaN before saving. That is a serious alpha boundary. Keep exported copies, use simple test files first, and retain source assets outside the editor.

Issue 4155 on CLI text export reproduces text layers disappearing from PNG, JPG, SVG, and GIF output. Issue 3862 on clipped circle export shows a vector cut at its right and lower edges. Neither report proves every export is broken. Together they justify opening every delivered file in a second viewer and checking text, bounds, fonts, and resolution before deleting the editable document.

Firefox 153 has a reproducible eyedropper crash

Issue 4399 on Firefox 153 reports a Windows 11 crash after selecting the eyedropper and clicking the canvas. The reporter reproduced it in a private window and a new Firefox profile, while Chromium and LibreWolf did not fail. That specificity makes the workaround straightforward for a trial: use a tested Chromium build when color sampling matters, while keeping in mind that another browser is only a workaround for this report.

The same project has 380 open issues and 178 open pull requests. That large queue includes feature tracking, refactors, browser defects, and user-facing bugs, so the combined count is not a defect total. It does show the size of the unfinished surface. Anyone evaluating the alpha should search the open queue for the exact browser, import format, export target, and tool they plan to use.

September 1 activity has not produced ordinary releases

GitHub recorded 27,032 stars and a last push on September 1, 2026. Issue and pull-request activity also continued into September, which is much stronger health evidence than an old tag. GitHub's latest-release endpoint returned no current release object. The source is active, yet downstream users still lack the versioned release rhythm expected from established desktop graphics software.

Issue 4227 on downstream packaging explains the consequence: a Linux package maintainer cannot find normal signed release artifacts tied to a known version. Graphite is easy to sample through the hosted web alpha and expensive to treat as pinned desktop infrastructure. Try its procedural editor on disposable copies, watch the active development, and wait for ordinary releases before making it the only tool that can open important work.

Alternatives

ProjectWhat it isPick it when
InkscapeA mature desktop vector editor centered on SVG authoring and interchange.pick this instead when dependable vector production, broad SVG handling, and established desktop releases matter more than procedural nodes.
KritaA desktop painting and illustration application with mature raster and animation tools.pick this instead when brushes, raster painting, tablet work, and finished desktop packaging are the main requirements.
Penpot gh↗A web-based design platform built for product teams and shared interface work.pick this instead when browser collaboration and interface design matter more than procedural artwork and raster experiments.

What people are saying

  1. [velocity-scout] GraphiteEditor/Graphite

Sources

  1. Graphite README
  2. Graphite repository metadata
  3. Graphite feature scope and roadmap
  4. Graphite source project setup
  5. Unreadable saved-document report
  6. CLI text export report
  7. Firefox eyedropper crash report
  8. Downstream release-packaging request

More web reviews

axios · super-productivity · fastify · tabler · go-zero · ruffle · the whole board →