859: Streaming Video in 2025

Episode Summary

Executive Summary: The episode breaks down how modern video streaming works in 2025, from HLS/M3U8 chunked delivery and FFmpeg transcoding to hosting, CDN, access control, and analytics. Wes and Scott compare DIY stacks with managed services like Mux, Cloudflare, Bunny, AWS, Vimeo, and Cloudinary, arguing that Mux and selective Cloudflare/R2 setups offer the best balance of cost, simplicity, and control for most creators.

Main Topics: How HLS streaming works: They explain that streaming video is delivered via HLS playlists (.m3u8) that reference small .ts chunks, enabling adaptive playback and easy insertion points for ads and captions. Transcoding and FFmpeg workflows: The hosts discuss FFmpeg as the standard tool for generating multiple resolutions/bitrates, chunking video, and orchestrating output files, whether locally or in a service pipeline. Adaptive bitrate and viewer experience: They describe how players start with a lower-quality stream, then switch up or down based on bandwidth, and how bitrate affects readability and compression artifacts. Storage, CDN, and cloud architecture: They compare S3, R2, CloudFront, and Cloudflare CDN strategies, emphasizing bucket organization, database metadata, and the need for global caching for good playback. Managed video platforms and cost tradeoffs: Mux, Cloudflare Stream, Bunny, AWS MediaConvert, Vimeo, Cloudinary, and Bitmovin are evaluated based on pricing, simplicity, 4K support, and developer experience. Player layer and Media Chrome: They recommend Media Chrome as a flexible web-component-based player layer that works across frameworks and supports skins, thumbnails, AirPlay, YouTube, Vimeo, Spotify audio, and more. Advanced features: analytics, subtitles, live streaming: The conversation covers dynamic ad insertion, view stats, clip stitching, subtitle tracks, live streaming pipelines, and how these features fit into HLS ecosystems.

Key Arguments: HLS is the core modern format for streaming because it breaks video into playable chunks and supports adaptive bitrate switching. FFmpeg remains the essential tool for transcoding, but orchestration and queueing become the real complexity at scale. Hosting video yourself is possible and can be cheap, but it requires careful organization, metadata management, and CDN caching rules. Cloudflare R2 can be used with Cloudflare’s CDN for video delivery, but R2 alone is not globally distributed; caching must be explicitly enabled. Mux is presented as the easiest managed option for most creators because it handles ingest, encoding, storage, playback, and analytics with predictable pricing. Cloudflare Stream is improving, but lack of 4K support makes it less attractive for high-quality video use cases. AWS’s video stack is powerful but overly complex and expensive for most independent creators or small teams. Media Chrome solves many pain points of player maintenance by offering a composable, framework-agnostic web component approach. If source files are stored cleanly in buckets, it becomes much easier to migrate between providers later. Advanced features like ad insertion, subtitles, and analytics are easier when the stream is already chunked and standardized via HLS.

Data Points: Video encoding size example: 15 terabytes of 4K video for $2.18 - Referenced from Steve and Aaron’s Cloudflare R2 usage thread as an example of extremely low bandwidth cost Course video length example: 30 videos x 15 minutes = 7.5 hours - Used to estimate storage and streaming costs for a sample course Estimated raw course storage: About 16 GB - Approximate size after chunking and multiple resolutions for the 7.5-hour course Cloudflare R2 storage price: 1.5 cents per GB per month - Used to estimate monthly storage costs for self-hosted video blobs Estimated R2 monthly cost: About $0.25/month - Cost to store the example 16 GB of video in R2 Estimated R2 yearly cost: About $3/year - Annualized storage cost for the example course Mux storage pricing: $0.003 per minute - Used to compare storage costs for the same 7.5-hour course Estimated Mux storage cost: About $1.35/month or $16/year - Derived from 450 minutes of content in the example course Level Up Tutorials video library: 6,000 minutes (100 hours) - Wes’s real-world Mux usage example for his course library Mux storage cost for library: $18 - Cost to store the 6,000 minutes of video Mux encoding cost for the month: $1 - Recent monthly encoding cost for already-encoded library content Mux streaming cost for the month: $13 - Monthly cost for streamed minutes in the library example Total Mux monthly cost: $33 - Combined cost for storage, encoding, and streaming of Level Up Tutorials Mux viewing cost: $0.05 per hour watched - Used to estimate per-view playback costs for long courses Example per-view cost: $0.43 - Estimated cost if a viewer watched all 7.5 hours of the sample course Cloudinary plan example: $224/month for 600 GB bandwidth - Illustrates pricing for an alternative managed video/media platform Cloudflare Stream resolution support: 360p to 1080p - Referenced from the FAQ; noted as lacking 4K support Vimeo cost issue: $10,000 to stream video - Wes’s reported current Vimeo cost after being told he was out of compliance PolyCapture price: About $5 - Scott described it as inexpensive relative to its usefulness Anker MagGo capacity: 10,000 mAh - Scott’s battery pack recommendation

Pivotal Quotes: "HLS is actually built into Safari, but it has been since version 6." — Scott Tolensky: Explaining browser support for HTTP Live Streaming and why Safari is the exception "You don't have to worry about storage or ingest. You don't have to worry about saving things database. You upload it and then you just get the M3U8 file and you just plop that in your site." — Wes Boss: Describing why Mux is attractive for developers who want simplicity "I could do a whole episode on video players I have used, loved and lost." — Wes Boss: Reflecting on the pain and maintenance burden of traditional video player libraries

Implications: For most teams, managed video services beat DIY unless scale or control demands a custom stack. HLS, FFmpeg, and global CDN caching are the core building blocks, while Mux and Media Chrome reduce operational burden and future migration risk.