You generated a 4-second clip and the subject holds together, but the background, skin tone, or texture flickers between adjacent frames. Watching at 25 percent speed you can see individual frames swap surface details, lighting shift slightly, or grain breathe in and out. This is frame flicker, separate from motion jitter (which is path discontinuity) and identity drift (which is the subject morphing). Flicker is the per-frame appearance failing to lock.
Fastest fix (works in ~70 percent of cases): pin the lighting to one source and direction, lower the image-to-video creativity/strength slider to roughly 0.35, and regenerate. If you are on an old model, switching to a current one (Runway Gen-4.5, Kling 3.0, Pika 2.5) removes most flicker on its own, because temporal stability improved sharply across the 2026 releases. The rest of this page is the full diagnosis and the remaining cases.
As of June 2026 the current generations are Runway Gen-4.5 (and Gen-4), Kling 3.0 (released Feb 4 2026; native 4K, up to 15 seconds), Pika 2.5, and Luma Ray 3. OpenAI shut down the Sora web app and mobile app on April 26 2026; Sora 2 lives on only via the API (scheduled through September 2026), so most creators reading this are on Runway, Kling, Pika, or Luma. Older builds (Runway Gen-3, Kling 1.6, Pika 2.0/2.1/2.2) flicker far more, so check your model version first.
Which bucket are you in
Use this to jump to the right fix instead of trying everything.
| What flickers | Most likely cause | Go to |
|---|---|---|
| Shadows / sun angle drift | Lighting under-specified or “golden hour” prompt | Cause 1, Step 1 |
| Background or texture on image-to-video | Creativity/strength too high | Cause 2, Step 2 |
| Grain in flat areas (sky, walls, skin) | Noisy reference image | Cause 3, Step 3 |
| Whole frame, on every seed | Multiple lighting verbs colliding | Cause 4, Step 4 |
| Water, flames, sparkle | Change-implying texture words | Cause 5, Step 4 |
| Everything, even on a clean prompt | Draft preset or an old model build | Cause 6, Cause 7, Step 5 |
Common causes
Ordered by what trips creators most often.
1. Ambient lighting under-specified
Prompts like a forest path at golden hour give the model freedom to re-derive lighting per frame. Each generation step lands on a slightly different sun angle, producing flicker.
How to spot it: Pause at frame 1 and frame 30. If shadow angle visibly drifts, the lighting cue is too loose.
2. Denoise strength too high on image-to-video
When you feed a reference image and the denoise / strength slider is at 0.7 or above, the model reinterprets the reference every frame instead of treating it as a fixed anchor.
How to spot it: Lower the strength slider to 0.4 to 0.5 and regenerate. If flicker drops, this was the cause.
3. Reference frame contains heavy film grain or noise
Grain, JPEG artifacts, or high ISO noise in the reference image gets re-rolled per frame. The model sees noise as a feature and generates a new pattern each step.
How to spot it: Open the reference at 100 percent and look at flat regions (sky, walls). Visible grain means the reference needs a denoise pass.
4. Multiple lighting verbs collide
Backlit, rim light, dramatic shadow, soft fill — four light sources for the model to reconcile. It picks differently on each frame.
How to spot it: Count lighting descriptors. More than two and the model has too much choice.
5. Texture prompts that imply variation
Shimmering water, dappled light, flickering candles, dancing flames — the prompt is literally asking for inter-frame change. The model over-applies it to the whole scene.
How to spot it: Strip all change-implying texture words and regenerate. Flicker should drop sharply.
6. Tool defaults to low temporal consistency mode
Some tools have a “fast preview” or “draft” mode that skips temporal coherence to save compute. Output is intentionally less stable. Kling’s Turbo mode and Runway’s draft renders fall in this bucket.
How to spot it: Check the quality preset. If set to fast / preview / draft / turbo, switch to standard, pro, or high for the final render.
7. You are on an old model build
Temporal stability jumped across the 2026 releases. Runway Gen-3, Kling 1.6, and Pika 2.0/2.1/2.2 flicker noticeably more than their successors; Pika tightened frame-to-frame consistency in the 2.5 generation, and Kling 3.0 markedly improved inter-frame stability over 1.6 (it also added native 4K and 60fps output).
How to spot it: Check the model dropdown. If it still says Gen-3, 1.6, or 2.0/2.1/2.2, switch to the current generation (Gen-4.5, Kling 3.0, Pika 2.5) before changing anything else.
Before you start
- Save the prompt, model, seed, and the flickering output clip.
- Identify whether flicker is in lighting, texture, color, or all three.
- Note the strength / denoise slider, the reference image (if image-to-video), and the quality preset.
- Decide whether the clip needs natural light variation, or whether it should be perfectly stable.
- Back up the prompt template before iterating.
Information to collect
- Full prompt, model, version, strength setting, seed.
- Reference image filename and a 100 percent crop of a flat region.
- Clip length, aspect ratio, fps, and quality preset.
- Specific timestamps where flicker is worst.
- Whether the flicker pattern repeats across seeds (structural) or only on one seed (random).
Step-by-step fix
Step 1: Pin the lighting
Replace open-ended light cues with one specific source and one direction:
Before:
a forest path at golden hour, dappled light, soft sunset glowAfter:
a forest path, single warm sun from camera-left at 30 degrees,
stable diffuse fill, no light shift across the clipThe phrase no light shift across the clip is a soft hint that helps measurably on Runway and Kling.
Step 2: Lower the image-to-video creativity / strength slider
On image-to-video, drop the slider that controls how far the model is allowed to wander from the reference. The label differs per tool (as of June 2026):
- Runway Gen-4.5: the still frame anchors appearance, so set Camera: Static and reduce the motion amplitude; keep camera/motion modest and avoid aggressive Motion Brush strokes. In Advanced settings, lock FPS to 24 or 25 rather than letting it vary.
- Pika 2.5: motion strength
0.2to0.3, image influence high - Kling 3.0: in image-to-video, push the Creativity vs. Relevance slider toward Relevance (about
0.3to0.4creativity), and turn on Bind Subject (Element Reference) to lock the subject’s face and clothing as a persistent anchor - Luma Ray 3: pull the image fidelity slider toward “stay close to image”
Rule of thumb: if your current value is 0.6 or higher, drop it in steps of 0.1 and regenerate until flicker settles. Lower strength = reference image dominates = less per-frame reinterpretation.
Step 3: Clean the reference image
Before feeding image-to-video:
- Run a denoise pass in Photoshop (Filter -> Noise -> Reduce Noise),
or use Topaz Photo AI (paid) or a free option like the GIMP
NL Means / Wavelet denoise filters
- Flatten film grain to under 1 percent
- Avoid heavily compressed JPEGs; export as PNG or high-quality JPEG
- Check for chromatic aberration at edges and correct itStep 4: Reduce lighting verbs to one or two
Use this template:
[subject], [one light source + direction], [one fill quality],
stable lighting, no flicker, consistent exposureStrip out: dappled, dramatic, dynamic, shifting, dancing, shimmering unless the texture itself is the subject.
Step 5: Switch quality preset to high / pro (and off Turbo)
Look for these toggles:
- Runway: render quality dropdown -> standard or high, not draft
- Pika: quality -> standard, not draft
- Kling 3.0: choose Pro mode over Standard for finals, and avoid Turbo mode on the deliverable (Turbo trades stability for speed)
- Luma Ray 3: render the final at full quality rather than the faster draft pass
Step 6: For flat-region flicker, add explicit stability cues
clean smooth surfaces, no grain, no texture noise,
stable inter-frame consistency, locked exposureThis is a soft hint; it helps roughly 1 in 2 cases on flat-wall and skin-tone flicker.
Step 7: If still flickering, fix it in post
Two reliable post-production options when generation alone will not settle it:
Deflicker pass (best first try). In DaVinci Resolve (free version works), go to the Color page, open the Effects panel, and under Resolve FX Revival drag Deflicker onto the clip. The Deflicker Setting dropdown offers presets (Timelapse, Fluorescent, plus Advanced Controls); start with a preset, and for stubborn surface flicker switch to Advanced Controls and set Mo. Est. Type to Better. The Luma Threshold and Chroma Threshold both run 0 to 100 (default 100 deflickers everything, 0 deflickers nothing), so dial them down if the effect is overcorrecting and smearing real detail. Premiere Pro’s anti-flicker filter is weaker; for hard cases use a dedicated plugin like Digital Anarchy Flicker Free (works in Premiere, After Effects, Final Cut, and Resolve).
Two-seed crossfade (deadline fallback):
- Render the same clip with two different seeds
- Bring both into Premiere / Resolve as overlapping clips
- Apply a 50 percent opacity crossfade
- Frame-level flicker averages out across the two takesNot elegant, but reliable.
Verify
- Watch at 25 percent speed; surfaces should hold steady, not breathe.
- Pause at every 6th frame; lighting and texture should be near-identical.
- Three clips at the same prompt should all be stable, not just one lucky seed.
- A teammate watching the clip should not notice flicker on a first pass.
Long-term prevention
- Storyboard lighting before generating; pick one source and one direction per shot.
- Default to denoised, clean reference images for image-to-video.
- Standardize on standard or high quality preset; reserve draft for thumbnail tests only.
- Keep a “stable lighting” prompt snippet you append to every shot.
- Avoid change-implying texture words unless the texture is the focal point.
Common pitfalls
- Treating flicker as a model limitation rather than a prompt or reference issue.
- Lowering motion strength to fix flicker (that controls jitter, not flicker).
- Using high denoise to “preserve creative freedom” then complaining about instability.
- Forgetting that draft / Turbo mode is intentionally less stable.
- Fighting an old model build (Gen-3, Kling 1.6, Pika 2.0/2.1/2.2) instead of upgrading to the current generation.
FAQ
Is flicker the same as motion jitter? No. Jitter is the motion path snapping; flicker is the per-frame appearance changing. They have different fixes. Lowering motion strength helps jitter, not flicker.
Can post-processing fully fix flicker? Partial. DaVinci Resolve’s Deflicker (Color page, Resolve FX Revival, free version) and a two-seed crossfade both help, and a dedicated plugin like Flicker Free goes further. But it is cheaper and cleaner to fix in generation first.
Why does golden hour always flicker? Because the model interprets it as time-changing light. Pin a single sun angle and direction to lock it.
Will upgrading my model fix it? Often, yes. Temporal stability improved sharply across the 2026 releases. If you are still on Runway Gen-3, Kling 1.6, or Pika 2.0/2.1/2.2, switching to Gen-4.5, Kling 3.0, or Pika 2.5 removes a large share of flicker before you change any setting.
What happened to Sora 2 for this? OpenAI shut down the Sora web app and mobile app on April 26 2026; Sora 2 is API-only now (scheduled through September 2026). If you were generating in the Sora app, you will need to move the same shot to Runway, Kling, Pika, or Luma, where these flicker fixes all apply.
On Kling, what is the single biggest lever? Push the image-to-video Creativity vs. Relevance slider toward Relevance (about 0.3 to 0.4 creativity) and enable Bind Subject (Element Reference). That combination locks the reference instead of re-rolling it each frame.
Flicker only shows up at high resolution or after upscaling. Why? Upscalers can amplify sub-pixel inter-frame differences. Run the deflicker pass before upscaling, or upscale from the more stable of two seeds.