WordPress Plugin Video: What to Make for Your Listing

Every plugin in the WordPress.org directory gets the same page: an icon, a banner, a handful of screenshots and a readme. Your competitors get exactly the same slots, and a screenshot of one settings screen looks a lot like a screenshot of another. A WordPress plugin video is one of the few things on that page that can actually show a site owner what installing your plugin will be like, and in most categories, very few listings bother to have a good one.

I manage a lot of these projects, and the conversations tend to start the same way: "we need a video for the plugin." Usually what the team actually needs is three different pieces doing three different jobs, and the one they were picturing is not the one that will save them the most time. This guide covers what those pieces are, how to film wp-admin without boring everyone, what directory guidelines mean for your demo, and how we run plugin projects on our WordPress video and motion page.

Why every plugin listing looks the same

The directory is a fair fight with a fixed layout. That is good for users and hard for marketers. Someone comparing five backup plugins or five membership plugins is not carefully reading feature lists. They are scanning for whichever one makes them feel confident that installing it will not break their site.

That decision is made on comprehension, not features. And comprehension is where static screenshots struggle, because the interesting part of most plugins happens between screens: you toggle a setting, something on the front end changes, and a number somewhere moves. A still of the settings page cannot show the cause and the effect together. A thirty second clip can.

The second problem shows up after the install. Plugin businesses tend to run lean, and support inboxes fill with setup questions that the readme already answered. Every one of those tickets is paid for in founder or developer hours, not in marketing budget, which is why the most valuable video a plugin business owns is often not the marketing one at all.

The three videos a plugin business actually needs

1. The demo, cut for the listing and your site

This is the one people picture. It needs to work in two places at once: your marketing site's hero, and the plugin description on WordPress.org, where a YouTube or Vimeo URL on its own line in readme.txt embeds directly in the listing. That second home changes how you cut it. The viewer has not read anything above it, the thumbnail is small, and there is a good chance they are watching with the sound off.

So the demo opens on a visible result, not a logo. The page that loaded slowly now loads fast. The empty forum now has a thread in it. The mechanism comes after, and only as much of it as earns trust. Our PixJet case study is built this way: it leads with a before and after of a bloated page turning into a fast one, and puts the compression and CDN delivery in the background rather than the headline.

2. The setup tutorial, cut per task

This is the one that pays for itself. It shows install to working result on the real settings screen, with nothing skipped. The key word is "per task". A twelve-minute tour cannot be linked from a support reply, because nobody will scrub through it to find their answer. Four short clips, each answering one question, can each be pasted into a canned reply.

PixJet uses its setup tutorial exactly like that, linked from both support responses and the plugin page. We will not promise you a specific drop in tickets, and nobody honest can. But the mechanism is simple: your team stops retyping the same answer, and the user gets to watch it instead of reading it. Our how-to and tutorial video service covers the capture and chaptering side in detail, and we wrote a full post on using tutorial videos to reduce support tickets.

3. The promo cutdowns

Short vertical and square cuts for a release announcement, a Product Hunt post, a newsletter, or the social accounts you keep meaning to post on. They come out of the same footage as the demo, so they cost a fraction of a separate production, and they keep your release week from being one post and then silence.

Which video does which job

Here is how the pieces map out. The packages in the last column are the ones plugin teams most often start with, all at fixed, published prices.

A scenario: a two-person team shipping version 2

Picture a small plugin business: two developers, a free plugin with a healthy install base, and a pro version they are about to relaunch with a rebuilt settings screen. Their current listing has no video and six screenshots of the old UI.

The instinct is to make a launch video. But walk through what happens on release day. Existing users update and land on a settings screen they have never seen. New users arrive from the directory with no idea what the plugin does. The support inbox gets both groups at once.

What that team needs is the demo for the listing, a tutorial for the new settings screen cut into three or four tasks, and a few short cuts for the release announcement. That is almost exactly the shape of our Solo Launch package: a product intro under 60 seconds, a walkthrough under two minutes, a tutorial under two minutes and five reels, for $300 on a 5-day turnaround with two revision rounds.

The one timing rule I would push hard on: capture the UI once it is frozen, not while the developers are still moving buttons. A tutorial that shows a setting in the wrong place is worse than no tutorial, because users stop trusting it.

Filming wp-admin without boring everyone

wp-admin is a hard thing to film. It is grey, dense, and full of chrome that means nothing to the viewer: unrelated menu items, notices from other plugins, a dashboard that looks identical before and after your feature runs. A raw screen recording of it is technically accurate and visually useless.

What we do before and during capture:

• Clean the environment. Only the plugins that matter, no update nags or notices from other products, and realistic demo content. A post titled "test test 123" will show up at full size in your video.
• Crop to the action. Frame the part that changes and let the sidebar fall away.
• Point at the change. The result of a setting is often a number that moved by one. Zooms and callouts direct the eye there.
• Show the front end. Site owners care about what visitors see, so cut from the setting to the result on the live page.
• Mask anything real. Emails, licence keys and customer data are masked before anything goes into an edit.

Free listing, pro upgrade, and what a demo may promise

Most plugin businesses run a free listing on WordPress.org and sell a paid upgrade. Directory guidelines are strict about how a free plugin's assets are used to sell the paid one.

So the demo that embeds in the free listing is about what the free version actually does once installed. Upgrade messaging and pro-only features go into the assets on your own site, where they will not put the listing at risk. For the image side of the listing, the official guide to how plugin directory assets work is worth reading once; we deliver banners at 772x250 and 1544x500, icons at 128x128 and 256x256, and numbered screenshots to match your readme captions.

Who this is for, and who it isn't for

This approach suits plugin and theme businesses with a stable UI, a listing that is losing comparisons it should win, or a support inbox full of the same setup questions. It also suits agencies that build plugins for clients and need a clean demo to hand over at launch.

It is not the right spend if your UI is still changing weekly. Wait until it freezes, or ask for abstracted interface shapes instead of pixel-accurate capture. And if the plugin does not exist yet, our guide to building browser extensions and WordPress plugins covers the development side, since we build plugins as well as film them.

How we run a plugin video project

From the project management side, this is the sequence:

1. Access first. A staging site or a pro licence, plus your readme, your brand files and your five most common support questions. The support questions decide which tutorials exist.

2. One named approver. Even in a two-person team, "we'll discuss it" adds a day to every gate.

3. Script and screen plan together. A word-for-word script paired with what is on screen during each line. Fix product terminology here, where it costs a line edit rather than a re-record.

4. Styleframes, then the draft. You approve the look on stills, then review a watermarked draft on a timestamped link. Feedback in one consolidated pass counts as one round, as our revision policy explains.

5. One delivery folder. Masters in every ratio, captions burned in plus .srt and .vtt files, poster frames, the directory artwork, and the editable source files, which you own on final payment.

Solo Starter runs a 3-day turnaround, Solo Launch 5 days and Startup Boost 7 days, each for the whole kit.

Frequently asked questions

Can you put a video on a WordPress.org plugin listing?

Yes. A YouTube or Vimeo URL placed on its own line inside the plugin description in readme.txt embeds in the listing. Because it sits on a page nobody has read yet, cut a version that opens on a legible result and still makes sense with the sound off.

How much does a WordPress plugin demo video cost?

With us, one demo under 60 seconds starts at $200 on Solo Starter, with a 3-day turnaround and one revision round. Solo Launch at $300 is the usual fit for a plugin release, since it adds a walkthrough, a tutorial and five reels. Startup Boost at $550 adds a feature explainer and a ten-asset social kit.

How long should a WordPress plugin demo video be?

Under a minute for the listing and site hero. The first ten seconds should show the result on their own, because many viewers stop there. Longer walkthroughs belong on your own site, and tutorials should be one task each, usually one to two minutes.

Do you make videos for WordPress themes?

Yes. The brief shifts toward front-end results and demo variety, then the customiser or builder. Themes with a page builder usually need a set of short per-module tutorials as well.

Will a setup tutorial reduce plugin support tickets?

It gives your team a clip to link instead of an answer to retype. We cannot promise a specific reduction and will not print one. Cutting the tutorial per task is what makes it linkable, and linkable is what makes it useful to support.

The takeaway

A plugin business rarely needs one video. It needs a demo that makes the result obvious on a listing where everyone else has the same slots, a setup tutorial cut into linkable tasks, and a few short cuts to keep a release visible. Film a clean wp-admin, keep the free listing honest about the free version, and capture the UI only once it has stopped moving.

The WordPress plugin and theme video page shows the full set of deliverables and asset specs, and the SaaS and app explainer service explains how the demo itself is built. Every kit mentioned here, with its deliverables, turnaround and revision count, is listed on our fixed-price video packages page. When you have a staging site ready, send us the brief and we will tell you which of the three to make first.