Remote and Controller Input
Plex HTPC accepts input from infrared and Bluetooth remotes, game controllers, HDMI-CEC signals sent by a television handset, and plain keyboards, so the same interface works no matter what is sitting on the coffee table.

Plex HTPC is a desktop player built for computers hooked up to a television, letting you browse and play a Plex media library with a remote, game controller, or keyboard instead of a mouse.
Plex HTPC is a desktop application for the computer that lives under the television. It presents a Plex media library in a layout designed for distance viewing, so titles can be chosen from across the room with a remote, a game controller, or a few keyboard keys rather than a mouse pointer. Playback is handled by the mpv engine inside Plex HTPC, which is what gives the app its wide handling of mixed media instead of a fixed set of supported formats. Point it at your Plex Media Server, sign in, and the library appears; from there you browse, queue an episode or two, and let the interface stay out of the way during playback.
The distinction that matters is what this app is not. It is a playback client for a media library, not a conferencing or screen-sharing tool, so live collaboration still belongs to services such as Cisco Webex Meetings while a finished recording can simply be dropped into a Plex library and watched from the couch. The other difference is control. Instead of a keyboard and mouse assumption, Plex HTPC reads input from whatever is aimed at the television: an infrared or Bluetooth remote, a game controller thumbstick, an HDMI-CEC signal from the television's own handset, or a standard keyboard. That flexibility is why a computer plus this app can replace a dedicated streaming box.
The main benefit of Plex HTPC is that it treats the television as the primary screen. Everything from text sizing to navigation is built for viewing at a distance, so nobody has to squint at a desktop interface designed for arm's length. The second benefit is input freedom: a programmable input map can be written for a specific remote or controller, mapping each button to an action such as seeking ten seconds, stepping to the next chapter, cycling subtitles, or switching aspect ratio. Underneath, the mpv playback engine accepts direct commands, which means advanced users can tune things like subtitle scale instead of waiting for a preference to appear in the interface. Because it runs on an ordinary computer, the same machine can act as a media centre, a retro gaming box, and a browser without separate streaming hardware. Troubleshooting is also straightforward, since Plex HTPC writes logs that can be attached to a forum post when something misbehaves.
Key capabilities and highlights.
Plex HTPC accepts input from infrared and Bluetooth remotes, game controllers, HDMI-CEC signals sent by a television handset, and plain keyboards, so the same interface works no matter what is sitting on the coffee table.
Each device can be described in a small JSON input map that names the remote, matches it with a regular expression, and assigns every button to an action, which is how unsupported hardware gets full functionality. Default maps ship with the app as reference examples.
Mapped buttons can handle far more than navigation: seeking in ten-second steps, jumping chapter by chapter, cycling audio tracks, subtitles, and aspect ratios, moving through a play queue, or toggling the watched status of whatever is playing.
Under the hood sits the mpv engine, so advanced users can send raw playback commands through an input map, for example adjusting subtitle scale or applying audio and video filters that the standard interface never exposes.
Text, artwork, and navigation are sized for viewing across a room, so browsing a library from a sofa does not require leaning forward, and the player can take over the whole screen while a film or episode runs.
Point the app at a Plex Media Server and sign in to see the same libraries, watch state, and play queues used by phone and TV clients, which keeps progress consistent across devices. Plex HTPC uses the account you already have.
Skip commands move through a play queue rather than stopping at the end of a single file, so a controller button can advance to the next episode or return to the beginning of the current one when playback has barely started.
The app writes logs that capture detected input devices, pressed buttons, and playback activity, which turns a remote that refuses to cooperate into a solvable problem rather than a guessing game. They can be attached to a forum post when asking for help.
Browse historical releases and previous builds.
Common questions about Plex HTPC.
It is a desktop player for a computer connected to a television. It shows your Plex libraries in an interface designed for distance viewing and plays them through the mpv engine, controlled by a remote, a game controller, or a keyboard.
The standard app assumes a mouse and keyboard at a desk, while Plex HTPC is built for distance viewing and for input devices aimed at a television, including HDMI-CEC signals and game controllers.
Infrared and Bluetooth remotes, game controllers and joysticks, HDMI-CEC signals, LIRC setups, Apple media keys, and ordinary keyboards are all recognised, and a device that is not natively supported can be described in an input map.
It is a small JSON file that gives the device a name, matches that name with a regular expression, and lists which action each button performs. Copies of the maps shipped with the app are the usual starting point.
Yes. Beyond the built-in actions, an input map can send raw mpv commands, so a button could change subtitle scale or apply an audio or video filter rather than only moving around the interface.
It connects to a Plex Media Server and uses the same account, libraries, and play queues as the other Plex apps, so nothing has to be reorganised for the TV computer.
The app keeps its own log on disk, and the folder that holds it differs by platform. Attaching that file to a forum post is far more useful than pasting its contents into a message.
No. Plex HTPC runs on the computer attached to the screen, so that machine handles the playback. A dedicated box is only necessary if you would rather not keep a computer powered near the television.
Plex HTPC is a desktop player built for computers hooked up to a television, letting you browse and play a Plex media library with a remote, game controller, or keyboard instead of a mouse.
Plex Media Player (Deprecated) is a retired desktop client that streamed movies, TV shows, music, and photos from a Plex Media Server to a home theater PC or desktop computer, with a full-screen TV interface and a windowed mode.
Plex Media Server is the software that turns your own computer or NAS into a private streaming hub, organising your movie, TV, music, and photo libraries and serving them to Plex apps on almost any screen.
Winamp is a media player for local music collections, internet radio, and podcasts. It plays the common audio formats, organizes files in a searchable library, and adds an equalizer, visualizations, and skin support that made it a benchmark desktop player.
JRiver Media Center is a media player and library manager that organises audio, video, images, and recorded television in one database, plays files bit-perfectly to high-end audio gear, and shares the collection across a home network to phones, TVs, and streamers.
Comments