ArtCraft on GitHub: where each app's code and downloads live

The 14 repositories, as GitHub reported them

Every row is one repository, read from GitHub on Oct 15, 2026. Star counts move daily, so treat ours as a snapshot from that morning. Release dates are converted to Eastern time. "Files" counts everything attached to that release — installers, checksums, command-line tools and the browser package.

Two details worth knowing before you read that table. The 13 app releases all landed within three hours of each other on Oct 14, 2026 — they ship together. And Studio is the odd one out: its release carries only four files, and it is the only release in the organisation with no checksum file.

The organisation holds more than the 14 repositories above: the shared launcher, the Rust libraries the apps are built on, the font bundle and the test-data repository are all public too. There is also AniCraft, a 2D animation editor in the same house style — it is not one of the 13 apps, and it has no release yet, so we leave it at that.

Which file in a release do I want?

Filenames in these releases follow one pattern: <app>-<version>-<system>.<extension>. Once you can read one, you can read all of them — and the same five names appear in every app's release.

The version in the middle is always the release tag without its leading v, so a filename tells you which build you have. If you are not sure which of the 24 to 28 files in a release matches your machine, our download guide walks through the picker with the current numbers and the checksums.

Building from source

Because the code is public, you can skip the installers. The steps are short — this is the PhotoCraft README's own sequence, unchanged:

Interface fonts for Japanese text come from a second repository, craft-fonts, which the README calls an optional build input; release builds always include it, and without it the apps fall back to your system fonts. The newer apps ask for more: LightCraft, PdfCraft, EffectCraft, DesignCraft, CADCraft and SoundCraft each say in their build section that the desktop and browser builds need Rust 1.95 or newer, while the core libraries under them still build from 1.90.

We have not compiled any of this ourselves. Everything we tested in our hands-on round came from the published installers and browser packages, so treat the build steps as the project's instructions, not as something we have run.

Is ArtCraft really open source?

Yes, and the paperwork is unusually tidy. Every one of the 14 repositories carries two license files and says, in its README, "dual-licensed under MIT or Apache-2.0, at your option" — you pick whichever suits you. GitHub's interface reports them all as Apache-2.0, because that is the license it recognises first, and that is why the table above and the repository pages look like they disagree when they do not.

What that means in plain terms: you can download the apps, read the code, change it and ship your changes. MIT is the short, permissive license; Apache-2.0 says the same things plus an explicit patent grant. Neither one asks for money or an account. FilmCraft's README adds that its code is an independent implementation with no Adobe code, icons or presets inside it.

One thing that can confuse people: the studio app is free to download, but its AI generations run on credits, and credits are a service rather than a license. The Craft apps have no such meter — no account, no subscription, nothing to top up.

Common questions