Flickering artifact during fast motion — caused by insufficient frame rate or inadequate motion blur. Kills smoothness in fast pans or whip moves at 24fps.
Strobing occurs when fast movements in the image appear jerky or flickering—as if the action is jumping between individual frames rather than flowing smoothly. The problem arises because too much time elapses between frames and there is insufficient motion blur to fill the gaps. At the standard 24fps of cinema, this is a classic pitfall: pans exceeding 100° per second, fast object movements, or camera crane movements can suddenly appear stroboscopic—especially if the shutter angles are too small.
The root cause lies in the shutter mechanism. At 24fps, you need approximately a 180° shutter angle (i.e., 1/48th of a second exposure per frame) to generate natural motion blur. If your shutter angle drops to 90° or less—because you need to expose faster or avoid high-frequency flicker—the movement loses its smoothness. This becomes particularly visible in digital work with high contrast (e.g., sunlight during fast pans, or quick cuts with a moving camera): the eyes perceive individual positions instead of a continuous motion sequence.
On set, you can fix this with several approaches: Increase the frame rate if possible (48fps or 60fps noticeably reduce strobing). Increase your shutter angles—the classic 180° is not a dogma but a minimum. Or slow down the movement itself: a slower camera move, a controlled pan instead of a jerky one—this is often more elegant than technical tinkering. In high-contrast settings (bright sunlight), the effect is amplified; check your ND filters to ensure you have enough exposure time.
In the edit, strobing is difficult to conceal. Motion blur in post-production looks artificial and costs sharpness. Therefore, think about it during the shoot. Strobing is particularly treacherous with VFX-heavy shots or green screen—the later composited movement (camera track, parallax) can then become terribly jerky. Modern high-frame-rate techniques (HFR) and 8K intermediate workflows are making this topic relevant again because more motion information is available, but more errors also become visible.