You generate a clip with Runway, Pika, or Kling. The subject in the foreground looks reasonable but the background does not sit still — foliage strobes between different shapes, neon signs change letters every few frames, distant figures pop in and out, brick walls warp. Background flicker is the most distracting class of AI video artifact and the hardest to ignore. Fixing it almost always comes down to simplifying the background, picking a single motion source, or switching to a model with stronger temporal stability.
Common causes
Ordered by what triggers flicker most often.
1. Background description too detailed
Crowded bustling night market with neon signs, steam, hanging lanterns, motorbikes, food stalls, crowds of people, rainy ground reflections — every one of those elements is independently regenerated each frame because the model has no temporal anchor. High-frequency elements (foliage, crowds, patterned walls) flicker first and worst.
How to spot it: Count distinct elements in your background description. Over 3 and you are in flicker territory.
2. Camera motion conflicts with subject motion
Your prompt says “tracking shot following a runner.” The model now has to maintain a coherent background that moves with the camera, while also moving the subject. With two motion sources active, the model often loses track of which background pixels go where and re-renders them inconsistently.
How to spot it: Pause on every 5th frame and watch background elements. If a building edge or tree branch is in different positions, the camera + subject motion are fighting.
3. Motion strength too high
Same root cause as drift: at high motion settings the model invents motion, and inventing motion in the background means inventing new pixels, which is flicker by another name.
4. Model struggles with high-frequency textures
Foliage, hair, fabric weave, brick patterns, crowd close-ups — these are areas of high-frequency information. Most current video models have weaker temporal coherence on high-frequency regions. Brick walls and tree leaves are the canonical examples of “areas that will always flicker.”
5. Aspect ratio mismatch with model training
Some models are trained primarily on 16:9 horizontal video. Asking for 9:16 vertical can degrade temporal coherence in less-trained regions. Pika in particular has shown this pattern with extreme aspect ratios.
6. Wrong tool for the scene
Runway, Pika, Kling, Sora each have different strengths. Some are stronger on static backgrounds with subject motion; others on moving cameras with locked subjects. Using the wrong tool for the scene type produces flicker.
7. Short clip with too much motion budget
Asking for major camera or scene changes in a 3-second clip forces too many spatial transitions, which compounds temporal incoherence.
Before you change anything
- Save the prompt, model, and the flickering output clip.
- Identify which background element is flickering worst (signs, foliage, crowd, walls).
- Decide whether the use case can crop or blur the flickering region.
- Note your aspect ratio and clip length.
- Commit or back up the prompt template before changing it.
Information to collect
- Full prompt, model name, version, motion settings.
- Clip length, aspect ratio, fps.
- A specific timestamp where flicker is most visible.
- Whether the same prompt with a simpler background still flickers.
Shortest path to fix
Step 1: Strip the background to one short noun phrase
Replace:
crowded bustling night market with neon signs, steam, hanging lanterns,
motorbikes, food stalls, crowds of people, rainy ground reflectionsWith:
soft out-of-focus city lights at night, blurred backgroundThe fewer high-frequency background elements, the less flicker. Add bokeh, blurred background, shallow depth of field to push the background out of focus — the model has to render less detail, so coherence improves.
Step 2: Pick exactly one motion source
If the camera moves, lock the background:
slow camera push-in, static background, no parallax movement,
background remains stillIf the background moves (rain, wind, smoke), lock the camera:
static camera, no pan, no zoom, gentle rain falling in backgroundNever have both moving in a 3-second clip. For 5+ seconds, even harder to maintain.
Step 3: Drop motion strength
Re-render at the lowest motion setting. If flicker drops dramatically, motion strength was contributing. Then dial up cautiously.
- Runway: Camera Motion
staticorslow - Pika: motion slider 0.3-0.5
- Kling:
subtlepreset - Sora: shortest tier
Step 4: Switch model
Different models have very different background-stability defaults. As of 2025-2026, rough strengths:
- Runway Gen-3 Alpha: strong on static backgrounds + subject motion
- Kling 1.6: strong on background coherence with moderate camera motion
- Pika 1.5: stronger on stylized backgrounds, weaker on photorealistic crowds
- Sora: strongest on simple scenes, struggles with crowds
If you are on Runway and the scene needs a moving crowd, try Kling. If you are on Pika and the scene needs photoreal brick or stone, try Runway.
Step 5: Switch to image-to-video with a still reference
Generate a still of the scene first (Midjourney, Imagen, Flux), then feed that PNG into the video tool as a reference image. The reference image gives the model a strong background anchor, which dramatically reduces flicker.
Step 6: Use background masking / motion brush
Runway Motion Brush and Kling reference lock allow you to paint which region should stay still and which should move. Paint the background as “no motion” and only the subject animates. Eliminates flicker in painted regions.
Step 7: Composite a static background
If the scene allows it, generate the background as a still image, then generate the subject on a green-screen-like simple background, and composite in post (Premiere, DaVinci Resolve). The background is then a JPEG that cannot flicker.
How to confirm the fix
- Watch the clip at 25% speed. Background elements should not visibly change shape or position frame-to-frame.
- Pause every 12 frames; the background should be nearly identical.
- Three clips at the same settings should all be stable, not just one lucky output.
- A viewer focused on the subject should not be distracted by background motion.
If it still fails
- Cut the clip to 2 seconds. Background flicker compounds over time; 2s shows the inherent stability ceiling of the model.
- Strip the prompt to subject + minimal background, regenerate. Add back one background element at a time until you find the trigger.
- Try a fundamentally different tool. Some scenes simply do not work in some models.
- For final delivery, composite static background + animated subject.
- Package the prompt, model, output, and flicker timestamp before asking community help.
Prevention
- Default backgrounds to simple, out-of-focus, or blurred when generating video.
- Always pick one motion source per clip (camera or subject), never both.
- Use image-to-video with a still reference for scenes that need a specific background.
- Keep clips at 3 seconds when background stability matters; concatenate for longer sequences.
- For brand or commercial use, composite static + animated rather than relying on single-pass video generation.