Reel is a Roku client for Plex Media Server (PMS). It reads your existing libraries and uses Plex for account access, metadata, media delivery, and playback state. Its own configuration controls how that information is presented and which choices are available to viewers.

This documentation is written for server owners. It explains the application behavior behind the interface, the data each feature depends on, and the setup required for optional server-supplied features.

Start here#

The application model#

Plex remains the source of your library structure and access rules. Reel adds its own navigation, a continuous episode guide, title and person discovery, player controls, and server-managed client preferences. Installing Reel does not require rebuilding your media libraries.

The distinction matters operationally. Hiding a library entry in Reel changes navigation. Revoking library access in Plex changes authorization. A Reel playback-quality default influences the playback request; it does not rewrite your source file or change the server's global transcoder settings.

What needs server preparation?#

FeatureOwner preparation
Browsing, the Atlas, title pages, searchExisting accessible libraries with correctly identified media and usable Plex metadata.
Shared Reel configurationSign in as the server owner and publish. Reel can create its configuration playlist.
Studio and rating artworkCreate a Photos library named REEL, add matching PNG files, and share it with the intended profiles.
Film-strip previews and chaptersSupply Plex preview-thumbnail and chapter data. Reel's film-strip interface currently targets Roku Ultra.
Curated collectionsManage collection membership, descriptions, and artwork in Plex.

Reading this documentation#

Server configuration covers the owner controls referenced by Settings. Libraries & discovery explains how Reel reads and presents your content. Playback covers delivery decisions and optional player features.

Current beta

These articles describe the current implementation. Pre-certification configuration formats can change. The feature availability article separates the owner-adoption model from beta compatibility limits.