> For the complete documentation index, see [llms.txt](https://support.skylum.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://support.skylum.com/how-to-use-luminar-for-desktop/catalog/catalog-files.md).

# Catalog Files

Learn about the different catalog files in Luminar for Desktop and how they store your editing data.

As you work in Luminar for Desktop, your edits are stored in a **Catalog file.** This Catalog tracks your images and the edits you make to them. Luminar for Desktop lets you create multiple Catalogs to better manage your photos. You can have Catalogs for different clients and events, a Catalog just for family photos — the sky’s the limit. Using numerous, relatively small, Catalogs can significantly speed up your workflow.

{% content-ref url="/pages/7AwQ3dizdF5PMIQeqaoO" %}
[Catalog Database](/how-to-use-luminar-for-desktop/catalog/catalog-files/catalog-database.md)
{% endcontent-ref %}

{% content-ref url="/pages/el6a92iJHmJCt7ZdHQlS" %}
[Multiple Catalogs](/how-to-use-luminar-for-desktop/catalog/catalog-files/multiple-catalogs.md)
{% endcontent-ref %}

{% content-ref url="/pages/8wPzLErto0IgeqRRTcoP" %}
[Backing Up a Catalog](/how-to-use-luminar-for-desktop/catalog/catalog-files/backing-up-a-catalog.md)
{% endcontent-ref %}

{% content-ref url="/pages/OBepPusEwrMtwTNj7LAT" %}
[Backing Up Your Photo Edits](/how-to-use-luminar-for-desktop/catalog/catalog-files/backing-up-your-photo-edits.md)
{% endcontent-ref %}


---

# 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://support.skylum.com/how-to-use-luminar-for-desktop/catalog/catalog-files.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.
