You hit Extend on a Runway, Kling, or Pika clip to push duration from 5 seconds to 10. The first segment looks great. The extended segment drifts — colors shift cooler, the character’s face is subtly different, the lighting flattens, or the background loses its specific texture. This happens because most extension features condition only on the last frame of the prior clip, not on the full style trajectory. Fix it by feeding a reference clip back in for style lock, restarting as image-to-video from a clean intermediate frame, or generating both halves at full quality and crossfading in post.
Common causes
Ordered by hit rate.
1. Extension conditions only on the last frame
Runway Extend, Pika Extend, and Kling Extend all use the trailing frame as the seed for the new generation. If that frame is mid-motion blur, slightly washed out, or at a weird crop, the new segment amplifies whatever drift was already happening.
How to spot it: Pause the original clip at the final frame. If it looks like a “transition” frame rather than a clean keyframe, the extension is starting from a bad anchor.
2. Prompt was not reapplied to the extension call
You generated the first clip with a strong style prompt, then hit Extend with the prompt field empty or shortened. The model loses guidance and drifts toward its default aesthetic.
How to spot it: Compare the original prompt and the extension prompt side by side. If the extension is shorter or missing style anchors, that is the cause.
3. Character anchor lost across the cut
The first clip rendered a specific face / hairstyle / outfit. The extension regenerates the same character from scratch, with only one frame of guidance, and produces a slightly different person.
How to spot it: Freeze-frame at the cut. Compare facial structure, hair color, and clothing 1 frame before and 1 frame after. Drift here is character-anchor loss.
4. Tool tier downgraded between clip and extension
Some tools render the original at high quality and the extension at a faster preview tier by default. The model is technically different and produces different output.
How to spot it: Check whether the extension UI defaults to “Fast” or “Standard” while the original was “HQ”. Match them.
5. Reference image not carried forward
You did image-to-video for clip 1 using a reference. For the extension, the reference is dropped — the tool only has the last video frame.
How to spot it: Look at the extension dialog. If there is no reference-image slot or it is empty, the style anchor from clip 1 is gone.
Shortest path to fix
Step 1: Re-paste the original prompt before extending
Sounds basic, but easy to skip:
# Both clip 1 and extension should have:
- Identical subject description
- Identical style and color cues (cinematic teal, golden hour, etc.)
- Identical camera language (locked tripod, slow push, etc.)
- A "consistent with prior shot" hint at the end
Example:
"Same woman in red coat from prior clip, identical lighting and color grade,
golden hour, locked tripod, walking forward, continuous motion from previous frame."Step 2: Use a reference clip or reference image for style lock
# Runway Gen-3 Alpha
- In Extend dialog, attach the original clip as Reference Video
- Strength: 0.7
- This conditions style + character + color
# Kling 1.6
- Use "Reference" mode with the original clip's first frame as reference image
- Strength: 0.8
- Keep character identity
# Pika 2.0
- Use Pikaframes with start = last frame of clip 1, end = a chosen target frame
- This gives both endpoints, much more stable than open-ended extendStep 3: Restart as image-to-video from a clean intermediate frame
If extension keeps drifting, abandon it. Pick a clean frame from clip 1, export it as a still, and use it as the start image for a brand-new image-to-video generation:
# Pick the cleanest frame near the end of clip 1
- Avoid motion blur frames
- Avoid frames mid-blink or mid-gesture
- Export as PNG at full resolution
# New image-to-video generation
- Use that PNG as start frame
- Reapply the full original prompt
- Generate 4-5 seconds
- Stitch to clip 1 with a 4-frame crossfade in editorStep 4: Match render tier for both clips
# Runway
- Both clips at Gen-3 Alpha Turbo OR both at Gen-3 Alpha (not mixed)
- Both at 1280x768 HQ
# Pika
- Both at 1080p
- Both at the same Motion preset
# Kling
- Both at Standard mode or both at Pro mode, not mixed
- Same duration settingStep 5: Crossfade in post to mask any residual drift
Even with everything matched, a 4-8 frame crossfade across the cut hides micro-shifts:
# Premiere Pro
- Place clip 1 on V1, clip 2 on V2 with 4-frame overlap
- Apply Cross Dissolve at the overlap
- Duration: 8 frames at 24 fps
# DaVinci Resolve
- Same approach, use Cross Dissolve transition
- Or Smooth Cut for character-anchor drift
# CapCut
- Drag transition: Dissolve, 0.3s
- Renders the cut nearly invisiblePrevention
- Always re-paste the full original prompt into the extension dialog.
- Generate extensions with reference clip / reference image style lock enabled.
- Prefer Pikaframes-style start+end conditioning over open-ended extend when available.
- Pick clean end-frames for clip 1 (no motion blur, no half-blinks) to give the extension a good anchor.
- Budget a 0.3s crossfade at every clip seam in your edit.