|This move exists primarily or exclusively within the Sonic Boom continuity.|
Information in this article may not be canonical to the storyline of the games or any other Sonic continuity.
When performing the Spin Dash, Sonic normally crouches down and curls into a ball where he starts performing an oval-shaped charge by spinning around in one place. Once charged up, Sonic dashes forward and homes in on his targets with his spin attack. Alternatively, Sonic can skip the revving and launch straight into the spin attack. Because of its reliance on the spin attack though, the Spin Dash cannot be executed properly if the user's legs are injured.
Sonic Boom: Rise of Lyric
In Sonic Boom: Rise of Lyric, the Spin Dash is one of Sonic's character-exclusive moves. The move has multiple uses: it can be applied for battle to damage opponents or deal continuously damage Commando Husks, give brief dashes to get around faster, and be used in conjunction with gimmicks like the Spin Ramp and the Spin Ball.
To use the Spin Dash in gameplay, the player must hold to rev the Spin Dash and then release the button to launch Sonic. The longer the button is held, the further will Sonic travel with the move.
Sonic Boom: Shattered Crystal
In Sonic Boom: Shattered Crystal, the Spin Dash is a move exclusive to Sonic. To perform this move in gameplay, the player must hold to rev the Spin Dash and then release it to launch Sonic. In terms of utility, it can be used to break containers and charge through non-shielded enemies.
Sonic Boom: Fire & Ice
In Sonic Boom: Fire & Ice, the Spin Dash returned as one of Sonic's character-exclusive moves and its mechanics and effects are the same as in the previous games. Like in Sonic Boom: Shattered Crystal, to use the move in gameplay, the player must hold to rev the Spin Dash and then release it to launch Sonic. With this move, Sonic can move faster than when Sprinting.
- In Sonic Boom: Rise of Lyric, there is a glitch that allows Sonic to launch himself at seemingly absurd distances with the Spin Dash.
- However, this was fixed in the January 2015 patch.