Chrome Dino world records and the highest scores ever recorded
The Chrome Dino game caps its visible score at 99,999. The competitive scene blew through that ceiling years ago. This is how high scores actually work, what the verified records are, and how the top players keep going past the rollover.
The 99,999 problem
Chrome’s Dino game stores the score in a 5-digit counter. When you hit 99,999, the counter rolls over to zero and the run continues. The high-score number you see in the corner stops being a reliable measure at that point. Top players track rollovers — how many times the counter has reset — and use that as the real metric.
A single rollover means you scored over 100,000. Two rollovers, over 200,000. The current verified-high tier is around the 3–4 rollover range, which puts real scores well over 300,000. Above that, the game’s speed becomes effectively unplayable on standard input devices.
Where records are tracked
There is no official Google-maintained leaderboard. The community has consolidated around speedrun.com, which tracks the Chrome Dino game under several distinct categories. Submissions require video proof — typically an unbroken screen recording with the score visible. Without video, a claim is just a claim.
The main categories on speedrun.com are time-based (“fastest to score X”) rather than highest-score-overall, because verifying an unbroken multi-hour run is logistically hard. The two most-watched:
- Any% (fastest to 99,999) — speedrun, requires near-perfect play because crashing means restart.
- Highest score in 1 hour — endurance, less about top-tier reflexes and more about sustained focus.
Both categories see steady improvement — the meta has shifted from “play it manually” to “play it manually but with a high-refresh-rate monitor and a mechanical keyboard with low key travel” — but the leaderboard is dominated by a small group of regular submitters.
What gets disqualified
Speedrun moderators reject submissions that show signs of:
- Modified game files — checked via visible browser state and timing inconsistencies. Any DevTools-manipulated config is auto-DQ.
- TAS (tool-assisted speedrun) — frame-by-frame input scripting. There’s a separate TAS category if you want to submit something automated; mixing them up is rejection.
- Auto-clickers / macros — banned in the main human categories.
- Edited video — any cut in the recording is suspicious; submissions need one continuous take from start to crash.
The speed wall
The game gets faster as your score climbs, but there’s a soft ceiling. Past roughly 13x base speed (around 6,000–7,000 points on the original counter), individual reactions stop being the limiting factor — you’re now playing on memorized patterns and visual rhythm. Past that, even top players are crashing on pterodactyl spawn-altitude randomness more than on skill execution.
This is the reason verified scores cluster at certain numbers (high tens of thousands, then individual rollovers). The speed wall makes the gap between “good” (5,000+) and “great” (a rollover) a much bigger climb than the gap between casual (300) and good.
How to break into the top tier
Practical advice from the regular submitters:
- Use a keyboard, not a mouse. Mouse latency is fine for early-game cacti. It’s not fine at speed-wall pace.
- Use a real keyboard, not a laptop chiclet. Key travel matters. So does avoiding double-tap on space.
- Play on a single static aspect ratio. Resizing the window mid-run changes the playfield. Pick a size and stick with it for every run.
- Tape your high-score memory to the wall. Knowing how you died last time keeps you from making the same call again.
- Practice the pterodactyl heights. The single biggest gain is internalizing high/mid/low. High = do nothing. Mid = duck. Low = jump.
- Don’t hold space. Tap. Hold-jumps over-shoot and cost you on the recovery cactus.
The cheating problem
Because the Chrome Dino game is a JavaScript program running on your machine, “cheating” is trivially easy. Open DevTools, set Runner.instance_.tRex.setJumpVelocity(100), and the dinosaur jumps the height of the playfield. A few minutes with the console and you can write an auto-player that achieves any score you want.
This is why community records require continuous video. A screenshot of “1,000,000 points” means nothing — you can produce it in two minutes with DevTools. A 90-minute screen recording with visible browser chrome, unmuted system audio, and no cuts is much harder to fake.
Records on dinogame.gg
The version of the Dino game on our homepage runs the same engine as the Chrome version. Your high score is stored in your browser’s localStorage. We don’t have a global leaderboard yet; if you want to claim a public record, the place is still speedrun.com.
For background on how the game’s mechanics shape what records are possible, see our complete list of Easter eggs and hidden features.
