Native .jws Format & Autosave

The native .jws format is the lossless editable JSlope project file. It holds the project, groups, scenarios, geometry, catalogs, loads, water, support, settings, and matching computed results in one saved file.

Opening and saving a local .jws file happens on your machine. This does not mean the entire application is offline: account/licensing, Cloud Materials, and optional hosted 3D data can still make their own network requests.

The .jws project file

A .jws file is a SQLite database. Scenario input hashes are calculated when the file is written. If computed results exist, JSlope creates a .jwsr results database and embeds it as the results.jwsr attachment inside the project.

On open, JSlope verifies that each bundled result's input hash matches its scenario before restoring it. A result is not silently attached to different inputs.

Saving and opening

Where the browser supports the File System Access API, Save can write back to the selected file and Save As chooses another destination. Other browsers use a file download for saving and a standard file picker for opening.

Standalone .jwsr results export

Choose File > Export Results to write the stored results for all computed scenarios to a standalone .jwsr SQLite file. This is an explicit export, not a sidecar that users must keep next to the .jws project.

The File > Open command accepts .jws projects; the current interface does not provide a standalone .jwsr import command.

Autosave

JSlope keeps a working recovery copy in browser local storage as the model is edited. It includes the scenario hierarchy and model state and may retain compacted result data while space permits. If browser storage is constrained, result data is trimmed before core model geometry.