# Metadata

Metadata helps CrossWatch match the same item across different services.

Without it, CrossWatch sees more missing peers and weaker ID coverage.

That matters more now that Plex, Jellyfin, and Emby default to strict ID matching.

### Why you want metadata

Most matching problems start with weak identifiers:

* Different services use different IDs.
* Titles are localized, renamed, or ambiguous.
* Episodes can be especially messy without external IDs.

Metadata helps CrossWatch:

* match items by stable IDs (TMDb/IMDb/etc. when available)
* reduce “missing peer” and “wrong match” issues
* make two-way sync less risky

{% hint style="info" %}
Recommended: set up metadata **before** your first real sync run.
{% endhint %}

### What CrossWatch supports

Right now, CrossWatch supports one metadata source:

* **TMDb**

### Setup

{% stepper %}
{% step %}

### Open Metadata

Go to **Settings → Metadata**.
{% endstep %}

{% step %}

### Configure TMDb

Create a TMDb API key and paste it into CrossWatch.

Guide: [Meta: TMDb](/crosswatch/providers/metadata/meta-tmdb.md)
{% endstep %}
{% endstepper %}

### Troubleshooting

* **Lots of missing matches**: configure TMDb, then re-run the pair.
* **Wrong match**: fix the item in the Editor (override IDs), then re-run.
* **Rate limits**: increase TMDb cache TTL and avoid rapid re-runs.


---

# Agent Instructions: 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:

```
GET https://wiki.crosswatch.app/crosswatch/providers/metadata.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.
