The round in one paragraph
A crash round starts at 1.00x and climbs until it stops. A bet taken before the stop is multiplied by the current value; a bet still in play when the round ends is lost in full. In most implementations the stopping point is fixed before the round begins, not chosen while the curve is rising.
Auto-cashout is a field where you enter a target multiplier. The bet closes by itself the moment that value is reached. The manual button usually stays active alongside it, so you can leave earlier than your target but never later.
The problems it actually solves
It removes reaction speed and connection quality from the equation. The target is locked in before the round, so the outcome no longer depends on whether you hit the button in time.
- Discipline. The exit is decided before the round, not while a number is climbing in front of you.
- Consistency. A hundred rounds follow one rule instead of your mood.
- Record keeping. You can see where every bet in a session closed.
Auto-cashout is not the same thing as auto-bet. One controls the exit, the other keeps sending new stakes into the game without you. Switched on together they turn play into a background process, and that is where people lose track of what they have spent.
What it cannot do
It does not change the maths
In the usual model the chance of surviving to multiplier x is roughly the RTP divided by x. Take 96% as a worked example: 2.00x arrives about 48% of the time and 10.00x about 9.6% of the time. Expected return is the same at every target, because the payout grows exactly as fast as the probability shrinks.
What changes is the shape of the results, not their average. A low target produces frequent small wins punctuated by costly losses; a high target produces long dry stretches decided by a handful of hits.
| Target | Hit rate in the 96% example | What a session feels like |
|---|---|---|
| 1.20x | about 80% | wins most rounds, but one loss undoes five wins |
| 2.00x | about 48% | roughly an even trade, runs of 5-7 misses are normal |
| 5.00x | about 19% | long empty stretches between payouts |
| 10.00x | about 9.6% | the whole session rests on isolated hits |
Those numbers illustrate the model rather than any particular title. Crash games in the catalogue come from different studios, so the declared RTP has to be read in the rules of the game you actually opened.
It does not protect against an instant crash
A round can end at 1.00x, before any auto-cashout can fire. Setting 1.01x does not create a near-certain payout: the share of instant crashes is precisely where the house edge lives.
It does not turn automation into a system
Doubling after every loss at a 2.00x target looks stable until the first long run of misses, and there is always a ceiling above you in the maximum stake and in your own bankroll. Automation improves nothing here; it only removes the pause where you might have stopped.
Auto-cashout while wagering a bonus
Bonus funds come with their own limits: 40x wagering, a seven-day window and a maximum stake of 5 USD per round. An auto-bet sequence with a rising stake will break the per-round cap quickly, so a flat stake is the simpler way to run it. The full terms are on the bonus page.
Before you start a session
- The rules of the specific title, since auto-cashout is not offered everywhere and is implemented differently.
- The stake range, and the payout cap where the rules state one.
- How results can be verified. In Tonza Originals a round is recomputed by hand from the server seed, your client seed and the nonce, as described under provably fair; provider crash titles use their own mechanisms.
Crash titles on Tonza sit in their own section. Treat auto-cashout as an execution tool rather than a strategy: it carries out a decision you already made, but it never makes that decision for you.
