A Streaming Platform’s New Frontend Foundation

Plex, the TV streaming platform offering live and on-demand content, rebuilt its web experience in 2021 with a unified architecture designed around user experience. The company refactored watch.plex.tv to Next.js on Vercel, tapping into native optimizations such as server-side rendering (SSR), on-demand Incremental Static Regeneration (ISR), and Edge Middleware. The result: a Real Experience Score improvement from 79 to 90, a rise in Google search ranking, and a traffic increase after relaunch.

Previously hosted on Kubernetes auto-scaling clusters, the site met performance requirements but taxed the development team. By moving to Next.js on Vercel, Plex cut roughly 40% of its codebase lines, enabling faster feature development. The integration itself took less than five minutes, according to Eric Matthys, Principal Software Engineer. "Vercel had us immediately impressed. In less than 5 minutes, we had Vercel hooked into our GitHub repository with an integration that felt polished."

Less Configuration, More Product Work

Plex previously managed a dense build configuration with cumbersome migrations. On Next.js, the team benefits from graceful, non-breaking adoption patterns, allowing them to shift effort from infrastructure upkeep to product development. Serving content at the edge further reduced page load times, improving both impressions and the developer experience.

Hybrid Rendering for SEO and Performance

Plex employs a hybrid rendering model: Static Generation delivers maximum performance for most pages, while SSR is used selectively to maximize crawlability—for instance, returning hard 404 responses instead of soft errors. This blend lets the team optimize for search engines without losing dynamic capabilities.

For catalog pages covering millions of movies, shows, and cast members, full static regeneration would be prohibitively expensive. Plex uses on-demand ISR to balance freshness with build efficiency. As Matthys explains:

"We use on-demand ISR to balance these by increasing the revalidate time of our static pages while allowing our backend to revalidate these pages on demand as important changes happen. This reduces the time spent rebuilding pages that did not have any meaningful changes."

This approach ensures that when a new title becomes available for streaming, it appears to users immediately without triggering a full site rebuild.

Personalization and Testing at the Edge

Edge Middleware enables Plex to serve geographically appropriate content based on title availability by region. The team also runs and tracks A/B tests for static pages without introducing Cumulative Layout Shift or adding to page load times.

Testing and Monitoring with Integrations

Two Vercel integrations support Plex's release confidence. The Checkly integration runs end-to-end tests across the platform whenever changes are made. The Axiom integration monitors crawl requests in real time, eliminating the roughly four-day delay Plex previously experienced with Google Search's native crawl stats and providing immediate feedback on modifications.

The unified foundation delivers on both developer and end-user fronts, and Plex continues to push for faster performance and improved search visibility with the new stack.