Decision tree from free cap to visual need
Format lists look like a ladder: taller numbers feel “better.” The useful question is which rung fits today’s constraints—free size ceiling, hotspot megabytes, disk headroom, and whether you actually need fine text. This decision tree turns that into an order of checks before you tap Download file.
Use it with Vidzilla’s labeled rows. It does not invent bitrates; it teaches you to read the sizes already printed beside each height.
If you only remember one habit from this page, make it confirmation on disk: the job is not finished when a progress bar hits 100%, only when the file size looks right and playback works.
Open HD download when the tree says you need it
Node 1: does Analyze show any rows?
If the list is empty, stop. Fix the URL or public-access problem. Quality choice does not exist yet. When rows appear, note each height and approximate megabytes—those megabytes drive every later node.
Node 2: eliminate rows over the free size ceiling
Cross out anything above the per-file limit shown for your tier. Hoping the ceiling will not apply wastes time. If every row is too large, you need a higher tier, a different source encode, or an audio-only path—not a wishful click on 4K.
Daily count limits also matter: one oversized failure can still consume a slot depending on how far the job got—verify carefully to avoid repeats.
- Strike rows above the tool’s size cap
- Keep remaining candidates
- If none remain, change plan (tier, audio, wait)
Node 3: fit the data and disk budget
On hotspot or near-full disks, compare remaining megabytes to each candidate. Pick the largest height that still fits comfortably with a buffer. On unlimited Wi‑Fi and spacious SSDs, this node rarely removes much—continue to visual need.
Node 4: what must human eyes resolve?
Talking-head podcasts and stage lectures often play fine at 720p. Code screens, sheet music, and whiteboard math may need 1080p or higher to keep glyphs legible. Phone-sized meme rewatching rarely needs 4K.
Ask: will I fullscreen on a TV, or glance on a commute phone? Match the rung to the display, not to pride.
Audio-only branch
If picture adds nothing for today’s task, take an audio row or plan an MP3 extract. That branch skips the height ladder entirely.
Node 5: prefer compatible containers when editing
When two heights both fit, and one row is clearly MP4-oriented for your editor while another is an exotic bundle your NLE rejects, pick the compatible label. Compatibility is part of quality of life even when pixel counts match.
Node 6: download, verify, then refuse FOMO re-grabs
Download the chosen row, confirm size and playback. Do not immediately spend another free slot on “maybe 1080p looks nicer” unless a real legibility problem appears. Re-download only when the tree’s facts change—new display, failed file, or newly available rights-cleared master needs.
Worked patterns without fake benchmarks
Travel hotspot + speech lecture → lean 720p or audio. Classroom projector with fine diagrams → 1080p if under caps. Archival personal keep on external SSD → tallest row under ceilings. Chat share later → download sensible master, then trim/compress derivatives instead of grabbing a second muddy row from the site.
Tie-breakers when two rungs both fit
After caps, budget, and visual need leave two survivors, break ties with destination, not vanity. Prefer the container your editor or classroom PC already opens, then the row whose labeled size leaves a comfortable free-tier buffer, then the height that matches the largest screen you will actually use this week.
If both rows are the same height and container, the heavier megabyte label usually spent more bits—useful for fine diagrams, optional for talking-head review. Write the chosen height and size in your notes so FOMO re-grabs have to beat a recorded decision, not a vague feeling.
When the tree collapses to one bad option
Sometimes every video row exceeds the free ceiling, or the only under-cap row is too soft for whiteboard text. Stop clicking. Switch to audio-only for note-taking, wait for Wi-Fi plus a higher tier if you truly need picture, or find a rights-cleared alternate source that publishes a leaner encode.
Forcing a doomed tall-row attempt does not educate the tree—it burns a slot and teaches nothing new. Treat no viable rung as a valid outcome that changes the plan, not as a prompt to ignore Node 2.
Re-running the tree when the display changes
The decision tree is not a one-time tattoo on a file. If you later move from phone rewatching to a classroom projector with fine diagrams, the visual-need node can justify a new download—provided caps and rights still allow it. Until the display or task changes, resist FOMO re-grabs of the next rung.
Write the chosen height and megabyte label into the project note beside the source URL. Future you can see why 720p was correct for a hotspot week without re-litigating the entire ladder from scratch.
Practical closeout for this guide
Keep the focus on “Decision tree from free cap to visual need.” Paste one public URL you can open signed out, run Analyze, choose a row by height and megabytes, press Download file, leave the tab open until the browser finishes, then prove size and playback on disk before you rename or move the file.
When a step fails, change one variable—the URL shape, the public-access check, or the selected row—then continue. Free daily counts and per-file ceilings still apply. Pro adjusts those limits and ads; it does not open private, password, or DRM-gated media.
Respect creators and platform terms. Personal offline copies of content you are allowed to keep are the intended use. Redistribution and access bypass are outside Vidzilla’s purpose.
- One public URL per paste
- Analyze, then Download file
- Confirm bytes and playback
- Quotas are not access keys
Frequently asked questions
Is the top row always best?
No. Best means fits caps, budgets, and visual need—not the maximum integer on the list. The top row is often the worst free-tier choice because it collides with size ceilings first.
Why do two 1080p rows show different sizes?
Publishers encode differently. Trust the megabyte label on each row.
What if I need 4K but the free cap blocks it?
Choose a lower legal rung, upgrade tier if appropriate, or wait—do not fight the ceiling.
Should I keep multiple qualities?
Usually one verified encode plus local derivatives (trim/compress) beats multiple online downloads. Extra online grabs spend quota; local copies from a known-good master do not re-hit Analyze limits the same way.
Does HD tool change the tree?
It focuses the UI on higher rungs; the same cap and budget checks still apply.
Where do subtitles fit in the tree?
After you can save a file at all. Pick a height that keeps caption text readable if captions are burned or intrinsic to the picture.
What is the shortest correct workflow?
Copy one public watch URL, paste into Vidzilla, Analyze, pick a row, download with the tab open, verify size and playback on disk.