Color grading AI footage in DaVinci Resolve is shot reconciliation, not single-clip look work, because each clip comes from a different generation with its own white balance and no usable metadata. Upscale first with Topaz Astra, pick one hero clip, then match every clip's neutrals and skin to it on the scopes. LUTs go on last.
DaVinci Resolve color grading for AI footage is shot reconciliation before it is look creation: every clip arrives from a different generation with its own white balance, contrast curve, and zero camera metadata, so nothing matches by default. The working order is fixed — upscale first with Topaz Astra, balance and read scopes, pick one hero clip, match every other clip's neutrals and skin tones to it, then build the look. LUTs go on last, never first.
Why grading AI footage in Resolve is different
Camera-shot footage shares a sensor, a color science, and metadata Resolve can read. AI footage shares none of that. Each clip is an independent generation: one renders warm, the next cool, skin density drifts shot to shot, and there is no LOG curve or color space tag to normalize from. That makes the match pass — not the creative look — the bulk of the work.
Two properties of AI footage compound this. First, generated clips ship with an ultra-sharp, plasticky surface quality — documented productions found Seedance 2.0 output needed deliberate softening in post to read as filmic. Second, many final shots are not single generations: in one documented animated episode, 17 of the final shots were stitched from two or more generations of the same prompt (the Frankenstein shot), which means you sometimes match within a single shot, not just between shots. Treat every cut point as a potential color seam.
Step 1 — Upscale before you grade, not after
Run the upscale pass before any color work. Topaz Astra on invideo is the first step in the post-production realism pipeline for exactly this reason: the upscaler changes texture, edge rendering, and fine detail, and a grade built on pre-upscale footage will sit differently on the upscaled version — qualifiers pull different edges, grain interacts differently, and you end up regrading. Upscaling first also gives Resolve cleaner data to key from; pulling a skin qualifier on soft, artifact-heavy footage produces chattering mattes.
If you generated inside invideo, you can batch this stage by spinning up a named upscale sub-agent so every clip arrives in Resolve already processed. Then conform the upscaled clips into your timeline and lock picture before grading.
Step 2 — Set up the node tree and read scopes first
Build a consistent serial node tree on every clip before touching a single wheel: balance → match → look → texture, in that order. Keeping the same node positions across all clips means you can copy grades between shots and adjust only the node that differs.
Then open the scopes and leave them open. With no metadata, the waveform and vectorscope are the only objective reference you have. On the waveform, check where blacks and whites actually sit per clip — AI generations routinely deliver lifted blacks on one shot and crushed blacks on the next. On the vectorscope, check skin tones against the skin-tone indicator line; generated faces frequently drift magenta or yellow between clips of the same character. Your eyes adapt within seconds; scopes don't.
Step 3 — Pick a hero clip and match everything to it
Choose one clip — the generation closest to your intended look, with the most accurate skin and the cleanest exposure — and make it the reference for the entire timeline. Save it as a gallery still, then work clip by clip in split-screen wipe against that still.
On each clip's balance node: set black and white points to match the hero on the waveform, neutralize any color cast with the offset or temperature controls, and rotate skin onto the same vectorscope position as the hero. Resolve's automatic shot match can give you a starting point, but verify every result on scopes — it has no metadata to anchor to either. For composited shots stitched from multiple generations, wipe the two halves against each other and match them before matching the shot to the hero. The pass is done when you can flick between any two adjacent shots and see no jump in neutrals or skin.
Step 4 — Apply the primary grade and let it carry the emotion
With the timeline reconciled, the creative grade becomes one decision applied everywhere instead of forty separate fixes. Build it on the look node of the hero clip — contrast, color balance, saturation, split-toning — then copy it across the timeline or apply it at the group or timeline level so it sits identically on every matched clip.
The primary grade is where directorial intent lives, so grade to a stated rule rather than by feel. Documented productions encode this upstream: one horror production locked an 85:15 dark-to-light ratio as its lighting grammar, and another encoded its director's color philosophy as named tonal modes with exact hex values — both translate directly into measurable targets on your scopes rather than vibes.
Step 5 — Secondaries, then texture
After the primary, use secondaries only for what the primary can't reach: a qualifier to settle skin that keys slightly differently on one clip, a power window to control a hot sky or lift a face. Keep them per-clip and surgical — broad secondary moves reintroduce the shot-to-shot variance you just removed.
Then run the texture pass on the final node, applied uniformly: a small amount of blur or softening to take down the over-sharp AI edge, film grain to unify the surface of clips from different generations, and optionally halation on highlights. Adding slight blur, grain, and grade on top of AI footage is the documented method for moving it toward a live-action film response — and a shared grain structure is itself a matching tool, because it gives every generation the same top layer.
Step 6 — LUTs as a finish, not a fix
Apply any LUT on the last node, after balancing, matching, and the primary grade. A LUT is a fixed transform: feed it forty unmatched clips and it amplifies their differences, pushing each clip's cast in a different direction. Feed it a reconciled timeline and it behaves like a film print emulation should — one consistent finish over a unified base. If a LUT clips highlights or crushes shadows, trim exposure on the node before it rather than editing the LUT's output. Never reach for a LUT to make two clips match; that is the balance node's job.
Step 7 — Final unify and review
Watch the full timeline at speed, then flick-test every cut — park on a cut point and toggle between outgoing and incoming frames, watching the scopes for jumps in black level, skin position, or saturation. Pull gallery stills from the first, middle, and last shots of each scene and compare them side by side; slow drift across a scene is invisible at the cut but obvious in stills. Fix discrepancies on the offending clip's match node, never by re-touching the global look.
A review pass beyond your own eyes is worth running: skipping the cut review is the most common mistake in AI-directed filmmaking workflows, and one documented production caught an emotional-register mismatch by sending the cut back to its AI agent with an open 'what's working, what's not' prompt. Then render once, at your delivery format.
Where the invideo agent fits
invideo is an agentic video creation tool with all the current video models — Veo, Kling, Seedance 2.0 — plus upscalers like Topaz Astra available in one place, so the generation and post-prep stages happen before Resolve ever opens. The invideo agent reduces your Resolve workload at both ends. Upstream, it holds a locked style across every generation: one documented production had the invideo agent output 12 parameters per shot including a lighting plan and color script, which means clips arrive in Resolve closer together than raw, unconstrained generations would. The same production followed an 8-step color grading guidance process the invideo agent produced against its loaded style document — a per-shot grading brief you can take straight into your node tree. Downstream, Topaz Astra runs on invideo, so the upscale stage of this workflow completes before export, and clips land in your media pool grade-ready.
What a graded AI film actually costs
Grading adds time, not generation credits — DaVinci Resolve's free version covers everything in this workflow, including nodes, scopes, qualifiers, and gallery matching. The footage itself is where documented budgets sit: complete AI short films ran roughly $315–$750 per finished minute, and every one of those finished films still passed through a post pipeline of upscale, match, grade, and texture before delivery. Budget the grade as a day of work, not a line item.
FAQ
Should I upscale AI footage before or after color grading in DaVinci Resolve?
Before. Upscaling changes texture, edges, and fine detail, so a grade built on pre-upscale footage shifts when the upscaler runs. Documented AI post pipelines put Topaz Astra first, then color work on the upscaled files.
Why don't my AI clips match even with the same prompt?
Each generation is an independent render with its own white balance, contrast, and exposure — there is no shared sensor or color science. Match every clip's neutrals and skin tones to one hero clip on the waveform and vectorscope before building any look.
Can a LUT fix mismatched AI clips?
No. A LUT is a fixed transform that amplifies whatever differences exist underneath it. Balance and match all clips first, then apply the LUT on the final node as a finish over the unified base.
Does AI footage need a texture pass after grading?
Yes in most cases. AI-generated clips carry an over-sharp, plasticky surface; adding slight blur, uniform film grain, and the grade itself is the documented method for moving generated footage toward a live-action film response — and shared grain helps unify clips from different generations.
Sources
- DaVinci Resolve — Blackmagic Design — official product page covering the color page, nodes, and scopes referenced in this workflow.
- r/colorists — working colorist community discussing shot matching, scopes-first workflows, and LUT discipline.