Metadata

Configure metadata providers (TMDb) to improve matching and stabilize IDs across services.

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

Recommended: set up metadata before your first real sync run.

What CrossWatch supports

Right now, CrossWatch supports one metadata source:

• TMDb

Setup

1

Open Metadata

Go to Settings → Metadata.

2

Configure TMDb

Create a TMDb API key and paste it into CrossWatch.

Guide: Meta: TMDb

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.