ScreenWisp does not upload projects to an account server. The default is local storage in the current browser. Supported Edge and Chrome versions can instead use a device folder that you explicitly select. Important work should also have a separate backup.
Test a restorable backup without deleting the original
Prepare
Use a small test project with a photo and a short caption. Do not delete real work or browser data to test recovery.
Steps
- Use Save backup in Storage, wait for the .ambientpack download to finish and add a date to the saved filename.
- Choose that file in Restore backup. Compare the restored photo, caption and layout with the original and run its preview. A project appearing in the list does not prove its media restored correctly.
- In supported desktop Chrome or Edge, connect a separate test folder. If a browser-project copy prompt appears, review the selection; connecting a folder does not mean all existing projects automatically moved.
- To move to another device, copy the .ambientpack or the complete project folder containing manifest.json, project.json and assets. Refresh the folder list if the project does not appear.
Check the result
Confirm actual media and placement in the restored copy, then keep the original and backup in separate locations. Two copies on one drive do not protect against that drive failing.
If the result differs
Reconnect and grant folder permission if it expired. If connecting does not update the list, refresh the page once. A cover image or project.json alone cannot replace missing assets.
When is browser storage convenient?
It needs no extra permission, so it is the fastest way to begin and works well for small projects or an initial trial.
Every ScreenWisp project under the same browser profile shares the site quota. Clearing site data or switching browser profiles does not carry the projects with you.
What changes with selected-folder storage?
In supported Chrome or Edge, approve read/write access to a folder. Each named project subfolder contains manifest.json, project.json and assets. A successfully generated cover is stored as preview.webp, but a project can work without it. Stable project IDs remain in the JSON files.
You can inspect and copy these files with the operating-system file manager and use disk space beyond the browser site quota. Browser security may ask you to grant the folder permission again on a later visit.
What happens when you connect a folder later?
On first connection, you can review projects that remain in browser storage and choose which ones to copy. If folder and browser versions of one project differ, keeping a separate copy is safer than overwriting either source.
A complete project folder copied from another PC can be placed under the connected top-level folder. Choose Refresh folder in My screensavers to validate it and add it to the list. If the view does not update immediately after connection, the page also tells you to refresh once.
Why keep an .ambientpack too?
Folder storage is a working location. An .ambientpack is a ZIP-based ScreenWisp package for moving or archiving one project, including scene settings and the actual images, GIFs, video, audio, and preview.
A selected folder can still be lost to device failure, accidental deletion, or sync conflicts. Keep dated .ambientpack copies on another drive or a personal backup destination you trust.
A simple choice by use case
- A few small projects or a quick trial: browser storage
- Large images and video with direct file management: selected-folder storage
- A browser without folder access: browser storage plus regular .ambientpack exports
- Device transfer or long-term archive: an .ambientpack in addition to the active storage
Try the workflow instead of only reading about it
ScreenWisp lets you create and preview a fullscreen display inside the browser without an account or a media upload.
Create in Studio ↗