Chrome Dino’s Funniest Glitches and Bugs

The Chrome Dino game is small, simple, and mostly well-behaved — but small, simple games tend to have the most interesting edge cases. Players have spent a decade poking at the T-Rex Runner from every angle, and the chrome dino glitches they’ve found range from useful (infinite jump) to ridiculous (the dino getting stuck under a cactus). Here are the best ones, what causes them, and which ones still work today.

1. The infinite-jump bug

The most famous one. In some older builds of the T-Rex Runner, mashing the spacebar while the dino was airborne would let you trigger a second jump mid-air, then a third, and so on. The result: a dino that hovered indefinitely above the action while cacti scrolled harmlessly underneath. The bug came from the game’s input handling treating each key press as a fresh jump request without checking whether the dino was on the ground.

It’s been patched in current Chromium, but it lives on in older mirrors of the source code and in some unofficial hosts. If you find a version where it works, you can use it to coast through arbitrarily long runs — though the score won’t increment any faster, so it’s mostly useful as a way to practice pterodactyl timing without dying first.

2. The “immortal dino” console trick

Not really a glitch — more of a documented Easter egg. Open the browser developer console (F12 on most desktop browsers), and type Runner.instance_.gameOver = function(){}. The game’s collision handler now does nothing. Run into a cactus and the dino bounces off, plays the death animation briefly, and keeps going. It’s the cleanest way to give yourself an unkillable run.

The trick exists because the game’s runner is exposed as a global object for debugging purposes — the original developers needed it to test and never bothered to hide it in production. The community treats it as canon. It works on any current build of the game in any Chromium browser.

3. Ducking through low cactus edges

A real collision quirk. The dino’s ducked hitbox is much smaller than its standing hitbox, and occasionally a small cactus will spawn at a position where the duck hitbox passes cleanly between its prickly bits. The dodge isn’t reliable — you can’t plan around it — but it does happen, and players who duck preemptively before small cactus clusters sometimes survive collisions that look like guaranteed deaths.

The cause is the way the game uses fixed rectangular hitboxes on irregularly shaped pixel art. Most of the time the rectangles approximate the visible shapes closely, but on the smallest cactus sprite the gap between hitbox and pixel art is just wide enough for the ducked dino to slip through.

4. The day-to-night transition hang

Every so often, the game’s color palette flips from light mode to dark mode (and back) as your score climbs. The transition takes a few hundred milliseconds and is normally smooth. But on some builds, if you tab away from the game during the transition, the screen freezes in a half-flipped state when you return — partial dark sky, light ground, weird stripe through the middle. Tabbing away again and back usually clears it.

This is a rendering bug, not a gameplay one. The game keeps running underneath; you just can’t see it correctly until the next palette flip resyncs the visuals.

5. Cactus phasing on resize

Resize the browser window in the middle of a run and the obstacle positions sometimes don’t update correctly on the same frame. The result: a cactus that visually appears in one position but collides at another, or — more rarely — a cactus that you can run through entirely as if it weren’t there. It’s a frame-timing bug related to how the game recalculates the play area on viewport changes.

Easy to reproduce: start a run, then drag the window edge mid-jump. Most of the time nothing weird happens, but sometimes a cactus ghosts through.

6. Pterodactyl invisible at extreme heights

The pterodactyl has three altitudes: low, middle, high. On very high-DPI screens (4K and above), the high-altitude bird sometimes spawns above the visible play area entirely. It’s still in the game world, still moving across the screen, just rendered above the canvas’s visible region. You don’t get hit (the dino’s hitbox is far below), but it looks like a phantom obstacle that never appeared.

This is a viewport scaling issue. The play area has a fixed pixel height in the source, and certain very-large screen configurations push the high-altitude bird’s Y coordinate past the rendering bounds.

7. The double-score audio cue

If you cross two 100-point milestones within the same frame (which can happen at very high speeds), the score chime occasionally fires twice in immediate succession. It’s not really a glitch — the game is correctly recognizing both milestones — but it sounds wrong, like a hiccup in the audio. Veterans treat it as a signal that they’re playing well: the double chime means a fast run.

8. Game over on the very first jump

The rarest one, and the most frustrating when it happens. Occasionally, on the very first input of a session, the dino’s jump animation starts a frame late and the dino collides with the first cactus before it leaves the ground. The cause is a one-frame initialization delay when the game loop boots — the first input fires before the dino’s state machine is fully ready.

It’s not common. But if you’ve ever pressed space, watched the dino just… stand there, and game-over’d immediately, you’ve hit this one. The fix is to start the game with any input first (tap, click, key press) to let the loop initialize, then start your real run.

9. Score reset on idle tab

Leave a Chrome Dino session paused (after a game over but before you restart) in an inactive tab for long enough and the localStorage entry for your high score sometimes fails to write. Come back, start a new run, beat your previous best — and the previous best is gone, so the new score becomes your benchmark. Not destructive (your new score saves fine), but mildly annoying if you were chasing a milestone.

10. The “phantom flap” sound

Very occasionally, the pterodactyl’s wing-flap animation triggers an audio frame that wasn’t supposed to be there. There’s no actual flap sound in the game’s audio sprite — the bird’s flap is silent by design — but the audio context occasionally produces a brief blip when the wing position changes. Pure curiosity, but if you’ve heard a noise you couldn’t explain mid-run, that might have been it.

What about mods?

Many of these glitches have inspired full-blown mods. There are dino game variants with intentionally infinite jumping, no-collision modes, and physics-bending power-ups, all built on top of the open-source T-Rex Runner. For a roundup of the community’s best mod work, see our list of Chrome Dino mods. The bugs above are the unintentional ones; the mods are the intentional ones.

Frequently asked questions

Does the Chrome Dino game still have an infinite-jump bug?

In current Chromium builds, the original bug is patched. Some older mirrors and unofficial copies of the source still have it. The console immortality trick (Runner.instance_.gameOver = function(){}) works on all current builds and serves a similar purpose.

Can you cheat in the Chrome Dino game?

There’s no online leaderboard, so “cheating” only matters for personal high-score chasing. The console trick that disables game-over is the most common way players give themselves immortality. The infinite-jump bug, where it still works, has a similar effect.

Why does the screen sometimes freeze in the Chrome Dino game?

Usually it’s the day-to-night palette transition hanging when the tab loses focus mid-flip. Tabbing away and back, or scrolling the page, typically resyncs the rendering. It’s a visual bug, not a gameplay one.

Is the Chrome Dino game’s source code public?

Yes. The T-Rex Runner is open source under a BSD-3 license and lives in the Chromium tree. A community-maintained mirror at github.com/wayou/t-rex-runner makes it easy to read and fork without checking out all of Chromium.

Do these glitches affect my high score?

Only locally. The Chrome Dino game stores high scores in browser localStorage on your own device — there’s no online ranking system to be affected. Whatever you score, with or without glitches, only ever shows on your own screen.

The takeaway

For a game that fits in a single open-source file, the T-Rex Runner has accumulated a surprising amount of folklore. Most of these glitches are harmless, a few are useful, and one or two are the kind of thing that makes you cackle when they happen mid-run. Try them out for yourself on the offline dinosaur game — the console trick is the easiest to start with.

Related: How to Trigger Chrome Dino’s Hidden Night Mode · How to Play Chrome Dino on iPhone (Browser & Workarounds) · How the Pterodactyl Works in Chrome Dino