The URL pieces that identify a video

Which part of a URL matters

A URL that reaches a video has three working parts: the host name, the path, and whichever identifier names the video—either in the path or in a query parameter. Everything else is bookkeeping added by whoever shared the address.

You do not have to separate those parts yourself. Paste the whole string. Vidzilla loads the address, follows redirects, and lists the files the resulting page serves. Each row shows a real encoding with resolution and size in megabytes.

Thinking in parts prevents two opposite errors: deleting something essential, and assuming every character is sacred decoration. Host, path, and id are essential. Tracking pairs are usually non-essential but still safer left attached than removed by guesswork.

When a URL contains a username in the path plus a video id later, both segments can matter. Truncating the username segment sometimes 404s even if the id remains. Prefer full-string pastes over surgical edits.

Host: where the request is sent

The host sits after https:// and before the first single slash. It names the server family that will answer. Without a valid host, there is no page to inventory.

Short links use a different host than the final watch page. That is normal. Paste the short link; redirects carry Analyze to the destination. If a short link is expired, open it in a browser and copy the final address bar value.

Internationalised hosts and punycode forms are still hosts. If a share link shows a non-ASCII domain, paste it exactly. Rewriting the host by hand to an ASCII guess is a common self-inflicted failure.

Ports in a host (example.com:8443) are part of where the request is sent. Dropping the port removes part of the destination and can send Analyze to the wrong service.

Path: the route on that host

The path begins at the first / after the host. Watch routes, clip routes, and media file paths live here. Changing or truncating the path is how people accidentally turn a video URL into a section or home URL.

Some hosts put the video id in the path (/watch/abc123). Others put it after a question mark. Both shapes are valid. What matters is that the id segment remains complete.

Identifier versus bookkeeping

The identifier is the stable code that selects one video. Bookkeeping includes campaign tags, session ids, and share tokens that describe how someone arrived.

Leave bookkeeping attached when you paste. Hand-trimming is risky because the identifier and a tracking tag often sit in the same query string and look alike.

Bookkeeping that resembles an id—long random tokens—still is required for many signed URLs. Expiry signatures are bookkeeping with teeth: without them the host refuses the file even though the path remains intact.

When a signed URL fails after hours, the id path may still be valid but the signature pair expired. Refresh from the page that issued the URL rather than inventing new query pairs.

• Safe to leave: campaign, referral, and session parameters after the video id.
• Safe to leave: a timestamp that starts playback mid-file—the full encoding still downloads.
• Risky to remove by hand: any parameter or path segment whose value is the video id.
• Worth removing by hand: nothing. Extra URL length does not cost a download slot.

Direct media URLs as a special case

Some URLs end in a media extension and point at the file itself rather than a watch page. They come from embeds, RSS enclosures, and CMS media libraries. Vidzilla accepts them.

Analyze usually returns a single row for a direct media URL because only one encoding lives at that address. There is no higher-resolution sibling to offer from that exact link.

Signed direct URLs that include an expiry parameter work while the signature is valid and fail after it lapses. Return to the page that issued the URL and copy a fresh one.

URLs damaged in transit

Email, PDFs, and terminals break long addresses across lines. Pasting a broken half reaches nothing. Check that your paste starts with http and ends with a complete id or file name.

If the string contains a line break or a space in the middle, clean it in a plain text field first, then bring it to this page.

Free use allows three completed downloads per day resetting at midnight UTC and blocks files over 150 MB. Analyze does not spend a free slot.

After the right parts resolve

When host, path, and id are intact and the page is public, you get a row list. Pick an encoding, run Download file, and keep the tab open until the browser finishes writing.

Rename the file on disk so you can find it later. Prepared server copies expire; the lasting archive is the file in your download folder.

Pro removes ads and lifts free size and daily caps when a job needs that capacity.

Putting the parts back together for Analyze

You rarely need to rebuild a URL from parts. The parts model exists so you can audit a broken paste: missing scheme, clipped host, clipped path id, or truncated query value.

Once the audit passes, paste the repaired full string, run Analyze, and choose a row that fits free rules—three completed downloads per day resetting at midnight UTC, 150 MB per free file.

After Download file completes, verify playback offline. A correct URL with a truncated transfer still yields a useless file; the parts of the URL cannot fix a closed tab mid-download.

Pro lifts free caps when the right URL parts resolve to a master larger than free use allows. The URL anatomy does not change under Pro; the size and daily gates do.

When you store URLs for later, keep host, path, and identifier together as one string. Saving only the id code without the host forces you to rebuild the address later and is how essential segments go missing before the next Analyze run.

Related pages

• Download video from a URL
• URL video downloader
• Save video from URL
• Download video from website
• Download video link