How to stop videos from autoplaying in Chrome on Mac: what works and what doesn't

Autoplay is when a video starts before you press play. You open an article, a clip starts, and the sound jumps out before you find the tab. Most people want the sound off first. Many also want the video to stop starting on its own. Chrome handles those two wishes differently, so it helps to know which one you can fix.

What Chrome on Mac can and cannot block

Chrome gives you control over sound, not over starting. The Sounds setting in Site settings decides whether a site can play audio. Google's Chrome Help page describes it that way. The same page does not mention autoplay, and it does not name a Mute option. That gap explains why older guides and newer ones describe different menus.

Chrome's developer documentation has the detail that matters most. Muted autoplay is always allowed. A site can start a video with the sound off. Blocking audio will not stop the picture from moving. Google's developers describe the autoplay policy in their blog, and they document no switch for users.

Turn off sound for one site in Chrome

Start with the site that annoys you most. Open it in Chrome first, so the address bar shows its address. The per-site controls apply only to the site you are on. Changes save automatically, so there is no Save button to look for. Then follow the steps in this guide to reach the Sounds control.

Labels will not always match what you see. Google's help page uses the name Sounds. Third-party guides describe Mute and Automatic (default) options, but Google does not confirm those names. Read the choices in the menu. Then pick the one that stops the site from playing audio.

Why a muted video still starts

Chrome's autoplay rules decide what a video can do on its own. Chrome 66 tightened autoplay for audio and video elements in April 2018. Under those rules, muted autoplay is always allowed. Autoplay with sound needs one of a few conditions. The list below shows them.

• Muted autoplay is always allowed.
• You have interacted with the site first.
• The site has crossed the desktop Media Engagement Index threshold.
• The site is an installed PWA on desktop.

The engagement rule explains why some sites get sound after a while. Chrome counts a playback toward a site's index only in certain cases. The playback must last over 7 seconds. It needs unmuted audio, an active tab, and a video larger than 200x140 px. Chrome's developer blog states those limits.

Check a site's engagement score

Chrome lets you view your own index. Click the address bar, type about://media-engagement, and press Return. The page is for viewing. This guide does not use it to block anything. Treat what you see as a clue about a site, not as a switch.

Stop autoplay on every site

No documented setting stops autoplay across every site at once. You have a few routes, and each covers something different. The per-site Sounds setting covers audio. The site's own player may cover the start. Muting a tab covers only the sound. Pick the route that fits the site, then test it.

• Per-site Sounds: blocks audio on that one site. Repeat it for each site.
• The site's own player: some video sites show an autoplay control near the play button.
• Muting the tab: silences sound, but the video keeps playing.
• A Chrome extension: some guides name Disable HTML5 Autoplay. Its status is unverified.

Permission prompts and what the buttons mean

Some sites ask to use a feature, and Chrome shows a permission prompt. Google's help page lists three choices: Allow this time, Allow while visiting the site, and Never allow. Use Allow this time for a single use. Use Never allow when you want that feature blocked for the site.

Mistakes people make

The most common mistake is following an old guide. A Macworld article from September 21, 2017 covers macOS Sierra and High Sierra. It relies on Flash and on a Chrome > Preferences menu. Current Chrome uses More > Settings, so skip any step that sends you to Preferences.

Another mistake is trusting mute as a fix. Muting silences the sound, but the video still plays on screen. Stopping the picture is a different job, and the options for it are limited. Test a video for at least a few seconds before you decide the setting works.

A third mistake is testing too early. Reload the tab after you change the setting. A page that is already playing may still reflect the old state. Then start the video again and listen for sound.

Requirements and versions

Chrome on Mac requires macOS 13 Ventura or later. Google's system requirements page gives that minimum but gives no date for it. On an older release, current Chrome will not run. Update macOS first, then return to these steps.

I could not confirm the current stable Chrome version from an official page during research, so this guide names no version number. Menu labels here follow Google's help pages. If your window shows different wording, pick the closest match and keep going.

Next steps if a video still plays sound

Start with the one site that bothers you. Confirm that Sounds now blocks audio for it. Reload the tab and play the video again. If sound still comes through, check whether the site's own player or an extension is causing it. Then repeat the same steps for the next site on your list.