Dino Game Guide: Tips, Hidden Features and How to Beat Your High Score

Below: where the T-Rex came from, how the mechanics actually work, the habits that got me from a few hundred points to a few thousand, and some details I only noticed after far too many runs.

The pixel T-Rex that shows up whenever Chrome loses its connection.

Where the Dinosaur Came From

The game shipped in Chrome in 2014. The Chrome UX team wanted the "No Internet" page to be something other than a dead end, and one of the designers sketched a dinosaur as a joke: no connection means you are back in the prehistoric age of the internet. Internally it was called Project Bolan, after Marc Bolan of the band T. Rex, which tells you roughly how seriously anyone took it at the start.

A runner with a single jump button made sense for practical reasons too. It works on any keyboard, on a trackpad, on a phone, needs no instructions and loads with no connection at all. The one thing the team apparently did not anticipate was how much people would play it at work. Enough IT departments complained that Google added an enterprise policy to switch it off, which is why the game is missing on a lot of school and office machines.

By 2018 Google was quoting a figure of around 270 million plays a month. For a page that was designed to be seen for a few seconds and then refreshed, that is absurd.

Playing It Without Pulling the Plug

The awkward part of the original is that you are supposed to lose your connection to see it. You can force the page by typing

chrome://dino

into the address bar, and that is what I did for a long time, but it only works in Chrome, and not at all on managed devices where the policy above is turned on. My work laptop is one of those, which is how I ended up looking for alternatives.

The easiest option is a standalone copy. I mostly practise on the dino game at dino-chrome.com, which is the same runner in a full-screen page: same controls, same speed curve, same night mode, and it opens in Firefox, Safari or Edge just as well as in Chrome. On a phone it is honestly nicer than the built-in version, since you get the whole screen instead of an error page with a dinosaur squeezed into the top third of it.

Everything that follows applies to either version. The timing is identical.

How the Game Actually Works

The whole rule set fits in a small table. What it hides is a handful of details that decide your score.

The speed never stops rising

Every few hundred points the T-Rex runs a little faster. You will not feel it happening, and then somewhere past 1,000 you will realise your jumps are landing on things. By 3,000 it feels like a different game. Almost every early death is a timing death: the obstacle was not hard, you were just still jumping at the speed you learned at score zero.

Obstacles are random, but not unfair

Cacti come small or large, alone or in clumps of up to three. Pterodactyls show up after roughly 450 points and fly at three heights. Low ones you jump. Middle ones you can duck or jump. High ones you run straight under, and the number of people who jump into a high pterodactyl that would have missed them anyway is, I suspect, very large. The generator never puts two obstacles so close that a jump is impossible. Close enough that an early jump kills you, yes, constantly.

Jump height depends on how long you hold the key

This one took me embarrassingly long to notice. A tap gives a short hop; holding space a little longer gives a full jump. Short hops recover faster, which is the whole point when the next cactus is right behind this one. If I had to name the single skill that moved me out of the 800-point range, it is this.

Night mode

Around every 700 points the palette inverts: black sky, moon, stars, white obstacles. It flips back a few hundred points later. Cosmetic, but the first flip has killed more of my runs than I would like to admit, because for half a second the cactus simply does not look like a cactus.

What happens at which score

Dino Game Tips That Actually Raised My Score

For context, here is roughly how my best score moved and what changed each time:

• First week: around 800. Watching the dinosaur, jumping the moment anything appeared.
• Started watching the right edge: 1,600 within a few days.
• Learned the short hop: 2,900. This was the biggest single jump.
• Started ducking under middle pterodactyls instead of jumping: 3,700.
• Now: 4,812, stuck there for a while, mostly dying at night-mode flips.

The tips below are just those steps, in the order I would take them again.

Look at the right edge, not the dinosaur. This is the big one. Beginners stare at the T-Rex. If you fix your eyes on the spot where obstacles enter the screen and let peripheral vision handle the jump, you gain a fraction of a second on every single obstacle. My average run roughly doubled the week I forced myself to do this.

Jump later than feels safe. The reflex is to press space the instant a cactus appears. At speed, that puts you on top of it. The correct moment feels reckless for the first fifty runs and then becomes the only timing that works.

Duck for the middle pterodactyls. Ducking has no recovery; jumping leaves you airborne with no control. If there is a cactus behind the bird, the duck saves you and the jump does not.

Tap for small cacti, hold for the triple clumps. Over-jumping a single small cactus is the classic way to be in the air at exactly the wrong time.

Short sessions. Ten focused runs beat an hour of playing in a background tab. If I die at the same score three times in a row, I close it. The wall is usually attention, not reflexes.

One more thing worth knowing about yourself: most players have a band, often somewhere between 1,000 and 2,000, where the speed crosses their comfort line and runs start collapsing. Mine was around 1,400 for months. Once you know your band you can practise staying calm through it specifically, and it stops being a wall.

Night mode kicks in roughly every 700 points and switches back a few hundred later.

Hidden Details

The score has a ceiling. Past 99,999 the counter rolls over to zero. The developers have said that at normal speed reaching it would take about 17 million years, which is roughly how long ago the real T-Rex went extinct. So no, nobody has done it, and if someone tells you they have, ask for the video.

Every 100 points the score flashes and a small sound plays. The "HI" number next to your score is your session best; on desktop Chrome it survives between games until you close the browser, which is why closing Chrome after a good run feels like a genuine loss.

For Chrome's tenth birthday in 2018 the dinosaur briefly wore a party hat and there was a cake on the track. And the game's source lives in the open Chromium codebase, which is why hobbyists have ported it to smartwatches, graphing calculators and at least one e-ink reader.

Quick Answers

Does the dino game ever end? Not in practice. The score caps at 99,999 and resets, and the speed keeps climbing until reaction time runs out. Nobody has legitimately reached the cap.

Why does chrome://dino not work on my computer? Almost always because it is a school or work device where an administrator has disabled the game through Chrome's policy settings. Standalone versions in the browser are the usual workaround.

Is the mobile version easier or harder? Slightly harder, in my experience. The screen is smaller, so obstacles appear closer to the dinosaur, and there is no separate duck key in the built-in version. Standalone pages that support swipe-down help with that.

Why It Still Holds Up

Plenty of far more ambitious browser games from 2014 are gone. The dinosaur is still here because it is a nearly perfect "one more try" loop: a run starts instantly, death is instant and obviously your own fault, and the score is a precise number to beat. No ads, no menus, no upgrades. It is also an unusually honest game to get better at. If your best went from 800 to 2,400 this month, you know exactly which habit changed.

Next time the connection drops, give it a minute before you refresh. Watch the right edge, jump late, duck when you can. 4,812 is beatable. I am fairly sure of it.