Fix Common PhotoCraft Browser Problems

Protect your work first

Download a saved or exported copy before reloading, changing renderer, closing the tab or clearing browser storage. The upstream web build does not provide crash recovery or server-side document autosave.

The editor has not loaded

The full editor is loaded only after you select Launch PhotoCraft. Its initial engine is about 24 MB uncompressed. Check the connection and allow the download to finish.

If the page remains on Loading PhotoCraft, open the full-window link. A modern browser and WebGPU or WebGL2 are normally needed. Use the WebGL fallback before launch; CPU fallback is also provided by the upstream build.

The app opens but the canvas is blank

Distinguish an empty document from a failed app. Use File → Open and try a small PNG or JPEG first. If only a particular PSD fails, keep that file and record its size, layers and symptoms before reporting upstream.

Large or complex documents can exceed the resources of a mobile browser. A desktop build may be a better environment; no universal browser compatibility is promised.

The file opens but looks different

1. Keep the source and compare against a reference image from the original application.
2. Inspect missing fonts, text wrapping, hidden layers, masks, blend modes, effects and color profiles.
3. Try a small PNG to distinguish a document-specific problem from a general rendering failure.
4. Record the exact source and receiving versions. Save a new copy and check the exported result in the receiving app.

See PSD checks and documented compatibility limits. A renderer switch is not evidence that a PSD feature is supported.

Saving or exporting did not download a file

Allow downloads for this page, check the browser’s downloads list and use the full-window editor if an embedded context is blocking a file dialog. File selection occurs inside the editor; files are not automatically transferred from the homepage preview.

Keep the original document and save to a new name. Do not treat a failed download as a reason to overwrite your only source file.

What has been checked in a browser?

The routes were checked at desktop and phone viewport sizes; that layout check does not test a mobile operating system, WebGPU or complex-file performance. Loading, blank-canvas, file-appearance and failed-save fixes above are diagnostic steps, not reproduced-and-fixed bug reports.

MCP cannot read or save a file

Check the headless versus bridge mode and the process that owns the file roots. The browser editor is not a desktop TCP control server.

For an upstream bug report, use storytold/photocraft on GitHub ↗ and include the app version, browser or OS, document type and reproducible steps. Avoid publishing private files in an issue.