The modern revival of plex-remote-transcoder — built by self-hosters who needed 4K transcoding without expensive hardware.
Every Plex and Jellyfin user hits the same wall: your server's CPU can't keep up with 4K HEVC transcoding. The old answer was "buy a bigger server" or "tell your users to direct play." Neither is great.
Years ago, plex-remote-transcoder solved this by offloading transcodes to a separate machine. It was brilliant — but it relied on SSH tunnels, shared filesystems, and broke with every Plex update. The project was abandoned. PlexBeam picks up where it left off.
HTTP, not SSH tunnels. PlexBeam streams transcode data over standard HTTP. No shared filesystem. No NFS mounts. No SSH keys to manage. Your media stays on your server — only the transcode job travels to the worker.
Self-healing cartridge. A watchdog daemon survives Plex and Jellyfin updates automatically. Install once, forget about it.
Automatic fallback. Worker down? Transcoding falls back to your local server. Your viewers never notice.
Full hardware decode → scale → encode pipeline. Intel QSV, NVIDIA NVENC, VAAPI — not software transcoding on a remote CPU.
PlexBeam streams the transcode job, not your files. Your media library never leaves your server.
No per-minute billing. No bandwidth charges. One flat price for a dedicated GPU worker.
One cartridge system supports both Plex Media Server and Jellyfin. Pick your platform — or run both.
Join the pre-beta waitlist and lock in 50% off for life.
Claim My Early-Adopter Spot →