Rulebooks/Fruit Ninja
Rulebook 06 · Reaction slicer
How to play Fruit Ninja
Fruit falls up into the screen and you swipe a finger through it to cut it in half. That is the entire idea, and it has not needed changing since 2010. The complication is that bombs are thrown in among the fruit, and touching one ends the run in the standard mode. Everything else — combos, the special fruit, the mode you pick — sits on top of that one decision: swipe, or keep your finger still.
Corrected 7 August 2026: this page previously said a dropped fruit costs you time in the timed mode. It does not — only bombs do. Thanks to the reader who wrote in.
- Game type
- Reaction-based slicing arcade, single player
- One run
- Sixty seconds in the timed mode; open-ended in the survival mode
- Input
- Swipe a finger across the screen; direction and length both matter
- Attention
- Fully reactive — the screen does not wait for you
- Progress
- A score per run
What is on the screen
A plain background, a score in one corner, and nothing else until the first fruit arrives. Fruit is launched from below the bottom edge, arcs up through the screen, and falls back out. You have the time it spends on screen — usually a little under two seconds — to swipe through it.
Bombs look nothing like the fruit: black, round, with a lit fuse and a sound cue that starts before they are fully visible. That sound is the actual warning, and it is why the game is harder with the volume off. In the classic mode one bomb touched is the end of the run. In the timed mode a bomb costs you time rather than the run itself.
Playing a run from scratch
The first ten seconds are deliberately gentle: one or two fruit at a time, no bombs, on wide slow arcs. This is the game letting you find the swipe length that works on your screen size. Use it. A swipe that is too short misses; a swipe that crosses the whole display is slower to reverse.
After that, fruit arrives in groups, and the groups start including bombs. The instinct is to swipe wildly through everything, which is exactly how runs end. The better habit is short deliberate strokes with a pause between them — your finger off the glass is your only safe state.
Missed fruit is not free in the classic mode: three pieces dropped ends the run just as a bomb does. So there is a real tension between the two failure conditions, and the whole skill is reading which one you are closer to.
Controls
One finger, one gesture. A swipe cuts anything its path crosses, so a single stroke through three aligned pieces cuts all three and scores them as a combo. Some players use two fingers on larger screens, which the game allows and which roughly doubles both your reach and your chance of catching a bomb.
There is no tap, no hold, no menu during a run. Lifting your finger is a real action — it is how you avoid a bomb that has drifted into a piece of fruit you wanted.
What a session feels like
Short and repeatable. A timed run is a minute; a classic run is usually well under two. It is the kind of game people play three rounds of and put down, which is the pace it was designed for.
The mood is closer to a reflex test than a puzzle. There is no board to read and no plan to make. If you like games where you sit and think, this is the wrong one — the sister pages on this site about grid puzzles will suit you better.
Pointers for a first hour
- Play with sound on. The bomb fuse is audible before the bomb is clearly visible, and it is the single biggest difference between a short run and a long one.
- Short strokes, not long sweeps. A long sweep catches more fruit and far more bombs, and it leaves your finger on the glass when you need it off.
- Wait for the arc. Fruit is easiest to cut at the top of its flight, where it is nearly stationary. Swiping at it on the way up is the common beginner error.
- Take the timed mode first. Bombs cost seconds there rather than ending the run, so you learn to read them without being punished for it.
- Let a piece go. One dropped fruit is cheaper than one touched bomb, every time.
Quick Play Notes is a reference site. This page describes Fruit Ninja from our own play; the score it mentions is a display number inside the game. We have no commercial relationship with its publisher, and the title is named only to say which game this page explains.