# Screenshots

On the **Screenshots** step, you can view, add, remove, and approve screenshot and preview videos that are currently staged to go out with this release in the app store for Apple and Google platforms.

<figure><img src="/files/RPyX8PHBWsDbSqe1PM8F" alt=""><figcaption></figcaption></figure>

### Viewing screenshots and preview videos

Use the **Device** selector to switch between assets for different device sizes or alternate hardware types. You can click on any given screenshot or preview video to view it in full size.

{% hint style="info" %}
If a particular size is set to share assets from another size on iOS/tvOS platforms, you’ll see a “Using XX Display” message.
{% endhint %}

Each localization for your app will be displayed in a separate tab.

* A <mark style="color:green;">green</mark> status dot will appear on tabs where specific assets have been found for that localization, and minimum app store requirements have been met.
* An <mark style="color:orange;">orange</mark> status dot will appear on tabs where required assets are still missing.

### Editing screenshots

Screenshots and preview videos can be added or removed for a given device size. Note that screenshot re-ordering is currently not supported.

{% hint style="info" %}
Videos cannot be directly edited on the Screenshots step for Google platform apps. To edit a video go to the [Metadata step](/using-runway/release-steps/metadata.md) and add or update the YouTube Video URL field.
{% endhint %}

{% hint style="warning" %}
For upcoming releases, the version must exist in the App store in order to edit screenshots.
{% endhint %}

### Approval

Granting approval for screenshots is a way for your team to communicate in Runway that screenshots have been verified on each release.

{% hint style="warning" %}
App stores are not affected by the approval status of the Screenshots step in Runway. Missing approvals on the Screenshots step will not block a manual submission or release performed from Runway or from the app stores.
{% endhint %}

Release pilots or other users with sufficient privileges can click the **Approve screenshots** button at the bottom of the view to mark this step as ready. This will set the Screenshots step as <mark style="color:green;">green/ready</mark> (and may unblock automations like [Submit app for review on target date](/automations/types-of-automations.md#submit-app-for-review-on-target-date) that depend on all previous steps being green).

Approval can be reversed by users with sufficient privileges by clicking the **Rescind screenshots approval** button. This will return the step status to <mark style="color:orange;">orange</mark> and may block automations that depend on this step being green/ready.

### Screenshots checklist

You can add checklist items to this step by visiting the Checklist tab.

[Checklist items](/using-runway/checklists.md) cover any unique parts of your team's release process and live across all your releases. Steps with checklist items won't be marked as complete (green) in Runway until all checklist items have been completed (in addition to the normal criteria that would mark a step as completed).


---

# Agent Instructions: Querying This Documentation

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

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.runway.team/using-runway/release-steps/screenshots.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.