Chrome Dino Sound Effects: What Every Beep Means

If you’ve played the Chrome Dino game, you might think of it as a silent game. It isn’t quite. The page makes no sound until you start a run, but the moment you press space, three short sound effects take over the entire feedback loop. Here’s what the Chrome Dino sound effects are, how the code loads and plays them, and why Google built such a quiet game.

The three sounds, decoded

Open the source for the T-Rex Runner and you’ll find a sound table with three entries: BUTTON_PRESS, HIT, and SCORE. Each points to an <audio> element in the page, with the IDs offline-sound-press, offline-sound-hit, and offline-sound-reached. There is no music file and no ambient track. That’s the entire soundtrack.

The jump sound

A short blip that plays as your dino leaves the ground. The code plays it on every jump started from the ground, and it is the same BUTTON_PRESS clip that plays when you restart after a crash. The point is confirmation — you pressed space, the input registered. The sound is light enough to fire dozens of times without grating.

The score milestone chime

A brief chime that plays each time your score lands on a multiple of 100. At the same moment the score display flashes on and off a few times. It’s the only sound the game uses to mark progress.

It is not a difficulty cue, though. The game’s speed doesn’t step up at each 100 points; it rises by a tiny amount every frame until it hits a fixed cap of 13. The chime is a pacing marker, not a warning.

The game over hit

A short hit sound that plays the moment your dino collides with a cactus or pterodactyl. It’s punctuation, not a sting. The visual cue (the dino’s wide-eyed crash pose and the restart button) handles the rest. On Android phones, the same crash also triggers a 200-millisecond vibration if the browser supports it.

Why the game stays quiet until you play

The game creates its Web Audio context and decodes its sounds only when you make your first jump. Until then, nothing is loaded and nothing can play. That fits the joke: the game appears silently on the offline page, and a beep on the no-internet screen would have been an obnoxious surprise.

It also fits how browsers work. Modern browsers block audio that the user hasn’t started with a click, tap, or key press, so waiting for the first input is the polite design anyway. One side effect: because the clips decode in the background, the very first jump of a session can be silent, with sound kicking in from the next jump onward.

How to turn the sound on

On desktop, there’s nothing to enable. Press space or the up arrow to start a run and the sounds play. If you still hear nothing, check your system volume, then make sure the tab isn’t muted (right-click the tab and look for an “Unmute site” option). If you’ve blocked sound for the site in your browser’s site settings, allow it there.

On Android, the sounds normally come through once you tap to start. On iPhone and iPad, the runner code checks for iOS and skips loading the sounds altogether, so you’ll play in silence no matter what your volume is set to. Our guide to playing Chrome Dino on iPhone covers the rest of the iOS quirks.

Where the audio files live in the source

The T-Rex Runner is part of Chromium, which is open source under a BSD-style license. The audio isn’t fetched as separate files. Each clip is inlined as base64 data inside an <audio> tag within a hidden <template id="audio-resources"> block. That’s part of why the game runs offline: it has no external dependencies, including no remote audio.

At start-up, the code strips the data-URI prefix, decodes the base64 into an ArrayBuffer, and hands it to the Web Audio API’s decodeAudioData. Each sound is then played by creating a fresh buffer source node and starting it immediately. A fun detail: the data URIs are labeled audio/mpeg, but the clips themselves are Ogg Vorbis audio.

Modding the sounds

Because the source is permissively licensed, swapping the audio is a small project. You’d encode your replacement clips as base64 and substitute them into the three <audio> tags. The harder part is matching the original’s volume and length so the new sounds don’t feel mismatched against the visual feedback. For more on what the modding community has built, see our piece on Chrome Dino mods worth trying.

Why such minimalism?

The Chrome Dino’s sound design is a study in restraint. Many endless runners lean on music and layered audio — think Subway Surfers or Temple Run. The dino game does the opposite: three short cues, no music, no ambient layer, no voice. That works because runs are short and the player’s focus is on spotting obstacles. A music track would just compete for attention.

It also matches the game’s origin story. The T-Rex Runner was built by members of Google’s Chrome UX team, including designer Sebastien Gabriel, as a small Easter egg in 2014, shipped quietly inside Chrome’s offline page. A maximalist soundtrack would have undercut that “you found me” tone.

Frequently asked questions

Why doesn’t the Chrome Dino game have music?

By design. The game is meant to be a quick distraction during a network outage, not an immersive experience. Music would compete with the player’s focus on obstacles and would feel intrusive on a page that’s supposed to be a quiet error screen.

Can I turn off the Chrome Dino sounds?

Yes, but not from inside the game, which has no mute button. On desktop, right-click the tab and choose the option to mute the site. On mobile, mute the site in your browser’s settings or turn down the system volume.

Are the sound effects on dinogame.gg the same as Google’s?

Yes. dinogame.gg runs a standalone copy of the open-source T-Rex Runner code with the same three embedded clips, the same triggers, and the same iOS behavior. If you start a run on desktop, you’ll hear exactly what Chrome’s offline page plays.

How many sound effects does the Chrome Dino game have?

Three: a button-press sound on jumps and restarts, a chime every 100 points, and a hit sound when you crash. There is no music, no voice, and no ambient track.

Why is there no sound on my iPhone?

The runner code deliberately skips setting up audio when it detects iOS, so the game is silent on iPhone and iPad regardless of your volume or mute switch. It isn’t a bug in your phone.

Do the sounds change at night mode?

No. The game flips to its inverted night palette every 700 points, but the audio doesn’t change. Same three sounds, same triggers.

The takeaway

Three short sounds, no music. The Chrome Dino game’s audio is one of the smallest soundtracks in game design, and it works because the game’s whole personality is restraint. If you’ve only ever played on an iPhone, try a desktop session with the sound on — the 100-point chime turns into a surprisingly useful pacing tool. Then get back to your offline dino run.

Related: How to play the Chrome Dino game offline (every method) · Every Chrome Dino Easter egg, secret, and hidden feature · How to Play Chrome Dino on iPhone (Browser & Workarounds)