How to configure a sync pair, feature toggles, and safety controls.
Pairs define what syncs, in which direction, and with what safety rules.
Left = Source
Right = Target
Enable only what you need. Source always wins conflicts.
First run: one-way and one feature
Most safe first pairs are media server → tracker.
Defaults are good for most users.
Most setups only require:
Pick Source and Target
Pick the right profiles
Enable Watchlist, Ratings, History, and/or Progress
Enabled: master switch for the pair.
Source / Target: provider pickers.
Source profile / Target profile: pick which profile to use.
Defaults to default.
default
See Profiles.
Mode:
One-way: target follows source.
Two-way: both sides contribute.
Choose Two-way only when you already trust matching on both sides.
For most setups, One-way is safer.
Feature tabs show up only when both providers support that feature.
Start here for feature-specific options: Features.
Pairs that contain AniList can show extra options on Watchlist and Ratings.
That includes Use Anime ID Mapping and, when AniList can receive writes, Anime-only sync.
See AniList pair options.
Watchlist
Ratings
History
Progress
Safety switches and guardrails: Global settings
Pair-scoped provider behavior: Provider settings
Pair-only library scoping: Pair-level Whitelisting
AniList-specific pair controls: AniList pair options
Watchlist controls and Jellyfin/Emby mode: Watchlist
Ratings scope and backfill window: Ratings
History behavior and safety limitations: History
Resume position syncing (media-server pairs): Progress
Dependent controls lock.
This prevents accidental changes.
Pair synchronization
Best practices
Last updated 21 days ago
Was this helpful?
