Two different clocks are running at once: the media addresses and the page credential. Knowing which one ran out tells you whether a single re-parse is enough.
Why the addresses expire at all
Each media address is wrapped in an encrypted token with a fixed lifetime. It is not a permanent file link, and it is not meant to be one: a shorter life limits how long a resolved address can be reused by anyone who sees it.
Forwarding a link does not work
Pasting an address into another tab, a chat message or a download manager after the window has closed fails: the address carries its own expiry and nothing renews it. Send the page link you started from instead.
Expiry during a merge
A merge reads both tracks while it runs, so a download begun near the end of the window can be interrupted partway through. The partial output is not a playable file — re-parse, then merge again.
Refresh, tabs and new links
Reloading the page clears the stored credential and returns the panel to its starting state. It does not extend media addresses, and a second tab has to pass its own check before it can parse.
Reference
These tables are shared across the site, so a figure you saw on one page is the figure you see here.
| When the platform… | The result panel shows | What you do |
|---|---|---|
| Serves one finished file | A single track with picture and sound already together | Use the offered save action without merging; completion still requires readable media and a supported browser. |
| Splits picture and sound | Two lists: video-only tracks and audio-only tracks | Choose one complementary track of each kind and merge in a supported browser; phones may have storage or memory limits. |
| Needs relaying or blocks browser reads | The same tracks, routed through a short-lived relay link | YouTube and X use relaying by default; merging chooses a transport automatically. For other single-file results, try the relay button if offered. |
Background and edge cases
Saved files are unaffected
Once a file is on your device, an expiring address changes nothing about it. Expiry only affects links that have not been used yet.
What expiry does not explain
If a download fails seconds after parsing, the cause is the source or the transport, not the clock. Compare the two failure guides before assuming a timeout.
