ArtCraft on GitHub: Every Repo Explained (PhotoCraft, VectorCraft, FilmCraft…)
A map of the official ArtCraft GitHub organization (storytold): what each repo is, star counts, licenses, and how to build PhotoCraft and the other Crafting Apps from source.
Published October 13, 2026 · Unofficial community guide
Search for “artcraft github” or “photocraft github” and you’ll get a mix of official repos, forks and look-alikes. This
is a map of the official ones, all under the storytold organization, and how
to build them.
Rule of thumb: if the repo owner isn’t
storytold, it isn’t official. See how to spot fake ArtCraft repos.
The app repositories
Star counts as of October 13, 2026:
| Repo | What it is | Stars | Latest |
|---|---|---|---|
| storytold/photocraft | PhotoCraft, image editor (Photoshop) | ~55.9k | v0.8.2 |
| storytold/artcraft | ArtCraft, the AI image and video studio | ~24.1k | v0.41.0 |
| storytold/pdfcraft | PdfCraft, PDF workbench (Acrobat) | ~12.1k | v0.7.1 |
| storytold/filmcraft | FilmCraft, video editor (Premiere Pro) | ~12.0k | v0.7.2 |
| storytold/lightcraft | LightCraft, RAW and photo library (Lightroom) | ~11.6k | v0.7.1 |
| storytold/wordcraft | WordCraft, word processor (Word) | ~10.2k | v0.6.1 |
| storytold/vectorcraft | VectorCraft, vector illustration (Illustrator) | ~8.2k | v0.10.0 |
| storytold/effectcraft | EffectCraft, motion graphics (After Effects) | ~6.0k | v0.9.2 |
| storytold/gridcraft | GridCraft, spreadsheets (Excel) | ~4.2k | v0.6.1 |
| storytold/cadcraft | CADCraft, 2D CAD (AutoCAD) | ~3.9k | v0.6.2 |
| storytold/designcraft | DesignCraft, page layout (InDesign) | ~3.6k | v0.7.1 |
| storytold/deckcraft | DeckCraft, presentations (PowerPoint) | ~2.8k | v0.6.1 |
| storytold/soundcraft | SoundCraft, DAW (Pro Tools) | ~2.4k | v0.6.1 |
| storytold/figcraft | FigCraft, UI design (Figma) | new | v0.5.1 |
Supporting repositories
- craft-launcher. The Craft App Launcher, a single launcher for the Crafting Apps.
- craft-libs. Shared Rust libraries used across the Crafting Apps.
- craft-fonts. Fonts the apps bundle, including the Japanese UI fonts. It’s an optional build input.
- photocraft-corpus. Test files (PSDs and more) that PhotoCraft is checked against.
- artcraft-services. Backend and web frontend for the ArtCraft studio.
License
The Crafting Apps are dual-licensed MIT OR Apache-2.0. You can use, modify and redistribute them, including
commercially. The exception is branding: the ArtCraft name and logos in docs/brand/ are trademarks, so forks have to
rename themselves.
Building PhotoCraft from source
You need a recent stable Rust toolchain (install via rustup).
git clone https://github.com/storytold/photocraft
cd photocraft
cargo run --release -p photocraft -- image.psd # the desktop app
cargo test --workspace # the test suite
Japanese UI and Type-tool fonts come from craft-fonts. Release builds always include them; for your own build:
git clone https://github.com/storytold/craft-fonts ../craft-fonts
CRAFT_FONTS_DIR="$PWD/../craft-fonts" cargo run --release -p photocraft
Building the other apps
Every app follows the same layout: an apps/<name> desktop crate, an apps/<name>-cli command-line tool and an
apps/<name>-web WebAssembly front end.
# VectorCraft desktop + MCP server
git clone https://github.com/storytold/vectorcraft && cd vectorcraft
cargo run --release -p vectorcraft
cargo run --release -p vectorcraft-cli -- mcp
# Any app's browser build (needs trunk and the wasm32 target)
rustup target add wasm32-unknown-unknown
cargo install trunk
cd apps/vectorcraft-web && trunk build --release
cargo xtask ci runs the same checks as CI: formatting, clippy, tests, crate layering rules and the wasm build.
Using the apps with AI agents (MCP)
Each app’s CLI can run as an MCP server. For example, to give Claude Code access to VectorCraft:
claude mcp add vectorcraft -- /path/to/vectorcraft-cli mcp
You can restrict which folders the agent may read and write with --automation-read-root and
--automation-write-root.
Contributing
Every repo has an AGENTS.md (instructions for humans and AI coding agents), a ROADMAP.md with honest parity
numbers, and a docs/gaps.md listing what’s missing. Those gap lists are the best place to find something to work on.
The team also runs a Discord.
Not ready to build?
You don’t need Rust to try any of this. Open the apps in your browser or grab the official installers.