Trackers vs. Media Servers
How to choose a source of truth between trackers and media servers.
Last updated
Was this helpful?
⌘Ctrlk
How to choose a source of truth between trackers and media servers.
Trackers and media servers solve different problems. Do not treat them as interchangeable.
Trackers include Trakt, SIMKL, MDBList, PublicMetaDB, and AniList.
Best for:
A portable watch history across devices.
Ratings and recommendations.
Watchlists that outlive any single server.
One profile across multiple servers.
Media servers include Plex, Jellyfin, and Emby.
Best for:
Scanning files and building a playable library.
Streaming to your devices.
Local users and profiles.
Playback state for what actually played.
This is the safest default.
Reasons:
The server knows what actually played.
The tracker turns it into portable history.
Multiple servers still roll up into one tracker profile.
Server ratings can feed the tracker ecosystem.
If you must pick a source of truth, do this:
Media server for playback.
Tracker for long-term history and discovery.
Do this only when you know the risks. It can overwrite local users and curated libraries.
Common reasons:
You only use the server as a playback surface.
Your tracker is the only place you edit lists and ratings.
Trackers often (if not always) contain more items than your media server library.
If you sync tracker -> media server, expect unresolved items when the target server does not already have those items in its library.
For history and ratings, the rule is simple: the item must already exist in your library before the server can store that data reliably.
The main exception is Plex watchlists. Plex watchlists use Plex's cloud service, so they can include items that are not in your local library yet.
Best practices - recommended defaults.
Configure Pairs - setup steps.
Tracker to Media Server - why it is risky.
Media Server to Media Server - why it is fragile.
Last updated
Was this helpful?
Was this helpful?