To swap the endcard across every version of your video in DaVinci Resolve, you duplicate the timeline once per ending, hand-replace the tail clip, then render each timeline as its own job. That native method works but gets error-prone at scale. Recutly crosses your endings with your cuts and outputs a correctly-named Resolve XML per combination, pairing the right ending with the right cut for you.
First, the disambiguation: which "endcard" do you mean?
This guide is about the endcard or outro segment baked into your edit, the clip that sits at the tail of your timeline and renders into the actual video file. Your animated logo sting, your subscribe card, your sponsor outro, your "watch next" frame.
It is not about YouTube's native end screen, the interactive overlay you bolt on inside YouTube Studio after upload. That's a post-publish overlay, handled by tools like TubeBuddy, and it never touches your edit. If that's what you're after, you're in the wrong place.
Still here? Good. You've got one master edit and you need it to ship in several flavors: different cut lengths, different aspect ratios, maybe a clean version and a sponsored version, and each flavor needs a specific ending. Here's how that actually works in Resolve, and where it bites.
The manual method in DaVinci Resolve (numbered)
There's a real native workflow. It works. It's also entirely by hand. For each ending variation:
- Lock the master edit. Stop changing the timeline once you start versioning. This step matters more than it looks (see the render-queue trap below).
- Duplicate the timeline, or, safer, copy all clips into a fresh blank timeline. More on why in a second.
- Delete the tail endcard clip from the new timeline.
- Drag the alternate endcard into the gap on the same track.
- Fix the duration and timing so the new ending lands clean against the preceding clip.
- Rename the timeline so you can tell versions apart (
MainCut_EndcardA,ShortCut_EndcardB, and so on). - Add each timeline to the render queue as its own job in the Deliver page. Set the output name with Custom Name, which supports
%metadatavariables and User Presets. - Render All. Multiple timelines batch-queue fine in one session. That part Resolve does well.
That's clean for two or three combinations. The problem is combinations multiply.
Why you can't shortcut this with the render queue
The obvious instinct is to keep one timeline, queue several render jobs, and swap nothing. It doesn't work, and it's a documented gotcha confirmed by Larry Jordan, the Blackmagic Design forum, and Resolve tutorials alike.
When you queue multiple render jobs from the same timeline and batch render, Resolve renders the current state of that timeline for every job, not the state it was in when you queued each one. As Larry Jordan puts it: "Though you exported three movies, they all have the content of the current version of the timeline... Resolve always looks to the current version." Unlike Final Cut Pro, Resolve does not snapshot a temp copy per job.
So a separate timeline per ending isn't optional padding. It's the only thing that makes per-version endcards actually render correctly.
The wrong-endcard-on-wrong-cut risk
Now scale it. Say you ship 3 cut lengths × 2 endings × 3 aspect ratios. That's 18 deliverables, each a hand-built timeline with a manually swapped tail clip and a manually typed filename.
Every one of those is a place to put Endcard A on the cut that was supposed to get Endcard B. There's no guardrail in Resolve telling you the sponsored cut got the clean outro by mistake. You find out when the client does, after it's rendered, uploaded, and live. The hand-work is O(N), and so is the error surface.
The compound-clip gotcha
There's a quieter trap inside step 2. When you duplicate a timeline, the copy references the same compound (or nested) clip as the original. Edit that compound clip in one timeline and it can change in the others, silently. If your endcard, or anything near it, lives in a compound clip, "duplicate" is not "independent."
The fix is to copy all the clips into a fresh blank timeline instead of duplicating. That fully decouples each version. It's also more steps per version, which is exactly the kind of careful, repetitive work humans get wrong on deliverable number 14.
And no, you can't fully script your way out. The Resolve Python API can automate the render queue and duplicate timelines, but it cannot edit timelines (no cut, split, or razor). The endcard swap itself stays manual even for power users.
How Recutly makes the endcard matrix foolproof
Recutly is a browser tool built for exactly this. You export your finished edit as an FCP7 XML timeline and upload the timeline, not your footage, which never leaves your machine. Then Recutly crosses your endings × cut durations × aspect ratios into every delivery version, pairs the correct ending with the correct cut automatically, and names each file to your convention.
The output is DaVinci Resolve timeline files (FCP7 XML), not rendered video. You re-import each XML into Resolve, the media relinks by filename, and you render with your own settings, on your own machine, in free or paid Resolve.
| Manual in Resolve | Recutly | |
|---|---|---|
| Endcard swap per version | Hand-delete + drag + retime, each timeline | Crossed automatically into every combination |
| Right ending on right cut | You verify by eye | Paired automatically by the tool |
| File naming | Typed per job | Named to convention automatically |
| Compound-clip trap | Manual fresh-timeline copy to decouple | Each version is its own self-contained timeline, so there's no shared compound to inherit |
| Output | Rendered video | Timeline XML you re-import and render |
| Scales to 18+ versions | O(N) hand-work + O(N) error risk | One batch export |
A couple of honest notes on the roundtrip. The FCP7 XML reliably carries your cut points, clip references, and timing, but it does not carry effects, transitions, speed ramps, Fusion titles, or graphics. Those get stripped on import. The XML's frame rate must match your project timeline exactly, or the import fails or plays the wrong sections. And if file paths don't line up, you may need to relink media (Conform Options / Relink Selected Clips). Recutly sets up the structure and the right-ending-on-right-cut pairing; your grade, titles, and effects still get applied in Resolve.
On aspect ratios, Recutly sets up the ratio and canvas for each version (16:9 = 1920×1080 / 3840×2160, 9:16 = 1080×1920, 1:1 = 1080×1080). It does not do AI subject-tracking auto-crop. Creative reframing per shot stays in Resolve (Transform, an Adjustment Clip, or Smart Reframe in Resolve Studio).
Recutly is free for up to 5 versions per export. Pro is $19/mo for unlimited, and Studio is $39/mo. The free tier covers a small endcard matrix, so you can test the right-ending-on-right-cut workflow before you pay.
FAQ
Is this the same as changing my YouTube end screen?
No. This covers the endcard or outro segment that's baked into your edit and rendered into the video file, meaning the clip on your Resolve timeline. YouTube end screens are an overlay you add in YouTube Studio after upload (TubeBuddy territory). If you want different outro footage inside different cuts of the same video, that happens in your edit, which is what this guide and Recutly handle.
Why can't I just queue multiple render jobs in Resolve's Deliver page?
Because Resolve renders the current state of the timeline for every queued job, not the state it was in when you queued it. Larry Jordan confirmed this: queue three versions, batch render, and all three come out identical to whatever the timeline looks like now. Unlike Final Cut Pro, Resolve doesn't snapshot a temp copy per job. You need a separate timeline per variation.
What's the compound-clip gotcha when duplicating timelines?
A duplicated timeline references the same compound or nested clip as the original. If your endcard or any element lives inside a compound clip and you edit it in one timeline, it can change in the others too. To fully decouple, copy all the clips into a fresh blank timeline instead of duplicating, so each version is independent.
Does Recutly render my final video?
No. Recutly outputs DaVinci Resolve timeline files (FCP7 XML), not rendered video, and your footage never leaves your machine since only the timeline is uploaded. You re-import each XML into Resolve, the media relinks by filename, and you render with your own settings. Make sure the XML frame rate matches your project, since a mismatch causes import failures.
How much does Recutly cost?
Recutly is free for up to 5 versions per export. Pro is $19/mo for unlimited versions, and Studio is $39/mo. The free tier is enough to test the endcard-swap matrix on a small batch before you commit. See recutly.com/pricing for current details.
