> For the complete documentation index, see [llms.txt](https://wiki.crosswatch.app/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://wiki.crosswatch.app/crosswatch/settings/connections/metadata.md).

# Metadata

Configure TMDb metadata, optional Fanart.tv artwork and Anime ID Mapping.

TMDb metadata and Anime ID Mapping help CrossWatch match the same item across different services. Optional Fanart.tv artwork adds logos, backgrounds and movie discs. Administrators can also [choose artwork for individual titles](https://wiki.crosswatch.app/crosswatch/settings/connections/metadata/artwork-selection.md).

Without them, CW sees more missing peers and weaker ID coverage.

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

Find this section in **Settings → Connections → Metadata**.

<figure><img src="https://565675962-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F3rh5THg1PdhVsBt3GALo%2Fuploads%2FBLX3zeA0brTgHPKTow8x%2Fmeta1.png?alt=media&amp;token=4cdb7c15-2a0c-49a4-a0f8-76c7ba1bef4c" alt=""><figcaption></figcaption></figure>

{% hint style="success" %}
Set up TMDb before your first real sync run.
{% endhint %}

### Why you want this section

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 and ID mapping help CW:

* 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" %}
If you use AniList pairs, enable Anime ID Mapping too.
{% endhint %}

### What CW supports

CW supports:

* **TMDb** metadata
* **Fanart.tv** logos, backgrounds and movie discs, alongside TMDb
* [**Artwork selection**](https://wiki.crosswatch.app/crosswatch/settings/connections/metadata/artwork-selection.md) for individual titles
* **Anime ID Mapping** for AniList pairs

<table data-view="cards"><thead><tr><th>Guide</th><th data-card-target data-type="content-ref">Open</th></tr></thead><tbody><tr><td>TMDb Metadata</td><td><a href="https://wiki.crosswatch.app/crosswatch/settings/connections/metadata/tmdb-metadata.md">TMDb Metadata</a></td></tr><tr><td>Fanart.tv</td><td><a href="https://wiki.crosswatch.app/crosswatch/settings/connections/metadata/fanart-tv.md">Fanart.tv</a></td></tr><tr><td>Anime ID Mapping</td><td><a href="https://wiki.crosswatch.app/crosswatch/settings/connections/metadata/anime-id-mapping.md">Anime ID Mapping</a></td></tr></tbody></table>

### Setup

{% stepper %}
{% step %}

### Open Metadata

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

{% step %}

### Configure TMDb

Create a TMDb API key and paste it into CW.

Guide: [TMDb Metadata](https://wiki.crosswatch.app/crosswatch/settings/connections/metadata/tmdb-metadata.md)
{% endstep %}

{% step %}

### Add Fanart.tv artwork (optional)

After configuring TMDb Metadata, select **Connect fanart.tv**, then choose logo and background sources in **Settings** and select **Save changes**. No separate key is required.

Guide: [Fanart.tv](https://wiki.crosswatch.app/crosswatch/settings/connections/metadata/fanart-tv.md)
{% endstep %}

{% step %}

### Configure Anime ID Mapping

If you sync AniList with another provider, enable Anime ID Mapping.

Guide: [Anime ID Mapping](https://wiki.crosswatch.app/crosswatch/settings/connections/metadata/anime-id-mapping.md)
{% endstep %}
{% endstepper %}

### Troubleshooting

* **Lots of missing matches**: configure TMDb, then re-run the pair.
* **AniList anime still missing peers**: enable Anime ID Mapping, then run the pair again.
* **Wrong match**: fix the item in the Editor (override IDs), then re-run.
* **Rate limits**: avoid rapid re-runs and repeated cache clearing. CrossWatch reuses saved TMDb metadata across features. Configure the Metadata key separately from TMDb Sync.


---

# 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://wiki.crosswatch.app/crosswatch/settings/connections/metadata.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.
