← All guides Home

Fruit Merge Box Tips: Merge Values, the Red Line and a Clean Stack

Updated October 2026

In Fruit Merge Box you drop fruit into a box, and two fruits of the same kind that touch fuse into the next size up. It looks like a game about chasing the biggest fruit, but the scoring and the overflow rule tell a different story: most of your points come from a steady stream of small merges, and runs end because of one awkward lump sitting high in the box for a second and a half. This guide walks through how a drop works, what each merge pays, the precise overflow rule, and a way of building the pile that keeps every fruit within reach of its partner.

How a drop actually works

Put your finger on the box and a faded copy of the fruit you are holding appears at the top, with a dotted guide line running straight down from it. Slide sideways to move it, then lift your finger to let it fall. The fruit falls from the exact column where you let go, except that it is pushed in from the walls so it never starts overlapping them. Nothing happens on a press alone; the release is the drop.

After each drop there is a short lockout of 0.4 seconds. During that time the faded preview is hidden, and a release does nothing at all, so a quick double tap wastes the second tap rather than dropping two fruits. The simple habit is: wait until you can see the ghost fruit under your finger, then let go.

The small box in the score bar labelled Next is easy to misread. It does not show the fruit in your hand; the one in your hand is the faded fruit under your finger. Next shows the fruit that comes after it. That gives you two fruits of planning at all times, which matters when you are deciding whether to spend the current drop on a merge or to set up a spot for what follows.

New fruits are always one of the five smallest kinds. In the game code the odds are 40% for the smallest, 30% for the second, 18% for the third, 9% for the fourth and 3% for the fifth. The two smallest sizes make up seven drops in ten, so a plan that relies on a big drop arriving soon is usually a bad plan.

What each merge is worth

A merge pays the square of the new fruit's rank, where the second smallest fruit has rank 2 and the largest has rank 11. In order of size the payouts are:

The striking part is what this means over a whole run. Work out the arithmetic of growing a single watermelon purely from the smallest fruit and it takes 512 cherry merges, 256 strawberry merges, and so on up to one watermelon merge. The total comes to 11,093 points, and the very last merge, the watermelon itself, contributes only 121 of them. The cherry, strawberry and kiwi layers together are worth 6,400. In other words, the score is mostly a measure of how much fruit you process, not of how spectacular the top of the chain looks.

That changes priorities. A run that keeps merging cleanly for a long time beats a run that builds one large fruit quickly and then chokes. Every small pair you leave unmerged is not just clutter; it is points you have not collected yet and space you are not getting back.

The red line, exactly

The dashed red line near the top is drawn at a fixed height: the diameter of the largest fruit you can be given, plus 18 pixels of margin. The game ends when some fruit has its top edge above that line for more than 1.5 seconds without a break. Two kinds of fruit are ignored while it checks: a fruit dropped in the last 0.35 seconds, and any fruit moving faster than a modest speed (80 pixels per second in the code). So a fruit that pokes over the line while it is still bouncing or rolling does not count; one that settles there does.

The countdown also resets the moment nothing is resting above the line. If a merge pulls the stack down, or a fruit rolls off the peak, the 1.5 seconds start again from zero next time. The line itself is your warning light: it is faint while the box is safe and grows stronger the longer something sits above it. When it starts to darken, you have well under two seconds and roughly three drops of time to fix the peak, given the 0.4 second lockout.

The useful response is usually not to drop more fruit onto the peak. Look for a matching fruit lower down next to the offending one, or drop a fruit that will merge with a neighbour of the high fruit so the whole pile sinks. A merge replaces two fruits with one larger fruit at their midpoint, and the larger fruit takes up less area than the pair, so merges are your main tool for lowering the stack.

Building a stack you can keep merging

The physics are soft and heavy. Fruit barely bounces (the bounce factor in the code is 0.18), so a fruit lands roughly where you aimed and then rolls into the nearest gap. On the floor it also slides a little before friction stops it. That makes the box predictable enough to build a deliberate shape rather than throwing fruit at it.

The shape that works best is a size gradient across the box: big fruit settled along one wall and the floor near it, getting smaller as you move away. The small, frequent fruits then live on the open side of the box, where new drops can reach them directly. When a medium merge happens on that side, the result is already heading toward the larger fruit of the same size near the wall.

Chain reactions and where the new fruit lands

A merged fruit appears exactly halfway between the two fruits that formed it, carrying their averaged motion, and it is instantly larger than either of them. The extra size pushes its neighbours aside, which is what makes cascades happen: the new fruit can be shoved into contact with another fruit of its own size, and that pair fuses a moment later.

Each fruit can take part in only one merge per frame, so a cascade unfolds as a quick sequence rather than all at once. That is worth knowing because the stack is shifting during a cascade. Wait for it to finish before you aim the next drop; a fruit aimed at a gap that is about to close lands somewhere you did not intend.

The midpoint rule also tells you where big fruit will end up. If you merge two fruits that sit on opposite sides of a gap, the result grows into the middle of that gap. Merging along the floor keeps big fruit low; merging two fruits that are stacked vertically produces a fruit higher up, which is exactly how the peak creeps toward the red line late in a run.

Screen size and fairness

The box is the same on every device: a fixed frame 360 units wide and 640 tall, scaled as a whole to fit your screen. Every phone therefore holds exactly the same number of fruit, and the red line sits at the same depth measured in fruit. On a tall phone the frame leaves a little empty space above it; on a short or wide screen it leaves narrow margins at the sides. Scores from different phones are directly comparable.

Rotating the phone or resizing the window in the middle of a run does no harm. The frame and every fruit in it scale together, so nothing changes size relative to anything else and the pile stays exactly as it was.

A routine for longer runs

  1. Wait for the faded preview before releasing; never double tap.
  2. Check the Next box, then choose the spot for the fruit in your hand.
  3. Collect small merges constantly. They make up most of the score.
  4. Keep large fruit along one wall and small fruit on the open side.
  5. When the red line darkens, stop building upward and look for a merge that lowers the peak.
  6. Let each cascade finish before aiming again.

Your best score is kept on your device, and any score above zero can be saved to the Hall of Fame from the game-over card. There is no time limit, so take a breath before each drop; the patient player who keeps the box tidy almost always outscores the one hunting for the largest fruit.

▶ Play Fruit Merge Box Drop, merge and keep the box below the red line.