From link to file
Four steps, and a clear line between what runs in your browser and what runs on your own server.
Paste the page link
Open the video on one of the supported sites and copy the address from your browser. The site and link shape are checked here first, so a bad link fails instantly instead of after a long wait.
The server reads the page
This app asks the extraction service, which fetches the page and finds the sources it exposes. Expect this to take a while — it retries through proxies and paces its requests, so tens of seconds is normal.
Compare what came back
You get the real list: resolution and container, exactly as the site published them. These sites do not publish file sizes, so none are shown rather than guessed at.
Play or save it
The result includes a player with a quality selector. Playback and downloads fetch video bytes straight from the source CDN. HLS downloads save as MPEG-TS or fragmented MP4, depending on what the site provides. A quality may play while remaining unavailable for direct download. No server or paid proxy video fallback runs.
Who talks to whom
Useful to know when something fails, because it tells you which side to look at.
- Your browser
- Validates the shape of the link, renders whatever the service returns, and starts the file save. It never contacts the source site directly.
- Your extraction service
- Fetches the page, runs the matching extractor, lists the renditions and signs a short-lived URL for the one you pick.
- The source site
- Only ever talks to your backend. Whether a video resolves, and at which qualities, is entirely up to what that site exposes.