Frame data is a way of describing exactly when a move starts working, how long it can hit, and how long the character is committed afterward. The three numbers beginners usually meet first are startup, active and recovery. They look like spreadsheet territory, but the useful question is much simpler: who gets to act first after an interaction?
You do not need to memorise an entire character table to get value from frame data. A small amount of it can explain why one button keeps interrupting another, why a blocked attack feels risky, and why some punish attempts arrive too late. Capcom's own Street Fighter teaching material breaks attacks into startup, active and recovery phases, while modern training modes such as Street Fighter 6 expose frame information so players can examine those timings directly.
Startup, active and recovery describe one attack
Startup is the period before an attack can connect. A move with shorter startup becomes threatening sooner than a slower one, although range, hitbox position and the situation still matter. That is why a fast jab can be useful at close range without automatically being the best answer everywhere on screen.
Active frames are the part of the move during which its hit can actually connect. A move can stay active for more than one frame, which matters when an opponent is moving into it or when an attack is timed to meet a wake-up or landing situation. More active time does not automatically make a move better; the rest of the move still has to be considered.
Recovery is the commitment after the active portion ends. During recovery, the attacker normally cannot immediately start another action. Long recovery is one reason a powerful-looking swing can be dangerous when it misses. Thinking in those three phases turns a vague feeling of “that move is slow” into something more useful: slow before the hit, active for a long time, slow afterward, or some combination of the three.
Plus and minus tell you who recovers first
Frame advantage compares when the two characters are able to act after a hit or block. If an attacker is plus, the attacker can act before the defender. If the attacker is minus, the defender recovers first. The size of that advantage or disadvantage helps explain whether continuing to attack is plausible or whether it is time to defend.
That does not mean every minus move is automatically punishable. Distance can push the players apart. A defender's fastest relevant attack may not reach. Some moves can be cancelled into another action, while game-specific mechanics can change what options are available. Frame data describes timing; it does not erase spacing, character matchups or system rules.
This is also why “safe” is contextual. A move that leaves the attacker slightly behind may still recover soon enough that the defender cannot land a guaranteed response. A much more negative move at close range can give the defender a clear punish. The numbers help identify the window, but the actual answer still has to work in that game and at that distance.
Use frame data to answer one problem at a time
The most practical approach is to start with a situation that is already bothering you. If an opponent keeps interrupting after you block a particular move, look at who is plus or minus. If your punish never lands, compare the available window with the startup and range of the button you are using. If a big attack keeps getting whiff-punished, look at its recovery and then recreate the miss in training mode.
Street Fighter 6 is a useful example because its training tools include frame data, timing displays and programmable practice situations. The broader lesson carries across fighting games that expose similar information: use the data to test a specific question instead of trying to memorise every number before playing.
Frame data is not a secret layer reserved for tournament players. It is just a precise language for timing. Learn startup, active frames, recovery and advantage first, then add character-specific details only when they solve a real problem you have identified.
Reporting notes