> 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/crosswatch/settings/scrobbler/playing-card.md).

# Playing Card

The Playing Card is a footer card that displays current playback sessions and their progress.

<figure><img src="/files/NrmA7bAuavBihHxjywc2" alt=""><figcaption></figcaption></figure>

### What it does

* Shows the current movie or episode, including poster, year, media type, and episode number.
* Shows whether playback is playing, paused, or buffering.
* Shows watched percentage and estimated time remaining when duration data is available.
* Updates displayed progress every second between source updates.
* Shows the source media server, such as Plex, Emby, or Jellyfin.
* Shows the configured provider instance when applicable.
* Supports multiple simultaneous playback sessions, with controls to switch between them.
* Adds an overview, rating, runtime, release information, genres, series information, and a TMDb link when metadata is available.
* Hides itself when there are no active playback sessions.
* Can be closed temporarily, or disabled in **Settings → UI → Playing Card**.

### Prerequisites

* Playing Card enabled in **Settings → UI → Playing Card**
* A configured TMDb API key in [Metadata](/crosswatch/settings/connections/metadata.md)
* At least one playback event source:
  * [Watcher](/crosswatch/settings/scrobbler/watcher.md)
  * [Webhooks](/crosswatch/settings/scrobbler/webhooks.md)

The event source must provide current playback state and progress data.

### Quick setup

{% stepper %}
{% step %}

### Enable the card

1. Open **Settings → UI → Playing Card**.
2. Set the Playing Card to **Show**.
3. Save the settings.
   {% endstep %}

{% step %}

### Configure metadata

1. Open **Settings → Metadata**.
2. Configure TMDb.
3. Save the settings.

TMDb is required for the Playing Card to be displayed.
{% endstep %}

{% step %}

### Configure a playback event source

Configure [Watcher](/crosswatch/settings/scrobbler/watcher.md), or configure supported [Webhooks](/crosswatch/settings/scrobbler/webhooks.md).

For accurate live progress, the source should provide playback progress, duration, state, and update timestamps.
{% endstep %}
{% endstepper %}

### Troubleshooting

#### I do not see the Playing Card

* Confirm that it is enabled in **Settings → UI → Playing Card**.
* Confirm that a TMDb API key is configured in **Settings → Metadata**.
* Confirm that a playback event source is enabled and receiving events.
* Start playback on the connected media server.
* Check that the session is reported as playing, paused, or buffering.

### Related topics

* [Watcher](/crosswatch/settings/scrobbler/watcher.md)
* [Webhooks](/crosswatch/settings/scrobbler/webhooks.md)
* [Metadata](/crosswatch/settings/connections/metadata.md)
* [User interface](/crosswatch/settings/ui-settings/user-interface.md)

### Summary

The Playing Card shows active playback sessions, progress, time remaining, source information, and TMDb metadata.

It requires TMDb configuration and a supported playback event source.

Watcher is suitable for monitored playback, while [Webhooks](/crosswatch/settings/scrobbler/webhooks.md) can also provide playback events.


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://wiki.crosswatch.app/crosswatch/settings/scrobbler/playing-card.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.