Vizard Agent

How to preview cheaply at low resolution and master at full quality

Last updated 2026-09-05 · 7 min read

Tell Vizard Agent to iterate at preview resolution and render the master only when you approve a version. It builds and revises the whole edit small, renders full size once the cut is agreed, and then checks the specific things — title sharpness, fine detail — that a downscaled preview cannot show you.

What is the short version?

Most of the rounds on a video are about decisions — is this the right shot, does the line land, is the ending too long — and none of them need a full-resolution render. Making that separation explicit is the cheapest change you can make to a big job.

  1. Go to Vizard Agent and say previews come at low resolution.
  2. Review and revise until you approve a version.
  3. Say to master at full size, then check the detail.

What do you need before you start?

A job big enough to care. On a fifteen-second reel this is bookkeeping; on a minute of generated shots with graphics over them it is the difference between iterating freely and flinching every time you ask for a change.

What do you type into Vizard Agent?

Say the rule to Vizard Agent once, right at the start. Said afterwards it saves you nothing at all, because the expensive renders have already happened by then — and the entire value of this is in the rounds you have not had yet.

Prompt

Iterate at 720p previews. Only render the full 4K master once I've approved a version. When you do, check the titles and fine detail at full resolution — the preview won't show those.

Variants worth knowing:

What does Vizard Agent actually do?

Here is the order Vizard Agent worked in on a real minute-long hype video full of generated shots. Notice the shape of it: preview, review, fix, preview again — with a full 4K render only ever starting after an approval, four times across the whole job.

  1. Renders the picture cut at preview size.
  2. Grabs frames from the preview and watches it back.
  3. Applies the fixes and re-renders the preview.
  4. Uploads the corrected preview for review.
  5. Uploads a revised preview after the next round of notes.
  6. Starts the full-resolution render once the cut is approved.
  7. Parallelises the master's shot renders to shorten the wait.
  8. Renders the final master and inspects it.
  9. Checks the title sharpness at full resolution.
  10. Previews new graphics in the cut — back to preview size.
  11. Rebuilds the preview with the new cards.
  12. Corrects a title size and re-renders the preview.
  13. Starts the next full render once that is approved.
  14. Verifies the delivered master and looks at the finished file.
  15. Checks a new narration line while the master renders.

Step nine is why this is not simply "work small". A downscaled preview cannot tell you whether a title is sharp, whether small text is readable, or whether a generated texture holds up — those only exist at full size, so they are checked there, deliberately, rather than assumed from the preview.

Step fifteen is a small efficiency worth copying. The master render takes time; the next round of notes does not have to wait for it.

What does the result look like?

The same finished master you would have got anyway, arrived at through more rounds rather than fewer — because each of those rounds cost Vizard Agent a preview render instead of a full-resolution one, and the saving went back into the number of revisions you could afford.

The visible difference is in how freely you ask for changes. When a revision is cheap, you request the one you actually want rather than the one you can justify.

When does this not work well?

Some decisions genuinely require full resolution to make at all, and taking them from a downscaled preview means discovering the problem after the expensive render rather than before it. Vizard Agent flags these rather than letting a preview stand in for them.

How do you fix a result that came back wrong?

Say whether the problem is in the cut or in the detail. Vizard Agent keeps the preview chain and the master settings separately, so a story note goes back to preview and a sharpness problem re-renders the master.

How does Vizard Agent compare to doing it yourself?

Every editor already knows to work at a proxy resolution — it is standard practice with camera footage. It is less automatic on generated work, where each shot costs something to make, and where the temptation is to render final because it is only one more click.

By hand Vizard Agent
Iteration size Full, out of habit Preview, by rule
When the master runs Whenever you export On approval only
Detail checks Assumed from the preview Done at full resolution
Cost of a round The same every time Much lower until approval
Number of rounds Rationed As many as the video needs

Common questions

What resolution should previews be? 720p is comfortable. Vizard Agent uses whatever you name.

Will the preview look different? Smaller and softer. Vizard Agent keeps the edit, timing and sound identical.

Can I approve part of it? Yes. Vizard Agent can master an approved section while you review the rest.

Does the master re-do the work? Vizard Agent re-renders at full size from the same decisions, not from scratch.

How much does this save? It depends on the job. Ask Vizard Agent for the comparison before you start.

What can't I judge from a preview? Sharpness, small text, fine texture and grade. Vizard Agent checks those on the master.

Can it master more than once? Yes. Vizard Agent gives each approved version its own master.

Does it slow things down? Slightly per round, and it usually removes the expensive rounds entirely.

Should I say this at the start? Yes. Tell Vizard Agent later and it saves nothing.

Can it preview just one shot? Yes. Vizard Agent will, and one shot often settles the question.

What about audio? Audio is cheap either way. Vizard Agent works it at full quality throughout.

Will it remember the rule? For the session, yes. Repeat it on the next job.

Can it render the master in the background? Yes. Vizard Agent carries on with your notes while it runs.

Why not just render final every time? Because the cost of a round decides how many rounds you allow yourself, and rationing revisions is how videos end up merely acceptable.