Chrome Dino Speedrun Categories Explained

The Chrome Dino game is one of the strangest entries in browser-game speedrunning. It doesn’t have a traditional ending. There’s no boss, no level select, no credits screen. The game is an infinite endless runner with a 32-bit score counter, which means the only natural finish line is the eventual integer overflow. This guide walks through the chrome dino speedrun categories that the small but real speedrunning community has built around an endless game, including the score targets, the distance milestones, and the score-cap run that takes about seventeen million points to complete.

Why Chrome Dino speedruns are unusual

Most speedruns have a defined goal — finish the game, reach a credits screen, hit a “you win” state. Chrome Dino has none of these. The T-Rex Runner is an endless game by design, intended to give Chrome users a few minutes of distraction during a network outage. There is no end state.

What the game has instead is a score counter that increases continuously with distance, an obstacle generator that gets faster over time, and a hard cap at 99,999 points where the counter resets to zero. These three features are what speedrun categories build around.

Because the game lacks a formal completion state, Chrome Dino has not been formally categorized on speedrun.com in the same way that games like Tetris or Cookie Clicker have been. The community runs informally — Discord-tracked records, YouTube-uploaded attempts, and occasional Twitch streams. AGDQ has featured Chrome Dino in past lineups (covered in our fastest Chrome Dino runs piece), which lent the scene some visibility.

Common informal categories

Any% high-score

The any% high-score category targets the highest score in a single run. There’s no timer pressure — the goal is pure survival. This is the closest Chrome Dino has to a traditional speedrun category, except optimization is for skill rather than time. Top players reliably reach scores in the tens of thousands; the absolute ceiling is the 99,999 reset.

Time to score milestone

The most popular timed category. Pick a score target — 1000, 5000, 10000 — and race to reach it as fast as possible. The time pressure comes from the score-vs-time relationship: the game’s scoring rate accelerates as the dino’s speed increases, so the optimal run is one that survives long enough for the speed-up curve to start delivering big points per second.

Common milestone targets in informal runs:

• 1000 points — reachable in roughly a minute by competent players.
• 5000 points — a few minutes, requires reliable mid-game survival.
• 10000 points — under five minutes for top players, longer for most.
• 50000 points — a serious sit-down attempt, often half an hour or more.
• 99999 points — the score cap, requires substantial commitment.

Distance any%

Distance is a less common category, but some runners track meters traveled rather than score points. The two are correlated but not identical because the score counter rounds and the distance counter (if exposed via dev tools) gives more precise measurement.

Score-cap reset run

The 99,999 score reset is the only “endpoint” the game has built in. Once you hit it, the counter rolls back to zero and the game continues. This is the closest thing Chrome Dino has to a “you win” condition. Runners targeting this finish state aim to reach the reset as quickly as possible, which at top speed is still a substantial time commitment (over half an hour for most attempts).

How the score counter actually works

The Chrome Dino game’s source is open under BSD-3 license at github.com/wayou/t-rex-runner, so the scoring math is verifiable. Points accumulate based on distance traveled, with a multiplier that increases as the dino’s running speed increases. The game has a hard-coded cap that resets the displayed score to zero when it hits five digits (99999 wraps to 00000).

This means the practical “endgame” for a Chrome Dino speedrun is the cap reset rather than any kind of integer overflow on the underlying counter. The display logic is what creates the loopback.

Obstacle generation and routing

The obstacle generator is deterministic from a seed, but the seed depends on game start time, which is effectively random across runs. This means players can’t memorize a specific obstacle sequence the way classic speedrunners memorize platformer level layouts.

What players can memorize is the obstacle-spawning rhythm — cacti at intervals that depend on current speed, pterodactyls at three vertical heights, and the day-night cycle that’s purely cosmetic but affects audio cues. Reading obstacles fast becomes a skill rather than memorization.

The game also has known edge cases: the pterodactyl-low-flight pattern (which can only be ducked, not jumped) and the dual-cactus close-spawn (which requires a precisely timed jump). These appear at higher speeds and are the most common death causes for experienced players.

The infinite-jump bug

There’s a known glitch where rapidly pressing space at certain frame timings can produce a higher-than-normal jump or a chained jump. Whether this counts in speedrun categories depends on whether the community treats it as a glitch (banned in glitchless categories) or a feature (allowed in any%). The Chrome Dino community is small enough that there’s no formal ruleset — runners self-report and viewers decide whether to count the attempt.

Game version variants

Chrome Dino has appeared in slightly different versions across Chrome releases. The original 2014 version had simpler obstacle patterns; later versions added the pterodactyl, the day-night cycle, and other features. For speedrun purposes, the version played matters because obstacle density differs.

The dinogame.gg recreation is a faithful BSD-3-licensed version of the open-source code, so it matches the standard modern Chrome Dino feel. Other recreations may have small differences in speed scaling or obstacle frequency.

The Chrome Dino speedrun community

The community is small. There are no full-time Chrome Dino speedrunners and no large prize pools. The scene exists mostly on Discord servers and YouTube, with occasional Twitch streams. AGDQ appearances bring temporary spikes of interest but the regular community is in the low hundreds rather than thousands.

This is fine — small communities can still run real categories with real records, and Chrome Dino’s accessibility means anyone can try a run with no setup. Open Chrome, lose Wi-Fi (or visit dinogame.gg), and start a stopwatch.

For external context, the Wikipedia Dinosaur Game article covers the game’s history and design.

How to start a serious Chrome Dino run

Pick a category

Start with time-to-10000 if you want a defined goal and a time you can compare. Pick any% high-score if you want pure survival challenge. Don’t start with the score-cap reset — it’s a long commitment.

Set up the timer

Use LiveSplit or a simple stopwatch app. Start the timer when the dino’s first frame moves; stop when the score hits your target.

Record the run

OBS or any browser screen recorder works. If you’re submitting to a community leaderboard, record the full run — most reviewers will verify by checking that the timer matches the on-screen score progression.

Practice the speed-up curve

Most failed runs die at the speed transition around 5000-7000 points where the obstacles start coming faster than the player adjusts. Practice the transitions until you can survive past 10000 reliably before targeting higher milestones.

Frequently asked questions

Is Chrome Dino on speedrun.com?

Not as a major formally categorized game. The community is small and most runs are tracked informally on Discord, YouTube, or community-maintained leaderboards rather than the speedrun.com central database.

What’s the highest possible Chrome Dino score?

99,999. The score counter resets to zero when it hits that cap. The game continues, but the displayed score loops. This is sometimes called the score-cap or rollover point.

How fast can you reach 10000 points?

Top players reach 10000 in around five minutes or less, but the variance is high because the game’s obstacle density affects survival. There’s no single accepted world record — community trackers vary.

Can you cheat in Chrome Dino?

Yes. The browser console has the well-known invincibility trick — opening dev tools, finding the Runner instance, and overwriting the gameOver function. This obviously disqualifies a run for any leaderboard, but it’s documented in the game’s open-source code.

Has AGDQ featured Chrome Dino?

Yes. The marathon has included Chrome Dino runs in multiple events. The runs are score-based and translate well to the live-stream format despite the game lacking a traditional ending. Our fastest Chrome Dino runs piece covers those appearances.

The bottom line

Chrome Dino speedrunning is a small, informal scene that has built real categories around a game with no built-in endpoint. The score-milestone runs are the most accessible category, the score-cap reset is the closest thing to a true ending, and the any% high-score chase is the longest-running tradition. The game’s accessibility makes it one of the easiest speedruns to attempt — open a browser, lose Wi-Fi, start the stopwatch.