Plex Comes to the What's Streaming Dashboard: Full Parity with Emby and Jellyfin

The What's Streaming Dashboard (WSDashboard) is QuickBox Pro's media-server operations layer - sessions, analytics, history, admin mirroring, all rolled into a single pane of glass on top of your media server. Until now it covered Emby and Jellyfin. Today that surface gets its third media server.

Plex Media Server is now a first-class streaming backend in QuickBox Pro.

In the dashboard, open App Dashboard and switch to the Package Management tab. Search for Plex, click Install, paste a claim token from plex.tv/claim into the install dialog, optionally toggle the Advanced settings for a custom data path or reverse-proxy domain, and click Install. Within a minute the Plex server is detected by WSDashboard, the connection URL and token are auto-populated from the install, and your library, sessions, and history start showing up alongside any Emby or Jellyfin server you already have configured. No copy-paste of API keys. No flipping toggles in three different settings pages. The dashboard owns the entire flow.

If you prefer the CLI:

qb install plex -u username -pct 'claim-xxxxxxxxxxxxxxxxxxxx'

Either path produces the same outcome. The full install reference (custom data directory, reverse-proxy domain, update with token rotation) is in the Plex application docs.

The point of WSDashboard is that the dashboard is the single pane of glass for what is happening on your seedbox right now. Plex was the one obvious hole in that picture. It is no longer a hole.

If you have used WSDashboard with Emby or Jellyfin, every surface you already know works the same way for Plex:

• ●Live Sessions. Every active stream on the Plex server is visible the moment it starts. User name, device, title, codec, bitrate, direct play vs transcode, playback position, and the same pause / resume / stop / kill / message actions you have on the other two backends. Details in the Live Sessions docs.
• ●Watch Analytics. Top titles, top users, transcode-vs-direct breakdown, peak hours, per-day activity - Plex sessions feed the same analytics pipeline. See Watch Analytics.
• ●History. Plex play history shows up in the watch-history datatable with episode posters, channel logos for Live TV (where the server supports it), and the same date-range filter the rest of the dashboard uses.
• ●User Intents. The "who is likely watching what next" prediction surface incorporates Plex viewing patterns the same way it does Emby and Jellyfin.
• ●Library and Section context. Plex sections appear in the library admin view, and every item page works against the Plex metadata graph - series, episode, movie, music - with TMDb cross-referencing for posters and metadata where the underlying library is sparse.
• ●Per-item detail pages. Click into any Plex title and you get the full item page: cast, ratings, related items, watch progress, play counts, sibling versions if you have multiple copies, and a continue-watching shelf that respects Plex's own resume positions.
• ●Admin Playback Mirror. The floating mirror dock - the feature that lets an admin actually see what a user is currently watching, without joining their session or interrupting their playback - now works against Plex. The dashboard pre-rolls the upstream transcoder so the mirror opens in sync with the source user's playback timeline rather than trailing behind it. The full security model is documented in the Live Sessions Playback Mirror section.

The philosophy is simple: a feature that works on one media server should work on all of them. If we have to compromise that because Plex's API does not expose something Emby's does, we say so out loud - but the bar is parity, not "Plex support."

A few features are not on parity because the underlying server APIs do not support them, and we are not going to fake what we cannot deliver:

• ●Live TV is currently Emby and Jellyfin only. Plex DVR session shape is different enough that mirroring a live channel does not work cleanly today - it is on the roadmap as a follow-up. VOD playback mirroring is fully supported.
• ●User policy templates (the per-user transcode / library / streaming limits) remain Emby and Jellyfin specific. Plex's user management is account-based via plex.tv and is intentionally read-only from third-party tools. You can see who is watching and what they are watching; modifying their account-level limits is something we do not attempt because Plex does not expose that surface.
• ●Per-user watch-state writes on Plex. Mark watched / unwatched works on Plex via the server-owner's account (the /:/scrobble and /:/unscrobble endpoints). Emby and Jellyfin support per-user writes - mark a movie watched for user A without touching user B - because their APIs expose that scope. Plex's API does not, so on Plex the operation always targets the owning account's watch state.
• ●Geo-Lock streaming session control routes through plex.tv for Plex sessions. We can read the geographic information for visibility, but enforcement on the Plex side is a server-feature gap, not a QuickBox feature gap.

If any of those become possible because Plex extends their API, we will pick them up. Until then we tell you what works.

Plex support is the headline, but it is shipping alongside a sweep of streaming-dashboard polish that applies across all three media servers:

Every streaming item card now has a rating control built in. On Emby and Jellyfin the control is a heart toggle that mirrors the server's favorite flag. On Plex it is a five-star rating that pushes directly into the Plex user-rating field. From any catalog grid - Library, Continue Watching, Top Watched, the per-section catalog - a user can mark a rating or a favorite in one click without leaving the dashboard.

The same item card surface lets you mark a movie or episode watched or unwatched on all three media servers - Emby, Jellyfin, and Plex. The state flips in the dashboard immediately and propagates to the media server within a single sync tick. Note the scope caveat in the server-specific section above: Emby and Jellyfin support per-user marks; Plex applies the mark on the server-owner's account.

The Streaming Dashboard, the System Dashboard widgets, the History datatable, and the item detail pages have all had a density and layout pass. Mobile, tablet, and ultrawide desktop all render more cleanly. The glassmorphic styling - the frosted-glass containers that frame every widget - is now consistent across surfaces. If you opened the dashboard on a phone and bounced off because it felt cramped, it is worth another look.

A handful of small fixes that add up to a meaningfully cleaner experience:

• ●Better contrast on the Watch History title column - readable in both light and dark themes.
• ●Live TV channel logos now render at the correct fit instead of stretched or cropped.
• ●Episode rows in any history or top-watched view now display the show poster instead of the per-episode screenshot. The screenshot was rarely a useful identifier; the show poster is.
• ●Top Watched now has a media-type filter - admins can pin which media types appear in their Top Watched panel, and the choice is saved per user. If you only care about movies and series and want anime collections to drop out of the rotation, that is two clicks.

A specific call-out for one of the dashboard's most powerful admin features, now that it works against all three media servers.

Playback Mirror is what we built for the moment an admin needs to actually see what a user is reporting as broken. The user says "the audio is out of sync" or "this episode keeps stuttering" or "I cannot resume from where I left off." Instead of asking them to screenshot or screen-share, the admin clicks Mirror on the user's active session, and a floating, draggable, resizable picture-in-picture player drops onto the dashboard streaming the same playback the user is watching.

The mirror runs entirely server-side: the upstream media server transcodes a fresh HLS stream that the dashboard proxies back to the admin's browser via short-lived HMAC-signed tokens. The user is not aware it is happening. The admin's browser never sees the raw media-server API key. Every mirror session is audit-logged. There is a per-admin concurrent cap of three mirrors at once, and the default TTL is two minutes - adjustable per install up to ten, or disable-able entirely if you want a mirror to run as long as you keep the dock open.

Plex parity here meant solving a specific Plex API quirk: the universal transcoder rejects requests that do not identify themselves as a known client profile. The dashboard forwards the admin's actual browser identity - Chrome, Firefox, Safari, Edge, Opera, on Windows, macOS, Linux, iPhone, iPad, or Android - so Plex selects codecs the admin's browser can actually decode, and the mirror starts cleanly.

Whether you are supporting a single household of users or a larger multi-tenant install, Playback Mirror changes what your support flow looks like. And now it covers every media server we ship. Full documentation is on the Live Sessions docs page.

WSDashboard sits on top of a deeper philosophy at QuickBox Pro: dashboards should expose what is actually happening on the seedbox, not what we want to appear to be happening. Real session data, real watch history, real transcode load, real per-user analytics. The data layer is in your database, on your hardware, and never leaves it.

Plex support is not just an integration tick-box. It means that a user who chose Plex as their media server, for whatever reason - the ecosystem, the apps, the friends-and-family sharing model, the existing library - now gets the same operational visibility that Emby and Jellyfin users have. It also means the bar for "is this dashboard worth running" levels out across the three media servers. Pick the server you like best. The dashboard is the same shape.

If you are already running QuickBox Pro, the dashboard's update flow picks up the next public release automatically. If you prefer to pull it manually:

qb update quickbox

You can update your dashboard directly, either via the Dashboard or in CLI manually:

qb update dashboard

If you have not installed Plex yet, open App Dashboard, switch to the Package Management tab, search Plex, click Install, paste a claim token from plex.tv/claim, and submit. The one-line CLI alternative is documented in the Plex application docs.

If you are new to QuickBox Pro, pick a plan on the pricing page. The community is active in the Discord, the full docs are at v3.quickbox.io/docs, and the changelog is at v3.quickbox.io/news.

A handful of items already moving for the next cycles:

• ●Plex Live TV in the Playback Mirror - DVR session-shape work to bring live-channel mirroring up to par with VOD.
• ●Cross-server "what should I watch next" surface - recommendation patterns that work against any media server, drawing on the combined watch history.

If there is a feature you would like to see on the streaming side, the feature-request tracker is open on the GitHub repo and the Discord is active.

Thank you for being a part of QuickBox Pro. Plex support has been one of the most-requested features in the community, and we are glad to finally hand it over.

• ●The QuickBox Pro Team