Project files: save, reopen and move your work
Choose the right kind of save
| Purpose | Use | What it preserves |
|---|---|---|
| Continue editing on this installation | Save scene / saved-project catalog | Project revision and accepted/draft state; referenced bytes stay in this installation. |
| Move or archive editable work | 💾 Save project (.qway) | Complete authoring checkpoint plus referenced original resources. |
| Publish a visitor experience | Export WorldPack | Compiled runtime data, optimized desktop/mobile media and RAMS site. |
| Back up all users and all projects | Server filesystem backup | Accounts, every workspace, resources, vault and operational data. |
The current toolbar may show the Italian labels Salva progetto (Save project) and Leggi progetto (Open project). The prose in this manual is English; screenshots preserve the actual application labels and authored project content.
Save a complete .qway checkpoint
- Stop playback/simulation. Apply any inspector form changes you want to keep. Unapplied form text and transient runtime movement are not authoring data.
- Choose 💾 Save project. Wait for archive creation and the browser download to finish; a large textured world can take time.
- Keep the downloaded .qway file in your project backup location. Do not confuse it with a plain QWAY source-text file, which historically uses the same suffix.
- Use a separate session or installation to test reopening before relying on the archive as your only copy.
The archive is a ZIP with a versioned manifest and per-member hashes. It preserves source, invalid drafts, accepted compiled state, WRIGHT, RIDLEY, RAMS, materials, current room, authoring history and the supported workspace checkpoint. Referenced original GLBs, measured manifests, images, audio, content, personas and already-generated speech dependencies travel with it. Save does not resize textures, recompress media or call an AI provider.
Open without overwriting the original
- Choose 📂 Open project and select the .qway archive.
- Wait for integrity and dependency validation, resource import and rendering. Avoid clicking Import repeatedly while the first operation is active.
- The import creates a new saved project identity/revision. Existing projects and conflicting resource bytes are not silently overwritten.
- Inspect the current room, materials, directing source, RAMS configuration and history. An invalid draft remains a draft over its last accepted scene.
- Continue editing and save the new project in the local catalog or export another checkpoint.
All archive members are verified before publication. Missing dependencies, corruption or conflicting UUID resources cause an explicit failure rather than a partial success. If a legacy project produces a schema error, keep the original and its data directory; inspect the reported field/version before attempting a migration. Do not substitute a WorldPack and assume that the lost authoring state can be reconstructed.
What is outside a project archive
Other projects, accounts, login sessions, deployment secrets, trusted SSH keys and job history are installation data. External links remain links; the archive does not crawl and snapshot remote websites. Built-in application texture presets require the corresponding application version. A full server backup is still necessary.
Importing a production WorldPack
WorldPack import registers the GLBs contained in the selected desktop/legacy profile, including packaged models that the current scene does not reference. It verifies bytes, creates local asset/manifests as needed and updates scene references. Mobile duplicates are not imported as separate authoring models.
Production textures may already be reduced. Import cannot recover original image detail, undo history, unsaved source or other authoring information absent from the package. Use .qway for lossless continuation of work and WorldPack for delivery.