> For the complete documentation index, see [llms.txt](https://cullshot.gitbook.io/cullix/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://cullshot.gitbook.io/cullix/reference/xmp-lightroom.md).

# XMP and Lightroom

## What Cullshot writes

Cullshot stores ratings in **XMP sidecars** (`Image.xmp`) next to the images. Foreign content in existing XMP files is preserved. RAW files are never modified.

| Value         | How it arrives                                                                                               |
| ------------- | ------------------------------------------------------------------------------------------------------------ |
| Stars (1–5)   | `xmp:Rating`                                                                                                 |
| Color labels  | by name only, in Lightroom's language (English: Red, Yellow, Green, Blue, Purple) – setting "label names"    |
| Pick / Reject | Lightroom generally does not read Picks and Rejects from XMP; Cullshot therefore offers "**Pick as Purple**" |

{% hint style="info" %}
"Pick as Purple" only applies to images without a color label of their own.
{% endhint %}

## Sidecars and embedded XMP

* **RAW formats with sidecar:** Lightroom reads the `.xmp` next to the file.
* **DNG, JPEG, HEIC:** Lightroom **does not read** sidecars. That is why [handing off](/cullix/guide/handoff.md) creates copies with **embedded XMP**.

## Workflow with Lightroom

1. Review and rate in Cullshot.
2. **⇧⌘E** → choose Lightroom or Lightroom Classic.
3. The copies with stars and labels are imported (for Classic, from the handoff folder).

## What Cullshot does not write

* AI suggestions do **not** end up in the XMP, but in a separate cache per folder. Lightroom stays "clean" until you accept suggestions.


---

# 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://cullshot.gitbook.io/cullix/reference/xmp-lightroom.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.