Overview

Who is this for?

• Websites that don’t use WordPress automatic embeds
• Performance-focused sites looking to remove unnecessary frontend functionality
• Agencies optimizing WordPress installations for clients
• Sites that prefer manually controlled video and media embeds
• Developers looking to reduce unused WordPress scripts, routes, and features

Features

Use Cases

Frequently Asked Questions

• What does Disable oEmbed Auto-Embeds do?

  It disables WordPress’s public-facing automatic oEmbed functionality, including frontend auto-embeds, the shortcode, wp-embed script, discovery features, embed rewrite rules, and the public oEmbed REST route.

• Does it disable oEmbed inside the WordPress editor?

  Not completely. The module keeps the functionality required by authenticated users who can edit posts so the WordPress editing experience isn’t unnecessarily disrupted.

• Does it remove the wp-embed JavaScript?

  Yes. The public wp-embed script is deregistered when the module is active.

• Does it disable the WordPress oEmbed REST endpoint?

  It removes the public oEmbed REST route for visitors. Authenticated users with appropriate content-editing capabilities can still use it.

• Will pasted URLs still automatically embed on the frontend?

  New visitor-facing automatic embeds are disabled while the module is active.

• What about existing embed blocks?

  Existing embed blocks may still render depending on how the content was created and stored. The module primarily prevents WordPress’s public auto-embed functionality.

• Should I enable this if my site relies on [embed]?

  No. If visitors rely on content generated through the shortcode or your site depends heavily on WordPress’s public oEmbed functionality, you should leave this module disabled.

• Are there any settings to configure?

  No. Disable oEmbed Auto-Embeds is designed as an enable-and-run module.