Meet ArtCraft: Open-Source Alternatives to Adobe Creative Cloud Built With Claude
Meet ArtCraft: Open-Source Alternatives to Adobe Creative Cloud Built With Claude
What if a collection of familiar creative tools could be rebuilt from scratch, released as open-source software, and developed with help from an AI coding assistant?
That is the idea behind ArtCraft, a project on GitHub that has attracted attention for its ambitious attempt to recreate workflows associated with Adobe Creative Cloud. Its growing collection includes PhotoCraft for image editing, VectorCraft for vector graphics, FilmCraft for video editing, and several other applications aimed at different parts of the creative process. The projects are written in Rust and are presented as independent, open-source implementations.
The interesting part is not simply that these tools look familiar. It is the combination of a large software ambition, a systems programming language, and AI-assisted development—and the question of how much of a professional creative workflow a project like this can realistically reproduce.
ArtCraft is worth exploring, but it is important to set expectations: its applications are still developing, and resemblance to established software does not automatically mean equivalent reliability or functionality.
What Is ArtCraft?
The Storytold GitHub organization describes ArtCraft as a collection of open-source tools and models for creatives. Its repositories cover several familiar categories of creative software, from image manipulation and vector illustration to video editing, motion graphics, photo development, page layout, and PDF handling.
The names make the intended use cases fairly easy to understand:
PhotoCraft — image editing and a Photoshop-style workflow.
VectorCraft — vector illustration and an Illustrator-style workflow.
FilmCraft — video editing, colour work, and audio-related workflows.
LightCraft — photo organisation and RAW development.
EffectCraft — motion graphics and visual effects.
DesignCraft — page layout and publishing.
PdfCraft — reading, organising, and working with PDF documents.
These applications are related, but they are separate projects rather than one finished, unified replacement for Adobe Creative Cloud. The original ArtCraft application also has a distinct purpose: interactive AI-assisted image and video creation, with tools for composing scenes and controlling creative output.
That distinction matters. ArtCraft is not just one editor with several modes. It is an attempt to build a broader creative software ecosystem.
PhotoCraft: A Photoshop-Style Editor Built in Rust
Explore the repository: PhotoCraft on GitHub
PhotoCraft is one of the most immediately interesting projects in the collection because image editing is a demanding combination of visual design, file handling, rendering, and precise user interaction.
According to its official repository, PhotoCraft is designed around familiar image-editing concepts, including layers, masks, adjustment layers, layer styles, text, vector elements, brushes, and support for real PSD files. It is written in Rust and is described as a clean-room reimplementation rather than a release of Adobe's original source code.
For someone who has used Photoshop, this is an appealing feature list. Layers allow different parts of a composition to be edited independently. Masks provide control over which areas of a layer remain visible. Adjustment layers and layer styles support non-destructive editing workflows, while typography and vector elements help combine photography with graphic design.
PSD support is particularly relevant because layered project files are central to many existing creative workflows. However, claiming support for a format is not the same as guaranteeing complete compatibility with every document, effect, font, smart object, or advanced Photoshop feature.
That is where the distinction between a promising project and a dependable production tool becomes important.
An editor may offer the right buttons and concepts but still struggle with complex documents, export options, colour management, or less common image formats. In its October 2026 review, TechRadar reported limitations in PhotoCraft's file-saving options and HEIC support.
PhotoCraft is therefore worth watching, especially for developers interested in native image-editing software and artists curious about open-source alternatives. But it should not yet be treated as a drop-in replacement for a mature Photoshop workflow.
VectorCraft: Illustrator-Style Vector Design Without the Usual Subscription
Explore the repository: VectorCraft on GitHub
VectorCraft is designed for the kind of precision work used in logos, icons, illustrations, posters, and scalable graphics.
Vector design is a different challenge from pixel-based image editing. Instead of manipulating a fixed grid of pixels, a vector editor works with paths, curves, shapes, fills, strokes, and mathematical descriptions of objects. That makes tools for path editing and object manipulation central to the experience.
The VectorCraft repository documents features such as Bézier path editing, layers, artboards, gradients, Pathfinder-style shape operations, and SVG and PDF import/export. It also describes a native project format and the ability to control tools through an agent-facing interface.
That last feature is particularly interesting from a developer's perspective. VectorCraft is not just presenting a graphical interface for humans; the project describes a command API and a Model Context Protocol (MCP) server that can let compatible AI agents interact with the editor.
In principle, that could make tasks such as generating a collection of icons, creating repeated design variations, or exporting assets more automatable. But the presence of an API does not automatically mean every design task can be completed reliably by an agent. The quality of the output still depends on the available operations, the agent's instructions, and the application's behaviour.
The project also targets multiple environments. Its documentation describes native builds for macOS, Windows, Linux, and FreeBSD, along with browser use through WebAssembly.
For developers, this combination of vector graphics, a native codebase, browser portability, and agent control is arguably one of the most technically compelling aspects of ArtCraft.
FilmCraft: A Premiere-Style Video Editor
Explore the repository: FilmCraft on GitHub
Video editing is where the ambition becomes especially demanding. A usable editor needs much more than a timeline and a preview window. It must coordinate video decoding, audio playback, clip timing, transitions, effects, colour processing, export settings, and support for the media formats people actually use.
The FilmCraft repository describes a video editor built in Rust, with goals covering editing, colour, effects, audio, titles, formats, export, and interchange. Like the other Craft applications, it is designed for native desktop use and browser-based execution through WebAssembly.
A familiar timeline is a useful starting point, but it is not enough to make an editor ready for professional production. Editors need precise trimming, dependable playback, predictable audio, stable rendering, and reliable export. Problems in any of these areas can make a project difficult to finish, even if the interface looks polished.
That distinction appeared in TechRadar's October 2026 hands-on review. The reviewer found the interface familiar and could perform some basic editing tasks, but also reported missing manual clip-trimming behaviour, sluggish performance, and unusable audio playback with the test footage.
Those findings describe the reviewer's experience at that point in development; they should not be treated as a permanent verdict on every future release. They do, however, illustrate the distance between implementing visible editing controls and building a reliable media pipeline.
FilmCraft is an intriguing project to follow, particularly for people interested in media software architecture. For anyone editing client work, long-form video, or deadline-driven projects, its current capabilities should be tested carefully before relying on it.
The Rest of the Creative Suite
ArtCraft's appeal comes partly from its breadth. Rather than concentrating on one editor, Storytold is developing a collection of applications intended to cover different creative tasks.
LightCraft: Photo Management and RAW Development
Repository: LightCraft on GitHub
LightCraft targets photo-management and RAW-development workflows. This category of software needs to handle large image libraries, metadata, previews, colour adjustments, and camera formats. Those details matter just as much as the editing interface.
EffectCraft: Motion Graphics and Visual Effects
Repository: EffectCraft on GitHub
EffectCraft focuses on motion graphics and visual effects. A mature tool in this category needs a dependable composition model, effect processing, animation controls, and predictable rendering—not just a collection of visual presets.
DesignCraft: Page Layout and Publishing
Repository: DesignCraft on GitHub
DesignCraft targets page-layout and publishing workflows. Typography, font handling, layout precision, and export fidelity are especially important in this category.
PdfCraft: PDF Tools
Repository: PdfCraft on GitHub
PdfCraft focuses on PDF-related workflows, including reading, organising, and managing documents. PDF support can involve complex requirements around fonts, annotations, page structures, forms, and document security.
These projects show the larger direction of the ecosystem, but their intended feature sets should not be confused with verified feature parity. The official repositories are the best places to inspect the current source code, releases, issue trackers, and documented limitations.
Why Rust Matters Here
One of the most interesting technical decisions is the use of Rust, rather than building the entire suite as conventional web applications.
Rust is a systems programming language designed around performance and memory safety. Its ownership and borrowing rules help prevent several classes of memory errors without relying on a garbage collector. Those properties can be valuable in applications that manipulate large images, complex vector scenes, media timelines, or other performance-sensitive data.
Rust does not automatically make software faster or safer in every situation. Application performance depends on algorithms, rendering architecture, memory use, platform integration, and the quality of the implementation. But Rust is a reasonable choice for software that aims to deliver native desktop performance while maintaining a strong emphasis on reliability.
ArtCraft's repositories also describe browser support through WebAssembly. WebAssembly provides a way to run compiled code in supported browser environments, potentially allowing parts of a shared codebase to work both as desktop applications and in the browser.
For a project attempting to serve multiple operating systems, that is an appealing architectural direction. A shared implementation can reduce the need to maintain completely separate versions for desktop and web. It does not eliminate platform-specific work, though: file access, native menus, media codecs, GPU behaviour, and operating-system integration can still create differences.
The important question is whether the architecture translates into a consistent user experience. A cross-platform target is a design goal; stable, polished support on every platform is something that must be demonstrated.
Claude and the AI-Assisted Development Story
The other part of the ArtCraft story is the role of AI-assisted coding. Recent coverage attributes the development effort to a workflow involving Anthropic's Claude Opus 5.5 and describes the creator as using AI assistance to build the Rust applications.
That is a significant development story because professional creative software is an unusually broad engineering challenge. A single editor can contain thousands of interacting decisions involving file formats, rendering, interface behaviour, keyboard shortcuts, undo and redo, performance, accessibility, and compatibility.
AI coding assistants can help developers generate code, explore unfamiliar APIs, implement repetitive components, refactor existing modules, and work through debugging tasks. They can also make it easier to attempt a much wider scope than a developer might otherwise tackle alone.
But there is a critical distinction between generating a large amount of code and validating a complex application. Code can compile and still contain subtle state-management bugs. An interface can look convincing while a save operation loses important information. A video editor can display a timeline without supporting reliable audio playback or precise editing.
The project's scale is therefore evidence of what an AI-assisted development workflow can attempt, not proof that the resulting applications have reached production quality.
It is also worth being careful about attribution. The public repositories and independent reporting provide evidence of the project and the stated use of Claude, but they do not independently establish that every line of code was generated by AI or document the complete development process. The most useful assessment is based on the source, the features that work, and the limitations that can be reproduced.
What About the Open-Source Licences?
The ArtCraft repositories describe the applications as independent, clean-room implementations and identify permissive licences such as MIT and Apache-2.0 for relevant projects. Some bundled assets may have their own licensing terms, and the repositories distinguish project licences from protected names and logos.
For developers, permissive open-source licensing can make it easier to inspect the code, fork a project, contribute fixes, and build upon its implementation, subject to the specific licence and notices.
However, an open-source licence does not automatically settle every legal question surrounding a product that resembles commercial software. Source code, trademarks, copyrighted assets, and potentially distinctive visual presentation can raise different issues. The project's clean-room description is the developer's position, not a legal ruling that every aspect has been cleared.
Anyone planning to redistribute, commercialise, or build a business around one of these applications should read the repository's current licence, inspect third-party asset notices, and seek qualified legal advice where appropriate. Similarity to a familiar workflow should not be mistaken for affiliation with Adobe.
Are These Real Adobe Alternatives Yet?
The answer depends on what “alternative” means.
If it means an open-source project with a familiar interface, an ambitious feature list, and code that developers can inspect, ArtCraft is worth exploring. If it means a dependable replacement for professional work, the evidence is much less convincing.
TechRadar's hands-on testing identified practical shortcomings in PhotoCraft and FilmCraft, including file-handling issues, missing editing behaviour, performance concerns, and audio problems. Ars Technica's coverage similarly framed the projects as ambitious but far from finished.
A useful way to evaluate them is to separate three stages:
Feature demonstration: Can the application show the intended tool or workflow?
Workflow reliability: Can it complete a realistic task, save the project, reopen it, and export the expected result?
Production readiness: Can it do that consistently with real-world files, demanding workloads, and deadlines?
ArtCraft's public feature descriptions establish what the projects aim to support. Independent testing helps reveal how they perform in practice. The remaining work is to close the gap between those two things.
For now, treat the applications as experimental projects. Try them on copies of your files, preserve your originals, and check export and reopening behaviour before trusting them with important work.
How to Explore ArtCraft Yourself
The easiest place to start is the official Storytold GitHub organisation, which links to the individual application repositories. You can then choose the tool that matches your interests:
For image editing: Start with PhotoCraft.
For vector graphics: Explore VectorCraft.
For video editing: Inspect FilmCraft.
For the broader suite: Browse the ArtCraft apps directory.
For the original AI creative studio: Visit ArtCraft on GitHub.
Before installing anything, check the current release notes, supported operating systems, build instructions, known issues, and licence. If you are interested in contributing, the issue tracker and source code can help you identify which features are implemented, which are still in progress, and where the project needs help.
The Bigger Picture: An Ambitious Project, Not a Finished Replacement
ArtCraft is interesting because it brings several important themes together: open-source creative software, native development with Rust, cross-platform ambitions, agent-accessible interfaces, and AI-assisted coding.
Its most compelling promise is not that Adobe Creative Cloud has already been replaced. It is that a small development effort can attempt a broad collection of complex creative applications and make the work available for public inspection and contribution.
That is a meaningful ambition. But the hardest part of creative software is often the work that is least visible in a screenshot: reliable file handling, precise controls, predictable rendering, compatibility, performance, and the small details that make an application dependable every day.
PhotoCraft, FilmCraft, VectorCraft, and the rest of the suite are worth following for what they reveal about modern software development. Their progress will be measured not by how closely their interfaces resemble familiar tools, but by how reliably they help people finish real creative work.
For developers, ArtCraft is a project to study. For artists, it is an ecosystem to experiment with cautiously. For anyone hoping to leave Adobe behind, it is a promising work in progress—not yet a reason to abandon a proven workflow.