The Snake and Apple Game: Why Does the Snake Eat Apples?

Ask anyone to describe snake and you will hear the same sentence: a snake eats apples and grows. Real snakes, of course, do not eat fruit. So where did the apple come from — and why did it stick?

From “food” to fruit

Early snake games were abstract: on 1970s arcade machines and 1990s phones, the thing you ate was just a dot or block — Nokia’s manuals simply called it food. As versions moved to colour screens, designers wanted food you could recognise at a glance, and fruit was the obvious pick: it reads instantly, it is friendly, and arcade games from Pac-Man onward had already trained players to see fruit as points. Google’s modern snake leaned into exactly that, with a bright red apple as the default — and that image is now how a whole generation pictures the game.

Why the apple works so well

It is a small masterclass in game readability. The apple is round on a square grid, so it never looks like a piece of snake. It is red on a green board, the strongest contrast pair available. And one apple = one point = one segment of growth keeps the whole economy of the game countable in your head. When we built our own games we kept the convention for the same reasons — you will find the apple on our Google-style board and across all twelve modes.

The apple changes how you play

Because every apple makes the snake longer, the food is also the difficulty dial: each bite makes the next one riskier. Strong players therefore treat apples selectively — an apple in a dangerous corner is a trap to skip, as we explain in our high-score tips and common mistakes. And on the standard Google board there are exactly 252 apples between you and a perfect game.

Play the snake-and-apple game free

The purest version of the formula is our classic snake game: deadly walls, one apple at a time, and a saved best score to beat. Prefer no walls? The wrap-around board keeps the apples coming without the edges ending your run.