Settings
Configure providers, pairs, scheduling, UI options, and maintenance.
Settings is where you configure providers, pairs, schedules, and UI behavior.
Start in Authentication, Pairs and Metadata.
CrossWatch has lots of knobs. Most users can leave the defaults alone.
Focus on the few things that matter:
Connect providers in Authentication
Add TMDb in Metadata
Create a Pair and enable the feature you want
Authentication
Connect providers like Plex, Jellyfin, Emby, Trakt, SIMKL, and MDBList.
Providers appear in Pairs only after they connect.
Related: Authentication.
Pairs
Pairs define what syncs with what.
The default pair settings are good for most users. You usually only need to enable Watchlist, Ratings, and/or History.
Direction: source → target (example: Plex → Trakt).
Mode: one-way or two-way.
Features: Watchlist, History, Ratings.
Writes: allow Add and/or Remove.
Related:
Metadata
Metadata (TMDb) improves matching. It reduces wrong links and missing peers.
Related: Metadata.
Scheduling
Configure periodic runs.
Avoid overlaps. Start daily and tune later.
Related: Scheduling.
Scrobble
Real-time scrobbling uses Watcher (preferred) or legacy Webhooks.
It requires connected providers (example: Plex + Trakt).
Defaults are good here too. Pick your Provider and Sink, then enable Watcher.
Related:
UI options
Watchlist preview: show/hide the Watchlist preview pane on Main.
Playing Card: show/hide the footer “Now Playing” card (used by scrobbling).
When no TMDb API key is configured, it may be hidden by default.
Protocol: HTTP or HTTPS.
Prefer HTTPS on untrusted networks.
See HTTPS/TLS.
Security (UI login)
Enable login to protect CrossWatch with a username and password.
Click Log-in to activate after enabling.
Sessions are kept for up to 30 days.
CW-Tracker
Configure CW-Tracker integration (if enabled in your build).
Maintenance
Operational tools:
Enable debug logging.
Clear state and cache.
Reset statistics.
Related: Maintenance.
Clearing state changes the next plan.
Use it after changing direction, features, or provider identity.
Saving and applying changes
Use Save to persist changes.
If a run is active, changes apply on the next run.
Last updated