> 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/help/glossary.md).

# Glossary

A quick reference for terms used in the Render Network web app and these guides.

| Term                                                            | Meaning                                                                                                                              |
| --------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------ |
| [Access token](/docs/web-app/access-keys.md)                    | A key that lets an app or tool use your account with the permissions you choose. It can also be used to sign in to the web app.      |
| Asset                                                           | A file your scene uses, such as a texture, linked model, or simulation cache.                                                        |
| [Auto approve](/docs/web-app/review-and-approve-frames.md)      | A job setting that approves rendered frames without waiting for your review.                                                         |
| [Auto download](/docs/web-app/download-frames.md)               | A job setting that sends rendered outputs to a chosen download destination automatically.                                            |
| [Cloud storage](/docs/web-app/cloud-storage.md)                 | A connected online storage service, such as Amazon S3, Dropbox, or Google Drive, used to deliver outputs.                            |
| DCC                                                             | Digital content creation application: the software you use to build a scene, such as Cinema 4D or Blender.                           |
| [Download Manager](/docs/tools-and-api/manager-app.md)          | The web app's name for using the Render Network Manager desktop app to download outputs.                                             |
| Frame                                                           | One image in a render job, identified by its frame number. A still render can be a job with one frame.                               |
| [Frame approval](/docs/web-app/review-and-approve-frames.md)    | Accepting a rendered frame so its output files can be downloaded.                                                                    |
| [Job](/docs/web-app/create-a-job.md)                            | A render submitted from a scene with a chosen target, frame range, and render settings. The same scene can be used for several jobs. |
| [OctaneBench score](/docs/web-app/cost-calculator.md)           | A measure of your computer's Octane rendering performance, used when estimating render costs. Also shown as **OB Score**.            |
| [Output](/docs/web-app/outputs.md)                              | A rendered file to download, such as a PNG or EXR. An output configuration chooses its format and related settings.                  |
| [Pass / AOV](/docs/prepare-your-scene/aovs.md)                  | A separate part of the rendered image, such as diffuse lighting or reflections, for use in compositing.                              |
| [Preview](/docs/web-app/review-and-approve-frames.md)           | An image used to review a frame in the app. Full-size previews are watermarked; final outputs are downloaded separately.             |
| [Project](/docs/web-app/projects.md)                            | A named group for related scenes and their jobs.                                                                                     |
| [Render Credits](/docs/web-app/render-credits.md)               | The balance used to pay for rendering on the Render Network.                                                                         |
| Render engine                                                   | The renderer that produces the images, such as Octane, Redshift, or Cycles.                                                          |
| Render node                                                     | A computer on the Render Network that renders part of a job.                                                                         |
| [Render target](/docs/get-started/concepts.md#targets-and-jobs) | The camera, geometry, lighting, and render settings used for a render. The equivalent is a take in Cinema 4D or a scene in Blender.  |
| [Render tier](/docs/web-app/render-tiers.md)                    | The service option selected for a job, affecting its price and available render nodes.                                               |
| [Scene](/docs/web-app/upload-scenes.md)                         | The uploaded scene package from which you create render jobs.                                                                        |
| [Scene version](/docs/web-app/scenes-and-versions.md)           | An uploaded revision of a scene. The latest version is marked **CURRENT**; **Upload Snapshot** adds another version.                 |
| [Video preview](/docs/web-app/video-preview.md)                 | An MP4 made from rendered frame previews, for reviewing the sequence as a video.                                                     |
| [VRAM](/docs/web-app/render-tiers.md)                           | Graphics-card memory. **Minimum Node VRAM** sets the memory requirement for the nodes assigned to your job.                          |


---

# 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/help/glossary.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.
