Hit Stop: The Frame Trick That Makes Every Hit Land

Play Street Fighter and land a heavy punch. The moment of contact, everything stops. For a fraction of a second - two, maybe four frames - both characters freeze. Then the animation continues, the opponent staggers, the screen shakes. That freeze is hit stop, and it is one of the most powerful and least understood techniques in game feel design.

Hit stop goes by several names: hit freeze, hitstop, impact freeze. The technique is simple - briefly halt or near-halt animation at the exact moment of a significant impact. The effect is profound. Actions that would otherwise feel like they pass through enemies suddenly feel like they connect with real weight. Remove hit stop from any fighting game and the combat instantly feels hollow, floaty, and unsatisfying.

Why the Brain Responds to Freeze

Hit stop exploits a fundamental property of visual processing. When motion suddenly stops, the brain registers it as a significant event - a moment of consequence worth attending to. The brief pause creates a processing window: the player has time to register that something important happened, to see the particle burst, to hear the impact sound, and to associate all of these signals before the action resumes.

Without hit stop, fast action games suffer from what designers call the floaty hit problem. Attacks animate correctly and damage numbers appear, but the hit feels like the weapon passed through the enemy rather than connected with them. The brain never gets its processing moment - the action is over before the significance registers. Hit stop is the solution: it manufactures a moment of consequence where the game's speed would otherwise eliminate one.

There is also a second mechanism at work. A freeze implies something so powerful that it momentarily stopped time. It is a physical impossibility that the brain accepts as metaphor - this hit was so hard it stopped the world. Games like Sekiro and Hades use hit stop extensively precisely because their combat is built on the fantasy of powerful, precise strikes. Every parry in Sekiro produces a sharp hit stop that sells the clash of steel as genuinely bone-jarring.

Scaling Hit Stop to Impact Weight

Hit stop duration must scale with the significance of the impact. The relationship is roughly linear: more weight, more frames. A general scale that works across most action games:

Light hits and fast attacks: 2 to 4 frames. Enough to register without feeling like a pause. A jab, a quick slash, a light projectile hit. Medium hits and standard attacks: 5 to 8 frames. This is the sweet spot for most action game combat. Heavy hits, charged attacks, and parries: 8 to 12 frames. These are the impactful moments the player should notice and feel. Boss slams, finishing blows, and critical hits: 12 to 20 frames. Reserve the longest durations for the game's most significant moments. Beyond 20 frames starts to feel like a bug rather than a feature.

The slow factor matters too. True hit stop is a complete freeze - Time.timeScale set to zero. But a near-freeze (timeScale of 0.02 to 0.1) often works better because particles and effects can continue playing during the freeze, keeping the moment visually active rather than completely static. Experiment with what reads best for your game's style.

Implementation

The simplest implementation uses time scale manipulation. On impact, scale time down to near-zero for the freeze duration, then restore it. In Unity this looks like: set Time.timeScale to your slow factor, wait using WaitForSecondsRealtime (not WaitForSeconds, which is affected by timeScale), then restore Time.timeScale to 1. The key distinction is using real time for the wait, not scaled time, otherwise the freeze duration itself gets scaled.

A more sophisticated approach freezes only specific objects rather than global time. This is important in games with continuous action - freezing the attacker and target while the rest of the world continues creates a localised impact moment without stalling environmental animations, projectiles already in flight, or other combat. Implement this by caching and zeroing the velocity and animation speed of specific objects on hit, then restoring them after the freeze duration.

For multiplayer games, be careful with time scale manipulation. Global timeScale affects physics simulation and can cause synchronisation issues. Per-object animation speed control is safer in networked contexts.

Combining Hit Stop With Other Techniques

Hit stop reaches its full potential when layered with other simultaneous effects. The freeze creates a processing window - a moment when the player's attention is fully focused on the impact. Other feedback should fire into that window.

Hit stop plus screen shake creates a two-beat impact rhythm that is immediately satisfying. The freeze is the first beat - the connection moment. The shake is the second beat - the consequence moment. The freeze draws attention, the shake delivers the force. This combination is the backbone of satisfying combat in most modern action games.

Hit stop plus particle burst works because the freeze gives the player time to actually see the particles before they dissipate. Without hit stop, fast particles on a fast action are often missed entirely. The freeze ensures the visual confirmation is actually perceived.

Hit stop plus chromatic aberration or colour flash adds a visual exclamation mark to the freeze moment. A brief lens distortion or white flash at the exact frame the freeze begins reinforces the physical shock of the impact. This should last only as long as the hit stop itself - one to three frames of aberration is enough.

Crucially: the impact sound should play at the moment the freeze begins, not when it ends. The brain links the sound to the freeze as a single event. If the sound plays after the freeze resolves, it is perceived as delayed feedback, which undermines the connection between cause and effect.

Common Mistakes

Uniform hit stop for all impacts is the most common error. If every attack, regardless of weight, produces the same duration freeze, hit stop stops communicating weight and becomes noise. Players stop reading it as information. Reserve longer durations for your heaviest hits and keep light hits at two to three frames at most.

Hit stop on player-received damage needs separate tuning from hit stop on player-inflicted damage. Damage received hit stop should be shorter and more disorienting - the player should feel the impact without losing control for too long. Getting the balance wrong here makes the game feel punishing rather than responsive.

Missing the audio synchronisation is also common. Test your hit stop with the sound muted and with the sound on. The two-beat rhythm of freeze-then-shake should feel exactly aligned with the crack or thud of the impact sound. If they feel out of sync, adjust the audio timing to match the visual freeze rather than the other way around.

Hit Stop as Skill Expression

The best use of hit stop does not just make all hits feel good - it makes skilled hits feel exceptional. Games that scale hit stop duration with hit quality (a perfect parry gets more freeze than a regular block, a critical hit gets more freeze than a normal hit) are using hit stop as a skill expression system. The more precise the player's timing or aim, the more satisfying the feedback.

This is the philosophy behind Sekiro's parry system. A perfect deflect produces noticeably more hit stop than a guard, which produces more than a missed block. The game teaches players to seek the longest freeze because that is the signal that they executed perfectly. Hit stop becomes the game's core feedback loop for mastery, not just a generic polish layer.

That is the full potential of hit stop - not a post-production effect you add to make things feel better, but a core feedback mechanism that communicates the quality of the player's performance and rewards the pursuit of mastery. Two frames of freeze on a light jab. Twelve frames on a perfect parry. The difference between them is the distance between adequate game feel and something truly exceptional.