> 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/get-started/quickstart.md).

# Quickstart

Complete a first render, from preparing a scene to reviewing and downloading the results.

Start with a short test render so you can check the result before submitting a full sequence.

{% stepper %}
{% step %}

## Prepare your scene

Choose your application in [Supported software and file formats](/docs/get-started/supported-software.md), then follow its preparation guide. Include the textures, caches, and other files the scene needs.

If you have not opened the web app yet, [sign in](/docs/get-started/sign-in.md).
{% endstep %}

{% step %}

## Check your credits and upload

Check the credit balance at the top of the app. Follow [Buy Render Credits](/docs/web-app/render-credits.md) if you need to top it up.

In **All Scenes**, click **Upload scene** and choose your prepared file. Follow [Upload Scenes](/docs/web-app/upload-scenes.md) for the upload requirements and ZIP choices. Wait for the scene to show **Ready**.
{% endstep %}

{% step %}

## Create a test job

Open the scene and click **Create Job**. Choose the take, scene, or render target you want to render, then set a short frame range. Check the output format and the network settings before submitting.

The [Create a job](/docs/web-app/create-a-job.md) guide walks through the form. Use manual approval if you want to inspect the rendered frames before approving them.
{% endstep %}

{% step %}

## Review the frames

Open the job in **All Jobs**. Check the rendered frames for missing textures, animation problems, and the expected lighting and colour.

Follow [Review and approve frames](/docs/web-app/review-and-approve-frames.md) to inspect full-size previews and approve the frames you want to keep. Jobs using **Auto Approve** do not wait for manual approval.
{% endstep %}

{% step %}

## Download the outputs

Use [Download frames](/docs/web-app/download-frames.md) to save the approved outputs. Open a downloaded file in your usual image or compositing application to check the format and passes.

Once the test is satisfactory, create another job from the same scene with the full frame range. A change to the scene itself needs an [updated scene version](/docs/web-app/scenes-and-versions.md).
{% endstep %}
{% endstepper %}


---

# 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/get-started/quickstart.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.