> 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-neo/catalog/catalog-files/catalog-database.md).

# Catalog Database

{% tabs %}
{% tab title="Windows Catalog Structure" %}

<figure><img src="/files/9Uxll5Mtv0KxrqdcZNwC" alt=""><figcaption><p>Luminar Neo Catalog Folder Structure on Windows</p></figcaption></figure>
{% endtab %}

{% tab title="MacOS Catalog Structure" %}

<figure><img src="/files/2TwJYo1HRAgubV38ywo5" alt=""><figcaption><p>Luminar Neo Catalog Folder Structure on MacOS</p></figcaption></figure>
{% endtab %}
{% endtabs %}

Luminar Neo 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 Neo 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:\
![Screenshot](https://userguide.skylum.com/hc/article_attachments/12444075191058)

By default, the Luminar Neo Catalog is created in your Pictures folder. Ensure you **don’t include the Catalog folder when adding images to Luminar Neo.** Doing so will add all of Luminar Neo’s preview images 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 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://support.skylum.com/how-to-use-luminar-neo/catalog/catalog-files/catalog-database.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.
