Projects and recovery
Save portable SQLite projects and distinguish file saving from browser recovery.
A .jmap project is a self-contained SQLite database containing project metadata, original geometry, display geometry and textures. The source folder is not needed after a successful save. JMapper currently accepts schema and payload version 3 and rejects earlier pre-production formats.
Save writes the associated portable file. Save As... writes another file and associates it with the session only after successful close. Cancellation or failure leaves the previous file association and unsaved state intact. Large files stream through bounded chunks; saving may temporarily pause editing and asset traffic.
Autosave writes a separate browser recovery database. Recovery up to date does not mean the portable file is saved. The title's dirty marker and file status track explicit Save. Recovery status reports pending, saving, current or failed; its tooltip shows the last successful recovery time.
Choose File → Recover Autosaves to inspect other recovered projects. Replacing unsaved work requires a decision to save, discard or cancel. The active project is excluded from this list. A second instance of an edited project opens read-only.
Clearing site data can remove recovery work. Browser storage belongs to the current origin: moving from an earlier standalone JMapper address does not transfer recovery storage or preferences. Save a portable file on the old address and open it at jmapper.jwgeo.tech.
Project files are not uploaded by account sign-in. Keep independent copies of portable saves for backup.