Home > Chrome Dino Game > Cheats & Hacks

Chrome Dino Game – Cheats, Hacks & Tips for High Scores

Chrome Dino (also called the “No Internet Game”, T-Rex Game, or Dinosaur Game) is one of the most famous hidden games in Google Chrome. Millions of players have spent countless hours jumping over cacti while waiting for their connection to come back.

In this guide, you will learn:

• How Chrome Dino works and how scoring is calculated.
• Legit tips to improve your high score without cheating.
• The most popular Chrome Dino cheats and hacks using the browser console.
• How to edit the score, adjust speed and experiment with advanced tweaks.
• Common issues when cheats don’t work and how to fix them.

How the Chrome Dino game works

The concept is simple: your T-Rex automatically runs through the desert and obstacles come from the right side of the screen. You avoid them by jumping or ducking. The longer you survive, the faster everything moves and the more your score increases.

• Space or ↑ – jump
• ↓ – duck / fall faster
• Any collision with a cactus or bird – game over

At certain score milestones, the background flips between day and night, forcing your eyes to adjust to slightly different contrasts. This doesn’t change the mechanics, but it makes long runs more demanding.

Legit high score tips (no cheats required)

Before diving into full-blown cheats, it’s worth squeezing as much performance as possible from legitimate play. These tips will help you improve even if you never touch the console:

• Play in full-screen mode. Fewer distractions means better reaction time.
• Ignore the score counter. Focus on obstacles and your timing, not on the number climbing.
• Disable notifications. Pop-ups and alerts will ruin good runs at high speed.
• Use a reliable keyboard. Input lag or key ghosting can end a run instantly.
• Train in short sessions. Several 10–20 minute sessions are better than one long tilted grind.

How to open the JavaScript console for cheats

Most Chrome Dino cheats work by calling functions on a global Runner object from the browser console. To open the console:

1. Open the Chrome Dino game (offline page or type chrome://dino in the address bar).
2. Press F12 or Ctrl + Shift + I (on Mac: Cmd + Option + I).
3. Switch to the Console tab.
4. Paste any of the commands from this guide and press Enter.

Classic Chrome Dino cheats – immortal Dino, speed, slow-motion

Make the Dino immortal (disable gameOver())

The most popular Chrome Dino hack simply disables the game over function. That means no matter what you hit, the game keeps going:

After you run this command, crashing into cacti or birds won’t end the run. This is perfect if you just want to watch the game at crazy speeds or test visual tweaks without constantly restarting.

Change the game speed

You can also change how fast the Dino runs by calling the speed setter:

The default speed is much lower. Try values like 8, 10 or 20 to see how quickly the game becomes almost impossible. This is an easy way to simulate high-level play instantly.

Slow-motion mode

On the other hand, you can use the same function to slow the game down and make it more accessible:

Slow-motion is useful if you want to practice reading obstacle patterns or if you find the default speed too stressful.

Simple auto-jump bot

A tiny JavaScript snippet can act as an auto-jump bot by checking the next obstacle every few milliseconds and triggering a jump when it gets close:

This script is intentionally simple and not perfect. Think of it as a starting point to build smarter bots that consider obstacle type, Dino state and speed.

More advanced Chrome Dino console tweaks

Once you’re comfortable with basic cheats, you can start experimenting with deeper tweaks. These won’t always work the same way in every Chrome version, but they show what’s possible when you explore the Runner.instance_ object.

Adjust gravity and jump height

In many builds, the Dino’s jump is controlled by configuration values such as gravity and initial jump velocity. By changing these, you can create floaty jumps or short, punchy hops:

Lower gravity values usually make the Dino stay in the air longer; higher gravity will pull it down faster. Play with the numbers until you find a jump profile that feels fun.

Changing obstacle spacing

Obstacles are spawned by a horizon manager that decides how far apart they should be, based on speed and random variation. If you find the configuration, you can increase the gap between obstacles:

Larger gaps reduce the number of tight jumps and make the game feel less hectic. Setting the gaps too small will produce unfair clusters; setting them too high can make the game boring.

Experimental teleporting and position tweaks

Internally, the Dino’s position is just a coordinate. In theory, you can “teleport” it by manipulating that position directly or by shifting obstacles away. This is much more fragile than simply disabling gameOver(), but it’s an interesting way to explore how the engine reacts.

If you like this kind of experimentation, try logging Runner.instance_ in the console, expand its properties and see what changes when you run and jump.

Editing the score for fake “high scores”

Another classic trick is modifying the score counter directly. This doesn’t improve your skill, but it’s amusing to see an absurd number on the scoreboard or test how your UI handles large values.

Replace 9999 with any value you want. Keep in mind:

• This only affects your local game – there is no official global ranking.
• It’s useful for testing score UIs in your own Dino clones.
• If you post screenshots, be honest that the score was edited, not earned.

Using cheats in Dino clones like Run Dino Run

Most Dino clones, including Run Dino Run, are inspired by the original game but implemented with their own codebase. That means they do not necessarily expose a Runner object with the exact same methods.

Still, the general principles carry over:

• There is usually a main game instance managing state and rendering.
• That instance tracks Dino position, speed, obstacles and score.
• There is some sort of update loop that moves everything every frame.

If you open DevTools and inspect the game scripts of a clone, you can:

• Search for keywords like speed, gravity, jump, gameOver.
• Find the main class and its instance on window or some global namespace.
• Write your own console snippets to modify properties at runtime.

Once you understand how cheats interact with the original Chrome Dino engine, it becomes much easier to adapt the same ideas to Dino-style games built by other developers.

Common problems when Chrome Dino cheats don’t work

If you paste a cheat and nothing happens, or you get errors in the console, it usually comes down to one of these:

• You’re not on the real Chrome Dino page.
  Many websites host copies of the game that don’t use the same internal Runner structure. Cheats written for chrome://dino won’t work on a different implementation.
• The internal code changed.
  Chrome updates can rename properties or change function signatures. A snippet that used to work may now log undefined. Try typing Runner.instance_ and exploring its properties manually.
• Wrong console context.
  If the page uses iframes, DevTools might be running commands in a different frame. Check the small context selector at the top of the console and ensure you’re targeting the frame that contains the game.
• Extensions interfering.
  Certain browser extensions can inject code or alter the page. If something behaves oddly, try repeating the process in Incognito mode with extensions disabled.

Ethical and practical use of Dino cheats

Chrome Dino is a single-player offline mini-game, so you’re not ruining anyone’s ladder or ranked mode by experimenting with cheats. Even so, it’s useful to keep a few simple principles in mind:

• Use cheats as a learning tool. They’re a great gateway into understanding how endless runners are built.
• Separate real runs from cheat runs. If you care about your genuine high scores, track them in sessions where cheats are off.
• Be transparent online. When sharing screenshots or clips, mention if you used console commands.
• Respect other people’s systems. Don’t abuse bugs or cheats on sites where scores are part of a public competition.

With that mindset, Chrome Dino cheats stop being a way to “break” the game and instead become a sandbox for exploration and learning.

Chrome Dino cheats – quick summary

To wrap things up, here are the key console commands and concepts covered in this guide:

• Immortal Dino: override Runner.prototype.gameOver so the game never ends.
• Speed control: Runner.instance_.setSpeed(value) for slow-motion or ultra-fast runs.
• Auto-jump bot: use setInterval to call tRex.startJump() before obstacles.
• Score editing: modify distanceRan and call updateDistanceMeter() to fake scores.
• Advanced tweaks: experiment with gravity, jump velocity and obstacle gaps inside Runner.instance_.
• Clones: adapt the same ideas to other Dino-style games by finding their main game object.

Whether you use these cheats purely for fun, for practising JavaScript, or as research for creating your own endless runner, the Chrome Dino game is a surprisingly rich playground hiding behind a simple “No internet” screen.