How Chunked HTTP Delivery Works
Browsers use HTTP Range Requests to fetch only the portion of a file they need right now. When you hit play, your browser sends a request like 'give me bytes 0–2MB of this file.' As you watch, it keeps requesting subsequent chunks. This is why you can seek to different parts of a video without downloading everything first — you're just requesting a different byte range.
What Makes a URL Streamable
Not every URL works. For streaming to work without a download, the server must support HTTP Range Requests (check for `Accept-Ranges: bytes` in the response headers). Direct file links from services like Google Drive, Dropbox public shares, or your own server all work this way. Redirect URLs, links that require cookie authentication, or URLs behind login walls typically won't stream cleanly.
Supported Formats in the Browser
The browser's built-in decoder supports MP4 (H.264/AAC) natively across all major browsers. WEBM (VP8/VP9) works in Chrome and Firefox. HLS (.m3u8) streams are supported natively in Safari, and FluxPlays loads hls.js automatically for Chrome and Firefox users. If your link ends in .mp4, .webm, or .m3u8, you're ready to paste and play.