VectorCraft for ArtCraft workflows: an open-source vector design tool

vectorcraft-cli run --in examples/ribbons.vectorcraft --export out.pdf

vectorcraft-cli mcp

What VectorCraft is

VectorCraft is the vector member of the Crafting Apps family around ArtCraft. Its job is different from PhotoCraft and ArtCraft: it works with paths, shapes, strokes, fills, artboards and type rather than starting from pixels or a generated shot. The project describes itself as a clean-room, open-source reimplementation of an Illustrator-shaped workflow, but that phrase should be read as workflow familiarity, not a claim of Adobe compatibility or endorsement. The source is public, the licence is MIT or Apache-2.0, and the release is still labelled alpha.

The file formats that matter

The native .vectorcraft format is the safest place to keep an editable working file because it is the format the project controls directly. For handoff, the repository documents first-class SVG and PDF import/export, as well as PDF-compatible .ai import and export. That is useful when a team has to move artwork between tools, but it is not the same as promising that every Illustrator effect, plugin, appearance stack or linked asset will make a perfect round trip. Keep the original file, export a reference PDF or SVG, and reopen the exported file before calling a workflow compatible.

Tools for everyday vector work

The current tool surface covers the parts most people mean when they say vector illustration: Pen and Direct Selection, shape tools, Pathfinder, Shape Builder, layers, swatches, gradients, transparency, appearance, smart guides, artboards and text. The project also documents multithreaded rendering and a structured undo model. Those are meaningful building blocks for posters, icons, diagrams, logos and layout experiments. They do not turn an alpha project into a drop-in replacement for a mature production suite, so the useful question is whether your own work depends on one of the missing edges.

Desktop, browser and automation paths

VectorCraft targets macOS, Windows and Linux desktop workflows, and the project also documents a WebAssembly browser build. The browser build is a way to try the same codebase in a tab; it should not be described as a hosted service or as proof that every desktop feature is equally ready online. The CLI and MCP surfaces are more distinctive for teams: a headless command can export a document, while an MCP client can drive menu actions, editing and export. Restrict an agent to a project read and write root, keep source files backed up, and test one document before batching a folder.

VectorCraft versus Illustrator

The comparison is about fit, not a winner. Illustrator has a long-established ecosystem, specialist production workflows and native plugin relationships that VectorCraft does not reproduce. VectorCraft offers public source, a permissive dual licence, a Rust implementation, a documented control channel and a lighter path for people who want to inspect or automate the editor. If your job is everyday path drawing, SVG/PDF interchange or experimenting with an agent-controlled vector workflow, it is worth testing. If your job depends on a particular native extension, a very specific Illustrator effect or a press pipeline that cannot tolerate an alpha release, keep Illustrator or another mature fallback in the loop.

Fonts and Linux display caveats

Fonts are a production concern, not a footnote. The project bundles craft-fonts in release builds and can also use installed system fonts, but a document can render differently when a required font is missing or has not been discovered yet. On Linux, the upstream documentation calls out Wayland and drawing-tablet limitations in some environments; XWayland is the practical fallback described by the project. Before delivering artwork, open the file on the target machine, inspect missing-font notices, convert critical display type to outlines only when the handoff requires it, and keep an editable text version separately.

Downloading the right build

Use the upstream GitHub Release rather than a third-party mirror. VectorCraft v0.11.0 is the current release recorded for this page, and the release page is the authority for the exact asset names, architecture choices and any checksums published alongside them. OpenCraftTools does not host or repackage installers. After downloading, compare the release asset and checksum information, then keep the release tag with the project file so another person can reproduce the environment later.

A safe first test

• Open a simple SVG with paths, a gradient, a text object and one embedded image.
• Save a native .vectorcraft copy before trying an imported .ai or PDF file.
• Export SVG and PDF, reopen each export, and compare artboard bounds and text placement with the original.
• Test one font that is installed on the production machine and one font that is not, so missing-font behaviour is visible.
• Run one CLI export or MCP action in a disposable project folder before granting an agent access to client artwork.

That test is deliberately small. It tells you more than a feature checklist because it follows the exact formats, fonts and exports your work depends on. VectorCraft is moving quickly, so record the version, operating system, display server and source file with the result. When a later release changes behaviour, you will know whether the change is in the app or in the environment around it.

Who should try it now

• Designers who want an open-source vector editor with a familiar path and artboard workflow.
• Linux users who need an SVG/PDF-oriented tool and are willing to test alpha software.
• Developers building a repeatable vector export pipeline through CLI or MCP.
• Contributors who want to inspect, improve or extend a pure-Rust creative application.