About CrossWatch

CrossWatch keeps your watch state aligned across services.

It connects media servers and trackers.

It runs locally and stores state on disk.

You control it from a web UI.

What you can do

• Sync watchlists, history, and ratings.

• Scrobble plays in real time with Watcher.

• Improve matching using TMDb metadata.

• Use local state + snapshots for safer planning.

The mental model

• Providers: Plex, Jellyfin, Emby, Trakt, SIMKL, MDBList, AniList.

• Pairs: one source + one target.

• Runs: manual or scheduled.

• State: local JSON files CrossWatch uses to plan changes.

Where to go next

Limits (quick)

CrossWatch stores state as JSON files (no database).

That keeps installs simple, but very large libraries can slow planning.

If something breaks, file an issue:

File issues here

Summary

CrossWatch syncs watchlists, history, and ratings between services.

It can also scrobble plays in real time with Watcher.

Start small: one pair, one feature, dry run.

Next steps

• Install / run it: Docker setup

• Do a first clean run in the UI: First-time setup

• Pick periodic syncing vs real-time scrobbling: What do you need?

• Use safer defaults before two-way sync: Best practice