User Guide · Saving & dashboard
User Guide
Developer
Saving: your work is never one tab-crash from gone
The editor autosaves to your browser as you work, share links freeze a scene into a URL, and signed-in workspaces list the projects stored on your account. Here is exactly what persists where.
Browser saves, per template
Every edit is autosaved to local storage after a short debounce, keyed by template — your mailer box and your RSC keep separate saves. The Save button in the toolbar writes the same snapshot immediately and flips to a green Saved check. Reopen the same template and you continue where you left off.
The restore order, highest priority first:
- 1
Share link
A ?state= URL always wins — that is what makes shared scenes reproducible.
- 2
Local save
Your browser save for this template, if one exists.
- 3
Template defaults
The catalog defaults: stock dimensions, the first material and finish, studio lighting.
Share links as snapshots
Share encodes the full editor snapshot into the URL itself — no server round-trip, nothing stored, nothing to expire. The trade-off is size: artwork above roughly 1.5 KB as a data URL is stripped from links (the toolbar warns), while sub-KB SVG symbols and patterns ride along fine. Links are public by construction: anyone with the URL sees the scene.
The dashboard
/dashboard is your signed-in workspace. It lists the projects stored on your account — newest first — each card showing the name, template, dimensions, and last-updated date. Clicking a card opens the editor for that template. The header shows your account email and current plan, with a direct link to compare plans.
Browsing galleries and editing work without an account; the dashboard is the part that needs one. Sign up at /signup — the Free tier needs no card. Sessions are token-based and last 7 days; your session lives in your browser, so clearing site data signs you out.
Account projects, honestly
When you are signed in, the editor's Save button also mirrors the snapshot to your account (POST /projects the first time, PUT /projects/:id after that), storing the name, template, dimensions, and the full editor state as artworkJson. The dashboard reads that same list back, and clicking a card reopens the editor with the saved scene restored — heavy upload artwork follows the same stripping rule as share links. The Projects API remains the supported path for your own tools, and it is exactly what the dashboard consumes.
What survives what