AppScreenshots DocsManage projects and backups
Keep editable screenshot masters organized, recover safely, and create versions without overwriting approved work.
Manage projects and backups
Use the dashboard as the home for active, approved, and historical screenshot projects. Good project hygiene turns a future release into an update, rather than a full rebuild.
Create a naming system
Name projects for retrieval, not just for the first person who creates them. A useful pattern is:
YYYY-MM platform or campaign — version — language or status
Examples:
2026-09 iOS 3.2 — English master2026-09 Android 3.2 — Japanese reviewSpring campaign — variant B — approved
Use the project name for the source record. The downloaded ZIP can then inherit a recognizable base name instead of becoming final-final-v3.
Start, duplicate, and retire work safely
| Dashboard action | Use it when | Safe practice |
|---|---|---|
| Create blank project | You have a new visual direction or a defined storyboard. | Name it immediately and add the release brief before designing. |
| Create from template | A template already matches the platform and information hierarchy. | Confirm that applying the template is appropriate before adding detailed work. |
| Duplicate | You are updating a live set, testing a variant, or adapting a market. | Duplicate first; preserve the approved project as the control version. |
| Delete | The project is genuinely obsolete and no longer needed for audit or reuse. | Export or duplicate anything worth retaining first. Treat deletion as irreversible. |
The editor does not replace a disciplined version history. Use project duplicates at meaningful approval points rather than treating one continuously edited project as the only record.
Understand saving and recovery
The editor keeps a local draft backup as you work, and existing cloud projects also save automatically when changes are pending. The header reports states such as Unsaved, Auto-saving, Saved, and Save failed.
For reliable work:
- Click Save before handoff, major template changes, or leaving the browser.
- If Save failed appears, keep the tab open, verify your connection and sign-in state, then retry saving before continuing elsewhere.
- When a restore prompt appears for a new or template-based draft, restore only when its time and content match your intended work.
- Do not assume a local backup is a replacement for a named cloud project and an approved exported package.
Organize assets for future changes
| Asset location | Put here | Example |
|---|---|---|
| Project Assets | Images relevant to one project or release | Current build captures, campaign illustrations, one-off badges. |
| Brand Assets | Reusable material that should be available across projects | Approved logo, stable icon, long-lived brand graphic. |
In Uploads, you can add JPG, PNG, WebP, GIF, or AVIF files up to 2 MB through file selection, drag-and-drop, or paste. Keep original captures outside the editor too, especially when they contain the only copy of an app state.
A light maintenance routine
- At release approval: duplicate or label the approved source and store the final ZIP with its release record.
- At the start of a new release: duplicate the latest approved master; never edit the only copy of a live set.
- After a campaign: remove stale material from the active project assets and identify the version that became live.
- Before deleting: confirm the project is not the only editable source for a market or experiment.
Continue with Publish and maintain screenshot sets, or use Troubleshooting if an editor action does not behave as expected.