One place for 13 Craft apps
List the suite, including FigCraft in v0.4.1, see installed versions and open each app without hunting through separate release pages.
Early alpha · MIT or Apache-2.0 · v0.4.1
ArtCraft Launcher: install the Craft App Suite
ArtCraft Launcher is the practical entry point when you want more than one Craft app. It lists the 13-app suite, picks a build for your operating system and processor, checks the release checksum, installs or updates the app, and lets you open the tools from one native window or system-tray entry. Version v0.4.1 adds FigCraft; this portal links the upstream release and does not bundle, mirror or silently update anything itself.
ArtCraft Launcher facts, checked 2026-10-15
- Latest release
- v0.4.1
- Released
- 2026-10-13
- Licence
- MIT or Apache-2.0
- Release assets
- Official release
- Stage
- Early alpha
- Source repository
- storytold/craft-launcher
| Platform | Architectures | Build formats | Where work runs |
|---|---|---|---|
| Windows | x86, x64, arm64 | MSI installer, portable zip | Local: your CPU, GPU and files |
| macOS | universal (Apple silicon and Intel) | DMG | Local: your CPU, GPU and files |
| Linux | x86_64, aarch64; riscv64 (selected packages) | AppImage, deb, rpm, Flatpak, tar.gz | Local: your CPU, GPU and files |
| FreeBSD | x86_64 | tar.gz | Local: your CPU, GPU and files |
| Web (static catalog) | modern browser | artcraft-launcher-web.zip | Browser build; confirm the current hosting and file boundary upstream |
What it does
Platform and architecture selection
Choose the release package for the operating system and processor, including Windows ARM64, Linux x86_64/aarch64, selected RISC-V assets and FreeBSD.
Checksum-aware installs and updates
The launcher checks published SHA-256 values before installing an app and keeps the updater on the same verification path.
Desktop, tray and menu-bar workflows
Open installed Craft apps from one native window or from the system tray/menu bar; the project is built with egui rather than Electron.
Web catalog build
The release also publishes a WebAssembly catalog that can be hosted as a static site; it is not a hosted editor or binary mirror on OpenCraftTools.
What it does not do yet
- Early alpha: installation and update edges can still be rough, so keep the upstream release and log path available when reporting a problem.
- The launcher installs upstream packages; it does not turn ArtCraft or the other apps into a single bundled binary.
- The web build is a static catalog, not proof that every Craft editor runs inside a browser.
- Linux package compatibility depends on the release requirements, including the documented glibc and desktop-library constraints.
ArtCraft Launcher preview and release limits
This is an upstream preview of ArtCraft Launcher. It helps you recognise the workflow, but it is not a promise that every panel, model or file format is unchanged in v0.4.1. Use the release and source links above for the version-specific truth.
What the launcher solves
The Craft apps publish their own releases. That is good for independent projects, but it also means a new user can spend an afternoon opening separate GitHub pages, guessing which architecture matches the machine and checking whether a tool is already installed. ArtCraft Launcher puts that catalogue in one place. It shows the apps and versions it knows about, chooses the package for the current operating system and processor, and keeps the update path tied to the upstream release rather than to a third-party mirror.
Install, update and verify
The upstream README describes one-click installation for formats such as DMG, MSI, AppImage, deb, rpm and Flatpak. It also describes SHA-256 verification before an install and an update flow that keeps the running application in place while the new package is prepared. That makes the launcher useful for a machine with several Craft tools, but it does not remove the need to read the release notes: a checksum proves that a file matches the publisher, not that an early-alpha build is right for production.
Which platforms are covered
| Platform | Published route | Practical note |
|---|---|---|
| Windows | x86, x64 and arm64 MSI or portable zip | Choose the installer for managed/user installation or portable when you cannot install. |
| macOS | Universal DMG | The upstream README describes macOS 11+ support for Apple silicon and Intel with a signed, notarized DMG. |
| Linux | x86_64, aarch64; selected RISC-V packages | AppImage, deb, rpm, Flatpak and tar.gz availability depends on the release asset; the README documents glibc and desktop-library requirements. |
| FreeBSD | x86_64 tar.gz | The README targets FreeBSD 14 and a tree laid out for /usr/local with the required desktop libraries. |
| Web | Static WebAssembly catalogue zip | This is a catalogue you can host; it is not a hosted image or video editor. |
The launcher is not the editor
ArtCraft Launcher manages the Craft apps; it does not make PhotoCraft, VectorCraft, FilmCraft or ArtCraft share one binary or one privacy boundary. PhotoCraft and VectorCraft still have their own file and automation behaviour, while ArtCraft generation still depends on the model provider used by that workflow. If you are evaluating one editor, its own fact card and release page are the right next click. If you are installing the suite, the launcher is the convenience layer.
Launcher versus installing from GitHub
Installing directly from GitHub is still the clearest choice when you need to pin one exact asset, compare release notes, or troubleshoot a project without another layer involved. The launcher is useful when the problem is discovery: it can show the available Craft apps together, match a package to the machine, and make a later update easier to find. Those are convenience benefits, not a new distribution channel. The upstream repository remains the authority for the asset name, checksum, licence, release notes and any breaking change. OpenCraftTools therefore keeps both paths visible: use the launcher for a workstation with several Craft tools, or use the direct release page when a build must be audited or installed in a script. The two paths should lead to the same publisher-controlled files rather than to copies stored on this portal.
What to record when something goes wrong
A useful launcher bug report names more than the sentence “it will not install”. Record the launcher version, the app and release version, operating system, processor architecture, package format, checksum result and the exact step that failed. Note whether the problem happened while discovering an app, downloading an asset, verifying it, unpacking it, or starting the editor. A screenshot of a generic system warning is less useful than the release tag and the relevant log excerpt with private paths removed. If a direct release asset works while the launcher path fails, say so; if both fail, check the upstream issue tracker and runtime requirements. Keeping this small evidence bundle makes an early-alpha report reproducible and helps distinguish a bad download from an editor crash or an unsupported file.
Safe first setup
-
Choose the exact release asset
Match your operating system and processor before downloading. Do not infer architecture from a filename that only looks familiar.
-
Verify the published checksum
Keep SHA256SUMS.txt next to the downloaded asset and compare it before opening the installer.
-
Install one app first
Open a disposable project in one Craft app before asking the launcher to install or update the whole suite.
-
Record the launcher and app versions
Keep the launcher release, the app release and the operating system together when reporting a problem.
Who this is for
- Installing several Craft apps without searching each release page by hand.
- Keeping a workstation’s Craft tools on the same update and checksum workflow.
- Finding the correct Windows, macOS, Linux or FreeBSD package for a machine.
- Separating the suite manager from the editor or AI-generation workflow it launches.
Questions people actually ask
Is ArtCraft Launcher the same as ArtCraft?
No. The launcher installs, updates and opens the Craft App Suite. ArtCraft is the AI image and video studio; PhotoCraft and VectorCraft are separate editors with their own releases.
Does the launcher host or mirror the Craft apps?
No. It selects and installs upstream release packages from the project’s release feed, verifies the published checksum, and manages the local installation. OpenCraftTools also does not host or repackage those binaries, so the release page remains the authority for the exact asset and licence terms.
Does ArtCraft Launcher run on Linux?
The upstream v0.4.1 README documents Linux x86_64 and aarch64 packages, plus selected RISC-V assets including deb, rpm and tar.gz routes. Check the exact release asset, glibc requirement and desktop libraries for your machine before installing.
Is the Web version an online editor?
No. The upstream project describes the WebAssembly build as a static catalogue you can host. It is not proof that every Craft editor runs in a browser.
What changed in ArtCraft Launcher v0.4.1?
The v0.4.1 release adds FigCraft to the launcher’s Craft App Suite catalogue and publishes a new set of signed release assets. It remains early alpha, so keep the exact release link, checksum result, operating system and launcher log when diagnosing an installation or update issue.