> For the complete documentation index, see [llms.txt](https://docs.openbrush.app/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.openbrush.app/user-guide/exporting-videos/offline-rendering-hq-renders.md).

# Offline rendering (HQ renders)

Offline rendering lets you re-render a recorded camera move. You can output higher resolution and/or higher FPS.

It works by saving the camera motion to a USD file. Then Open Brush can replay that motion later.

### Enable camera path saving

Set `"SaveCameraPath": true` in your config. See [The Open Brush config file](/user-guide/the-open-brush-config-file.md).

### What files you get

When you record a video with `SaveCameraPath` enabled, Open Brush writes extra files. On Windows, you’ll see a batch file next to the video in `Documents\Open Brush\Videos`.

Example:

```
Untitled_13_00.mp4
Untitled_13_00.HQ_Render.bat
```

### Re-render using the Windows .bat

Double-click the `.bat`. Pick an option from the menu.

![](/files/s7cI21RTtcVlBsR2s5sr)

Open Brush will:

1. Launch
2. Load your sketch
3. Render the video
4. Exit

Higher quality settings can make the framerate choppy. Don’t wear the headset during the render.

#### “No Quick Load” option

The “No Quick Load” option forces a full load. Use it when your render finishes before the sketch fully loads.

### Render a saved camera path from the command line

The camera path is saved in ASCII USD (`.usda`). If you have other USD tools, you may be able to edit it.

To render directly:

```
Openbrush.exe --renderCameraPath <path/to/camerapath.usda> <path/to/sketchfile.tilt>
```

### Video camera paths vs Camera Paths tools

These are different concepts:

* **Camera Paths tools** create a path that Open Brush records.
* **Video camera paths** are the saved motion data used for offline re-rendering.

The saved `.usda` path can be combined with USD exports. That can recreate camera motion in other pipelines.


---

# 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 dynamically by asking a question.

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

```
GET https://docs.openbrush.app/user-guide/exporting-videos/offline-rendering-hq-renders.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.