> 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/related-information/trackers-vs.-media-servers.md).

# Trackers vs. Media Servers

How to choose a source of truth between trackers and media servers.

Trackers and media servers complement each other.

Use trackers for portable account data. Use media servers for the libraries and playback devices you control.

### Trackers

Best for:

* A portable watch history across devices.
* Ratings and recommendations.
* Watchlists that outlive any single server.
* One profile across multiple servers.

### Media servers

Media servers include Plex, Jellyfin, Emby, Kodi etc.

Best for:

* Scanning files and building a playable library.
* Streaming to your devices.
* Local users and profiles.
* Playback state for what actually played.

### Use both together

Many setups sync in both directions, with each direction serving a purpose.

**Media server → tracker** records new playback from your library in a portable history.

**Tracker → media server** restores or carries your existing watched state, ratings, and supported lists into the library where you watch.

{% hint style="info" %}
Choose the direction that matches where you manage each kind of data:

* Use the tracker for history, ratings, and lists you manage across services.
* Use the media server for local library availability and active playback.
  {% endhint %}

### Related topics

* [Best practices](https://wiki.crosswatch.app/getting-started/best-practices.md) - recommended defaults.
* [Configure Pairs](https://wiki.crosswatch.app/crosswatch/settings/configure-pairs.md) - setup steps.
* [Tracker to Media Server](https://wiki.crosswatch.app/related-information/tracker-to-media-server.md) - setup guidance for local libraries.
* [Media Server to Media Server](https://wiki.crosswatch.app/related-information/media-server-to-media-server.md) - align data across server libraries.


---

# 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/related-information/trackers-vs.-media-servers.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.
