Works with your stack
Cookie consent for Beaver Builder
background videos wait too
Beaver Builder sets no cookie on your visitors’ pages. Its videos are what matter: a YouTube background on a row loads YouTube on every visit, before any choice. Cookie Rocks holds that background until the visitor agrees.
By Beaver Builder · wpbeaverbuilder.com · WordPress.org
Is this your product? Tell us if anything here is out of date. Write to us
Beaver Builder
WordPress plugin
- Tested version
- 2.11.1.2
- How
- Tested automatically around each Cookie Rocks version
- Last test
- 7 November 2026
- Latest version
- 2.11.1.2 tested
- Active installs
- 100,000+
What Beaver Builder adds to your visitors’ browser
No trackers In our test of Beaver Builder 2.11.1.2 on 7 November 2026, the plugin itself added no tracker and no cookie. What you place in your pages with it, such as a video or a map, still counts.
What matters for consent with Beaver Builder
YouTube backgrounds are held
A row with a YouTube background video loads YouTube’s player script on every visit. Without a banner that handles it, YouTube sets its cookies on the first page. Cookie Rocks holds it: nothing from YouTube loads before the choice.
The Video module
In embed mode, the Video module writes a standard YouTube or Vimeo iframe. In lightbox mode the iframe is still in the page, only hidden until the preview is clicked.
Google Fonts: one stylesheet
A Google font used in a module or the global style loads from Google’s servers, and Beaver Builder merges the theme’s Google Fonts into the same request. Fonts from the WordPress font library are served from your site. See Fonts.
Cookie Rocks with Beaver Builder
- Stays out of its visual editor: no banner and no blocking while you design.
What our tests found on Beaver Builder
Set before the choice · Cookie RocksWordPress video players wait for consent
Since Cookie Rocks 2.11.1, the YouTube header video of WordPress, the [video] shortcode with YouTube or Vimeo, the video widget with YouTube, and the Beaver Builder Video module in lightbox mode send nothing before the choice or after Reject all. After Accept the video starts without a reload.
Seen in our tests, 6 November 2026, Cookie Rocks.
Good to knowYouTube and Vimeo background videos wait for consent
- Held without a box: the section shows its fallback image or colour.
- After consent: muted, looped, no reload.
- A video hosted on the site (MP4, WebM) plays for everyone.
Read in its code, 4 November 2026.
Full detail
A YouTube or Vimeo background video of a section or container (Elementor, Kadence, Beaver Builder) is held without any box until consent: the section shows the builder's fallback image, or its background colour. After consent it starts muted and looped, without a reload; visitors who refuse never see it. A background video hosted on the site (MP4 or WebM) is never held and plays for everyone, so it is the better choice for a hero section, with a fallback image set in any case.
Good to know · Beaver Builder LiteBeaver Builder background videos start after consent, without a reload
Held until the choice, then the YouTube or Vimeo background starts without a reload.
Seen in our tests, 3 November 2026, Beaver Builder Lite 2.11.1.2.
Full detail
With Cookie Rocks Pro, a YouTube or Vimeo background video on a Beaver Builder row loads nothing before the choice. After Accept all, without a reload, the player script loads and Beaver Builder builds the muted background player in the row; on the next page it starts at once. Beaver Builder waits for the YouTube player script on its own, so no extra code is needed.
Set before the choice · Beaver Builder (Lite)Beaver Builder YouTube background videos set cookies on the first page
Background videos load the YouTube or Vimeo player script on every visit. Without a banner that handles it, YouTube sets five cookies. Cookie Rocks holds the YouTube background.
Seen in our tests, 16 October 2026, Beaver Builder (Lite) 2.11.0.6.
Full detail
A YouTube or Vimeo background video on a Beaver Builder row enqueues www.youtube.com/iframe_api (handle youtube-player) or player.vimeo.com/api/player.js (vimeo-player) as ordinary script tags on every visit, then builds the player in JavaScript. Without a banner that handles it, YouTube sets YSC, VISITOR_INFO1_LIVE, VISITOR_PRIVACY_METADATA, __Secure-YNID and __Secure-ROLLOUT_TOKEN on the first page. Cookie Rocks holds the YouTube background: in our test, nothing from YouTube loaded and no cookie was set before the choice.
Good to know · Beaver Builder (Lite)Beaver Builder's video lightbox keeps the video frame in the page
In embed mode the Video module writes WordPress's standard video frame. In lightbox mode the frame is still in the page, only hidden, and opens when the preview image is clicked.
Read in its code, 16 October 2026, Beaver Builder (Lite) 2.11.0.6.
Full detail
Beaver Builder's Video module in embed mode writes WordPress's standard oEmbed iframe into the page. In lightbox mode the iframe is still in the HTML, only hidden (mfp-hide), and Magnific Popup opens it when the preview image chosen by the author is clicked.
Good to know · Beaver Builder (Lite)Beaver Builder Lite sets no cookie but loads Google Fonts from Google
It has no consent signals and no storage on visitor pages. A Google font loads from fonts.googleapis.com; fonts from the WordPress font library are served locally.
Read in its code, 16 October 2026, Beaver Builder (Lite) 2.11.0.6.
Full detail
Beaver Builder Lite sets no cookie and uses no browser storage on visitor pages; its localStorage keys exist only in the page editor. It has no WP Consent API or Consent Mode code and does not move iframe src to data-src. When a module or the global style uses a Google font, it loads fonts.googleapis.com, and it merges the theme's Google Fonts stylesheets into one new handle (fl-builder-google-fonts-<md5>). Fonts from the WordPress font library are served locally.
How we test it
Around each version, with its latest release
Around each Cookie Rocks version, a fresh WordPress installs its latest version from WordPress.org next to Cookie Rocks and runs the same checks. A new version joins the next run on its own.
- Beaver Builder 2.11.1.2, tested on 7 November 2026.
- The banner shows, the trackers of the test page wait for consent and load after it, and Cookie Rocks raises no PHP error.
- Settings of the test: Default settings after activation.
- Last run: Beaver Builder 2.11.1.2 on 7 November 2026, with WordPress 7.1.3.
Page builders and themes
Other plugins of the same kind.
Questions
Does Beaver Builder store anything for visitors?
No. Its browser storage is used only in the page editor. It has no consent code of its own.
What happens after the 30-day trial?
The banner, your visitors’ choices and your proofs of consent keep working. Without a key, most settings lock, updates and support stop. Take a key at any time and everything opens again.
For Beaver Builder sites
Your rows keep their videos, after the choice.
background videos wait too
Every feature of the complete plugin for 30 days, no card. Beaver Builder keeps working as it does today.
- During the trial: everything, including the full settings and the scans
- After 30 days without a key: the banner, your visitors’ choices and your proofs of consent keep working
- What waits for a key: most settings, updates and support
Get your trial key
Your e-mail and your site. Your key arrives as soon as you confirm your e-mail.