> 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/synchronization.md).

# Synchronization

Adapter reference for how CW reads/writes provider data during syncing.

Synchronization adapters are the “connectors” the orchestrator uses for syncing. Each adapter knows how to read a provider and how to write changes back.

{% hint style="info" %}
Start with one pair and one feature. Expand only after the first run is clean.
{% endhint %}

### How to use this section

{% stepper %}
{% step %}

### Connect providers

Use [Connections](https://wiki.crosswatch.app/crosswatch/settings/connections.md).
{% endstep %}

{% step %}

### Build a pair

Create one pair and enable one feature.
{% endstep %}

{% step %}

### Check adapter behavior

If a provider acts oddly, open its adapter page.
{% endstep %}
{% endstepper %}

### Follow a run

The [sync bar on Main](https://wiki.crosswatch.app/crosswatch/main-dashboard.md#sync-progress) shows the current read or write stage, with provider, feature, and counts when available. Progress continues across pairs and features. Open **View details** after the run to check actual changes and items needing attention.

### What adapters do

Adapters implement the same core flow:

* **Index**: fetch a present-state snapshot (what exists now).
* **Normalize**: turn provider rows into common items + stable IDs.
* **Apply**: add/remove/update on the target side.
* **Stabilize**: use local state to avoid repeats and flapping.

### Feature semantics (how to think about “changes”)

* **Watchlist**: set-like. Adds and removes are straightforward.
* **History**: watched state and, where supported, individual plays. Dates can be known or explicitly unknown; see [History date support](https://wiki.crosswatch.app/crosswatch/settings/configure-pairs/features/history.md#unknown-watch-dates).
* **Ratings**: numeric. Scale differences matter. Deletes can be destructive.
* **Playlists**: ordered. Often provider-specific. Not widely supported yet.

### Collection support

Collection sync is one-way only. Enabling it locks the pair to **One-way** mode.

**Source only:** Plex, Emby, Jellyfin, Kodi, Silo, and Tofa.

**Source and target:** Trakt, MDBList, CrossWatch, FlickList, PunchPlay, Floppy, and Scrob.

For media servers and Kodi, Collection uses items from selected libraries. Named Silo collections and Favorites use Playlists instead.

### Stability knobs (common patterns)

* Snapshot caching to reduce API load.
* Chunking + small pauses to avoid rate limits.
* Shadow/unresolved files to prevent endless retries.
* Activity/watermark logic for delta providers (example: SIMKL).

### Adapter guides

<table data-view="cards"><thead><tr><th>Adapter</th><th data-card-target data-type="content-ref">Open</th></tr></thead><tbody><tr><td>Plex</td><td><a href="https://wiki.crosswatch.app/crosswatch/settings/synchronization/media-servers/plex.md">Plex</a></td></tr><tr><td>Jellyfin</td><td><a href="https://wiki.crosswatch.app/crosswatch/settings/synchronization/media-servers/jellyfin.md">Jellyfin</a></td></tr><tr><td>Emby</td><td><a href="https://wiki.crosswatch.app/crosswatch/settings/synchronization/media-servers/emby.md">Emby</a></td></tr><tr><td>Silo</td><td><a href="https://wiki.crosswatch.app/crosswatch/settings/synchronization/media-servers/silo.md">Silo</a></td></tr><tr><td>Tofa</td><td><a href="https://wiki.crosswatch.app/crosswatch/settings/synchronization/media-servers/tofa.md">Tofa</a></td></tr><tr><td>Nuvio</td><td><a href="https://wiki.crosswatch.app/crosswatch/settings/synchronization/media-clients/nuvio.md">Nuvio</a></td></tr><tr><td>Trakt</td><td><a href="https://wiki.crosswatch.app/crosswatch/settings/synchronization/trackers/trakt.md">Trakt</a></td></tr><tr><td>SIMKL</td><td><a href="https://wiki.crosswatch.app/crosswatch/settings/synchronization/trackers/simkl.md">SIMKL</a></td></tr><tr><td>MDBList</td><td><a href="https://wiki.crosswatch.app/crosswatch/settings/synchronization/trackers/mdblist.md">MDBList</a></td></tr><tr><td>PublicMetaDB</td><td><a href="https://wiki.crosswatch.app/crosswatch/settings/synchronization/trackers/publicmetadb.md">PublicMetaDB</a></td></tr><tr><td>AniList</td><td><a href="https://wiki.crosswatch.app/crosswatch/settings/synchronization/trackers/anilist.md">AniList</a></td></tr><tr><td>Tautulli</td><td><a href="https://wiki.crosswatch.app/crosswatch/settings/synchronization/others/tautulli.md">Tautulli</a></td></tr><tr><td>CW local backup</td><td><a href="https://wiki.crosswatch.app/crosswatch/settings/synchronization/others/cw.md">CW</a></td></tr></tbody></table>

### Troubleshooting quick checks

* **Adds keep reappearing**: provider didn’t “stick” the write. Check adapter state files.
* **Recent changes not syncing**: reduce caching, or force a fresh read if supported.
* **429 / 5xx errors**: reduce chunk size, add delay, run less often.
* **Mismatches**: add [Metadata / ID Mapping](https://wiki.crosswatch.app/crosswatch/settings/connections/metadata.md) and prefer stable IDs.

### Related topics

* [Configure Pairs](https://wiki.crosswatch.app/crosswatch/settings/configure-pairs.md) — step-by-step pair setup.
* [Best practices](https://wiki.crosswatch.app/getting-started/best-practices.md) — safe defaults.


---

# 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/synchronization.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.
