PhotoCraft & Crafting Apps: WordCraft, VectorCraft & More
Meet the ArtCraft app family: PhotoCraft, VectorCraft, FilmCraft, LightCraft and WordCraft. Compare their purposes and find each upstream project and release.
Project links checked 18 October 2026. Each app has its own release cycle and availability.
PhotoCraft, ArtCraft and the Crafting Apps
PhotoCraft is the open-source image editor from the ArtCraft team and community. The upstream projects link to getartcraft.com as the team's website. This independent resource site hosts the original PhotoCraft v0.12.0 browser release; it is not the team's product website or a browser launcher for the entire suite. The identity guide explains the distinction.
Which app does what?
| App | Main purpose | Upstream source |
|---|---|---|
| PhotoCraft | Image editing and PSD workflows | PhotoCraft |
| VectorCraft | Vector illustration | VectorCraft |
| FilmCraft | Video editing, color and sound | FilmCraft |
| LightCraft | Photo library and raw development | LightCraft |
| WordCraft | Word processing and documents | WordCraft |
The table maps purposes, not feature parity or compatibility. Follow each repository's releases and documentation for the supported platform, package and maturity of that app. Shared authorship does not establish equal stability or seamless file exchange. WordCraft is a separate document editor, not a PhotoCraft text-layer plugin; LightCraft is not a mode inside this browser editor.
Downloads and version status belong to each project
For the current version of any app, open its own release record rather than borrowing PhotoCraft's version number. A repository README describes that project's state; it does not prove those features exist in this site's pinned PhotoCraft build. The download guide separates PhotoCraft native packages, our browser editor and the ArtCraft Launcher v0.6.1 macOS download.
VectorCraft, FilmCraft, LightCraft and WordCraft are not embedded here, and this guide does not claim to have tested their native binaries. Check their release notes before installing or choosing an interchange workflow. ArtCraft's AI image/video studio is also a distinct product: the name does not add generative AI to our hosted editor.
Start with the tool for your actual task
For a small image edit, try the PhotoCraft browser workspace and read the tested workflow. For vectors, video, raw photos or documents, visit the corresponding upstream project. Keep an original copy and verify exported files in the app that will receive them.
Choose an application by the output you need
A shared project family is useful context, but it is not a file-compatibility guarantee. Begin with the deliverable: a raster image, vector artwork, video, photograph adjustment or written document. Then inspect the relevant application's own source, release and supported workflow. A familiar family name does not establish that every application has the same maturity, platform support or editing model.
This site hosts PhotoCraft's fixed v0.12.0 browser release. The other projects linked here are external applications with independent artifacts and requirements. Their repositories can change without changing the editor on this website. Record the version of each application used in a multi-app workflow so that a later handoff or bug report can identify the actual participants.
Plan a raster-to-vector exchange explicitly
For artwork that moves between an image editor and a vector application, decide which parts need to stay editable and which can be delivered as an image. Export a small representative example and reopen it in the destination application. Check dimensions, transparency, appearance and the structure the recipient expects. Do not infer editability from the fact that an imported image looks correct.
If the exchange uses a flattened raster file, say so in the handoff. It is a reference or image asset rather than a promise of editable paths. If a vector or layered format is required, test that exact route separately. This website has not published a comprehensive interoperability benchmark for the family, so untested routes should remain clearly identified as unverified.
Treat video, photography and writing as separate tasks
A video workflow introduces its own frame, timing, color and export requirements. A photography workflow can depend on camera formats and color processing that a basic PNG edit does not exercise. A writing application has document-structure and typography requirements of its own. These differences matter more to the task than the similarity of project names.
Follow each project's documentation and test a small output in the actual receiving tool. Do not assume that installing the launcher creates a shared cloud workspace, common account or automatic synchronization across all applications. This website provides none of those services. If a particular app documents an integration, identify the relevant version and test the integration you intend to use.
Keep Launcher and application versions separate
ArtCraft Launcher is a manager for obtaining and opening applications, with its own download and update process. A launcher version is not a PhotoCraft engine version. An Update and restart control for the launcher should not be interpreted as updating every application or this website's browser assets. The download and usage guides distinguish the routes.
When a managed application behaves unexpectedly, record both the launcher and application version where available. Include whether the application was installed through the manager or directly from an upstream artifact. That context helps distinguish a distribution problem from a defect in editing behavior. Keep documents outside application installation folders and back them up before changing versions.
A small cross-application acceptance checklist
Choose a non-sensitive representative input, record the starting application and version, perform the export and reopen it in the destination. Compare the required appearance and editable elements separately. Record anything lost or changed and agree on a fallback format before using the route for important work. Keep the original input and a visual reference.
No family-level slogan can replace this check. A compatible result for one simple image does not establish that complex effects, fonts or color behavior survive every transfer. If a route remains unverified, explain that limitation to the recipient and use an already tested workflow for requirements that cannot be compromised. That gives the ecosystem links a practical purpose without inventing seamless integration.
Beyond manual use, PhotoCraft ships an MCP server for AI coding clients; see the Photocraft MCP setup guide.