What your connection does to a download
Analyze barely touches your network. The transfer that follows depends on it completely, and this page is about that second half.
Paste a URL to download
Paste a public video or playlist URL.
Quick check — then you can download
Finding streams…
Usually a few seconds
Note: Only download content you have the rights/permission to download. Some platforms rotate signed URLs; if a download fails, paste the URL again and click Download.
Paste one video URL per line (2–100 URLs on Pro or Creator). Upgrade to Pro to unlock batch mode.
Supported sites:
and 1000+ more — including YouTube Reels, Shorts & Stories, Vimeo, Dailymotion, and regional hosts.
YouTube, TikTok, Instagram, Twitter/X, Facebook, Vimeo, Reddit, Dailymotion, Twitch, and 1000+ more.
Pro users enjoy an ad-free downloader. Free tier may show sponsored placements. No URL history sold. Optional Vidzilla extension for Page Media — same privacy standards.
Files go straight to your device.
Only the second half of the job runs over your line
Opening the address you pasted, reading the page, and measuring each media file happen between our servers and the source. Your network carries none of that traffic, which is why a phone on a weak signal reaches the results list as fast as a desktop on fibre.
The transfer is the opposite. Every megabyte of the row you selected crosses your connection to reach your storage, so from the moment you press Download file the quality of that line is the whole story.
What a drop leaves behind on your disk
A video file is written from the beginning to the end. When the connection fails at sixty percent, your browser has already committed sixty percent of the bytes to storage, and it stops there.
The awkward part is that the fragment behaves like a real file. It carries the right name, it takes up space, and a player opens it and plays the opening minutes before ending in the middle of a sentence. Six months later that is easy to mistake for a video that was always short. Delete the fragment as soon as a transfer fails, rather than leaving it in the folder to be sorted out later.
Why the next attempt starts from zero
There is no resume. Nothing on our side holds the position you reached, because prepared files expire on a short timer and no per-visitor copy waits around for a second connection. A new attempt asks for the whole file again from the first byte.
That changes the arithmetic on a bad line. Restarting a 40 MB file after a drop costs you a minute. Restarting a 900 MB file after a drop at ninety percent costs you everything you just spent, and the second attempt has no better odds than the first on the same connection.
Changing networks in the middle of a transfer
A device that swaps networks mid-transfer ends the transfer. Walking out of range of home Wi-Fi and letting the phone fall back to mobile data does it, and so does a laptop moving from one office access point to another.
Two smaller interruptions have the same effect and are easier to forget. A phone that locks its screen and suspends the browser stops the download, and a laptop that goes to sleep on its power settings stops it too. On a long file, plug the machine in and keep the screen awake before you begin.
Turning the size column into an honest estimate
Every row shows the real size of that file in megabytes before you commit to it. Combined with a rough idea of your own download speed, that number tells you how long you are asking the connection to hold steady.
Judge the risk by that duration rather than by the picture quality alone. A save that needs ninety seconds of a wobbly line usually completes. A save that needs forty minutes of it is a different proposition, and the top row on a long recording is exactly the case where the two diverge.
Choosing a smaller row when the line is poor
One step down the results list is the practical answer to a connection you cannot rely on. It is a smaller file, it is exposed to the network for less time, and it is the version you can actually finish.
Work out what the copy is for before you decide. Video for a phone screen, a reference copy, or something you want to watch once loses very little at a lower row. An audio-only row, where the source publishes one, is smaller again and finishes on connections that no video row survives. Keep the top row for the times you are on a line that will hold.
Confirming the file arrived whole
Check the saved file against the number that was on the row. A file noticeably smaller than the size you agreed to is a transfer that ended early, whatever the browser reported.
Then open it and jump to the last minute rather than the first. Playback that reaches the end is a complete download, and doing that check now is cheaper than discovering the truncation on a train with no signal.
Questions about downloading over a real connection
My Wi-Fi dropped at eighty percent. Can the download carry on from there?
No. There is no resume, so the next attempt requests the file again from the first byte. Delete the partial file before you start over.
Why does a half-finished video still open in my player?
The bytes that arrived are genuine video from the start of the file. A player reads them happily and then runs out, which looks like a short video rather than a failure.
Does a slow connection reduce the quality of the file I receive?
No. The file is the encoding named on the row you picked, and a slow line changes only how long it takes to arrive.
Should I download over mobile data or wait until I am on Wi-Fi?
Mobile data works and the file is charged against your allowance once. On a large row, waiting for a network you can stay on for the whole transfer avoids paying for a save that fails.
My phone locked its screen while the file was saving. What happened?
The browser was suspended and the transfer ended with a part-written file. Set the screen timeout longer, or pick a row small enough to finish inside it.
Is a second attempt on the same row worth trying after a drop?
On a line that has settled, yes. On a line that is still unstable, choose a smaller row instead, because the same file over the same connection faces the same interruption.