AppScreenshots DocsTroubleshooting
Resolve common Screenshot Editor, localization, asset, and export issues before delivery.
Troubleshooting
Work through the checks below before rebuilding a frame. In most cases, the issue is a selected language, missing asset, unsaved project, or an output package that has not yet been inspected.
Save, restore, and project issues
| Symptom | What to do |
|---|---|
| Header says Unsaved | Select Save before leaving the editor or sending the project to review. |
| Header says Save failed | Keep the editor tab open, verify your network and sign-in, then retry Save. Do not assume the latest changes reached the project until the status changes. |
| A restore dialog appears | Restore only when the date and contents match the draft you intended to resume. Otherwise discard it and open the correct project or template. |
| Need to try a different design | Duplicate the project from the dashboard rather than overwriting the approved source. |
| Accidentally applied a template | Templates replace current content. Use a saved version, duplicate, or a suitable restored draft to recover; save before experimenting next time. |
Screens, devices, and assets
| Symptom | What to do |
|---|---|
| A device has no app screen | Select the device, then use Device Properties → Upload Screenshot. You can use Replace later without rebuilding the layout. |
| Uploaded asset cannot be selected | Upload a supported PNG, JPG, or SVG file under 10 MB through Uploads, then select it from Project Assets or Brand Assets. |
| UI is too small to understand | Enlarge the device and simplify decoration; the product screen should remain readable at final export size. |
| Content is cropped unexpectedly | Inspect the frame edges at 100% output, then reposition, resize, or reduce shadows. If resizing an existing export, choose a suitable cover, contain, or crop treatment in Screenshot Resizer. |
| An element is hidden | Select it and adjust its layer order with the property controls, or use the layer shortcuts from the editor guide. |
Text and localization
| Symptom | What to do |
|---|---|
| A locale shows master-language copy | Switch to that language, select the text element, and add deliberate localized content. Do not treat fallback content as approved by default. |
| Text overflows or overlaps the device | Shorten the approved copy, adjust text size or placement, and review the entire frame at normal output scale. |
| Characters render incorrectly | Choose a font that supports the language and check the font in the active locale. |
| Batch translation is unavailable | The interface marks Batch Translate for Pro/Lifetime access. Use per-element language content if it is not available to the current account. |
Export and delivery
| Symptom | What to do |
|---|---|
| Need only one image | Select the intended language and use Download → Current Frame. |
| Need the full current locale | Use Download → Current Language, then unzip and inspect every file. |
| Need several languages together | Use Batch Export All Languages after reviews; choose folders or filename suffixes as the receiver requires. The feature is marked Pro/Lifetime in the product. |
| Export package looks wrong | Verify active language, frame order, saved state, and current app screens; export again, then inspect the extracted PNGs rather than relying only on the ZIP name. |
| Store rejects a file | Check the destination store’s current dimensions, count, file type, policy, and required device coverage. Update the project or use Screenshot Resizer only when the source image remains appropriate. |
What to include in a useful support report
Use the editor’s floating menu to send feedback, or use the contact page. Include:
- Project name and whether it is a new, template, or existing project.
- The frame number and active language.
- The action you took and the expected result.
- The actual result, error wording, and whether it repeats after saving and reopening.
- A non-sensitive screen recording or screenshot when it helps explain the issue.
Do not include customer data, secrets, or unredacted production credentials in a support image.
If the issue is procedural rather than technical, return to Getting started or Plan a complete screenshot set.