> For the complete documentation index, see [llms.txt](https://docs.hedge.video/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.hedge.video/postlab/faq/where-should-i-store-postlabs-caches.md).

# Where should I store PostLab's caches?

In PostLab there are 3 categories of caches:

1. Productions - `Preferences > General > DEFAULT PRODUCTION LOCATION`
2. Drive - `Preferences > Drive > CACHE LOCATION`
3. Your host NLE - Final Cut Pro, Premiere Pro

Store these caches on a dedicated SSD or NVMe disk, whether internal or external over Thunderbolt 3/4.

In Final Cut Pro, set your Library's Cache to a folder outside your Library.

For Premiere Pro, if you're using Projects with PostLab Productions, PostLab creates Scratch Disks for you in the same folder where your Productions are cached (`Preferences > General > DEFAULT PRODUCTION LOCATION`).

{% hint style="danger" %}
Do not store PostLab's caches on:

* A spinning disk or a RAID with spinning disks.
* Solid-state hybrid drives (e.g. SSHD's or Fusion Drives).
* Shared storage - network attached storage (NAS), a storage area network (SAN), or cloud storage (e.g. PostLab Drive).
  {% 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 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.hedge.video/postlab/faq/where-should-i-store-postlabs-caches.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.