Fruit Merge: All 11 Fruits Evolution Guide — Sizes, Points, and the Path to Watermelon

I spent three weeks picking these 11 fruits. The original prototype used vegetables, and I can tell you from painful experience: nobody wants to merge two carrots. Vegetables lack that gut-level size logic that fruits carry. A grape is tiny. A watermelon is massive. Your brain already knows the hierarchy before I explain a single rule.

This guide breaks down every fruit in Fruit Merge's evolution chain -- their sizes, their scores, what they cost to create, and the strategies I've learned (sometimes the hard way) for each one. If you've been playing blind, dropping fruits and hoping for the best, this is where the game starts making sense.

How the Evolution Chain Works

Two identical fruits touch each other, and they merge into the next fruit up. That is the entire mechanic. Grape plus Grape makes Cherry. Cherry plus Cherry makes Strawberry. This keeps going until you hit Watermelon, the final form, the thing every run is chasing.

I tested 15 different fruit sets before settling on these 11. Some early versions had 8 fruits, others had 14. Eight felt too short -- you'd hit the endgame in minutes and get bored. Fourteen made the early game a slog, with too many tiny merges before anything satisfying happened. Eleven is the sweet spot, and I'm not entirely sure I could explain why it works so well. It just does.

The physics matter here. Two grapes need to physically collide to trigger a merge. I built a forgiveness buffer into the collision detection -- the merge radius is 2 pixels wider than the visual sprite itself. During early testing, players kept telling me merges felt "broken" when they had to land pixel-perfect contacts. That invisible buffer fixed the frustration without anyone noticing it exists.

The Complete Evolution Table

Here is every fruit, from smallest to largest, with the numbers that govern the game under the hood.

#	Fruit	Diameter (px)	Points	Cumulative Grapes Needed	Merge Recipe
1	Grape	24	1	1	-- (starting fruit)
2	Cherry	32	3	2	Grape + Grape
3	Strawberry	40	6	4	Cherry + Cherry
4	Lemon	50	10	8	Strawberry + Strawberry
5	Orange	62	15	16	Lemon + Lemon
6	Apple	76	21	32	Orange + Orange
7	Pear	92	28	64	Apple + Apple
8	Peach	110	36	128	Pear + Pear
9	Pineapple	132	45	256	Peach + Peach
10	Melon	156	55	512	Pineapple + Pineapple
11	Watermelon	180	66	1,024	Melon + Melon

The scoring formula is triangular: each fruit scores n*(n+1)/2 where n is its position in the chain. I chose this over linear scoring because, with linear scoring, merging two Melons into a Watermelon felt about as exciting as merging two Grapes into a Cherry. The triangular formula makes each tier feel progressively more rewarding. That Watermelon merge hits different when you see 66 points land instead of 11.

Tier 1: The Small Fruits (Grape through Lemon)

Grape -- The Seed of Everything

The Grape is 24 pixels across. It is the smallest object in the game and the one you will see more than any other. Every run starts here. Every Watermelon traces its lineage back to 1,024 of these little things.

I watch new players ignore Grapes. They drop them carelessly, treating them as clutter. This is a mistake. Grapes that land in awkward positions become obstacles for the rest of the game. They wedge between larger fruits, block potential merges, and eat up vertical space you cannot afford to lose.

My approach: I keep Grapes near one wall. I let them accumulate in a cluster, then merge them in bursts. The sound of four rapid Grape merges cascading up to a Lemon -- that satisfying little chain of pops -- never gets old.

Cherry -- First Merge, First Lesson

At 32 pixels, Cherry is only slightly bigger than Grape, but it teaches you the core lesson: positioning matters. Your first Cherry merge happens within seconds of starting a game. Where that Cherry lands determines the shape of your next 30 seconds of play.

I used to drop Grapes wherever they fit. Now I place them deliberately, thinking about where the resulting Cherry will sit and whether that Cherry is near another Cherry. When you start thinking two merges ahead, your scores jump.

Strawberry -- The Chain Starter

Strawberry at 40 pixels is where chain reactions become realistic. You have enough Strawberries accumulating that the odds of two touching go up. This is the first fruit where I noticed players beginning to "feel" the game rather than just reacting to it. They start predicting. They start planning.

The red color helps too. Strawberries are visually distinct from the green Grapes and red Cherries because of their shape and that little crown of leaves. I picked fruits partly for gameplay and partly because players need to instantly tell them apart in a cluttered container.

Lemon -- Where the Container Starts to Tighten

Lemon jumps to 50 pixels, and this is where casual players first feel pressure. Four fruits in, and the container is starting to fill. Lemons take up real estate. You cannot stack them as freely as the smaller fruits.

The bright yellow is deliberate. When your container gets crowded, I wanted Lemons to shout at you -- "deal with me or lose." That visual urgency pushes players to prioritize Lemon merges even when they'd rather focus on smaller combos.

Tier 2: The Mid-Tier Fruits (Orange through Pear)

Orange -- The Turning Point

At 62 pixels, Orange is the first fruit that genuinely disrupts your layout. It is big enough to roll and push other fruits around when it forms. I have watched Oranges bulldoze carefully arranged Grape clusters just by appearing in the wrong spot. The physics engine does not care about your plans.

Orange is also the first fruit where the score starts to feel meaningful. At 15 points per merge, creating Oranges is noticeably more rewarding than chaining small fruits. This is intentional. The triangular scoring formula kicks into gear right around here, and I wanted players to feel pulled toward creating bigger fruits rather than safely grinding small ones.

Apple -- The Trickiest Fruit to Manage

Apple at 76 pixels is large enough to dominate a section of your container but small enough that you'll accumulate multiples. This creates a unique problem: two Apples that cannot quite reach each other, with smaller fruits jammed between them, blocking the merge.

I did not anticipate how frustrating this would be until I had played 30 or 40 games myself. The fix is preventive: when you see an Apple forming, make sure the area around it is clear. Do not let debris build up between potential Apple pairs.

Pear -- The Most Underrated Fruit in the Game

Here is something I did not realize until 50-plus games in: the Pear is the transition point. At 92 pixels, it is the dividing line between "small enough to manage" and "large enough to cause real problems." Everything below Pear, you can rearrange and recover from. Everything above Pear starts to feel permanent.

Pear sits at position 7 in the chain, needing 64 Grapes' worth of merges to create. Players who understand the Pear's role treat it with respect. They build toward Pear merges with the same care they give to the fruits above it. Players who do not understand this -- well, they wonder why their games keep ending with two Pears stuck on opposite sides of the container.

If you take one lesson from the Beginner's Guide, make it this: treat Pears like big fruits, not small ones.

Tier 3: The Giants (Peach through Watermelon)

Peach -- The Quiet Giant

Peach at 110 pixels takes up a chunk of your container. It is round, heavy, and it settles into whatever position physics dictates. You do not place a Peach. A Peach places itself.

Creating a Peach feels like an accomplishment. You have merged through seven tiers to get here. But the celebration is short because you immediately realize: this Peach is enormous and you need a second one. Where is the second one going to fit?

I watch experienced players build their entire strategy around Peach placement. They leave a designated area open for the first Peach, then work on building the second one nearby. It is the fruit that forces you to plan your container layout from the very first drop.

Pineapple -- The Size Jump That Surprises Everyone

The Peach-to-Pineapple jump always surprises people. Including me, honestly. At 132 pixels, Pineapple is a 20% size increase over Peach, and it feels massive. The visual shock when two Peaches merge and this spiked monster appears -- players audibly react to it. I have watched streams where people gasp.

Pineapple is also where the game becomes genuinely difficult. You need 256 Grapes' worth of merges to create one. Two Pineapples means 512 Grapes' worth of work. The container is screaming at this point. Every drop matters. Every misplaced Grape is a potential game-ender.

For Pineapple strategies, check the Advanced Strategies guide where I go deep on container management for the late game.

Melon -- The Penultimate Beast

At 156 pixels, the Melon dominates your container. When a Melon forms, you can feel the other fruits compress around it. There is barely room to breathe.

Getting a Melon means you are doing almost everything right. But "almost" is the key word. I have lost more games with a single Melon on screen than at any other stage. The temptation to rush the second Melon leads to sloppy play, and one sloppy drop at this stage means game over. If you are managing two Melons simultaneously, you are in the top tier of players. No question.

Watermelon -- The Final Evolution

The Watermelon. 180 pixels of glory. The endgame. The thing that makes you pump your fist even if nobody is watching.

To create one Watermelon from scratch, you would theoretically need 1,024 Grapes. That is where the "2048" in the original game concept comes from -- it is 2 to the 10th power, which maps to the 10 merges needed to go from Grape to Watermelon. In practice, you are never building from pure Grapes. You are merging from multiple tiers simultaneously, catching chain reactions, and occasionally getting lucky with physics bouncing two fruits together.

Creating a Watermelon scores you 66 points from that single merge. But the real score comes from the chain: all the intermediate merges you triggered along the way. A Watermelon created through a long chain reaction can net you over 200 points in a single cascade. That is the peak experience of Fruit Merge. That is what keeps you clicking "Play Again."

For a breakdown of the 10 most common mistakes that prevent players from reaching Watermelon, see Common Mistakes.

The Math Behind the Merges

The scoring and sizing systems are not arbitrary. Here is what drives the design.

Scoring is triangular, not linear. Each fruit scores n*(n+1)/2. This means:

Grape (position 1): 1 point

Cherry (position 2): 3 points

Strawberry (position 3): 6 points

And so on up to Watermelon (position 11): 66 points

Linear scoring (1, 2, 3, 4...) made late-game merges feel flat during testing. Exponential scoring (1, 2, 4, 8...) made early fruits feel worthless. Triangular hit the sweet spot -- it rewards progress without making early play feel pointless.

Size scaling is proportional but not uniform. I scaled each fruit so the size jump feels roughly consistent in terms of visual impact. The Grape starts at 24 pixels. Each step up adds a bit more diameter than the last. But the Peach-to-Pineapple jump (110 to 132) is the steepest proportional increase after the early fruits, which is why it feels like such a shock.

The 1,024 Grape requirement means each tier doubles the investment of the tier below. This creates a natural difficulty curve -- early tiers are cheap and fast, late tiers are expensive and slow. You spend 80% of your game time working toward the top three fruits.

Strategy Tips by Evolution Tier

Here is how I approach each tier after hundreds of games.

Early game (Grape through Lemon):

Drop fast, merge faster. Do not overthink small fruits.

Keep one side of the container clean for future big fruits.

Let chain reactions happen naturally -- do not force them.

Mid game (Orange through Pear):

Slow down. Each drop matters more now.

Always know where your largest fruit is. Build toward it.

When in doubt, merge down rather than building up. Clear space.

Late game (Peach through Watermelon):

Your container layout should already be set. If it is not, you are probably going to lose.

One Peach or Pineapple in the wrong spot can block three potential merges. Precision over speed.

The final Melon merge into Watermelon is the most tense moment in the game. Breathe. Aim carefully. I still feel my shoulders tighten every time.

For a full breakdown of scoring tactics, see 10 Tips to Boost Your Score.

Why These 11 Fruits (And Not Others)

Players ask me this a lot. Why not 12? Why not bananas or coconuts?

I chose fruits with a natural size progression that people intuitively understand. Nobody needs to be told that a grape is smaller than a watermelon. That instant recognition means zero learning curve for the evolution chain itself -- you just know.

Bananas were in an early build. They looked wrong. Their elongated shape broke the collision physics, and they did not stack cleanly with the round fruits. Coconuts had a similar problem -- too close in visual size to some of the mid-tier fruits, which caused confusion.

Eleven is also a practical number. Ten merges to go from bottom to top. Enough variety that the game feels deep, but not so many tiers that reaching the endgame feels impossible. I wanted casual players to see a Melon within their first few sessions. That carrot keeps them coming back. Reaching an actual Watermelon takes skill and patience, but seeing a Melon tells you the Watermelon is close.

The original Suika Game concept from Aladdin X used a similar fruit set, and there is a reason that design endured. The fruit hierarchy is universal. It works across languages, cultures, and age groups. My version tweaks the sizes and scoring, but the core insight -- fruits as a natural difficulty ladder -- is borrowed from a design that already proved itself.

Frequently Asked Questions

How many fruits are in Fruit Merge's evolution chain?

There are 11 fruits total: Grape, Cherry, Strawberry, Lemon, Orange, Apple, Pear, Peach, Pineapple, Melon, and Watermelon. Each fruit merges with an identical copy to produce the next one in the chain. I settled on 11 after testing sets of 8 through 14 and finding this count balanced depth with accessibility.

What happens when you merge two Watermelons?

Watermelon is the final fruit. When two Watermelons merge, they disappear and you receive a large point bonus. There is no 12th fruit. I considered adding one, but the Watermelon works as a satisfying endpoint -- and removing two massive fruits from the container creates a rush of space that feels incredible.

How many Grapes does it take to make a Watermelon?

Theoretically, 1,024. Each tier doubles the requirement: 2 Grapes make a Cherry, 4 Grapes' worth makes a Strawberry, 8 for a Lemon, and so on. In actual gameplay, you are never funneling 1,024 Grapes sequentially. You merge across multiple tiers at once, which is what makes the game dynamic rather than repetitive.

Why does the Peach-to-Pineapple size jump feel so dramatic?

Because it is the largest proportional diameter increase in the upper tiers -- jumping from 110 to 132 pixels. I scaled fruits to feel proportional, but the Pineapple's spiky shape amplifies the visual impact beyond the raw numbers. The pineapple was always going to be a visual disruptor, and I leaned into that rather than fighting it.

What is the highest-scoring single merge in the game?

Creating a Watermelon from two Melons scores 66 points for that merge alone. But the real scoring power comes from chain reactions. If merging those Melons triggers a cascade of other merges below them, you can net 200-plus points from a single drop. The Advanced Strategies guide covers how to set up these cascades.

About the Author