Mave for WordPress
Most organizations that use WordPress want video to feel simple.
They simply want to publish a customer story, add a product video, share an internal update, or make a campaign page more engaging. But video in WordPress is often more complicated than it should be.
Teams either upload heavy video files directly into WordPress, embed a third-party player, or rely on platforms that were not built with European privacy expectations in mind. What looks like a simple video block can introduce cookies, external scripts, tracking, consent banners, and data flows that are hard to explain.
That’s why we built a Mave plugin for WordPress.
A way to add fast, cookieless video to WordPress, directly from the block editor.
Video should fit the way teams already work
WordPress is still one of the most widely used content management systems. For many marketing, communications, and content teams, it’s where the website comes together.
If video requires a developer every time, it slows teams down. If video is easy to add but difficult to approve from a privacy perspective, it creates another kind of friction. And if video works visually but adds tracking in the background, it does not really fit the needs of many European organizations.
Editors should be able to add video where they are already working. Developers should not have to maintain heavy custom integrations. Privacy and legal teams should not have to review a new tracking layer every time video is added to a page.
Video should be part of the content workflow.
A Mave video block for Gutenberg
The new Mave plugin adds a dedicated Mave Video block to the WordPress block editor.
That means editors can add Mave videos directly inside Gutenberg, just like they add other content blocks. They can upload new videos to Mave, choose existing videos from the Mave library, and publish them with a fast, cookieless player.
The plugin supports direct uploads to Mave, so editors do not need to leave WordPress to add a new video. It also includes a library picker, with support for collections. This makes it easier to work with larger video libraries, campaign groups, internal content sets, or structured publishing workflows.
For teams that want a consistent brand experience, the plugin includes global player defaults. Administrators can configure the standard player theme and color once, while editors can still override those settings per block when needed.
And for teams that still rely on shortcodes, the plugin supports a [mave_video] shortcode as well.
We made it simple for editors, flexible for teams, and lightweight for developers.
Built for privacy from the start
The Mave WordPress plugin is built around the same principles as Mave itself. Cookieless video. No cross-site tracking. No advertising identifiers. No viewer profiling.
When a Mave video is rendered on a WordPress page, the browser loads the Mave component and video resources from Mave’s video delivery infrastructure. Playback events may be used for aggregate video analytics, but not to track people across websites or build viewer profiles.
This gives teams useful insight into how video performs, without turning every viewer into a data source.
Safer configuration for WordPress teams
A video plugin should not make sensitive access easy to expose.
That is why the Mave API key is stored server-side in WordPress options. It is not exposed to public visitors. Editors also do not receive direct access to the API key. Their requests go through WordPress REST routes.
This keeps the workflow simple without making the setup careless.
Administrators can configure the Mave API key once. They can also define an upload target, so uploads from WordPress can be scoped to a specific Mave collection. From there, editors can work with video in a way that feels natural inside WordPress.
Part of a broader CMS approach
The WordPress plugin is not our first CMS integration.
We previously built a Statamic addon, supported the Sitebox CMS from CARE, and created a custom integration for Mett. Each integration had the same goal: make privacy-friendly video easier to use inside the systems teams already rely on.
Because every organization has its own digital architecture.
Some teams work in WordPress. Others use Statamic, Sitebox, a custom platform, or a headless setup. Some need a simple editor-friendly block. Others need an API-first workflow that fits a broader digital ecosystem.
Mave is designed to support both.
A lightweight embed when you want speed, an API when you need control, and a CMS integration when video should flow directly into the editorial process.
A better default for WordPress video
WordPress makes publishing accessible. Mave makes video private, fast, and easier to control.
Together, they give teams a better default for adding video to their websites.
- Upload a video.
- Choose one from your Mave library.
- Set the player style.
- Publish it inside the block editor.
- Deliver it through a fast, cookieless player.
All without tracking, complicated implementation and the need to choose between ease of use and privacy.
With the Mave plugin for WordPress, European organizations can bring privacy-friendly video directly into their everyday publishing workflow.
Ready to make video simpler in WordPress?
Install the Mave Video plugin and start publishing privacy-friendly video directly from your editor.
