Does Chrome Dino Have a Speed Cap? The Real Limit

If you’ve ever pushed past 1,000 points in the Chrome Dino game and felt the screen scroll like it was about to lift off the page, you’ve probably wondered: does this thing ever stop getting faster? The chrome dino speed limit is real. The game hits a maximum speed and holds it for the rest of the run. Here’s where the cap is, what the code actually does, and what changes once you reach it.

Yes, there’s a speed cap, and it’s by design

The Chrome Dino game raises its speed gradually as you run. Every frame that you don’t crash, the game adds a small acceleration value (0.001) to its current speed. Without a cap, that would keep going until the obstacles moved faster than anyone could react. The code includes a maximum-speed constant, MAX_SPEED, set to 13. Once the current speed reaches it, no more acceleration is added.

It’s a one-line check in the game loop: if the current speed is below the maximum, add the acceleration. The cap doesn’t slow you down; it just stops you from getting faster.

When you hit the cap

The climb from 6 to 13 takes 7,000 frames. On a standard 60 Hz screen that’s about 117 seconds. Since the score is the distance run in pixels times 0.025, our estimate is that the cap arrives at roughly 1,660 points. The acceleration is gentle, so it feels continuous rather than abrupt. You won’t notice a click when the cap engages; you’ll just gradually realize the screen has stopped speeding up.

One wrinkle: acceleration is added per frame, while distance is measured in real time. On a 120 Hz screen the speed-up happens twice as fast, so the cap comes after about a minute, at around half the score. Narrow mobile screens start below 6, but the code still caps them at the same 13.

Many runs end before that point, so reaching the cap shows you’ve made it through the whole speed ramp.

Why the cap exists: reaction time

Google hasn’t published the reasoning behind the number 13, but the human side is easy to see. To clear a cactus, you have to time a jump to an obstacle coming at you at the current speed. The window between “the obstacle is on screen” and “you must have already jumped” shrinks as speed rises. Keep accelerating forever and that window would eventually drop below human reaction time, which is when the game would become pure luck.

At 13, the late game is hard but still readable. A cap set much higher would likely feel unfair.

What happens to difficulty after the cap

Once the speed stops rising, the code doesn’t add any new difficulty. Each new obstacle is picked at random from small cacti, large cacti and pterodactyls (pterodactyls only become eligible once speed passes 8.5, around 450 points). The gap before each obstacle is also random, within a range that scales with speed. A code comment notes that the minimum gap, measured in pixels, gets wider as speed increases, which partly offsets the faster scrolling. Once speed stops rising, that range stops changing too.

That means the late game is the same challenge repeated: top speed, random patterns. What changes is you. Long runs become a question of how many obstacles in a row you can read correctly before fatigue or a lapse in focus ends the run.

What the cap is not

The speed cap is sometimes confused with two other limits people talk about online. It isn’t a score cap: the score keeps climbing well past the speed cap, and the display gains a sixth digit after 99,999 rather than stopping there. We cover that in our piece on the dino game’s max score. It’s also not a “level cap.” The Chrome Dino game has no levels. The only discrete events are pterodactyls becoming eligible to spawn around 450 points and the night-mode flip every 700 points.

Can you remove the cap?

The source code is open under a BSD-style license, so yes. If you copy the game and edit the maximum-speed constant, you can run a version with a higher cap or no cap at all. Expect it to become unplayable quickly once the speed climbs well past 13, because the reaction window keeps shrinking. In Chrome itself you can also change the speed temporarily from DevTools, which some players use as a party trick.

The original source lives in the Chromium codebase. The speed constants (SPEED, ACCELERATION and MAX_SPEED) sit near the top of the runner’s config block.

How the speed cap interacts with mobile

The cap value is the same on mobile and desktop. As noted above, small screens start a little slower, and the code drops the middle pterodactyl height on mobile, leaving only low and high birds. Touch input also feels different from a physical key, and some players find it harder at top speed. Your mileage will vary with your device.

If you’re playing on a tablet with a Bluetooth keyboard, you can use Space and the arrow keys just like on a laptop.

Frequently asked questions

What is the maximum speed in the Chrome Dino game?

The maximum is 13, in the game’s own units (pixels per 60 fps frame). Speed starts at 6. On a standard 60 Hz screen, our estimate is that you reach 13 at about 1,660 points, after roughly two minutes of play.

Does the Chrome Dino game ever stop getting faster?

Yes. The game speeds up gradually from the start, then stops at a fixed maximum. After that point, the game continues but doesn’t speed up or get harder. Obstacles and gaps stay randomized the same way for the rest of the run.

At what score does Chrome Dino max out?

The speed cap arrives around 1,660 points on a 60 Hz screen, by our estimate from the code. Higher refresh-rate screens reach it sooner. The score itself keeps going far past that; see our writeup on the maximum displayable score.

Can the Chrome Dino speed cap be removed?

Yes, by editing the open-source code and raising or removing the maximum-speed constant. The higher the speed climbs, the less time you have to react, so an uncapped version soon becomes unplayable.

Why did the developers add a speed cap?

Google hasn’t spelled it out, but without a cap the speed would keep climbing every frame and eventually outpace human reaction time. A cap keeps the late game hard but playable, which makes it a design choice rather than a technical limit.

The takeaway

The Chrome Dino game caps its speed at 13, reached at around 1,660 points on a typical 60 Hz screen. After that, it’s the same random mix of cacti and pterodactyls at the same speed, and your focus is what gets tested. For the numbers behind long runs, see our max score data. Then put it to the test in your next session of the T-Rex Runner and see if you can reach the wall.

Related: Why Does Chrome Dino Have Cacti? The Desert Design Choice · Does the Chrome Dino Game Ever End? The Score Cap Explained · How to Play Chrome Dino on iPhone (Browser & Workarounds)