It only fails in Safari: two HLS engines, and how to debug across hops

BhaveshSGupta@disroot.org (Bhavesh S. Gupta) — Tue, 06 Oct 2026 09:03:00 +0530

When a live stream breaks in Safari and plays in Chrome, the tempting conclusion is that Safari’s player is the problem. Often it isn’t. Both browsers receive the same files from the same CDN. They differ in what they do when one of those files is wrong, so a delivery fault that Chrome quietly recovers from becomes a Safari bug report.

In short: Chrome, Edge and Firefox usually play HLS through hls.js, which retries failed requests and skips small gaps; Safari uses its native player, which surfaces the same faults as errors or stalls. Both get identical bytes, so a problem that only shows in Safari is usually a delivery problem. Find it by measuring each hop separately: compare responses at the origin and the CDN, probe from many regions, group logs by browser, and inspect the segments.

Debugging on Everyone Has a Story

It only fails in Safari: two HLS engines, and how to debug across hops