Hosted on this site

2048

numberssingle-playeroffline

How to play 2048

Every move slides every tile on the board in one direction at once — that is the rule most new players underestimate. You are not moving one tile, you are committing the whole board. When two tiles showing the same number collide, they merge into their sum, and a new tile appears in a random empty cell.

On a keyboard, use the arrow keys. WASD and the vim keys HJKL are wired to the same four directions, so use whichever your hands prefer. On a phone or tablet, swipe in the direction you want the board to move. There is no timer, so you can take as long as you like over a move — and there is no undo, which is the reason taking that time is worth it.

The board is 4x4. The game ends when the board is full and no two adjacent tiles can merge. Reaching the 2048 tile shows a win message, and you can dismiss it and keep playing for a higher tile.

The one number that explains the difficulty

Each new tile is a 2 ninety percent of the time and a 4 the other ten percent. That single ratio drives everything else about the game.

It means a 2048 tile is the result of merging 1024 separate spawned tiles, each of which has to be merged eleven times over. It also means the board fills with small tiles far faster than it consolidates into large ones, so the real resource you are managing is not score — it is empty cells. A board with six empty cells has options; a board with one empty cell plays whatever move it is given.

This is also why the occasional 4 matters more than its 10% suggests. A 4 that lands where you wanted a 2 breaks a merge chain, and unlike a 2 it cannot pair with the 2 next to it.

Strategy that actually works

Pick one corner and never let your largest tile leave it. This is the whole game in one sentence. Most players lose because they use all four directions freely, which lets the biggest tile wander into the middle of the board where it blocks merges from every side.

Use two directions, not four. If your corner is bottom-left, press Down and Left almost exclusively. Reach for a third direction only when neither of those two changes the board. The direction you must treat as a mistake is the one that pulls tiles away from your corner — with a bottom-left corner, that is Up.

Keep your bottom row in descending order. A row reading 256-128-64-32 merges as a cascade: the 32 feeds the 64, which feeds the 128. A row reading 256-32-128-64 has the same tiles and no chain at all, because nothing sits next to its own match.

Never leave your anchor row half-empty. If the bottom row is 512-256-_-_, an Up press anywhere in the game can drop a 2 into that gap and wedge it between your large tiles. Fill the anchor row before you build the row above it.

Think about the spawn before you move, not after. Because a new tile appears after every move, the question is not "does this move merge something" but "where can the new tile land, and does that ruin me". A move that merges two 4s but opens your anchor row is a bad move.

Where runs actually end

Most losses are not caused by one bad move — they are caused by a slow drift that only becomes visible when it is too late. Two patterns cover the majority of them.

The first is the stranded large tile. A 512 ends up in the middle of the board with smaller tiles on all four sides. Nothing can merge with it, and it splits the board into regions too small to build in. This is always the consequence of an earlier Up press.

The second is the odd tile out. You build 1024-512-256-128 along the bottom and then need a second 128 to continue — but the only tiles left are 2s and 4s in the rows above, and there is no room to combine them into anything useful. The fix is upstream: build the next tile in the sequence while you still have empty cells, not after you run out.

Device support

The game runs directly in this page with nothing to download and no account to create, and it works in a desktop browser or on a phone. After the page loads it makes no network calls, so an interrupted connection will not interrupt a run. Your best score is saved in local browser storage on the device where you play, along with the board itself — so closing the tab mid-run and coming back keeps the game you were playing. Clearing site data resets both.

Frequently asked questions

How do I play 2048?
Slide the whole board with the arrow keys, WASD or HJKL on a keyboard, or swipe on a touchscreen. Tiles showing the same number merge into their sum, and a new tile appears after every move. Reach the 2048 tile to win.
What is the best strategy for 2048?
Choose one corner, keep your largest tile there permanently, and use only the two directions that push tiles toward it. Keep your anchor row in descending order so merges cascade, and never leave a gap in it for a new tile to fall into.
Is 2048 solvable every time?
No. Tile spawns are random, so some boards become unwinnable regardless of play quality. Strong play wins the large majority of runs, not all of them.
Why do I keep getting 4s instead of 2s?
Each new tile is a 2 with 90% probability and a 4 with 10% probability. Fours feel more common than they are because they are more disruptive: a 4 cannot merge with the 2 beside it, so it breaks a chain a 2 would have continued.
Can I undo a move in 2048?
No. This version has no undo, which is why it is worth pausing before a move that changes your anchor row. There is no timer, so nothing rushes the decision.
What is the highest possible tile?
On a 4x4 board the theoretical maximum is 131072, but it requires a near-perfect spawn sequence. Reaching 8192 is already exceptional.
Can you keep playing after reaching 2048?
Yes. The win message can be dismissed and the run continues, so you can push for 4096 and beyond on the same board.
Does it work offline?
Yes. The game is a single self-contained page with no network calls after load.
Is my progress saved?
Yes. The board and your best score are kept in local browser storage on that device, so you can close the tab mid-run and resume. Clearing site data removes both.

Created by Gabriele Cirulli, licensed under MIT. View source

Browse other categories

View all