Read the stage shown by the loader
The host downloads a pinned release and shows progress from bytes actually received. At 100%, the browser still needs to compile WebAssembly and initialize rendering. That stage has no honest percentage estimate.
The panel disappears after the original app removes its startup indicator and provides a canvas. A completed network download by itself does not establish that the editor is ready.
Check a stalled or failed transfer
Confirm the connection and retry before starting a document. The error panel identifies HTTP failures, an incorrect WASM content type or an incomplete download. Network filtering can also block an asset.
The v0.7.0 engine is 24,996,331 bytes before compression. A slow connection needs time. If an error persists, report the page URL and displayed message without attaching private files.
Try a fallback deliberately
The official web build prefers WebGPU and supports WebGL2 fallback. The startup error panel offers Try WebGL2 and Try CPU mode. CPU mode is a slower troubleshooting path.
You can open the WebGL2 editor or the CPU editor. Either starts a fresh session. Download open work first. The site does not refresh an active editor or change its renderer automatically.
Check the browser and document size
Use a current desktop browser with hardware acceleration and compatible graphics drivers. HTTPS is needed for WebGPU and clipboard features. Test a small PNG to distinguish startup trouble from a large document exhausting memory.
The editor has a desktop interface. Touch editing and mobile exports are not part of this host's initial acceptance test. The official desktop application is another option when a browser cannot run a file reliably.
Based on the official web hosting guide and v0.7.0 source documentation. Independent guidance; keep original files and verify your outputs.