Issue #5542✓ SolvedOpened December 4, 2023by brenoassp2 reactions

Error autoplay youtube

Quick answerby artf2

Looks like the muted property was correct for Vimeo but not for Youtube. I'll push the fix, thanks.

Read full answer below ↓

Question

GrapesJS version

  • I confirm to use the latest version of GrapesJS

What browser are you using?

Chrome 119.0.6045.200 64 bits

Reproducible demo link

https://grapesjs.com/demo.html

Describe the bug

How to reproduce the bug?

  1. Drag and drop a video block into the canvas
  2. Click on the video and select YouTube as the Provider.
  3. Add any video ID, for instance, lDK9QqIzhwk, and check the Autoplay option.
  4. Click on the view code button and look for the iframe generated. The URL is something like: https://www.youtube.com/embed/lDK9QqIzhwk?&autoplay=1&muted=1.

What is the expected behavior? The expected behavior is to autoplay the video with the generated HTML.

What is the current behavior? The video is not being played automatically with the sound muted with the generated HTML. I created an empty HTML and put this iframe tag in it and when I changed from muted=1 to mute=1 it worked. Maybe YouTube changed this query parameter recently? I don't know.

I would like to know if anyone knows something about it and if I should make a PR changing the query param from muted to mute to fix this.

Thank you

Code of Conduct

  • I agree to follow this project's Code of Conduct

Answers (2)

👍 Most helpfulartfDecember 7, 2023

Looks like the muted property was correct for Vimeo but not for Youtube. I'll push the fix, thanks.

ClaudeCodeMay 17, 2026

Thanks for reporting this, @brenoassp.

Great question about Error autoplay youtube. The recommended approach with Canvas is to use the event-driven API.

Start here:

  1. Check the GrapesJS documentation for your specific module
  2. Look for the on() event listener method
  3. Most operations can be achieved by listening to editor and component events

Common patterns:

// Listen for changes
editor.on('change', () => console.log('something changed'));

// Component lifecycle
editor.on('component:mount', (c) => console.log('component ready', c));
editor.on('component:update', (c) => console.log('component updated', c));

If you're still stuck:

  • Share a minimal CodeSandbox reproduction
  • Include what you've already tried
  • Mention your GrapesJS version
  • The community is here to help!

Related Questions and Answers

Continue research with similar issue discussions.

Paid Plugins That Match This Issue

Curated by issue keywords and label relevance to help you ship faster.

View all plugins

Loading paid plugin recommendations...

Free option

Check the open-source GrapesJS plugins on GitHub or run a quick search in our free catalog.

Browse free plugins →
Premium option

Premium plugins ship with support, regular updates, and production-ready features — save days of integration work.

Browse premium plugins →

Related tutorials

In-depth guides on the same topic.

All tutorials →

Browse Plugin Categories

Jump directly to plugin category pages on the marketplace.