For PhotoCraft 0.10.0. Keep the original file and check layers, fonts and the saved or exported result before relying on a complex PSD.

Start with a full reload, then try compatibility mode. PhotoCraft’s editor page has retry and compatibility controls exactly for this situation, and the app is a large download on first visit — some waiting is normal. Version reference: 0.10.0.

Why is the editor stuck on loading?

The browser editor downloads the application in parts (a small boot module plus the compressed application), then compiles it. On the first visit — or after a version update — this can take tens of seconds on a slow connection.

Wait briefly; the page itself shows a stall hint after 20 seconds.
Check the network connection, then use Try again to reload the workspace.
The editor needs WebGPU or WebGL2. Any current desktop browser has at least WebGL2.

If the editor fails with an explicit error, the page shows it and offers the same actions.

How do I use compatibility mode?

Choose Try compatibility mode on the error or slow-loading panel. It restarts the editor with the safer WebGL2 rendering path — useful when WebGPU drivers misbehave or the canvas stays black.

Compatibility mode restarts the editor. Save or export your document before switching if anything is still open; the editor warns you before restarting for this reason.

What happens if I retry?

Retry rebuilds the workspace with the same renderer setting. Your document state in the browser is not preserved across the restart — unsaved edits are lost. Finished exports and saved PSD files on your device are, of course, unaffected.

My work: what is safe and what is not?

Safe: files you saved or exported to your device; the original photos and PSDs on disk.
Not safe: unsaved work in an open editor tab. The web build has no autosave and no crash recovery — a closed tab is a lost document.

This is different from a file that opens but misbehaves — that has its own guide: why a PSD file will not open.

When nothing helps

Try another current desktop browser (Chrome, Edge, Firefox or Safari — a recent version).
Check that hardware acceleration is enabled in the browser settings; WebGL2 depends on it.
Use the desktop download — the native app does not depend on browser graphics support.

The editor also runs from the desktop app with the same document features; the browser build simply has stricter graphics requirements.