ArtCraft repositories
ArtCraft GitHub: find the right repository
The ArtCraft GitHub starting point depends on your product: storytold/artcraft contains the AI Studio, craft-launcher manages Crafting Apps, and each app has its own repository. Use the map below before downloading a file or reporting an issue.
Which ArtCraft GitHub repository do you need?
| Your goal | ArtCraft GitHub repository | What to look for |
|---|---|---|
| Use or develop the AI image and video Studio | storytold/artcraft | Studio README, models and providers, development setup, and Studio releases. |
| Install, open or update several Crafting Apps | storytold/craft-launcher | Launcher releases, installation behavior, catalog and update documentation. |
| Edit an image with layers or work on PhotoCraft | storytold/photocraft | Image-editor releases, document features, packaging and PhotoCraft issues. |
| Organize photos or develop RAW files | storytold/lightcraft | Photo library, RAW development, supported inputs and LightCraft releases. |
| Find another member of the family | Official app directory | Open the actual product page and follow its View on GitHub link. |
The shared storytold account is an entry point for these projects, not a single installer. Searching “GitHub ArtCraft” can also show forks and similarly named projects. Confirm the product-to-repository relationship from the official website instead of choosing a result because its title sounds right.
Sources: Studio website and GitHub link · App directory and product links · Launcher README.
Confirm an ArtCraft GitHub repository before choosing a file
- Start from the product. Open the Studio site or the Crafting App’s official product page and follow the source link.
- Check the owner and project. Read both parts of the URL.
storytold/artcraftandstorytold/photocraftare different repositories. - Read the README’s task. An AI generation workflow, a software manager and a layered image editor solve different problems.
- Use that repository’s Releases. Check the tag, notes, prerelease label and package names before installing.
For a specific example, the Studio README discusses interactive AI image and video creation and links its own releases. The PhotoCraft README describes an image editor and links its PhotoCraft product page. A file or issue in one project does not automatically describe the other.
The ArtCraft apps guide explains those product boundaries. For the image editor’s exact release navigation, use the existing PhotoCraft GitHub guide; this page maps the wider family.
Sources: Studio README · PhotoCraft README.
Release assets, source archives and development files
| What GitHub shows | What it contains | Choose it when |
|---|---|---|
| A named DMG, MSI, AppImage or other release package | A build published for a stated platform and architecture. | You want a ready-made application and the release documents that package. |
| A portable application ZIP | An application directory intended to be extracted. | Its release notes identify it as the portable build for your computer. |
| A CLI archive | A command-line or headless tool. | You are following an automation workflow that requires that tool. |
| A WebAssembly or web archive | Files intended for web hosting or a documented browser setup. | You plan to follow that app’s hosting instructions. |
| Source code ZIP or TAR.GZ | The source tree attached to a release tag. | You want to inspect or build source, not install a desktop package. |
| Code → Download ZIP | An archive of the selected source branch. | You specifically need that branch’s development files. |
The extension alone is insufficient: a ZIP may contain a portable app, a CLI, a web build or source. Read the full filename and the release description. The version, operating system and architecture should correspond to the product you selected.
When the release publishes a checksum manifest, compare your exact downloaded asset with the manifest from the same release. A checksum helps check that file against the publisher’s manifest; it is not a general guarantee about the software’s behavior. Our PhotoCraft checksum instructions — Documentation checklist cover that app’s published files.
Sources: PhotoCraft package documentation · Launcher package and verification documentation · GitHub releases and tags documentation.
Launcher and standalone app repositories
A download or update failure can happen before the actual application launches. If the Launcher cannot fetch a release or select a package, start with the Launcher’s issue history. If the installed image editor opens but cannot save your sample, start with the PhotoCraft project. Keep the launch or installation failure separate from the document problem.
The Launcher README says it installs the apps’ own published release packages. It is therefore useful to record both the Launcher version and the affected app version. An update manager’s version does not tell a maintainer which image-editing engine you used.
For a normal installation, choose the official download route first. Building source is a separate developer task. Each repository has its own requirements and setup; the PhotoCraft source-build guide — Documentation checklist should not be copied as the Studio’s setup instructions.
Sources: Launcher installation and updates · Studio development entry points.
ArtCraft GitHub issues: where to report a problem
Use a small reproducible example and place it in the project that performs the failing action. Search that project’s existing issues before opening a new one; similar wording in another app’s tracker may describe a different component.
| Failure you observed | Likely starting point | Useful detail |
|---|---|---|
| The Launcher download or update fails | Launcher issues | Launcher version, affected app, package name, OS and exact error. |
| A PhotoCraft document renders or saves incorrectly | PhotoCraft issues | App version, minimal permitted sample, steps and expected output. |
| A RAW file or photo-library action fails | LightCraft issues | App version, camera/file type, operation and error. |
| The AI Studio workflow or provider integration fails | Studio issues | Studio version or browser, workflow, selected model and visible error. |
Account-specific billing details belong in the provider’s private support channel, rather than a public issue. Do not post access tokens, full account screenshots or private client material. For ordinary document problems, a reduced example you have permission to share is more useful than an entire project.
Record what was expected and what actually happened. If you only read about a feature, label your question as a documentation question instead of claiming that you reproduced a bug. Our evidence in this guide is the public repository mapping, checked on 2026-10-13; it is not a test of every release or service.
Read the chosen project’s contribution and license files
Before changing source, read the instructions and contribution files inside the repository you selected. The Studio, Launcher and PhotoCraft projects have separate structures, release processes and issue histories. A command that builds one project is not a universal command for the entire family.
Read the chosen revision’s licenses and third-party notices when distributing a modified build. “Open source” describes permissions and available code; it does not supply cloud model access, waive another service’s fees, or establish that your changes pass a release’s checks.
If you only wanted a program to install, return to the release assets rather than setting up a build environment. If you wanted to inspect how the Studio is offered, continue to ArtCraft AI access, models and costs.
Sources: Studio source and notices · PhotoCraft contribution and license entry points.