In fighting-game terminology, a hitbox marks where an attack can connect; a hurtbox marks where a target can be hit. That distinction explains a surprising amount of the âhow did that miss?â conversation. Other genres sometimes use âhitboxâ for the targetâs collision region too, so the vocabulary is not universal. This guide uses the attack-versus-target distinction, then looks at the rules surrounding the invisible geometry.
Table of Contents
- What Is a Hitbox?
- What Is a Hurtbox?
- Hitbox vs Hurtbox: The Core Difference
- Other Boxes You Need to Know: Pushbox, Throwbox, Blockbox
- Why Fighting Games Live and Die by Hitboxes
- Hitboxes in 3D Games: From Souls to Shooters
- Disjointed Hitboxes and Why They Feel Unfair
- How Designers Tune Hitboxes Frame by Frame
- FAQ
What Is a Hitbox?
A hitbox is a region used to test an attackâs contact with a target. Overlap can register a candidate hit, but it does not automatically mean damage: blocking, invulnerability, team rules, and other conditions can change the outcome. Rivals of Aetherâs developer documentation shows how many properties can accompany a hitbox beyond its dimensions.
Simple shapes such as rectangles, spheres, or capsules are convenient for collision tests, though games can use other shapes and methods. Engines also filter which objects should be tested rather than necessarily comparing every pair. Godotâs Area2D documentation offers one example of overlap detection with collision layers and masks. Update rates and implementation details vary.
An attack hitbox is often enabled only during the moveâs active period. Imagine a move with a windup, a brief contact window, and recovery afterward. Those phases affect when it can connect and when the character can act again. Exact frame-counting conventions vary, so do not assume a made-up numerical example is frame data for a real Street Fighter move.
What Is a Hurtbox?
A hurtbox is the invisible region attached to a character that, when touched by an enemy hitbox, takes damage. It is the defensive box. The body that can be hit. The head, the torso, the limbs that count as “you” for the purpose of receiving pain.
Hurtboxes usually wrap around the character’s vulnerable silhouette. A standing fighting game character has a tall hurtbox covering the body. A crouching character has a shorter, wider one. When that character ducks under a high punch, the hurtbox shrinks below the line of the incoming hitbox, and the punch sails over their head. No collision, no hit.
Changing a hurtboxâs shape or position can let a low-profile move evade an attack. Some games also use attack-height classifications and invulnerability flags, so not every ducking interaction can be explained by geometry alone. The animation is a clue to the rules, not their complete specification.
Hitbox vs Hurtbox: The Core Difference
The hitbox describes the attack region; the hurtbox describes the vulnerable region. An overlap is part of resolving a hit, alongside rules about which targets are eligible and what state they are in. The boxes start the conversation. The game still gets a vote.
Three consequences fall out of this:
- You can have a hitbox without a hurtbox. Projectiles often do this. A bullet has a hitbox but no hurtbox of its own, because the bullet cannot be damaged. A projectile can also be made destructible or parryable through additional collision rules; the exact implementation depends on the game.
- You can have a hurtbox without an active hitbox. A character standing still has a hurtbox but nothing offensive going on. They can be hit but cannot hit.
- Hitboxes and hurtboxes on the same character can be in totally different places. This is where things get interesting, and where the next sections live.
Other Boxes You Need to Know
Hitbox and hurtbox are the famous pair, but most games have a small zoo of invisible boxes doing different jobs.
Pushbox
The pushbox is what keeps two characters from occupying the same space. It is collision against other characters, not against attacks. When you walk into your opponent in a fighting game and they slide back instead of phasing through you, that is two pushboxes refusing to overlap.
Throwbox or Grabbox
Throws commonly have distinct eligibility checks, such as range, target state, and throw invulnerability. A game may use dedicated regions for these checks. Names such as throwbox and grabbox vary, and the reason an ordinary guard does not stop a throw is a gameplay ruleânot a magical property of a differently named rectangle.
Blockbox
Some games use a proximity region to trigger a guarding animation when an attack approaches. That need not be a shield-like volume intercepting a hitbox before it reaches the body. High and low guarding can be handled through attack classifications and character state. Check the particular game before giving every invisible rectangle the same job.
Why Fighting Games Live and Die by Hitboxes
Fighting games are the genre where players openly discuss hitbox vs hurtbox interactions in casual conversation. Watch any top player talk about Street Fighter, Tekken, Guilty Gear, or Mortal Kombat for five minutes and you will hear the words “disjoint”, “active frames”, “shrinks the hurtbox”, “the hitbox is huge”. They are reading the invisible geometry in real time.
Frame data describes timing, but it does not fully describe the shapes or all the rules. Startup tells you how soon a move becomes active under that gameâs counting convention. Safety on block also depends on recovery, the opponentâs available punish, range, and the situation. A fast jab need not always mean three frames, and a negative move need not be punishable at every distance.
At a 60-Hz simulation rate, two frames are about 33 milliseconds. That is enough to change a tight interaction, but it is not âhalf the reaction-time floorâ for a trained player. Many close exchanges involve anticipation, committed inputs, and known timing rather than reacting from scratch to every frame. A small number can still make a large balance difference.
Hitboxes in 3D Games: From Souls to Shooters
Three-dimensional games may use several collision regions around a character. A shooter can distinguish a head from a torso when applying damage, but it need not simulate every bullet as a moving hitbox. Hitscan weapons can use ray tests instead. Valveâs explanation of lag compensation describes evaluating shots against past player positions, another reason a screenshot alone may not explain a networked hit.
In Soulslike games, attack timing and visible contact are important to how combat feels. A delayed swing may involve a long windup rather than a hitbox lingering after the attack. Whether an apparent mismatch is deliberate, a bug, or a misunderstanding needs evidence from that move; the genre label does not settle it.
During invincibility frames, eligible attacks do not damage the player. A developer can implement this with state checks, collision changes, or other logic. The hurtbox does not have to be moved out of the world. Rivals of Aetherâs attack documentation exposes invincibility settings as part of its own system; other games organize the behavior differently.
Disjointed Hitboxes and Why They Feel Unfair
A disjointed hitbox is one that exists in a place where the character’s hurtbox does not. The classic example is a sword swing. The blade has a hitbox at the tip. The character holding the sword has a hurtbox around the body. If the opponent attacks the blade itself, there is no hurtbox there to hit. The sword swing wins, the opposing attack hits nothing, and the player on the receiving end yells at their screen.
A sword attack illustrates the idea: the attacking region can extend beyond the wielderâs vulnerable body. A punch may expose a limb along its reach, but not every unarmed move is fully vulnerable, and not every sword move wins an exchange. Timing, spacing, clashes, and recovery remain part of the result.
Disjointed reach can be a deliberate design tool, balanced through timing, recovery, damage, or other limitations. It does not guarantee safety. Reaching farther than the opponent can hit you during one moment is different from being untouchable throughout the entire move.
How Designers Tune Hitboxes Frame by Frame
Hitbox and hurtbox tuning is one of the most thankless jobs in game development. The work is invisible by definition. When it is right, players say the game “feels good”. When it is wrong, they say the game “feels off” and cannot explain why.
The basic workflow looks like this. The animator delivers an attack animation. The combat designer opens an editor that shows the model with collision boxes drawn on top. They scrub through the animation frame by frame, drawing or adjusting hitboxes to follow the weapon, the fist, the foot. They mark the active frames. They tweak the hurtbox to follow the body’s actual silhouette during the move, shrinking it during dodges, extending it during awkward poses where the character leans out.
Playtesting then asks whether the geometry and timing produce the intended interactions. A confusing hit might need a collision change, an animation change, or a different rule. The goal is not always the smallest possible box: readable feedback and consistent behavior matter as well. A developer may test situations repeatedly without every project following an identical ritual.
For a concrete example, Capcomâs December 2018 Street Fighter V adjustments include changes to hurtboxes and hitboxes, including matching an attack more closely to its visuals. That is the invisible geometry appearing in public patch notes. No need to invent how many hours a designer spent on one pixel.
Related reading on the topology of hidden game systems: how procedural generation builds worlds you never see twice, how cartridge saves stored your progress before cloud existed, and how speedrunners investigate game rules and glitches.
FAQ
Is a hitbox always a rectangle?
No. 2D games often use rectangles because they are computationally cheap and easy to author. 3D games use spheres, capsules, or compound shapes built from multiple primitives. Some modern engines support arbitrary convex polygons. The principle is the same regardless of shape: it is a region the engine tests for overlap.
Can you see hitboxes in normal gameplay?
Usually no. They are debug tools, not gameplay elements. Some fighting games include a “training mode” toggle to show hitboxes for learning purposes. Modders and tournament broadcasters sometimes overlay them too. In normal play, players read hitboxes through animation, hit sparks, and frame data, not by seeing the boxes directly.
What is the difference between a hitbox and a hurtbox in one sentence?
The hitbox is the part of your attack that can damage someone. The hurtbox is the part of your body that can be damaged.
Why do some games have “bad hitboxes”?
âBad hitboxesâ can mean a mismatch between visible action and collision, but it may also describe timing, invulnerability, or network behavior the player has not accounted for. Examine the actual interaction before assigning blame to the box. Sometimes the complaint is correct. Sometimes the replay needs another look.
Do hitboxes exist in non-combat games?
Non-combat games also use collision regions, triggers, ray tests, or other interaction methods. A pressure plate can detect overlap, for example. Those regions need not be called combat hitboxes, and not every interaction requires a volume overlap.
Conclusion
Hitboxes and hurtboxes make the hidden structure of combat easier to discuss. Geometry matters, but timing, state, and game-specific rules decide what the contact means. Once you know what to look for, a baffling miss becomes something you can investigate instead of merely accusing the television of conspiracy.
đž Curiosity looks good on you. Explore the Goodies, or find our illustrated books on Amazon.
