> For the complete documentation index, see [llms.txt](https://know.rendernetwork.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://know.rendernetwork.com/docs/web-app/review-and-approve-frames.md).

# Review and approve frames

Inspect rendered frames, play an animation, approve results, and request a re-render.

Double-click a job in **All Jobs** or in a scene's job list to open its frames.

## Choose a frame view

Use the view controls above the frames:

| View        | Use it to                                                                                               |
| ----------- | ------------------------------------------------------------------------------------------------------- |
| **Grid**    | See the status of many frames at once. The totals above the grid show how many frames have each status. |
| **Table**   | Compare frame numbers, progress, and render times.                                                      |
| **Bars**    | Browse a strip of thumbnails. Click a frame to show it in the player.                                   |
| **Gallery** | Compare frame images side by side.                                                                      |

Thumbnails appear as images become available, including during rendering.

Double-click a frame to open its preview. You can also use the enlarge button on a Gallery thumbnail, in the frame's right-click menu, or on the open job's thumbnail in its details panel. Left and Right arrow keys move between frames; Escape closes the preview.

Full-size previews are watermarked. If a full-size preview is not available, the preview may show the thumbnail instead. [Final renders](/docs/web-app/download-frames.md) are downloaded separately after approval.

## Play the sequence

If the player is hidden, click **Show video player** at the bottom of the frames list. Clicking the job's thumbnail or the image in a frame's right-click menu also opens it. Selecting a frame in the list chooses the frame shown in the player.

* Use Play, Previous, Next, or the bar below the image to move through the sequence.
* Choose **Low-Res** for thumbnails or **Hi-Res** for full-size previews. Click **Cache** to load available images at that resolution before playback; click **Caching** to stop loading them.
* Use the FPS control to change playback speed, loop to repeat the sequence, or yoyo to play forwards and backwards.
* Use **Background selector** to adjust the background behind transparent areas.

Click the player's image to open its preview. To save a movie of the sequence, see [Create a video preview](/docs/web-app/video-preview.md).

## Approve frames

Frames marked **Need Review** are ready for your decision. This applies when **Auto Approve** was left off during [job creation](/docs/web-app/create-a-job.md).

| What to approve                      | Action                                                                                                                                                                                          |
| ------------------------------------ | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| One or several frames                | Select the frames and choose **Accept Selected** in the toolbar at the bottom or the right-click menu. Table rows also offer this action.                                                       |
| Every frame waiting for review       | Choose **Accept All Frames** in the frames toolbar, right-click menu, or a table row. This approves all frames currently waiting for review in the job, including those outside your selection. |
| The frame shown in the player        | Click **Accept** below the image.                                                                                                                                                               |
| The frame in the full-screen preview | Press Space.                                                                                                                                                                                    |

Approved frames become available for download. Frames still rendering are not approved by **Accept All Frames**.

## Request a re-render

For an incorrectly rendered frame marked **Need Review**:

1. Select it and choose **Re-render Frame** in the toolbar at the bottom, the right-click menu, or its table row. You can select several frames together.
2. Choose a reason in the confirmation window, if applicable.
3. Click **Re-render**.

You can also click **Re-render** in the player or press R in the full-screen preview for the displayed frame. Requested frames are rendered again automatically.

{% hint style="warning" %}
Excessive re-rendering may reduce your reputation score.
{% endhint %}

## Request another render node

If a frame is taking too long and is still assigned to a node, select it and choose **Request New Node** from the toolbar, right-click menu, or table row. Check the frames in the confirmation and click **Confirm**. The player offers **New Node** for its displayed frame; the full-screen preview uses N.

{% hint style="warning" %}
You pay both the original node and the replacement node for time spent rendering.
{% 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://know.rendernetwork.com/docs/web-app/review-and-approve-frames.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.
