What “ArtCraft online” means here

OpenCraftTools does not host ArtCraft and does not proxy the browser session. The online button leaves this site and opens the address published by the official ArtCraft project. Once the tab opens, the upstream application controls sign-in, session storage, file handling, model-provider calls and any usage limits. That distinction matters because a community guide can point to the right door without becoming the operator behind it.

Browser entry versus desktop release

A safe first visit

1. Start at the upstream address

   Use the OpenCraftTools launch button or type app.getartcraft.com yourself. Check the address bar before opening a file or entering an account.

2. Read the current upstream notice

   Confirm whether the session needs an account, where files are handled and which model services are called. These details can change independently of this guide.

3. Try a disposable asset

   Use a sample image or a copy of a project first. Do not assume a hosted browser surface has the same local-only boundary as a self-hosted WebAssembly build.

4. Move to desktop when the workflow matters

   If you need a pinned release, repeatable local files or a feature that is only available in the installed build, download the v0.41.0 desktop release and record the asset you tested.

Why the distinction affects SEO and real users

“Online” is often used as if it means free, private, accountless and identical to desktop. It means none of those things by itself. A browser entry can be convenient while still having a separate service boundary; a local WebAssembly archive can run in a browser while being self-hosted; and a desktop binary can still call a model provider when you choose a generation step. A useful answer names the architecture instead of attaching a promise to the word online.

When to choose each one

What a browser test can and cannot prove

A successful page load proves only that the published entry can be reached in your current browser. It does not prove that an import will preserve every layer, that a model call will be available in your region, that a session will remain signed in, or that a project can be reopened from the desktop release. Keep those questions separate. First test the entry with a small disposable asset. Then test the exact file, feature and export that matter to your job. If the browser surface gives you a useful result, save the output and note the date, browser, operating system and upstream release information shown in the application. That record is more reliable than a generic “works online” badge.

What to record before a team adopts it

Teams should write down four boundaries before making the browser entry part of a shared process. Record who owns the external account, whether the source asset is allowed to leave the workstation, which provider is called during generation, and where the resulting project can be reopened. Also record the fallback: the ArtCraft desktop release, PhotoCraft for local layered finishing, or another established application. This is not bureaucracy for its own sake. A browser service can change independently of a pinned desktop tag, and the recovery plan is part of the creative workflow whenever a client file or paid generation is involved.

• Choose the browser entry for a quick look at the current upstream workflow or when you cannot install software yet.
• Choose the desktop build when you need a release tag, local project control or a workflow you can test on one known machine.
• Do not use either surface for sensitive client material until you have read the relevant upstream file and privacy terms.
• Use PhotoCraft for local layered finishing when the task is PSD, masks or pixel editing rather than AI scene direction.

Who this is for

• Previewing the ArtCraft workflow without installing a binary
• Checking whether a browser session fits a short creative test
• Separating hosted-app privacy questions from local desktop questions
• Choosing between a browser trial and a pinned release for a team workflow

Limits worth knowing

• The online surface is controlled by the upstream project, not this portal.
• Browser and desktop feature parity is not assumed without a current test.
• The browser entry does not remove model-provider accounts, pricing or network dependencies where those apply.

Questions this guide gets asked

01

Is ArtCraft available online?

The official ArtCraft site links to app.getartcraft.com as a browser entry. Availability and feature behavior belong to that upstream application and can differ from the desktop release.

02

Is ArtCraft online the same as ArtCraft v0.41.0?

Do not assume exact parity. The desktop release is a versioned macOS and Windows asset; the browser entry is a separate upstream surface whose current capabilities should be checked when opened.

03

Does OpenCraftTools host the ArtCraft app?

No. OpenCraftTools only documents the project and sends you to the upstream address after an explicit click. The portal does not receive the external session, files or tokens.

04

Can I upload private files to ArtCraft online?

Only after reading the current upstream privacy and file-handling notice. This portal stores nothing, but it cannot guarantee the behavior of an external hosted application.

05

Which version should I cite in a tutorial?

For desktop instructions, cite the exact release tag, currently ArtCraft v0.41.0 in this fact card. For the browser entry, record the access date and the upstream page because it is not a desktop asset tag.