Browser and offline requirements

Use desktop Chrome or Edge over HTTPS or localhost. Portable file access requires browser permission. Browser working storage uses SQLite in the origin-private filesystem (OPFS); the app must be cross-origin isolated. If isolation or storage is unavailable, follow the displayed error rather than assuming recovery is active.

Opening or reloading JMapper requires an internet connection to verify sign-in. After verification, the open tab can map and save local projects through temporary outages until its session expires. Models, measurements, textures and numerical resources remain local. The website manual requires a connection.

Application updates wait for existing JMapper tabs to close, avoiding replacement of a running project session. Save portable copies before closing your tabs to load an update. An unsuccessful application cache leaves the current workspace available but does not guarantee cached resources on a later load.

Ensure enough disk and browser quota for original data, prepared assets, scratch space and a portable save. Private browsing or restricted profiles can reduce storage availability. A published admission ceiling does not establish performance on every machine.

If a save fails, keep the current project open, review the error and available disk space, and retry Save As to a suitable location. Recovery status alone does not confirm a successful portable-file write.