> 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/catalog-database.md).
# Catalog Database
Understand the structure of Luminar for Desktop's catalog database to manage your photo library effectively.
{% tabs %}
{% tab title="Windows Catalog Structure" %}
Luminar for Desktop Catalog Folder Structure on Windows
Luminar for Desktop Catalog Folder Structure on MacOS
{% endtab %}
{% endtabs %}
Luminar for Desktop automatically creates a Catalog when you first install it. A Catalog contains all information about your files, including metadata on flags and edits you make.
Remember that edits you make in Luminar for Desktop are always non-destructive and are saved in your current Catalog. This means you aren’t changing the actual files but rather are capturing instructions in a database. When you’re ready to share or use your files elsewhere, you can export images with your edits applied.
You can back up your photos by exporting them in different formats:
By default, the Luminar for Desktop Catalog is created in your Pictures folder. Ensure you **don’t include the Catalog folder when adding images to Luminar for Desktop.** Doing so will add all preview images from Luminar for Desktop to your Catalog, resulting in **duplicate photos in your Luminar Catalog.**
{% hint style="warning" %}
**Note: Total backup**\
The contents of a Catalog are stored inside a folder. If you’re backing up or moving a Catalog, be sure to back up or move the entire folder.
{% 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://support.skylum.com/how-to-use-luminar-for-desktop/catalog/catalog-files/catalog-database.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.
