Skip to main content
airglow ai

Product

Data & Storage

airglow ai keeps working data in your browser (local storage and IndexedDB) so sessions feel fast and private. You can move a listing to another device by exporting an Airglow save (.airglow) below. Knowing what clears local data helps you avoid surprises before a deadline.

What is stored locally

  • Listing snapshots: photo references, edits, AI-edit timelines, and analysis results (localStorage).
  • Enhanced and cached images for faster reloads (IndexedDB).
  • In-progress UI state for the current browser tab (session storage).
  • Guest-mode projects stay on the same browser profile until cleared.
  • Signing in aligns billing and credits; it does not sync your gallery to our servers. Use an exported Airglow save or your own photo exports for portability.

Export / import Airglow save

Export downloads one .airglow file (a ZIP archive with a manifest) for the listing currently open in the studio. It holds the full snapshot: photo list and order, listing metadata, AI analysis results, per-photo AI edit timelines (versions and prompts), which enhanced image is selected, display URL overrides, and paths to originals. Cached image blobs for those paths (including each AI-edit version) are embedded. On the other device, open this page, import that .airglow file, and you’ll return to the studio with everything restored. Plain JSON listing files are not supported.

Files can be large if you have many AI edits. Treat the file as sensitive (it contains your listing imagery and metadata). Credits cannot be exported in an Airglow save; they stay tied to the account you signed up with and are available whenever you sign in with the same credentials on any device.

Open a listing in the studio to export an Airglow save. You can import a save anytime.

What can cause data loss

  • Clearing browser data, “reset site permissions,” or uninstalling progressive web app data for airglowai.com.
  • Using private/incognito windows for long-running projects (data is discarded when the session ends).
  • Switching browsers, profiles, or devices without an exported Airglow save—local projects do not sync automatically. Export a save before you migrate.
  • Enterprise device policies or disk-cleaning utilities that purge browser caches aggressively.

Recommended habits

  • Download finished photos and keep a dated folder per listing.
  • Pause browser cleaners while you are mid-project.
  • Prefer a standard browser profile with sync disabled only if you understand the trade-offs.
  • Before a new device or browser, export an Airglow save on this page and keep your finished photo exports.
  • Document which device holds the canonical project if your team shares access.

Signed-in accounts

Authentication keeps billing and credits tied to your account. Credits are not inside an Airglow save, but signing in with the email you registered reconnects your balance on any device. Your gallery still depends on local storage—treat Airglow saves and photo exports as the durable record for listing work.

Wrapping up a project

  • Run a final pass in your OTA gallery preview to confirm ordering, crops, and captions.
  • Keep Airglow saves (.airglow) and finished exports in cloud backup or DAM tooling your team already trusts.
  • Only clear site data after you have verified downloads open correctly on another device.