VectorCraft builds from source with Cargo, and its agent control channel is the unusual part
VectorCraft: An open-source, vector art tool written by scratch in pure Rust
At a glance
- What is it?
- storytold/vectorcraft is a vector illustration app written in Rust that runs natively on four desktop systems and in the browser through WebAssembly. Its command API doubles as a JSON control channel and an MCP server, and every release so far is below 1.0.
- Who is it for?
- Try VectorCraft if you want a vector editor you can build with Cargo and drive from scripts or an MCP client, and you can tolerate a 0.x version that changed three times in four days. Do not make it your only production tool for client work yet.
- Can I use it commercially?
- Yes. Apache-2.0 is a permissive licence: you can use, modify and sell software built on it, as long as you keep its copyright and licence notices.
- Is it still maintained?
- Yes. The repository received new commits within the last day.
- What is it written in?
- Mainly Rust, according to GitHub's language statistics.
Answers come from the project's GitHub data, last synced on November 6, 2026, and from our analysis. They are not legal advice.
Star history
- storytold/vectorcraft11,438 ★ · +1,134
| Repository | 2026-10-21 | 2026-11-06 |
|---|---|---|
| storytold/vectorcraft | 10.3k | 11.4k |
1,134 Stars in the last 16 days, measured from the daily GitHub snapshot. Compare with other projects
Editorial analysis
Cargo runs the desktop app, the control channel, the MCP server and the batch exporter
There is no installer command in the project text for the build path. The Quick start is a clone followed by cargo run invocations, each selecting a different binary or mode:
git clone https://github.com/storytold/vectorcraft
cd vectorcraft
cargo run --release -p vectorcraft # desktop app
cargo run --release -p vectorcraft -- examples/dusk-poster.vectorcraft
cargo run --release -p vectorcraft -- --control 7979 # + JSON control channel
cargo run --release -p vectorcraft-cli -- mcp # MCP server (stdio)
cargo run --release -p vectorcraft-cli -- run --in examples/ribbons.vectorcraft --export out.pdf # headless batchTwo packages carry this. The vectorcraft package is the app, and vectorcraft-cli is the command line tool with the mcp and run subcommands, plus a bench subcommand for benchmarking a document such as examples/neon-drive.vectorcraft. Passing a .vectorcraft file after the double dash opens that document.
The workspace in Cargo.toml sets rust-version to 1.95 and edition to 2024, so an older toolchain fails before it compiles a line. Its members are crates/*, apps/* and xtask. The project also links a Downloads section from its table of contents.
Every menu item is reachable over a JSON control channel and an MCP server
The distinguishing claim is the agent interface. Every menu item, tool gesture, panel and dialog can be driven over a JSON control channel and an MCP server, so Claude and other agents can draw, edit and export the way a person does. Two commands start those interfaces: the app with --control 7979 opens the JSON channel on port 7979, and vectorcraft-cli with mcp serves the MCP protocol over stdio.
The gallery makes a stronger statement. Each piece in the Made in VectorCraft section was built entirely through the command API, the same one the MCP server exposes, and exported by VectorCraft's own renderer. The source files are in examples/: neon-drive, still-life, bracket-drawing, perspective-city, ribbons, feature-sheet and dusk-poster, each a .vectorcraft file, with dusk-poster also provided as an SVG.
That gives you a reproducible test: open any of those files and compare it with what your own scripted session produces. Check the docs/ folder before building automation on the control protocol.
The .vectorcraft format is JSON, and the import list is longer than the export list
The native format is documented and stored as JSON, with the .vectorcraft extension. SVG is first class. PDF and PDF-compatible .ai files are supported for both import and export. Export also covers PNG, JPEG and WebP, plus Export for Screens. On open, the app additionally reads SVGZ, templates, GIF, TIFF and BMP.
Read that carefully before relying on a round trip. In the README's feature list, GIF, TIFF and BMP appear only on the open side, and SVGZ is described the same way.
There is one more guarantee, and it is about files. The project says file round trips are property-tested, which means the save and load path is checked against generated inputs, not only hand-picked samples. It makes no claim about round trips through other programs, so a PDF opened in a third-party editor is outside what that promise covers.
The format is documented and JSON-based, which fits the command API above.
20,000 shapes in about 27 ms is the project's own number, at retina resolution
The speed claim is specific: multithreaded SIMD rendering off the UI thread, with 20,000 shapes rendering in about 27 ms at full retina resolution while the interface stays at 120 fps. That figure comes from the project's own README.
The subcommand to check it yourself is the last line of the Quick start block, cargo run --release -p vectorcraft-cli -- bench followed by a document path, with examples/neon-drive.vectorcraft as the suggested input. Run it on your own hardware, since the 27 ms figure is the project's own.
Two other mechanisms sit behind the claims. Exact curve booleans are there so Pathfinder operations do not end in a cannot perform operation error. Unlimited undo uses structural sharing, which keeps the history from copying the whole document at each step.
On machines with two graphics processors, the app renders on the integrated, power-saving one by default on Windows and macOS, and on the one the desktop runs on under Linux. To change it, use Preferences, Performance, Graphics Processor, and restart. If a graphics processor cannot show the window, VectorCraft starts again on another one.
Japanese text needs the craft-fonts checkout, or it falls back to system fonts
Japanese fonts come from a separate repository, storytold/craft-fonts. It is an optional build input, though release builds always use it. To include it in a source build, point CRAFT_FONTS_DIR at an absolute path to the checkout, for example one sitting next to the vectorcraft folder, then run cargo run --release -p vectorcraft.
Without it, Japanese text uses the installed system fonts. A source build on a machine with no suitable Japanese font will therefore render that text differently from the released binary, and a document built for print could change appearance between the two. The details are in docs/development.md under the fonts section.
Typography has its own guide, docs/typography-lettering.md, for text and custom letter shapes. Large-format work has docs/print-tiling.md, covering posters and sewing patterns printed across multiple pages.
Git dependencies pinned to one commit tie the build to the craft-libs repository
Cargo.toml pulls several workspace dependencies straight from git: craft-pdf, craft-print, craft-docpath, craft-ui, craft-keymap and craft-window, all from storytold/craft-libs at revision 92d392cff132eaf53e13afff77f38b5c11b73aa0. The craft-update dependency pins a different revision, c5a1cbfb5f9049f9270955caffb5bee5997aebf7, and an exact version of 0.1.0.
Pinned revisions make a build reproducible. They also mean a clean build needs network access to GitHub, and it fails if that repository or commit becomes unavailable. These are not crates.io packages, so a vendored or offline build requires extra work.
The workspace members live under crates/*, apps/* and xtask. The same codebase serves the desktop apps and the browser build through WebAssembly, per the project description.
Three releases in six days, all below 1.0, from a project part of a larger suite
v0.19.0 was tagged on 2026-10-31, v0.20.0 on 2026-11-01 and v0.21.0 on 2026-11-03. The last push is 2026-11-02, the repository is not archived and the workspace version reads 0.21.0. Pre-1.0 numbering at that cadence means file format and command API details can shift between tags, so pin the version you script against.
VectorCraft belongs to the Crafting Apps by the ArtCraft team, listed at getartcraft.com/apps. The suite shares libraries through craft-libs, and other apps in it, not part of this repository, have their own pages on that site.
Licensing needs a closer look. GitHub reports Apache-2.0, and the repository contains LICENSE-APACHE, LICENSE-MIT, a NOTICE file and a licenses/ folder, while Cargo.toml says MIT OR Apache-2.0. Read those files before redistributing, particularly if you bundle the Japanese fonts.
Editorial conclusion
Try VectorCraft if you want a vector editor you can build with Cargo and drive from scripts or an MCP client, and you can tolerate a 0.x version that changed three times in four days. Do not make it your only production tool for client work yet. Before committing, open one of the files in examples/ and export it to PDF and SVG to check the output you need.
Frequently asked questions
What is VectorCraft?
VectorCraft is an open-source vector illustration application written in pure Rust. It runs natively on macOS, Windows, Linux and FreeBSD, and in the browser via WebAssembly, and is built by the ArtCraft team.
How to install VectorCraft?
Clone https://github.com/storytold/vectorcraft and run cargo run --release -p vectorcraft from the folder. The project also lists a Downloads section and a page at getartcraft.com/apps/vectorcraft.
How to use VectorCraft?
Launch it with cargo run --release -p vectorcraft, optionally passing a file such as examples/dusk-poster.vectorcraft. Its tools include the Pen, Direct Selection, Pathfinder, Smart Guides, Appearance, Swatches and Layers.
Is VectorCraft free and open source?
It is open source, and GitHub reports the license as Apache-2.0. Cargo.toml lists MIT OR Apache-2.0, and the repository contains both LICENSE-APACHE and LICENSE-MIT.
Official sources
Add this badge to your README
If you maintain this project, the badge below links readers to this analysis and shows its maintenance status from the daily GitHub snapshot. Paste the markdown into your README; add ?metric=license or ?metric=stars to the image URL for a different field.
[](https://hysenlabs.com/projects/storytold-vectorcraft)Star history chart for your README
[](https://hysenlabs.com/projects/storytold-vectorcraft)Was this useful?