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. You can test the whole chain in Fruit Merge's free browser version without downloading anything or paying for a console game. For players searching for a Suika Game fruit order or watermelon game evolution chart, this is the Fruit Merge version of that same question. If you've been playing blind, dropping fruits and hoping for the best, this is where the game starts making sense.

Puzzle

Fruit Merge

Browser

This is a physics-based 2D puzzle game.

Merge two watermelons to remove them from the screen.

▶ Play

How the Evolution Chain Works

Two identical fruits touch each other, and they merge into the next fruit up. That is the entire mechanic. Cherry plus Cherry makes Strawberry. Strawberry plus Strawberry makes Grape. 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 matching fruits need to physically collide to trigger a merge. The game uses circular collision shapes whose radius is half the fruit height; it does not add a special two-pixel merge buffer. A fruit that looks close still needs to make contact before the merge can start.

The Complete Evolution Table

Here is every fruit in evolution order. Sizes use game units, not fixed screen pixels; the rendered size changes with your browser layout. The points column shows the score added when that fruit is created by a merge. Cherries arrive as drops, so they have no creation-merge score.

#	Fruit	Size (game units)	Displayed points on creation	Base Cherries Equivalent	Merge Recipe
1	Cherry	52	0 (drop)	1	-- (starting fruit)
2	Strawberry	78	2	2	Cherry + Cherry
3	Grape	108	4	4	Strawberry + Strawberry
4	Ponkan	119	6	8	Grape + Grape
5	Orange	153 × 152	8	16	Ponkan + Ponkan
6	Apple	183	10	32	Orange + Orange
7	Pear	186	12	64	Apple + Apple
8	Peach	258	14	128	Pear + Pear
9	Pineapple	308	16	256	Peach + Peach
10	Melon	428*	18	512	Pineapple + Pineapple
11	Watermelon	404	20 + 200 bonus	1,024	Melon + Melon

*The current merge-generated Melon uses 428 game units, even though its sprite frame is 302 units. Do not confuse the frame size with its playing size. Watermelon uses 404 game units. Scoring increases by 2 displayed points per creation tier through Melon at 18. Creating a Watermelon adds 20 points and a further 200 after the celebration. A Double Watermelon adds 22 points and removes both Watermelons; there is no extra chain multiplier.

Tier 1: The Small Fruits (Cherry through Ponkan)

Cherry -- The Seed of Everything

The Cherry is 52 game units across. It is the smallest fruit and the first one you drop. After the fixed opening sequence, each of the first five fruits has the same 20% drop chance. A Watermelon represents 1,024 Cherries' worth of fruit, although higher-tier drops mean you do not need to drop that many Cherries.

I watch new players ignore Cherries. They drop them carelessly, treating them as clutter. This is a mistake. Cherries 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 Cherries near one wall. I let them accumulate in a cluster, then merge them in bursts. The sound of small-fruit merges cascading up to a Ponkan -- that satisfying little chain of pops -- never gets old.

Strawberry -- First Merge, First Lesson

At 78 game units, Strawberry is bigger than Cherry, but it teaches you the core lesson: positioning matters. Your first Strawberry creation happens within seconds of starting a game. Where that Strawberry lands determines the shape of your next 30 seconds of play.

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

Grape -- The Chain Starter

Grape at 108 game units is where chain reactions become realistic. You have enough Grapes 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 purple color helps too. Grapes stand out from the red Cherries and Strawberries, while the Strawberry artwork has a small crown of leaves. I picked fruits partly for gameplay and partly because players need to instantly tell them apart in a cluttered container.

Ponkan -- Where the Container Starts to Tighten

Ponkan is 119 game units across, and this is where casual players first feel pressure. Four fruits in, and the container is starting to fill. Ponkans take up real estate. You cannot stack them as freely as the smaller fruits.

Ponkan is the small citrus fruit between Grape and Orange in the evolution chain. Two Grapes make a Ponkan, and two Ponkans make an Orange. Keep these two citrus tiers distinct when planning your next merge.

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

Orange -- The Turning Point

At 153 by 152 game units, 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 8 displayed points for creating an Orange, creating Oranges is noticeably more rewarding than chaining small fruits. This is intentional. The increasing merge rewards become more noticeable 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 183 game units 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 186 game units, it is the dividing line between "small enough to manage" and "large enough to cause real problems." With smaller fruits, there is often more room to recover from awkward placements. Everything above Pear starts to feel permanent.

Pear sits at position 7 in the chain, needing 64 Cherries' worth of fruit 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 258 game units 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 308 game units, Pineapple is about a 19% diameter 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 Cherries' worth of fruit to create one. Two Pineapples means 512 Cherries' worth of fruit. 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 428 game units in the current merge-generated form, 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. 404 game units of glory. The endgame. The thing that makes you pump your fist even if nobody is watching.

To create one Watermelon entirely from the smallest fruit, you would theoretically need 1,024 Cherries. The doubling will feel familiar to players of 2048: 1,024 is 2 to the 10th power, representing ten increases in fruit tier. In practice, the queue also supplies larger starting fruits, so you build from multiple tiers and use chain reactions to bring matching pairs together.

Creating a Watermelon adds 20 points immediately and 200 more after the celebration. Other merges in the same cascade add their own points, so a well-planned chain can be worth even more. That is the peak experience of Fruit Merge. That is what keeps you clicking "Restart."

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.

The displayed merge rewards increase by 2 points per creation tier, with a special bonus for creating a Watermelon:

Strawberry (position 2): 2 points

Grape (position 3): 4 points

Ponkan (position 4): 6 points

Watermelon (position 11): 20 points plus a 200-point celebration bonus

Chain reactions add the rewards from each merge; there is no separate combo multiplier. A Double Watermelon adds 22 points and frees the space occupied by both fruits. Remaining fruits also contribute points during the Game Over clear-out.

Size changes are not uniform. Cherry starts at 52 game units, Peach uses 258, and Pineapple uses 308. Peach to Pineapple is about a 19% diameter increase, but it is not the largest upper-tier jump. In the current build, the merge-generated Melon uses 428 units, while Watermelon uses 404. Screen pixels vary with the browser layout.

The 1,024-Cherry equivalent 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. A long run can involve a great deal of work toward the top three fruits.

Strategy Tips by Evolution Tier

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

Early game (Cherry through Ponkan):

Take the easy small-fruit merges, but let the pile settle before the next drop.

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.

Puzzle

Fruit Merge

Browser

This is a physics-based 2D puzzle game.

Merge two watermelons to remove them from the screen.

▶ Play

Frequently Asked Questions

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

There are 11 fruits total: Cherry, Strawberry, Grape, Ponkan, Orange, Apple, Pear, Peach, Pineapple, Melon, and Watermelon. Matching pairs produce the next fruit, except two Watermelons, which disappear together. 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 -- a Double Watermelon -- they disappear and add 22 displayed points. 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 Cherries does it take to make a Watermelon?

Theoretically, 1,024 Cherries. Each tier doubles the requirement: 2 Cherries make a Strawberry, 4 Cherries' worth makes a Grape, and 8 makes a Ponkan. The queue also supplies fruits above Cherry, so a real run does not require 1,024 individual Cherry drops.

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

Peach to Pineapple increases diameter from 258 to 308 game units, about 19%. It is a noticeable change, but not the largest proportional increase in the upper tiers. The Pineapple artwork adds to the visual impact, so planning space for it still matters.

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

Creating a Watermelon from two Melons adds 20 displayed points, then a 200-point bonus after the celebration. Other merges in the same chain add their normal rewards. The Advanced Strategies guide covers how to set up these cascades.

Profile