ArtCraft and PhotoCraft: Where a Free, AI-Written Editor Stops

ArtCraft is the name in coverage for a suite of creative applications that rebuilds the Adobe workflow as free, open-source software. The app that carried the story is PhotoCraft, a Photoshop replacement: layers, masks, non-destructive adjustments, working on files that already sit on your own machine. Around it the reports describe LightCraft for photo development, FilmCraft for video editing, and a launcher holding the set together — each aimed at one line item of the bundle people have been renting by the month since the creative suite went subscription.

The detail that did the work was not on any feature list. Reports describe one developer — Brandon Thomas, by their account — pushing an AI coding agent to rebuild that workflow, with the coverage printing the model name (Claude Opus 5.5), then publishing the result under a permissive licence; the objection to monthly rent is the motive the articles give. Hold two caveats while you read the rest of this page. Nothing below came from our own machine: we never installed the suite, so every capability is dated inside the October 14–27, 2026 window of coverage and unverified outside it. And nobody seems to agree on how large the suite is — roughly seven applications in articles published around October 19, more on the download page that surfaced later, spreading into vector drawing, PDF, design, audio and CAD.

• 1

  October 14–15: install demos

  The first wave is video and posts showing PhotoCraft installed and driven like Photoshop, at no cost. At this stage the object of interest is one application, not a suite.

• 2

  October 16–18: the suite becomes the story

  Coverage widens from the photo app to the whole set, framed as "Adobe, CAD and Office, free and open-source". An encyclopedia entry appears on the 18th, alongside the first openly sceptical piece — a question rather than a claim: revolution, or hype?

• 3

  October 19–21: the meaning-of-it-all phase

  The larger tech titles now run headlines about artificial intelligence rebuilding Photoshop and Premiere. By the 21st most of the copy has turned away from the software and toward what its existence says about the people who write software.

• 4

  October 24–27: the second wave

  The framing shifts to the method — an agent-driven codebase rebuilt from scratch — and a download page for PhotoCraft starts showing up in search. Read in November, that is the newest layer of the story, not the most reliable one: a download page is not a project you have inspected.

Almost every article about ArtCraft frames it as "free Adobe", and that framing is why the comment threads keep talking past each other. An editor is a control surface over pixels you already supply: you point at one region of one photograph and change only that region. A generator is a sampler: it proposes pixels from a description, increasingly with a reference image to steer it. Both can sit in one window now, and one model can even have written both codebases. The difference between the jobs does not go away because of that.

This matters more on a site like this one than it does in the Adobe arguments, because the two halves are sold separately here. Layers, masks and a curves panel are not nostalgia — they are the only interface that promises you will leave the other nine thousand pixels alone. A prompt cannot make that promise. It is the reason a generated image and a retouched one are different purchases even when they open in the same window.

Swap a subscription editor for an open-source one and the story is about money, which is a fight that can be won — that is the entire content of "free and open-source". Swap the cloud half and the story changes shape. Coverage of ArtCraft draws the same split: applications that run locally cost nothing to run, while a feature that reaches for a distant model may burn credits, since the hardware answering that call was never inside your machine. The headlines mostly sanded this distinction away.

The reported weak points fall the same way. What the articles name as thin is file-format support, colour management, and audio on the video side — not design problems, but the unglamorous parts of a creative application: codecs, profiles, twenty years of edge cases. The screen is the cheap part to rebuild. A tool that is two years old reads a raw file from a camera that did not exist when the tool started, and that is a maintenance story, not a licence story.

A fast-rising project has a real risk profile, and almost all of it is about how you find it. "ArtCraft" and "PhotoCraft" are exactly the strings a search engine fills with lookalikes, and a download page that appeared in October 2026 says nothing about who published it. So the order of operations matters.

• Find the repository before you find an installer. Open-source means the code is somewhere public under a named licence. A page that offers a download and never shows you that is not the project; it is a page about the project.
• Open the licence text instead of trusting the headline. The reports say permissive; only the file tells you which permissive — MIT, Apache-2.0, something else — and whether it reaches the code, the models, or both. That answer stops being trivia as soon as money is involved.
• First run where being wrong costs nothing. Leave your real library at home; use a spare machine or the browser build. Code that arrived within a few weeks has not been probed by the people who have spent years probing the incumbents it replaces.
• Find out where the meter is. A free application can still sit in front of a paid GPU call. Treat every AI-branded menu item as billed until a document you actually read says otherwise.

If the half you actually want is generating rather than retouching, you can test it in this browser without installing anything. Our text to image tool runs Nano Banana 2.1, GPT Image-2, Flux-2 Pro, Wan 2.7 Image and Seedream 5.0 Lite, and image to image takes a reference photo plus a description and returns a new version of it. Credit costs are on the pricing page before you run a batch; a failed run does not spend credits.