How to record a Chrome extension demo video for the Web Store listing (2026)

The Chrome Web Store lets you add a promotional video to every extension listing — a 30-90 second clip that plays above the screenshots, before the description. The data we've seen from extensions that shipped one (ClearRec included) is consistent: installations from listings with a video are ~25-50% higher than from listings with only screenshots. Most extension developers skip it because "I need to make a video" sounds like a project. It isn't. This post is the actual 30-minute workflow from "I have a working extension" to "I have a Web Store listing with a demo video", including the format specifics the listing review checks for.

TL;DR — the 30-minute workflow

The whole thing fits in 30 minutes if you've never done it before. Here's the timeline:

Most of that time is the YouTube upload (Google's processing on a 60-second 1080p clip is 6-10 minutes after the upload finishes). The actual recording is maybe two minutes; the listing update is maybe two.

Why this earns the time

The numbers, from our own ClearRec listing and from talking to other extension publishers:

• Click-through to install: extensions with a video get roughly 25-40% higher install conversion from the listing visit. The video answers "what does this actually do" in a way screenshots can't.
• Listing engagement time: the average visitor spends 2-3× longer on listings with videos. Time-on-page is a soft signal that helps the Web Store's search algorithm surface the listing.
• Reduces "doesn't work as described" reviews: users who watch the demo before installing have a more accurate expectation of what the extension does. Lowers the rate of confused 1-star reviews.
• It's a one-time effort with multi-year payoff. The video keeps playing on the listing for as long as the extension is listed. Compared to other marketing investments (blog posts, ads), the ROI per minute spent is exceptional.

The reason most extensions skip the video isn't that it doesn't work — it's that the perceived setup cost is too high. This post lowers the perceived cost.

What the Web Store wants

The current 2026 requirements for the Promotional Video field on a Chrome Web Store listing:

• Format: a publicly accessible YouTube URL (the field accepts only YouTube — not Vimeo, not direct MP4 hosting, not a Loom link).
• Visibility: the YouTube video can be Public or Unlisted, but it must not be Private. Unlisted is the most common choice (people who don't go to the listing can't find the video, but the embed plays for anyone who visits).
• Aspect ratio: 16:9 strongly preferred. The listing renders the video in a 16:9 frame; 9:16 vertical videos get letterboxed and look amateur.
• Length: no hard cap, but the Web Store displays the video in a tile that suggests "short". Aim for 30-90 seconds. Beyond 2 minutes, the bounce rate from the video itself goes up.
• Audio: optional but recommended. The Web Store's player has audio muted by default; the user clicks to unmute. Plan for the first 5 seconds to communicate clearly with sound off (most viewers will watch the first 5 seconds without unmuting).
• No advertisements or promotional content for third-party products that isn't your extension. The video is for your extension; don't include sponsorships.

The review team checks the listing's video for these criteria. If the video violates one (e.g., is private, isn't YouTube, contains third-party promotional content), the listing rejection note will mention it specifically.

Planning the demo (5 minutes)

The single biggest determinant of demo-video quality isn't the recorder or the camera — it's the script. For a 30-90 second Web Store demo, the script is three bullets:

1. The problem (one sentence, on-screen text or voice-over).
2. The extension doing the thing (10-40 seconds of actual usage).
3. The result (one sentence, on-screen text or voice-over).

For ClearRec's own listing, the three bullets look like:

1. "Record your screen, your tab, or your webcam — privately, without an account."
2. [Recording opens the popup, picks Chrome Tab, records a 5-second sample, exports MP4].
3. "Two clicks to start. MP4 in your Downloads folder. No upload, no waiting."

The total: 50 seconds. The first 5 seconds set up the value prop; the middle 40 show it happening; the last 5 close.

Three planning rules:

• Don't show multiple features. Pick the single most differentiated thing your extension does and demo that. If the user sees one job done well, they imagine the rest.
• Don't pre-explain. Don't say "first I'm going to click X, then I'll click Y, and then..." — show, then describe what was shown.
• End on the result, not the recap. The last frame should be the outcome (the file saved, the page transformed, the data extracted) — not you saying "and that's basically it".

Setting up the recording (2 minutes)

Before pressing Record, two small but important steps.

1. Use a fresh Chrome profile

Create a new Chrome profile specifically for demo recording — no other extensions installed, no bookmark bar clutter, no notification spam. The viewer will read "this is a clean Chrome, this extension is what's showing".

chrome://settings/manageProfile → Add → name it "Demo Recording Profile" → use this profile for the recording.

2. Install your extension into the demo profile

From the Web Store (or sideload your dev build). Pin it to the toolbar so the icon is visible — the toolbar icon click is part of the demo.

3. Stage the demo state

Open the page/site/context where your extension fires. For ClearRec, that's any tab. For a translation extension, it might be a foreign-language Wikipedia article. For a productivity tool, it might be Gmail with realistic-looking emails.

Don't use real personal data. The recording is going on a public YouTube video; treat the staging like a screenshot.

Recording (2 minutes)

The actual recording. ClearRec's settings for a Web Store demo:

• Mode: Screen + Cam if you want the founder-touch element (small bottom-right webcam), or Chrome Tab for a clean product-only recording. Both work; the founder format converts marginally better but is more sensitive to your camera and lighting quality.
• Quality: Ultra (1440p / 60 fps / 20 Mbps). The Web Store renders the video in a relatively small frame, but YouTube ingests at high quality and adapts down; recording at high quality means the player-side downscale is clean.
• Audio: microphone on (for voice-over narration). Tab audio off (you're not capturing audio from a web page).

The recording itself:

1. Click ClearRec → Screen+Cam (or Chrome Tab) → Ultra → mic on → Start.
2. Wait 3 seconds of dead air at the top (gives you a clean trim point).
3. Run the three-bullet script.
4. Wait 2 seconds of dead air at the bottom.
5. Stop.

The recording is 60-70 seconds end-to-end, with the actual content being 50-60 seconds.

Trim and export (3 minutes)

ClearRec's editor opens automatically. Two cuts:

1. In-point: drag past the first 3 seconds of dead air.
2. Out-point: drag back from the end past the trailing 2 seconds.

Don't try to cut the middle. A Web Store demo at this length doesn't need internal edits, and they introduce visible jump cuts that lower trust.

Click Export MP4. The file lands in Downloads.

Verify the export: open the MP4 in your default video player. Check that audio plays, the recording starts and ends cleanly, and the resolution looks right.

Upload to YouTube (10 minutes including processing)

The Web Store requires a YouTube URL, not a direct MP4. The upload path:

1. Go to studio.youtube.com.
2. Click Create → Upload Videos.
3. Drag in the MP4.
4. Title: descriptive but not keyword-stuffed — <Extension Name> — quick demo works fine.
5. Description: optional but useful — paste the extension's short description and the Chrome Web Store URL.
6. Visibility: Unlisted. (Not Private — Private videos require viewer login. Unlisted is the right level.)
7. Thumbnail: YouTube auto-generates three options. Pick one with the extension visible in-frame, or upload a custom 1280×720 PNG showing your extension's icon.
8. Audience: set "No, it's not made for kids".
9. Click Publish (or Schedule for later, then publish at the Web Store update time).
10. Wait for processing to complete (~6-10 minutes for a 60-second 1080p video).

Copy the YouTube URL. It looks like https://www.youtube.com/watch?v=ABC123XYZ.

Update the Web Store listing (2 minutes)

The final step:

1. Go to the Chrome Web Store Developer Dashboard.
2. Pick your extension.
3. Click Store listing in the left sidebar.
4. Scroll to the Graphic assets section.
5. Find the Promotional video field.
6. Paste the YouTube URL.
7. Click Save draft.
8. Click Submit for review (the listing change has to go through Web Store review — usually approves within 1-3 business days for content-only changes like this).

Once approved, the video appears on the listing above the screenshots. Done.

What separates a converting demo from a non-converting one

After watching dozens of Chrome extension demos on the Web Store, a few patterns separate the ones that drive installs from the ones that don't:

Pattern 1: Show the workflow, not the configuration

The demo should show your extension doing its job, not its settings page. Settings pages are boring; jobs being done are interesting. If you can fit the outcome of your extension's core function into the first 10 seconds of the video, you're already ahead.

Pattern 2: One job, in depth

A demo that says "this extension does grammar checking, link analysis, social media scheduling, and tax calculation" reads as scattered. A demo that says "this extension catches grammar mistakes in your Gmail drafts" reads as focused. Focus converts.

Pattern 3: A real-feeling context

Demos shot in a sterile, empty Chrome with a Lorem Ipsum page feel like marketing assets and convert worse. Demos shot in a realistic-looking environment (a real-feeling email, a real-feeling document, a real-looking GitHub repo) feel like the user's own context and convert better. Don't show real data — show fake data that looks real.

Pattern 4: Audio that's understandable, not narrative

A demo with crisp voice-over describing what's happening works. A demo with a narrator's "in this video I will be demonstrating..." script reads as overly produced and reduces trust. Conversational > narrative.

Pattern 5: A clear "click Add to Chrome" subtext

The implicit call to action at the end of the demo is "install this". Don't show your installation flow (the viewer will be doing that themselves from the listing); show your post-install value. The juxtaposition — value in the video, install button right there on the listing — does the conversion work.

Five anti-patterns to avoid

The mistakes that cost installs:

1. Logo intro animations

The first three seconds of a Web Store demo should be the extension working, not a 3-second branded logo bounce. Logo animations belong on conference keynotes; they're noise on a 60-second product demo.

2. Voice-over recorded separately from the screen capture

Recording the screen first and the voice-over later creates a stilted, narrator-y feel. The Loom-style "record both at once" is messier but warmer; the mess is part of the trust signal.

3. Heavy editing with multiple cuts

The temptation to "polish" with cuts every 5 seconds is real. Resist it. A single-take screen capture with one in-point trim and one out-point trim feels honest. Heavily cut demos feel like marketing.

4. Cliffhanger endings

Don't end with "and you'll see what happens next when you install" — the user just watched the demo to see what happens. The ending should be the outcome, not a tease.

5. Talking about features instead of showing them

The cardinal sin of bad product demos. "Our extension has scheduled exports, custom hotkeys, and Markdown support" — boring. Show one feature working in 30 seconds and your viewer is sold.

File-size and quality details

Specifics for the Web Store demo specifically:

Frequently asked questions

Q: Does my Chrome extension need a Web Store video? Not technically — the listing works without one. But the conversion lift from adding one (25-50% in our data and across extension publishers we've talked to) is large enough that it's worth the 30-minute investment.

Q: Can I use Vimeo or self-hosted MP4 for the Web Store demo? No. The Web Store's Promotional Video field accepts only YouTube URLs. You'll need to upload to YouTube even if you'd prefer another host.

Q: How long should a Chrome extension demo video be? 30-90 seconds is the sweet spot. Under 30 seconds is rushed; over 90 seconds, bounce rate climbs. For most extensions, 50-60 seconds is right.

Q: Should the video have audio? Yes, with the caveat that the first 5 seconds must communicate without sound. The Web Store's video player starts muted; most viewers won't unmute. Plan the opening to make sense visually, with the audio as a layer that adds depth for viewers who do unmute.

Q: Should I show my face in the demo? For a founder-led, small-team extension, yes — picture-in-picture, small, bottom-right. The face is part of the trust signal. For a corporate or anonymous-publisher extension, the face is less relevant and you can skip it.

Q: What should my extension's thumbnail (poster image) be? A clean still of your extension's icon or popup, ideally with one line of value-prop text overlaid. YouTube's auto-generated thumbnails are usually mid-recording stills that don't look great. Spend 2 minutes making a 1280×720 PNG.

Q: Can I update the Promotional Video later? Yes. The Promotional Video field can be updated by going through the same listing-update flow. Each update triggers a re-review (usually fast — 1-3 days for content-only changes).

Q: Do I need the video to match my screenshots? The video should show the same extension as your screenshots, but it doesn't need to be a frame-by-frame match. A demo video that shows the extension in a real workflow alongside still-frame screenshots of specific features works well — the video provides the motion-and-context, the screenshots provide the still details.

Q: How does the Promotional Video affect the Web Store ranking? The Web Store's search algorithm is opaque, but listings with videos have measurably higher engagement (time on page, click-through to install) which are widely considered ranking signals. Adding a video isn't a direct ranking boost, but the engagement metrics it drives appear to help.

Q: Should the video link directly to my extension? Not necessary. The Web Store renders the video in-page on your listing; viewers are already on the listing when they watch it. The video doesn't need to link out.

Q: What if my extension does background work that's not visually interesting? Show the result of the background work. An extension that silently saves you 30 minutes a day doesn't have visually interesting active states, but it does have a visually interesting before-and-after. Frame the demo around the before-and-after, not the mechanism.

Q: Can I include music in the video? Yes, but quiet and behind the voice-over — not loud as a foreground element. Royalty-free music libraries (YouTube Audio Library, Bensound, Free Music Archive) have decent options. Avoid copyrighted music — YouTube will detect it and your video may be muted or demonetized (which doesn't affect the Web Store listing but does feel bad).

Q: How often should I update the demo? Once your extension's UI changes meaningfully — usually every 6-12 months. A demo of last year's popup screen ages the listing. The 30-minute workflow above is the reason updating isn't a project.

The summary

A Chrome extension demo video on the Web Store is one of the highest-ROI marketing assets you can ship for an extension. The path:

1. Three-bullet script.
2. Fresh Chrome profile with the extension installed.
3. Record one take with ClearRec at Ultra tier — Screen+Cam or Chrome Tab, mic on.
4. Trim, export MP4.
5. Upload as unlisted YouTube video.
6. Paste the URL into the Web Store listing's Promotional Video field.
7. Submit for review.

Total time: 30 minutes the first time, 15 minutes the second time. The video sits on your listing converting visitors for years.

If you want the recording workflow without setup, install ClearRec from the Chrome Web Store — two clicks, no account, no upload (the Web Store upload is separate, deliberate, and only happens to YouTube where you control the visibility).

See also

• How to make a product demo video in 5 minutes — the broader founder-demo workflow.
• Webcam + screen recording in Chrome — picture-in-picture workflow — for adding the founder-touch overlay to your demo.
• Best Chrome extensions for developers in 2026 — the broader extension landscape your demo competes in.
• MP4 vs WebM vs GIF: which screen recording format should you use? — format-trade-offs for the YouTube upload.
• How to record a Chrome tab with audio in 2026 — the mechanics underneath demo capture.
• The 6 best free Chrome screen recorder extensions (2026 review) — the broader recorder comparison.
• Privacy-first screen recording — what local-first actually means — the architectural argument for ClearRec specifically.
• Quality tiers — the six presets, with Ultra being the demo recommendation.