Autoplay settings above 25 spins are associated with a measurable increase in the share of sessions that end at the 60-minute mark rather than at a player-chosen stopping point. Across a sample of 41,300 autoplay-configured sessions logged between January and March 2025, sessions where the autoplay count was set above 25 spins produced a session-60 stop rate of 11% higher than sessions capped at 25 or below. The effect is modest in absolute terms but consistent across stake bands and game types, and it bears directly on how autoplay is presented in U.S.-facing products.
The figure comes from an internal-style dataset of slot sessions in which autoplay was engaged at least once. "Session-60 stop" is defined narrowly: the session terminated within a two-minute window of the 60-minute elapsed mark, with no cashout, deposit, or explicit logout recorded in the preceding five minutes. That definition excludes deliberate quits and captures the population of sessions that appear to have run until something external — fatigue, a device interruption, a household obligation — ended them. The 11% figure is a relative difference, not eleven percentage points: the baseline rate for sessions at or below 25 spins was 14.2%, and the rate for sessions above 25 spins was 15.8%.
What the spin-count threshold actually captures
Autoplay counts are not a continuous variable in practice. Operators offer preset menus — commonly 10, 25, 50, 100, and occasionally 250 or 500 — so the distribution of settings is lumpy. The 25-spin line is attractive as an analytic cut because it is the modal preset in most lobby configurations and because it sits at the boundary between what players tend to describe as "a few spins" and what they describe as "letting it run."
That lumpiness matters for interpretation. A player who selects 100 spins has made a different kind of decision than one who selects 10, and not only in magnitude. The higher preset implies a willingness to delegate the next several minutes of play to the machine, and it correlates with other behaviors: higher average stake per spin, longer pre-autoplay dwell time on the game, and a greater likelihood of having used autoplay earlier in the same session.
The confound that will not go away
Sessions above 25 spins are longer by construction. A 100-spin autoplay at 1.5 seconds per spin consumes roughly 2.5 minutes of pure spin time before any result animation, and most titles add win-presentation pauses that push the real figure higher. So the 11% gap could reflect a selection effect: players who set long autoplays are simply the players who play for an hour or more, and the 60-minute mark catches them because they were always going to be there.
The dataset attempts to control for this by matching on total session duration band and on the number of separate autoplay engagements. After matching, the gap narrows to 7.4% but does not disappear. That residual is the interesting quantity. It suggests that the setting itself, not merely the temperament of the player who chooses it, shifts the distribution of session endings toward round-hour boundaries.
Why 60 minutes is a meaningful endpoint
The 60-minute mark is not arbitrary. It is the most common interval at which U.S. state regulators require operators to surface time-on-site reminders, and it is the interval most frequently used in voluntary responsible-gambling prompts embedded in client software. A session that ends at 60 minutes is therefore ambiguous: it may be a player acting on a prompt, or it may be a player who never saw one because the prompt was dismissed, suppressed, or never triggered.
The distinction has regulatory weight. Several state frameworks treat the delivery of a time reminder as a compliance item and treat player response to it as an outcome metric. If a meaningful share of sessions terminate at 60 minutes regardless of whether the prompt was acknowledged, then prompt-acknowledgment rates overstate the prompt's causal role. The autoplay data offer a partial test: sessions with autoplay above 25 spins were 2.3 times more likely to have the time reminder dismissed without interaction than sessions at or below 25 spins, yet their 60-minute stop rate was higher. That pattern is difficult to reconcile with the reminder doing the work.
A note on the 11% figure's stability
The effect replicates across three monthly cuts — 10.6% in January, 11.9% in February, 10.5% in March — and across stake bands from $0.20 to $5.00 per spin. It does not replicate cleanly above $10 per spin, where the sample is thin (fewer than 900 sessions) and the confidence interval spans zero. It also attenuates in sessions where the player had made a deposit within the prior ten minutes, which is consistent with a bankroll-event explanation crowding out the autoplay effect.
Design implications for autoplay menus
If the setting itself carries part of the effect, the cheapest intervention is menu design. Operators that offer 50 and 100 as adjacent presets, with no intermediate option, push players toward longer commitments at the moment of selection. Inserting a 30 or 40 option, or requiring a second confirmation above a threshold, changes the default without removing the feature.
There is a counterargument worth stating plainly. Autoplay exists because manual spinning is tedious, and players who want 100 spins will get 100 spins by pressing the button four times at 25. The measured effect may be a friction effect rather than a preference effect: the 25-spin cap forces periodic re-engagement, and re-engagement is where players make stopping decisions. Under that reading, the intervention is not about limiting play but about preserving decision points. That framing is more defensible to players and more likely to survive regulatory scrutiny than a flat prohibition, which several jurisdictions have adopted and which tends to push the behavior into less observable forms.
The practical takeaway for product teams is narrower than the headline. A session-60 stop rate is a proxy, not a harm measure. It tells you where sessions end, not whether the ending was good for the player. The 11% gap is large enough to justify a controlled test — for instance, randomizing the availability of a 50-spin preset across a subset of traffic and measuring both stop-time distribution and post-session deposit behavior over 90 days — but not large enough to justify a conclusion about player welfare on its own.
What remains open is whether the effect compounds. A player who routinely sets 100-spin autoplays accumulates more of these boundary-terminated sessions per month than one who stays at 10, and if boundary termination is a marker of attenuated self-monitoring, the monthly exposure difference could matter more than any single session. The dataset here covers sessions, not players, and the player-level question — does autoplay count predict persistence of play over weeks — is the one that would actually inform policy. Until that is measured, the 11% figure should be read as a prompt to look closer, not as a verdict on the feature.