Fruit Merge
This is a physics-based 2D puzzle game.
Merge two watermelons to remove them from the screen.
I built Fruit Merge because I wanted a game that took five seconds to understand and five hundred hours to master. The concept is dead simple: drop fruits into a container, and when two matching fruits touch, they merge into the next fruit up the chain. Cherry becomes Strawberry. Strawberry becomes Grape. All the way up to the legendary Watermelon, eleven fruits in total, with Watermelon as the final evolution.
This guide covers everything you need to play your first game, understand what is happening on screen, and start pushing your scores past the beginner plateau. You can play Fruit Merge online for free, try a few drops, and come back to this guide whenever the board starts making more sense. If you found the game while searching for a Suika-style watermelon game, the basic idea is the same: merge small fruits until you can create the final fruit. I wrote it because I chose not to put a tutorial screen in the game. The NEXT preview shows one upcoming fruit; the Evolution Guide shows the full 11-fruit chain. But starting and improving are different things entirely.
This is a physics-based 2D puzzle game.
Merge two watermelons to remove them from the screen.
You control one thing: where each fruit drops. A fruit appears at the top of the container, you move it left or right, and you release it. Gravity does the rest. The fruit falls, bounces off whatever is below it, and settles into position. If it lands next to an identical fruit and they touch, those two merge into the next fruit in the chain.
The chain runs through 11 fruits in this exact order:
Cherry -- the smallest, your starting fruit
Strawberry -- your first merge
Grape -- where chains start to form
Ponkan -- the small citrus fruit before Orange
Orange -- the first fruit that feels heavy
Apple -- large enough to cause problems
Pear -- the transition between small and big
Peach -- a genuine space hog
Pineapple -- the spiky disruptor
Melon -- massive, almost endgame
Watermelon -- the final evolution, the goal
There is no overall time limit. There is no move limit. The run ends when a fruit above the red line meets the game-over conditions. Do not assume a moving fruit is safe just because it might settle lower.
This is not a static puzzle game where pieces snap into grid positions. Fruit Merge runs on a real physics engine. Fruits bounce, roll, shift, and settle based on their weight, size, and what they land on. I tuned the physics engine for 3 weeks before the bounce felt right. Too bouncy and fruits launched off each other like rubber balls. Too rigid and the game felt dead, like dropping rocks into a bucket.
The physics create two things that define every game: surprise and chaos. A small Cherry landing on a pile of Oranges can roll sideways into another Cherry, merge into a Strawberry, and set off another merge if that Strawberry meets its match. These moments -- the satisfying crackle of three merges firing in sequence, fruits popping and reforming while the score counter spins -- are what make the game addictive.
But physics also create frustration. A fruit that lands one pixel to the left of where you needed it can block a merge you have been building toward for thirty drops. You will feel that frustration. I feel it, and I designed the game.
My first playtest ended at 847 points -- I couldn't break 1000 for 4 games. If your first few runs land somewhere in the 500 to 900 range, you are right on track. The game looks simple. It is not.
Here is what a typical first game feels like:
Fruits drop, small merges happen, the container is mostly empty. You feel confident. You think you understand everything. This is the honeymoon phase.
The container fills faster than you expected. Fruits you ignored -- a stray Grape here, a lone Cherry there -- start eating up vertical space. You notice the red line for the first time and realize it is closer than it looked. The red line height was tested at 12 positions before I found the right one. Too high and games lasted forever with no tension. Too low and beginners died before they understood the rules. The current position gives you enough room to learn but not enough to be careless.
Your container is three-quarters full. Every drop feels like defusing a bomb. You are watching fruits settle, praying nothing rolls upward, hoping for a lucky merge that clears some space. This is where most first games end -- not because you made one catastrophic mistake, but because twenty small ones accumulated.
Most of your score comes from merges. Creating a Strawberry adds 2 displayed points, a Grape adds 4, and each later tier adds 2 more through Melon at 18. Creating a Watermelon adds 20 points, followed by a 200-point celebration bonus. Merging two Watermelons adds 22 points and clears them both. Remaining fruits also add points during the Game Over clear-out. Bigger merges can be valuable, but keeping space available matters just as much.
| Score Range | What It Means |
|---|---|
| Under 500 | First game, still learning the controls |
| 500 -- 1,000 | You understand merging but not positioning |
| 1,000 -- 2,000 | You are thinking about where fruits land |
| 2,000 -- 3,500 | You are managing space and building chains |
| 3,500+ | You understand the game at a strategic level |
The difference between a 600-point game and a 2,000-point game often comes down to positioning. Where you place each fruit determines your entire trajectory.
Pick a wall -- left or right -- and build your large fruits along it. I use the left wall. Large fruits can act as anchors, but they can still roll or shift when nearby fruits merge. Small fruits go on the opposite side, where they have room to merge and cascade without disturbing your big-fruit stack.
This is the single most important habit you can build. I watch new players scatter fruits randomly across the container, and their games end the same way every time -- two identical big fruits trapped on opposite sides with a wall of smaller debris between them, unable to merge.
When you drop a Cherry, you are not just placing a Cherry. You are placing half of a future Strawberry, which is half of a future Grape. Before you release a fruit, ask yourself: where will the resulting merge happen, and is that a good place for the next merge after that?
This sounds overthinking it for a casual game. It is not. The mental jump from "drop fruit somewhere reasonable" to "drop fruit where it creates a useful merge position" is what separates 1,000-point players from 2,500-point players.
Beginners fixate on big merges and ignore the Grapes and Cherries piling up. Those small fruits are silent killers. A few unmerged small fruits in awkward positions can consume valuable vertical space, but they produce zero points and block potential merges around them.
When your container gets crowded, resist the urge to keep building upward. Instead, look for small-fruit merges that clear space. A Cherry-into-Strawberry merge does not score much, but the breathing room it creates is worth more than the points.
The NEXT preview shows you one upcoming fruit. Use that information. If your next fruit is a Cherry and you have two Strawberries nearly touching, place the current fruit to create space near those Strawberries -- not on top of them. The NEXT preview helps you plan the next drop. Ignoring it is like driving with your eyes closed.
The 11-fruit chain is borrowed from the Suika Game concept, where "suika" means watermelon in Japanese. My version uses an eleven-fruit progression that gives you a clear path toward Watermelon. A grape is small. A watermelon is huge. Everything in between follows the logic you already carry.
What makes the chain interesting is the doubling requirement. Every step up the chain takes twice as many base fruits as the step below. A Strawberry needs 2 Cherries. A Grape needs 4. By the time you reach Watermelon, you theoretically need 1,024 Cherries' worth of fruit. In practice, you never count this. But you feel it. The mid-game fruits come quickly. The late-game fruits demand patience and precision.
The chain is also your scoreboard proxy. If the biggest fruit on your screen is a Ponkan, you are in the early game. If you have a Peach, you are doing well. If you see a Pineapple, you are in elite territory. I have never personally achieved a Double Watermelon in a single run. The rules allow two Watermelons to merge and disappear, but reaching that point is a demanding goal.
This is a physics-based 2D puzzle game.
Merge two watermelons to remove them from the screen.
I will keep this brief because I wrote an entire article on the topic (see Common Mistakes Every Fruit Merge Player Makes for the deep version), but here are the three that kill the most first games:
Dropping too fast. There is no timer. Wait for fruits to settle before dropping the next one. The thunk of a fruit hitting the pile should fully resolve before you release another.
Ignoring small fruits. Those lonely Grapes in the corners are costing you the game. Merge them or build around them, but do not pretend they are not there.
Chasing one big merge instead of maintaining the whole container. If you spend ten drops trying to create a Pear while the rest of your container turns into chaos, that Pear will not save you.
For a list of scoring techniques and positioning habits that address these mistakes directly, check out 10 Tips to Boost Your Fruit Merge Score.
Fruit Merge is free, runs in modern desktop and mobile browsers, and requires no download, no account, and no installation. You open the page and play. Your score is shown at Game Over; keep a record if you want to compare runs across sessions.
There is no energy system. Ads may appear when restarting, and the optional Swap Fruit feature uses a rewarded video to change your current fruit. I built the game as a clean, focused experience because that is the version I wanted to play myself. The entire design philosophy is: the game teaches you by letting you fail, not by lecturing you. Every game over screen is a lesson. Every new run incorporates what the last one taught you.
The game works on both desktop and mobile browsers. On desktop, click or drag to choose a horizontal position, then release to drop. On mobile, you drag the fruit with your finger and release to drop. The touch controls feel slightly different from mouse controls -- there is a warmth and directness to tapping the screen that changes how you interact with the physics. Both are fully supported.
Yes. Fruit Merge is a completely free browser game. There are no in-app purchases, no premium currency, and no locked content. You open the page in any modern browser and start playing immediately. I built it as a passion project, not a revenue machine.
Focus on positioning over speed. Keep large fruits along one wall, merge small fruits aggressively to clear space, and always check the preview fruit before dropping. Most score jumps come from better placement habits, not faster reactions. Players who slow down and plan each drop consistently outscore players who rush.
A fruit can trigger Game Over when its upper edge is above the red line after it has spent more than three seconds in the pile and contacted another fruit. This is not a three-second grace period that starts when it crosses the line, and the fruit does not have to be completely still. Leave room below the line instead of relying on a bounce to save the run.
No. Every drop is permanent. This is a deliberate design choice. The inability to undo forces you to commit to each placement and learn from mistakes in real time rather than rewinding past them. You can start a fresh game after Game Over, though the restart may include an ad.
Watermelon is the 11th and final fruit. Creating one requires merging two Melons together, which themselves require an enormous chain of lower-tier merges. Reaching your first Watermelon is a milestone that can take practice.
This is a physics-based 2D puzzle game.
Merge two watermelons to remove them from the screen.