Mail Max

Your provider in email marketing

Slots autoplay stops at 25 spins, and 61% restart it manually

· 3 min read
Slots autoplay stops at 25 spins, and 61% restart it manually

A quirk in how autoplay is configured across a large share of online slots produces a predictable pattern: the session halts at 25 spins, and 61% of players immediately set it running again. That figure comes from aggregated play-log data covering roughly 4.2 million autoplay sessions across 180 titles in the twelve months to March 2025. The 25-spin cap isn't a player preference in most cases — it's the default the game ships with, and the restart is usually a single tap.

Why 25 spins became the invisible ceiling

Autoplay limits vary by jurisdiction and operator, but a cluster of defaults has settled around 25, 50, and 100 spins. The 25-spin option tends to sit at the top of the menu, which is enough to make it the most-selected setting even when players never consciously choose it.

The data backs that up. Among sessions that ended at the 25-spin mark, 61% were restarted within four seconds — a window too short for deliberation and consistent with muscle memory. When the cap was raised to 50 spins on a subset of titles, restart rates at the first stop fell to 44%, suggesting the limit itself, not the player's intent, drives the behaviour.

The four-second tell

Restart latency is the useful signal here. A player who genuinely wants to reassess after 25 spins typically takes longer — checking balance, adjusting stake, or leaving. Sub-four-second restarts cluster heavily on mobile, where the autoplay control sits close to the spin button.

What the restart pattern actually costs players

Each restart is a moment where the session could end. Most don't, but the friction isn't neutral: it's a repeated interruption to whatever rhythm the player had established. More importantly, it's a natural checkpoint that many players override without noticing.

  • Stake drift: In sessions with three or more manual restarts, average stake rose 18% between the first and last restart. Players topping up mid-flow tend to nudge bets upward.
  • Session length: Sessions with frequent restarts ran a median 41 minutes versus 27 minutes for uninterrupted autoplay runs of comparable total spins.
  • Losses at the checkpoint: Only 9% of players who restarted checked their net position first. The other 91% resumed without looking.

That last number matters more than the others. A forced pause every 25 spins is, in theory, a built-in responsible gambling feature. In practice, if nine in ten players tap straight through it, the feature is doing structural work that nobody is using.

Where the cap comes from, and why it varies

Regulators have taken different views. The UK Gambling Commission's rules on autoplay require that it stop on any loss limit, single win, or balance change defined by the player — but don't mandate a specific spin count. Malta and several EU markets allow operator-set limits. Some jurisdictions require autoplay to be disabled entirely, which is why the feature disappears on certain sites for certain players.

The result is a patchwork where the same title behaves differently depending on where you're playing and which licence the operator holds. A 25-spin default in one market might be 100 spins or no autoplay at all in another.

The open question

If the 25-spin stop is meant as a pause for thought, the 61% restart rate says it isn't functioning that way — it's functioning as a speed bump players have learned to ignore. The more interesting question is whether a longer default would help or hurt. Raising the cap to 50 spins cut restarts to 44% in the test group, but it also meant fewer forced interruptions per hour of play.

Operators and regulators both have reason to look at this. A checkpoint that 91% of players skip isn't protection; it's decoration. Whether the fix is a longer interval, a mandatory balance display at each stop, or something that actually interrupts the flow is unresolved — and the data so far suggests the current design mostly measures how fast people can tap "resume."