Stop Autoplay Video Ads on Recipe Sites: A Complete Guide

Survey any group of people who cook from online recipes and one complaint comes up every time: the video. Not recipe videos — those are often useful. The autoplay video ad that starts blaring before you've found the ingredient list, the sticky video player that follows you down the page after you've tried to close it, the video that reloads itself when you accidentally scroll back to the top.

This is the #1 complaint about recipe sites. It's been the #1 complaint for years. It hasn't gotten better, because video ads pay more than almost any other format, and the economics aren't changing.

Why Recipe Sites Are So Aggressive About Video

Video advertising commands dramatically higher CPM rates than standard display advertising. Where a banner ad might earn $3-8 per thousand impressions, a pre-roll or mid-roll video ad earns $15-30 per thousand on the same audience. A sticky video player — one that stays visible and keeps cycling through ads as you scroll — can generate significantly more revenue than an equivalent amount of screen real estate in static ads.

Recipe sites discovered this calculus and acted on it. The typical implementation now is a video player embedded in the article content that, once triggered, sticks to the bottom corner of your screen as you scroll. It plays ad after ad, often with no sound initially (muted autoplay is allowed under browser policies), but with unmissable visual motion. Click anywhere on the player and it unmutes. Try to close it and it may briefly disappear before reappearing when you scroll back.

The most sophisticated implementations use a persistence mechanism — if you close the player, a timer fires and it reappears. If you scroll back past the original embed point, it re-anchors. Some players detect when you're trying to navigate away and resize themselves to fill more of the screen.

The Technical Landscape

Autoplay video on recipe sites typically comes from a few sources:

• Ad network video units: Mediavine, AdThrive, and Raptive all provide video player products that recipe bloggers add to their sites. These are distinct from the ad blocker evasion tools the big media companies use, and they're somewhat more susceptible to standard ad blockers.
• Corporate media video players: Dotdash Meredith, Hearst, and other large publishers run their own video infrastructure. These players are built to survive ad blockers and are continuously updated to stay ahead of block lists.
• Embedded YouTube/third-party players: Some recipe videos are embedded YouTube clips with YouTube's own ad system. These behave differently and don't have the sticky persistence of native ad players.

Browser Settings: What Works and What Doesn't

Every major browser has autoplay settings, and they all have limits.

Chrome

Go to Settings → Privacy and Security → Site Settings → Additional content settings → Sound. You can mute specific sites or all sites by default. This doesn't stop the video from playing — it just starts muted. The visual motion continues, and many sites detect muted playback and show a large "Click to unmute" button that blocks the content.

Chrome also has a "Block autoplay" option per site. Right-click the lock icon in the address bar, go to Site Settings, and set Sound to Block. Again, this mutes rather than stops the video on many sites.

Safari

Safari on macOS has the strongest built-in autoplay controls. Go to Safari → Settings → Websites → Auto-Play. You can set "Stop Media with Sound" site-by-site or for all sites. Safari's implementation is more aggressive — it actually prevents video from starting in many cases, not just muting it. On iOS, autoplay for videos with sound is blocked by default and has been for years.

Firefox

Firefox offers similar controls under about:preferences → Privacy & Security → Autoplay. Block audio and video autoplay is available as a global setting. Firefox's enforcement is reasonably effective against standard video embeds but can be bypassed by players that use JavaScript to manually start playback rather than relying on the HTML autoplay attribute.

Why Browser Settings Don't Always Work

The browser settings above work against video players that use the HTML5 autoplay attribute — the standard, straightforward implementation. Recipe site video players from major ad networks don't work that way.

They use JavaScript to manage playback: the video element loads without autoplay, then a script detects when the player scrolls into view and calls video.play() programmatically. This bypasses the browser's autoplay blocking because from the browser's perspective, a user script is requesting playback, not the page's initial load. The browser can't distinguish "user clicked play" from "script called play() on a timer."

Some players go further: they initialize with a static image, then swap in the video element only when the play call is ready, so the browser never sees an autoplay video — it sees a regular image that later becomes a video that immediately starts playing.

This is a long-running arms race. Browser makers add blocking; video players update to circumvent it; repeat. As of 2026, browser settings reduce the problem but don't eliminate it, especially on desktop Chrome where the autoplay restrictions are weakest.

Ad Blockers and the Video Gap

uBlock Origin is the most effective ad blocker available and it handles many video ad units, particularly from ad network video players. But the major corporate media players — the ones on Food Network, Allrecipes, The Kitchn — are specifically built to resist blocking. They're hosted on the same domain as the site, use randomized script names, and update regularly to stay off block lists.

There are filter lists specifically targeting video ads on recipe sites, and some are included in uBlock Origin's extended lists. Adding EasyList, EasyPrivacy, and the uBlock Origin supplemental lists covers more cases. But coverage is incomplete and requires periodic maintenance as the block lists update.

The Extraction Approach

The most complete solution to autoplay video on recipe sites isn't blocking — it's leaving. When you extract a recipe to a clean viewer, you're not on the original site anymore. There are no video players because no video infrastructure was loaded. There are no scripts managing playback because the extracted page has no ad scripts at all.

Ad-free recipe viewing via extraction strips out everything: the video players, the sticky banners, the newsletter modals, all of it. What you get is a page that contains only the recipe content, formatted for cooking — ingredients embedded in steps, servings scaler, Cook Mode to keep the screen awake.

The tradeoff is that you lose access to the original site's recipe videos, which are sometimes actually useful. Recipe videos from skilled recipe developers — not the autoplay ad filler — can help you understand techniques or see what the finished dish should look like. If you want the video, you need the original site.

The practical split: use extraction for cooking from the recipe. Open the original in a separate tab if you want to watch the video first. You get the legitimate recipe video content and the clean cooking experience without the ad video following you around the page.

RecipeStripper handles the extraction — copy the URL, paste it, get the clean version. No installs, works on phones and tablets where browser extensions aren't available.