> For the complete documentation index, see [llms.txt](https://docs.gyroflow.xyz/app/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.gyroflow.xyz/app/advanced-usage/settings-presets.md).
# Settings Presets
Gyroflow allows you to create a preset with all or some settings you commonly use and then load that preset to videos and in the render queue.
Presets can be used to store your common preferred settings in the UI. You can then have them in the Lens profile search box, or you can drag & drop them in the UI or in the [render queue](/app/advanced-usage/render-queue.md), or use in the [CLI](/app/advanced-usage/command-line-cli.md).
## Creating presets
In order to create a preset, set any settings you want in the UI, then click on the arrow on the **Export** button and choose **Create settings preset.**
Then simply select settings you want to include in the preset:
{% hint style="info" %}
If you save the preset in `camera_presets` directory, it will show up in the Lens profile search box. It can be favorited and searched.
{% endhint %}
Preset in the lens profile search box
## Default preset
If you save your preset as `default.gyroflow` in the `camera_presets` directory, it will be loaded automatically with every video.
`default.gyroflow` loads in the main window, as well as in the render queue.
{% hint style="info" %}
On macOS, the `camera_presets` directory is located by right-clicking on the Gyroflow app -> Show package contents -> Contents -> Resources -> camera\_presets
{% 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://docs.gyroflow.xyz/app/advanced-usage/settings-presets.md?ask=&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.
