The Fastest Chrome Dino Runs Ever Recorded
Calling a Chrome Dino run “fast” requires defining what fast means. The game has no finish line — it ends only when you hit an obstacle. So the community has built a small constellation of categories around what to measure: highest score before death, longest survival, time to reach specific score milestones, and various restriction-laden challenge runs. Here’s what the fastest Chrome Dino game runs actually are, how the categories work, and why the records are harder to pin down than for traditional speedruns.
Key takeaways
- The Chrome Dino game scores by distance traveled, not time elapsed — so “fastest run” usually means highest score before dying.
- The game’s speed rises from 6 to a fixed maximum of 13, reached around 1,500–2,000 points; after that, endurance is the only limit.
- There is no 99,999 score cap — that’s a myth. The counter gains a sixth digit and only appears to roll over past 999,999.
- There is no official leaderboard, and community record-keeping is informal, so record verification is harder than for traditional games.
- AI-trained bots can keep playing far longer than any human, but bot runs aren’t counted as human records.
How Chrome Dino scoring actually works
The game’s scoring is distance-based. Every frame the dinosaur survives, the score grows with the distance covered — and the speed at which the world scrolls toward the player increases gradually over the run. This is the key constraint: the game gets harder the longer you play, because the obstacles approach faster and your reaction window shrinks.
At around 1,500–2,000 points, the scroll speed hits its hard maximum — the game continues, but the speed stops increasing. From that point on, the limit is purely the player’s sustained reaction time. Long runs end somewhere on that high-speed plateau when the player finally misses one obstacle after many minutes of clean inputs.
This scoring structure is why “fastest” is a misleading word. The fastest you can theoretically score is constrained by the game itself, not by your speed. What separates top runs from average ones is endurance — how long you can sustain perfect-or-near-perfect inputs.
The game’s known mechanical limits
The Chrome Dino source code is part of Chromium, released under a BSD-style license, and widely available as standalone extractions such as the wayou/t-rex-runner project our homepage game is based on. It includes the scroll-speed formula: the speed starts at 6 and adds a small fixed amount every frame until it reaches a maximum of 13. The day-night cycle toggles every 700 points, which is itself a handy visual marker for tracking progress.
The pterodactyl obstacle can only spawn once the game reaches a set speed (8.5 in the code), which works out to roughly 450 points. Before that, the only obstacles are cacti. After that, you’re juggling jump-and-duck inputs against mixed obstacle types.
Knowing the formula matters for speedruns because the difficulty curve is fully predictable. You can map a run into phases — the early game (cacti only), the pterodactyl entry (around 450), the climb to top speed (roughly 1,500–2,000), and the long plateau where attempts eventually end.
Categories the community tracks
Community challenges for Chrome Dino tend to fall into a few informal categories:
- Highest score: The total points scored in a single run. The flagship challenge.
- Time to N points: How quickly you reach a milestone. Because the speed curve is fixed, this mostly tests survival rather than skill at going faster.
- No console tricks: Excludes DevTools edits such as overriding the game-over function on
Runner.instance_. Any serious human record has to be untouched. - Platform: Runs in Chrome’s built-in game are usually kept separate from runs on recreations, since a third-party version may not match the original’s timings exactly.
Our breakdown of Chrome Dino speedrun categories goes through these in more detail.
The category fragmentation is part of why a single “fastest Chrome Dino run” record is hard to point to. Different categories produce different records, and there is no official body declaring one universal record-holder.
Why human-record verification is harder than usual
Three reasons. First, the game has no built-in end state, so every run depends on the player choosing when to stop or when they fail. That makes “cheated” runs harder to spot than in a game with a clear finish line.
Second, the score is the only state that persists, and the score is displayed only on the active page. A run recorded without continuous video from start to death can’t be verified — a reviewer needs to see the score go from zero to the claimed final value without cuts.
Third, the offline-only nature of the original game means runs frequently happen in conditions that aren’t naturally streamed or recorded. Players who hit big scores during a genuine network outage aren’t usually recording at the time. That’s why any claim worth taking seriously comes from a runner who set up recording from the start.
The AI angle
AI-trained bots can keep a run going far longer than a human can. YouTuber Code Bullet’s widely shared video, in which a NEAT-style evolving neural network learned to play the Chrome Dino, is the best-known example. Other hobby projects — using reinforcement learning, computer vision, or reading the game’s state directly — show bots playing for as long as they’re left running. More in how AI plays Chrome Dino.
Bot runs don’t count as human records. They measure different things — the AI runs show the game can go on indefinitely under perfect play, while human runs measure what’s achievable with human attention and a real keyboard.
What top human runs actually look like
A credible top run has a few characteristics. It uses Chrome’s built-in game or a faithful copy of the original code. It’s recorded as continuous video from a fresh page load to the crash. It shows the score counter throughout. And it involves sustained clean inputs for many minutes at a time on the top-speed plateau.
Long runs tend to become pure pattern recognition — the cacti and pterodactyls arriving faster than you can consciously process, the inputs becoming reflexive rather than deliberate. Many end not with an obvious misread but with a brief lapse in attention after a long stretch of concentration.
How long is a top run, in real-world time?
The math is simple once you know the code. At top speed on a standard desktop window the dino covers about 780 pixels a second, and the score is distance multiplied by 0.025, so the counter climbs by roughly 1,150–1,200 points a minute. A 20,000-point run is therefore around 17–18 minutes; reaching 99,999 takes well over an hour of unbroken play. The score-per-minute rate is lower in the opening couple of minutes, while the game is still accelerating.
This is unusual for a speedrun category. Most speedrun records target the smallest possible run time, not the longest. Chrome Dino inverts the relationship: in the highest-score challenge, longer is better. That makes the run more like a marathon than a sprint.
What’s the actual ceiling?
There’s no score ceiling in the code. The popular claim that “the maximum score is 99,999” is a myth: the counter starts at five digits, gains a sixth once you pass 99,999, and only past 999,999 does it show just the last six digits, so it looks like it rolls over. The game itself keeps running, and the day-night cycle continues indefinitely. See the max score explained for the details. In practice, runs end because of human attention and minor input errors at high speed. The theoretical infinite is real but the practical infinite isn’t, by any human verification standard.
For our broader piece on the milestones the Chrome Dino game has produced over the years, see our Chrome Dino world records article.
How to try for the top yourself
If you want to push your own Chrome Dino score, three habits matter. First, play untouched — console tricks are fun once but they don’t count. Second, set up OBS Studio to record from page load through death, so any run you’re proud of is verifiable. Third, treat the run as a marathon, not a sprint. The high-speed plateau is the test; everything before it is the warmup.
You can practice right now without any installation — the standard Chrome Dino game runs in any browser, and the recording setup is exactly what you’d use for any other browser speedrun.
Frequently asked questions
What’s the highest Chrome Dino score ever?
There’s no official answer. Google doesn’t run a leaderboard, and claims circulate without a single trusted verifier, so we don’t quote a specific number. Treat any record claim without an unbroken video of the whole run with caution.
Does Chrome Dino have an ending?
No. The game runs indefinitely until the player hits an obstacle. The scroll speed reaches its maximum of 13 around 1,500–2,000 points, and the run continues at that speed until the player makes a mistake.
How fast does the game get?
The scroll speed starts at 6 and climbs a little every frame to a cap of 13, defined in the source code. Most players who get past roughly 2,000 points have already seen top speed; everything after that is about holding it.
Can AI bots reach higher scores than humans?
Yes, in informal demonstrations. Neural-network and reinforcement-learning projects have shown bots playing for as long as they’re left running. These aren’t counted as human records.
Where can I see verified Chrome Dino records?
There’s no official Google leaderboard. Record claims are scattered across community sites, forums and video uploads, so the best evidence is a continuous, unedited recording of the full run. Our Chrome Dino world records article covers what to look for.
The takeaway
The fastest Chrome Dino runs aren’t measured in seconds — they’re measured in score, distance, and endurance. The game’s no-ending design makes traditional speedrunning categories awkward, which is why players have come up with so many ways to measure it. If you want to try for your own top score, the lowest-friction starting point is one tab away: open the T-Rex Runner, hit space, and see how long you can hold the line.
