Cheat Sheets / Chrome Dino

Cheat Sheets · Chrome Dino

Chrome Dino game: max score, top speed and secrets

The Chrome Dino game never ends on its own: at 99,999 the score counter grows a sixth digit and keeps counting, and its code would show 000000 at a million. The dino starts at speed 6 and gets 0.001 faster every frame until it tops out at 13, which takes 116.7 seconds on a 60 Hz screen. Night falls every 700 points, and birds can show up once the speed reaches 8.5, 41.7 seconds into a run.

Every fact carries a mark. seen means we watched it happen in the game running in Chromium. code means it was read in the game's code only. Tap a mark to see the file and line it comes from.

How far will I get?

Work it out from
Any score up to 2,000,000.
Most screens draw 60 frames a second; fast phones and gaming screens 120. Not sure? Measure mine counts this screen's frames.

99,999 points: about 1 hour 26 minutes at 60 Hz

Time from the start of the run
...
Speed then
...
Nights so far
...
Moon
...
Score counter
...
On the track
...

How it works: the calculator plays the game's own update rule, one update per screen frame, with the numbers from the game's code: the speed starts at 6 and gains 0.001 an update up to 13, each update moves the dino its speed in pixels for every 1/60 of a second that passed, and the score is that distance times 0.025, rounded code. It assumes a perfect run from the first update. The nights and moon phases it gives match the runs we recorded seen.

Does the Chrome Dino game end? The max score

No. Nothing stops the score at 99,999, and the run goes on until the dino hits something. The score is the distance the dino has run, in pixels, times 0.025 and rounded code, and the counter starts with 5 digits, so the first number it cannot show is 100,000 seen. Instead of stopping there, the game gives the counter a sixth digit and keeps counting, up to 999,999 seen. It only does that once, so there is never a seventh digit code: at 1,000,000 the counter draws the last six digits and would read 000000 code.

How long is that? At top speed the score climbs about 19.5 points a second, so 99,999 takes about 1 hour 26 minutes of perfect play on a 60 Hz screen, and a million about 14 hours 15 minutes. Nobody has recorded the 000000 here: it is in the code, and the calculator above shows the run that gets there.

Every 100 points the counter flashes and the game plays its "reached" sound seen. The flash is 4 blinks of 250 ms off and 250 ms on, and the digits hold still while it blinks seen, which is why the counter can say 100000 while the run is already at 100,005.

How fast does the dino get?

The speed is how many pixels the ground moves each frame at the 60 frames a second the game is built for code. It starts at 6 seen and every update adds 0.001, not every second seen, until it reaches 13 seen. That takes 7,001 updates, 116.7 seconds at 60 a second code, and the run then has about 1,663 points. The last step lands the speed at 13.001, a hair over 13, and after that it never changes.

Speed60 Hz120 HzScore (60 Hz)What changes
6startstart0small cacti, alone or in groups of up to 3
716.7 s8.3 s163large cacti can come in groups too
8.541.7 s20.8 s453birds can appear
13116.7 s58.3 s1,663top speed: no more speed-up

The game updates once for every frame your screen draws, so on a 120 Hz screen everything in the 120 Hz column comes twice as soon. The distance does not double with it: each update moves the dino by the time that really passed code. The ground and the obstacles move a whole number of pixels each update, while the score counts the exact speed code.

Jumps grow with speed too: a jump starts upward at 10 plus a tenth of the speed in pixels a frame code, and gravity takes 0.6 off every frame code.

Night and the moon

Each time the score hits a multiple of 700, night falls seen: the game flips the page's colors code for 12 seconds code. The moon has 7 phases. Each night moves it to the next one, and after the last it starts over seen. The code numbers them 0 to 6, and phase 3 is the full moon, the only one drawn 40 pixels wide seen. So the first night shows phase 1, the third night the full moon, the seventh phase 0, and the eighth starts again at phase 1.

NightScoreTime (60 Hz)Moon phase
170059.8 s1
21,400102.8 s2
32,100139.1 s3 (full moon)
42,800175.0 s4
53,500210.9 s5
64,200246.8 s6
74,900282.7 s0
85,600318.6 s1

The moon drifts 0.25 pixels an update and the stars 0.3 code, and the moon fades in and out by 0.035 an update code.

Obstacles: the safe start, cacti and birds

Every run starts with 3 seconds and no obstacles seen, and a restart sets that clock back to 0 code. In the hidden audio-cue mode the clear start is 3.6 seconds code.

Keys, gamepad and chrome://dino

Space or Up jumps, Down ducks and Enter restarts code. Press Down in the air and the jump is cut short: the dino drops 3 times as fast code. After a crash Enter restarts at once seen, but Space and Up wait until 1.2 seconds have passed code.

The dinosaur game lives in Chrome's no-internet page, but it also has a page of its own: type chrome://dino in the address bar seen. The game sees that the page's title starts with chrome://dino/ and switches to its full-window arcade mode seen, and there a gamepad works too: button 0 jumps, button 1 ducks and button 9 restarts code. The code follows the standard gamepad layout, where those are the bottom face button, the right face button and Start.

The game is 600 by 150 pixels by default seen. A game narrower than 600 pixels starts at 6 times its width / 600 times 1.2, but never faster than 6, so only a game under 500 pixels wide starts slower seen. When the browser marks the game as switched off, which the code's own note says is for enterprise-enrolled Chromebooks, a message shows instead of the game code.

Starting and restarting

Before your first run the dino blinks, at most 3 times code, each after a random wait of up to 7 seconds code. Remember those blinks: they matter for the first bug below. Your very first jump makes no sound, because the game only starts unpacking its sounds on that key press code. It has three sounds in all: the jump, the crash and the every-100-points sound code.

The high score, and how to erase it

A crash saves the run as your high score when it beats the old one seen, shown as HI and the digits code. The browser keeps it in your profile and hands it back to the game whenever the page loads seen.

To erase it, tap it twice. On the game over screen, tap or click the HI score once and it starts to blink; tap it again while it blinks and it goes back to 0 seen. Tap anywhere else, which starts a new run, or just wait, and nothing is lost: the blinking stops by itself after 7 flashes code.

Hidden modes: audio cues and Start slower

The game has a mode for screen reader users. Press a key while the game itself has keyboard focus, before your first run, and it switches to sound cues it makes itself code, with a longer clear start code.

There is also a hidden switch labelled Start slower. It appears when the game gets focus, so one click on the game is enough to show it, and at game over in audio-cue mode seen. It only does anything with audio cues on: then the game starts at 4.2, tops out at 9, speeds up by 0.0005 an update and brings night every 350 points code. The code can also swap in other game modes when the browser switches them on, but the list of them is empty in this version code.

Three bugs in the code

1. Start during the blinks and the dino speeds up twice as fast

While the dino waits and blinks, the game keeps one frame booked so it can draw the next blink code. Press Space before the third blink and the key press runs an update straight away, and that update books a frame of its own. Now two update loops run side by side, and both add 0.001 to the speed. The distance does not double, since each update counts only the time that really passed, but the speed climbs twice as fast and hits 13 in about 58.3 seconds instead of 116.7, much like a 120 Hz screen. We measured it in Chromium itself: started during the blinks, the game ran 1.95 updates per frame; started after the third blink, 0.97 seen. A crash and restart ends it, so only a first run can have it.

2. The speed-up depends on your screen

The speed rises per update, and the game updates once per frame your screen draws, so a 120 Hz screen reaches top speed in 58.3 seconds and a 60 Hz one in 116.7 code. The score per second at the same speed is the same, so a fast screen gives no free points: it just brings the hard part sooner, and reaches 99,999 only about 16 seconds earlier. Switch the calculator to 120 Hz to compare.

3. The first obstacle can come a frame early or late

The safe start is a sum of frame times, and whether 180 frames of 1/60 of a second add up to more than 3,000 ms comes down to rounding, so the first obstacle comes on frame 180 or 181 seen. Harmless, but real.

Every fact on this page, with its line

All 60 facts, grouped by topic. Each one names the file and line of the game's code it comes from, at the version named at the top, and says whether we also saw it happen in the running game.

Score and the counter 7

  1. The score is the distance run in pixels times 0.025, rounded. The distance is first rounded up to a whole pixel.

    round(distance x 0.025) distance_meter.ts line 34, distance_meter.ts line 172, offline.ts line 897

    code Read in the code only.

  2. The score counter starts with 5 digits, so the first top it can show is 99,999.

    5 digits, 99999 distance_meter.ts line 28, distance_meter.ts lines 95 to 101

    seen 5 digits and a top of 99999 at the start of every recorded run (chrome-dino-past-99999).

  3. The game does not stop at 99,999: past it the counter gets a sixth digit and keeps counting, up to 999,999.

    6 digits, 999999 distance_meter.ts lines 186 to 190

    seen At 100,000 points the counter had 6 digits, its top was 999999 and the screen showed 100000 (chrome-dino-past-99999).

  4. The counter grows only once. There is never a seventh digit.

    only while it has 5 digits distance_meter.ts line 187

    code Read in the code only.

  5. At 1,000,000 points the counter draws only the last 6 digits, so it would show 000000.

    000000 distance_meter.ts lines 202 to 203

    code Read in the code only. Not recorded: a run to a million takes about 14 hours of play.

  6. Every 100 points the score flashes and the game plays its 'reached' sound.

    every 100 points distance_meter.ts line 31, distance_meter.ts lines 194 to 199

    seen The sound played every 100 points in every recorded run.

  7. The flash is 4 blinks of 250 ms off and 250 ms on, and the digits hold still while it flashes.

    4 blinks of 250 ms distance_meter.ts line 37, distance_meter.ts line 40, distance_meter.ts lines 210 to 224

    seen At 100,000 the run was already at 100,005 when the frozen 100000 first showed (chrome-dino-past-99999).

Speed 7

  1. The game is built for 60 frames a second: speed is in pixels per frame at that rate.

    60 constants.ts line 19

    code Read in the code only.

  2. Start speed.

    6 offline.ts line 69

    seen 6 at the start of every recorded run.

  3. Top speed.

    13 offline.ts line 67

    seen 13.001: the last +0.001 is added while the speed is still a hair under 13 (chrome-dino-past-99999).

  4. The speed goes up by 0.001 every update (every frame), not every second, until it reaches the top speed.

    +0.001 per update offline.ts line 62, offline.ts lines 889 to 891

    seen Measured: exactly 0.001 more per update.

  5. From 6 to 13 at 0.001 an update takes 7,001 updates (after 7,000 the sum is still a hair under 13, so one more is added): 116.7 seconds at 60 updates a second.

    116.7 s at 60 Hz offline.ts line 62, offline.ts line 67, offline.ts line 69

    code Read in the code only.

  6. The distance is time based: each update adds speed x frame time / (1000 / 60).

    speed per 1/60 s offline.ts line 182, offline.ts line 887

    code Read in the code only.

  7. Obstacles move a whole number of pixels each update (the speed is rounded down), while the score counts the unrounded speed.

    floor(speed x 60 / 1000 x frame time) obstacle.ts line 178

    code Read in the code only.

Night and the moon 7

  1. Night falls every time the score is a multiple of 700.

    every 700 points offline.ts line 66, offline.ts lines 912 to 921

    seen Nights began at 700, 1400, 2100, 2800, 3500, 4200, 4900 and 5600 (chrome-dino-moon-phases).

  2. A night lasts 12 seconds.

    12 s offline.ts line 49, offline.ts lines 905 to 909

    code Read in the code only.

  3. Night is the page's colors flipped: the game puts the class inverted on the page.

    class inverted offline.ts line 96, offline.ts lines 1550 to 1562

    code Read in the code only.

  4. The moon has 7 phases. Each night moves to the next one, and after the last it starts over.

    7 phases night_mode.ts line 14, night_mode.ts lines 66 to 71

    seen The 8 recorded nights showed phases 1, 2, 3, 4, 5, 6, 0 and 1: night 8 had night 1's moon (chrome-dino-moon-phases).

  5. Phase 3 is the full moon, the only one drawn 40 pixels wide; the others are 20.

    phase 3 night_mode.ts line 30, night_mode.ts lines 111 to 112

    seen The full moon came on night 3 (chrome-dino-moon-phases).

  6. The moon drifts 0.25 pixels per update and the stars 0.3.

    0.25 and 0.3 night_mode.ts line 25, night_mode.ts line 28

    code Read in the code only.

  7. The moon fades in and out by 0.035 opacity per update, about 29 updates.

    0.035 per update night_mode.ts line 23

    code Read in the code only.

Obstacles 10

  1. No obstacle comes for the first 3 seconds of a run.

    3000 ms offline.ts line 43, offline.ts lines 829 to 830

    seen In 3 restarts the first obstacle came on the first frame past 3000 ms each time (chrome-dino-safe-start).

  2. A restart sets the run's time back to 0, so every run gets the same safe start.

    runningTime = 0 offline.ts line 1446

    code Read in the code only.

  3. In the hidden audio-cue mode the obstacle-free start is 1.2 times longer: 3.6 seconds.

    3600 ms offline.ts line 961

    code Read in the code only.

  4. Birds (the code calls them pterodactyls) only come once the speed is 8.5 or more.

    from speed 8.5 offline_sprite_definitions.ts line 172, offline_sprite_definitions.ts line 178, horizon.ts lines 269 to 270

    code Read in the code only.

  5. Birds fly at 3 heights: y 100, 75 or 50 in the 150 pixel tall game. On a phone (Android, or Chrome on an iPhone) only 2: y 100 or 50.

    100, 75 or 50; phones 100 or 50 offline_sprite_definitions.ts lines 175 to 176, constants.ts line 8, constants.ts lines 12 to 13

    code Read in the code only.

  6. Each bird flies 0.8 faster or 0.8 slower than the ground, picked at random.

    speed + 0.8 or - 0.8 obstacle.ts lines 131 to 132, offline_sprite_definitions.ts line 189

    code Read in the code only.

  7. Small cacti can come in groups from speed 4 (so from the start), large cacti from speed 7, at most 3 in a group.

    groups from 4 and 7, up to 3 offline_sprite_definitions.ts line 148, offline_sprite_definitions.ts line 162, offline.ts line 52, obstacle.ts line 94

    code Read in the code only.

  8. The same kind of obstacle never comes more than twice in a row.

    at most 2 in a row offline.ts line 53, horizon.ts line 269

    code Read in the code only.

  9. The gap after an obstacle grows with the speed (gap coefficient 0.6).

    grows with speed offline.ts line 65, obstacle.ts lines 204 to 209

    code Read in the code only.

  10. Only the first obstacle on screen is checked for a hit.

    obstacles[0] offline.ts lines 848 to 852

    code Read in the code only.

Jumping, ducking and keys 6

  1. Space or Up jumps, Down ducks, Enter restarts.

    Space, Up, Down, Enter offline.ts lines 115 to 117

    code Read in the code only.

  2. The faster you run, the harder the jump: it starts upward at 10 + speed / 10 pixels a frame.

    10 + speed / 10 trex.ts line 90, trex.ts line 469

    code Read in the code only.

  3. Gravity pulls the dino down by 0.6 per frame.

    0.6 trex.ts line 87

    code Read in the code only.

  4. Down in the air cuts the jump: the fall speed is set to 1 and the dino falls 3 times as fast.

    3 times as fast trex.ts line 71, trex.ts lines 497 to 499, trex.ts lines 539 to 542

    code Read in the code only.

  5. Ducking shrinks the dino's hit area to one box 55 pixels wide and 25 tall.

    55 x 25 trex.ts line 97

    code Read in the code only.

  6. In chrome://dino a gamepad works: button 0 jumps, button 1 ducks, button 9 restarts.

    buttons 0, 1 and 9 offline.ts lines 1055 to 1058, offline.ts lines 1219 to 1224

    code Read in the code only.

Starting and restarting 6

  1. The very first jump makes no sound: the game only starts unpacking its sounds on that key press, and they are not ready yet.

    silent offline.ts lines 453 to 480, offline.ts line 1101, offline.ts line 1113

    code Read in the code only.

  2. After a crash, Enter restarts at once.

    Enter offline.ts line 117, offline.ts lines 1151 to 1156

    seen Used for every restart in chrome-dino-safe-start.

  3. After a crash, Space or Up only restarts once 1.2 seconds have passed.

    1.2 s offline.ts line 47, offline.ts lines 1154 to 1155

    code Read in the code only.

  4. The game has three sounds: the jump, the crash and the every-100-points sound.

    3 sounds offline.ts lines 105 to 109

    code Read in the code only.

The high score 5

  1. A crash saves the run as the high score when it beats the old one.

    saved on a crash offline.ts lines 1383 to 1386

    seen HI 00364 after a crash at 364 (chrome-dino-erase-high-score).

  2. The high score shows as HI and its digits.

    HI distance_meter.ts lines 275 to 281

    code Read in the code only.

  3. The browser keeps your high score in your profile and hands it to the game when the page loads.

    kept by the browser offline.ts line 259, offline.ts lines 1309 to 1323

    seen HI 00000 showed from the start in chrome://dino.

  4. On the game over screen, tap the high score once and it blinks; tap it again while it blinks and it resets to 0.

    two taps offline.ts lines 1252 to 1272

    seen HI 00364, then HI 00000 and a stored high score of 0 (chrome-dino-erase-high-score).

chrome://dino and screen size 5

  1. The game has its own full-window page: chrome://dino.

    chrome://dino/ offline.ts line 139

    seen Every recorded run was played at chrome://dino/, with the page in arcade mode.

  2. The game switches to its full-window arcade mode because the page's title starts with chrome://dino/.

    title check offline.ts line 1484

    seen Arcade mode was on in every recorded run.

  3. The game is 600 by 150 pixels by default.

    600 x 150 constants.ts lines 21 to 23

    seen chrome://dino laid it out 552 pixels wide at every window size.

  4. A game narrower than 600 pixels starts at speed x width / 600 x 1.2, but never faster than normal, so only a game under 500 pixels wide starts slower.

    under 500 px offline.ts line 68, offline.ts lines 488 to 496

    seen At 552 pixels wide: 552 / 600 x 1.2 = 1.104, so the start speed stayed 6.

  5. When the browser marks the game as switched off (the code's note names enterprise-enrolled Chromebooks), a message shows instead of the game.

    a message instead offline.ts lines 191 to 192, offline.ts lines 339 to 355

    code Read in the code only.

Hidden modes and settings 4

  1. Audio-cue mode, made for screen reader users: press a key while the game itself has keyboard focus, before your first run, and it switches to sound cues it makes itself with oscillators.

    a key on the focused game offline.ts lines 956 to 966, offline.ts lines 1035 to 1036, generated_sound_fx.ts lines 43 to 44

    code Read in the code only.

  2. A hidden Start slower switch appears when the game gets focus (one click on it is enough), or at game over in audio-cue mode. Its label is the browser's own text for the speed toggle.

    Start slower offline.ts line 33, offline.ts lines 539 to 556, offline.ts lines 1007 to 1014

    seen The switch appeared after one click on the game (chrome-dino-erase-high-score).

  3. Slow mode only works with audio cues on: start speed 4.2, top speed 9, speed-up 0.0005, night every 350 points, gap coefficient 0.3.

    4.2 to 9 offline.ts lines 72 to 81, offline.ts lines 980 to 1001

    code Read in the code only.

  4. The code can swap in other game modes when the browser switches them on, but the list of them is empty in this version.

    empty list offline.ts lines 278 to 283, offline.ts lines 326 to 334, offline_sprite_definitions.ts line 14

    code Read in the code only.

Bugs in the code 3

  1. The speed-up depends on the screen's refresh rate: the game updates once per frame the screen draws, and every update adds 0.001, so a 120 Hz screen reaches top speed in half the time of a 60 Hz one.

    58.3 s at 120 Hz, 116.7 s at 60 Hz offline.ts lines 889 to 891, offline.ts lines 1294 to 1299

    code Read in the code only. Not recorded: the recorder's screen runs at 60 Hz.

  2. The first obstacle can come one frame early or late: the run's time is a sum of frame times, and whether 180 frames of 1/60 s add up to more than 3000 ms is down to rounding, so it comes on frame 180 or 181.

    frame 180 or 181 offline.ts lines 829 to 830

    seen Frame 180 in all 3 restarts of chrome-dino-safe-start, with run times of 3000.00000000008 and 3000.0000000002 ms.

Questions people ask

Does the Chrome Dino game ever end?

No. At 99,999 the score counter grows a sixth digit and keeps counting, and the speed stops rising at 13, so from then on the run keeps going at the same speed until you hit something.

What is the highest score in the Chrome Dino game?

The counter can show up to 999,999. It starts with 5 digits, grows a sixth once and never a seventh, so at 1,000,000 it would read 000000. At top speed the score climbs about 19.5 points a second: 99,999 takes about 1 hour 26 minutes and a million about 14 hours 15 minutes of perfect play.

What is the max speed in the Chrome Dino game?

13, from a start of 6. The speed rises by 0.001 every update, so it takes 7,001 updates: 116.7 seconds on a 60 Hz screen and 58.3 seconds on a 120 Hz one.

When does it turn night in the dinosaur game?

Every 700 points: at 700, 1,400, 2,100 and so on. Each night lasts 12 seconds and shows the next of the moon's 7 phases, and the third night has the full moon.

When do birds appear in the Chrome Dino game?

Once the speed reaches 8.5: 41.7 seconds into a run on a 60 Hz screen, around a score of 453. They fly at 3 heights (2 on a phone), and Down makes the dino duck.

How do you reset your high score in the dino game?

On the game over screen, tap or click your HI score once so it blinks, then tap it again while it is blinking. It goes back to 0.

How do you play the Chrome Dino game without going offline?

Type chrome://dino in Chrome's address bar. The game opens on a page of its own in full-window mode, and a gamepad works there as well.

What are the controls for the Chrome Dino game?

Space or Up jumps, Down ducks, and Down in the air drops you fast. Enter restarts at once after a crash; Space restarts too, but only 1.2 seconds after it.

How this was checked

The dino's code is part of Chromium, the browser Chrome is built from, in the folder components/neterror/resources/dino_game. We fetched it at the version named at the top from chromium.googlesource.com, read it, and wrote each fact down with the file and lines it comes from: the list above links every one. Then we ran the game in Chromium itself, at chrome://dino, with a recorder that reads the game's own numbers while it plays and changes nothing, and marked what we watched happen as seen. The calculator plays the game's update rule with the numbers from those lines. Nothing here was taken from another site.

  1. The game's code: components/neterror/resources/dino_game on chromium.googlesource.com, read as text and never run on this site.
  2. The running game: chrome://dino in Chromium, the same version, recorded with no change to the page; the double speed-up was measured in a plain Chromium window with no recorder clock.

Chrome Dino is Google's game, built into Chrome. GardenFlouer is a fan site and is not connected to Google.