> For the complete documentation index, see [llms.txt](https://help.adalo.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.adalo.com/publishing-apps/publishing-to-the-apple-app-store/creating-screenshots-for-the-app-store.md).

# Creating Screenshots for the App Store

Creating effective screenshots for the app stores is crucial for attracting potential users. Not only do these images provide a visual preview of your app, but they can also convey its main benefits, features, and user experience. Here's a step-by-step guide to create compelling screenshots for the app stores:

### Requirements

1. Some screenshot sizes are required in order to submit your app for review.
2. Screenshots have to be taken on a physical device using the Testflight version of your app.
3. Apple provides required specifications in their [Screenshot Reference Guide](https://developer.apple.com/help/app-store-connect/reference/screenshot-specifications).
4. Screenshots can only be changed when submitting a new app for review. You cannot edit existing screenshots as they may not reflect the current version of the app.&#x20;

### Walkthrough

1. Open app in Testflight. This needs to be done on an iPhone that meets the requirements in the Apple [Screenshot Reference Guide](https://developer.apple.com/help/app-store-connect/reference/screenshot-specifications).
2. Take Screenshots that give users a visual preview of your app.
3. Load screenshots to the Apple Store Connect Version of your app that you are wanting to submit for review.

### Making Great Screenshots

As with the other files, make sure to pay attention to the requirements under this field - your images will not upload if they are not compliant. You can use most of the same tools for these screenshots, such as [Mockuphone](https://mockuphone.com/), [CleanMock](https://cleanmock.com/), [AppScreens](https://appscreens.com/), and [AppLaunchpad](https://theapplaunchpad.com/). Many makers use the device previewer in Adalo to capture screenshots using a screen capture tool such as [Screen Capture on Mac](https://support.apple.com/en-us/HT201361) or the [Snipping Tool on Windows](https://www.makeuseof.com/tag/how-to-take-a-screenshot-on-windows-pc/)

{% hint style="danger" %}
Because the screenshot specifications for Apple are very specific, we recommend you do not edit or crop the screenshots as this will change the specs and render them unusable.
{% endhint %}


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://help.adalo.com/publishing-apps/publishing-to-the-apple-app-store/creating-screenshots-for-the-app-store.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
