How Chrome Dino Has Changed Since 2014

When the Chrome Dino game first appeared on Chrome’s offline page in 2014, it was just a dinosaur that ran past cacti. No bird. No night mode. No real progression beyond the cactus dodge. Over the next decade, Google quietly added new mechanics, visual flourishes, and one-off birthday Easter eggs that turned the T-Rex Runner into a small, surprisingly rich game. Here’s the chrome dino version history — what changed, when (broadly), and why each addition mattered.

2014: launch

The T-Rex Runner shipped with Chrome’s offline page in 2014. Sebastien Gabriel, a Google designer, built it as a small Easter egg — a quiet bit of personality on what was otherwise the most boring screen in the browser. The original release was minimal: a dinosaur, a horizontal ground line, scrolling cacti, and a score counter. Jump with space, restart on death. No flying enemies, no palette shifts, no audio variation beyond a single milestone chime.

That minimalism is part of why it stuck. The game was the right length for a no-internet moment (under a minute per run on average) and the right difficulty curve (gentle at first, eventually unwinnable). It didn’t take itself seriously, and it didn’t try to.

Early updates: pterodactyl and night mode

In the years after launch, Google added the two features that did the most to make the game replayable. The pterodactyl — the flying enemy that appears after 450 points — introduced a second obstacle type and a second input (duck). Before that, the entire game was jump-or-die. Adding the duck input doubled the gameplay vocabulary without complicating the controls.

The night mode palette flip came around the same time. At certain score thresholds, the game’s color scheme inverts: dark sky, light dino, light cacti. After more score progress, it flips back. The flip is purely cosmetic, but it gives long runs a sense of progression beyond the climbing number — there’s a visual milestone to chase past the first night, the second night, and so on.

Mobile touch support

The original game was keyboard-only. Mobile Chrome added touch support so the offline page on a phone could trigger the same game without an attached keyboard. The touch model is the obvious one: tap to jump, press and hold to duck. The translation was clean enough that the mobile version feels native, not ported.

That update mattered because most people first encounter the Chrome Dino game on their phone. Without touch support, the offline-page Easter egg would have been a desktop-only joke; with it, the game became universally accessible across Chrome.

Birthday Easter eggs

The most visible content updates have been time-limited Easter eggs tied to events. The most famous was the Tokyo 2020 Olympics update (which ran in 2021 due to the games’ delay), when the dino gained event-themed obstacles and could “win medals” by passing certain score thresholds. The graphics swapped to include track-and-field elements, and a podium animation played at milestones.

That update was the most ambitious change to the game’s loop in its history — and Google reverted it after the event ended. It’s a useful demonstration that the dino game’s engine is flexible enough to support more elaborate content, even though the canonical version stays minimalist.

Quiet under-the-hood changes

Not every update is visible to players. Across the game’s lifespan, Chromium engineers have made small fixes to the runner’s code: input latency improvements, frame-rate stability on lower-spec hardware, security tweaks to keep the offline page from being a vector for unintended exploits, and adjustments to the way the game initializes on different screen sizes. None of these change how the game feels to play, but they’re the reason the dino still runs smoothly on hardware ranging from a top-end MacBook to a cheap Chromebook.

The Chromium source repository tracks every change. If you want to read the actual changelog at the code level, the runner files in the Chromium tree have full commit history.

What hasn’t changed

The core game loop is the same as it was in 2014. The dino, the cacti, the speed acceleration, the score increment, the localStorage-saved high score — all of it persists across every update. That stability matters. Players who learned the game in 2014 can come back in 2026 and find a game that looks and plays the same. The additions are additive; nothing has been removed or fundamentally changed.

That continuity is a deliberate choice. The Chrome Dino game is a piece of design that works at its current size. Adding too much would break the loop’s elegance. Google’s restraint has kept the game what it is.

The open-source story

One reason the game has aged well: the source has been open under a BSD-3 license throughout. Anyone can fork, modify, or rehost the T-Rex Runner without permission. A community-maintained mirror at github.com/wayou/t-rex-runner has tracked the official source closely enough that most fan mods and clones are built off it rather than off the canonical Chromium tree. That openness is a big reason the game has spread far beyond Chrome — every “play dino” site you’ve ever seen is running some derivative of the same code.

For a longer look at how the game became a cultural artifact in its own right, see our full Chrome Dino history piece.

Where the game might go next

Google has stayed conservative with the dino game for years. Major updates are rare, and the Tokyo Olympics Easter egg was the last big themed event. It’s reasonable to expect more one-off seasonal updates — anniversary tweaks, holiday themes — but no fundamental redesign of the core game. The minimalist offline Easter egg is too much of a brand asset to risk changing.

What’s more likely to evolve is the broader ecosystem of fan mods. The open license has spawned versions with power-ups, multiplayer modes, character swaps, and entire reskins. Those are where most innovation happens now, not in the official Chromium codebase.

Frequently asked questions

When was the Chrome Dino game first released?

The game launched in 2014 on Chrome’s offline page, designed by Google designer Sebastien Gabriel. It was originally a minimal cactus-dodging Easter egg without the pterodactyl, night mode, or mobile touch support that came in later updates.

Who created the Chrome Dino game?

Sebastien Gabriel, a designer at Google, is credited as the creator of the T-Rex Runner. The game’s source is open under a BSD-3 license and has had additional Chromium engineers contributing over the years.

When did the pterodactyl get added to Chrome Dino?

The pterodactyl was added in one of the post-launch updates after the initial 2014 release. Precise timing isn’t widely documented, but the bird’s introduction is the most significant gameplay change in the game’s history — before it, the game was cactus-only.

Has Chrome Dino ever had multiplayer?

Not officially. The canonical Chrome Dino game has always been single-player. Fan-made mods have added multiplayer variants, but none ship with Chrome.

Will Google add new features to Chrome Dino?

Google has been conservative with updates and is unlikely to make major changes to the core loop. Themed seasonal Easter eggs (like the Tokyo Olympics update) are the most likely form of future additions. The game’s minimalism is a design feature, not an oversight.

The takeaway

The Chrome Dino game’s update history is mostly about additions that preserved the original feel. A flying enemy. A night mode. Mobile touch. A handful of event Easter eggs. The core game has been recognizably itself since 2014, and that consistency is probably why it’s still alive in 2026. Try the current version on the offline dinosaur game and see how the small additions add up.