Is ArtCraft Safe? A Practical Look at the Open-Source Adobe Clones and Their License

Facts checked on November 1, 2026. GitHub numbers come from the public GitHub API on that date.

In October 2026, a set of free, open-source "Adobe-style" desktop apps went viral. The apps are PhotoCraft for Photoshop-style editing, FilmCraft for Premiere-style video, plus several siblings. The suite is called ArtCraft, it comes from Brandon Thomas's company Storyteller.ai, and the code is published under the storytold organization on GitHub. The coverage took a range of angles:

• Ars Technica framed it as a bold developer "taking aim at Adobe" (Ars Technica, Oct 2026).
• CineD covered the FilmCraft and EffectCraft releases (CineD).
• InfoQ wrote about PhotoCraft's push toward Photoshop parity (InfoQ, Oct 2026).
• XDA said the suite is "almost ready to replace the real thing" (XDA).
• Creative Bloq tried the apps and reported "some big problems" (Creative Bloq).

Whenever a free tool gets this much attention, two questions follow: is it safe to install? and what am I actually allowed to do with it? This piece answers both using only things you can check yourself.

1. What "open source" gets you here

GitHub's API reports the license of storytold/photocraft and storytold/artcraft as Apache-2.0. On November 1, 2026, the PhotoCraft repository had about 75,700 stars and the main ArtCraft repository about 38,000.

Apache-2.0 is a permissive license. In plain terms:

• You can use the software for free, including commercially. Making client work in PhotoCraft doesn't owe anyone a fee.
• You can modify and redistribute it. You have to keep the license and copyright notices and mark files you changed.
• There's an explicit patent grant from contributors, which goes beyond what MIT or BSD licenses spell out.
• There's no warranty. The software is provided "as is." If an alpha build corrupts a file, the license gives you no recourse.

One thing the license does not cover is your artwork. Images and videos you create are yours. Apache-2.0 governs the code, not the output.

A second point people miss: a permissive license also lets anyone repackage the software. That's a feature for open source, and it's also exactly what makes the next section necessary.

2. The real risk isn't the code, it's the download

Open source means the code can be inspected. It doesn't mean every file with "PhotoCraft" in its name came from that code.

Here's a concrete example from this month. A public launch-tracking site lists an entry titled "PhotoCraft-Photoshop." It's sourced from a GitHub repository and dated October 10, 2026. Its description is mostly keyword stuffing ("photocraft, artcraft photocraft, github photocraft…"). It advertises an "Official free download" of "v0.5.0" as a "Local zip" for Windows. Meanwhile, the newest release in the official storytold/photocraft repository was v0.18.0, published October 31, 2026.

I haven't analyzed that zip and I'm not linking to it. Still, the pattern is classic, and it's how most people get burned by popular free software:

1. A trending name.
2. A page that insists it's "official."
3. A version number that doesn't match upstream.
4. A bare zip with no checksum.

How to tell an official build apart

As of November 1, 2026, official PhotoCraft releases on GitHub follow a consistent layout:

• File names look like photocraft-0.18.0-windows-x64.msi, photocraft-0.18.0-windows-x64-portable.zip, photocraft-0.18.0-macos-universal.dmg, plus Linux .deb, .rpm, .AppImage, and .flatpak packages.
• Each release ships a SHA256SUMS.txt file.

That gives you a simple checklist:

• Get files only from github.com/storytold/... releases or from getartcraft.com. If the URL is anything else, stop.
• Compare the version to the latest official release. If a "download site" offers a version that doesn't exist upstream, it isn't upstream.
• Verify the checksum. On Windows: certutil -hashfile photocraft-…-windows-x64.msi SHA256. On macOS or Linux: shasum -a 256 <file>. Compare the result with the line in SHA256SUMS.txt.
• Be suspicious of "launcher" or "installer" wrappers from third parties. The official layout already includes MSI installers and portable zips, so there's no reason for a middleman.

3. Alpha software and your files

The second risk is ordinary and honest: these apps are young. The project describes them as early-stage, and Creative Bloq's hands-on reported real problems. That isn't a security issue, but it's a data-safety issue:

• Work on copies, not originals, especially when opening PSDs or project files from other tools.
• Don't make an alpha app the only tool on a client deadline.
• Expect fast change. A release on October 31 and frequent updates mean behaviour can shift week to week. Read the release notes before updating mid-project.

4. "Written with AI": does that change anything?

Much of the coverage focuses on the suite being built heavily with AI coding tools. For safety, the questions that matter are the same as for any project:

• Is the source public?
• Are builds published from the official repo with checksums?
• Can problems be reported in public issues?

All three are true for the storytold repositories as of today. Whether AI-assisted code is good is a fair debate about quality and maintainability. It isn't evidence that the official binaries are malicious, and nothing I found suggests they are.

5. Bottom line

• The official ArtCraft apps: free, Apache-2.0, public source, checksummed releases. Reasonable to try, with the normal caution you'd apply to alpha software.
• Unofficial "official downloads": the actual danger. Treat any PhotoCraft or ArtCraft file that didn't come from storytold on GitHub or from getartcraft.com as untrusted, however convincing the page looks.
• Your output is yours. The license covers the code, not your art.

If you want a running, dated checklist of official download locations, license details, and how each Crafting App compares, I keep one at ArtCraft Review. It's an independent, unofficial guide and isn't affiliated with ArtCraft, Storyteller.ai, or Adobe.

---

Disclosure: I run the unofficial guide linked above. I have no relationship with the ArtCraft project. Sources: the GitHub API (repos storytold/photocraft and storytold/artcraft, retrieved Nov 1, 2026) and the articles linked inline.