How Long Should a Product Demo Video Be?
There's no universal answer, but there is a right way to find yours: the destination sets the ceiling, and everything past it works against you.
"How long should this video be?" comes up on every product demo, and the honest answer is that there's no universal number — there's only the number that fits where the video is going. Treat length as a downstream decision, set by the destination, not an upstream one you pick before you know where it'll run.
If you haven't shot the footage yet, What to Look for in an iPhone Screen Recording App and How to Make a Product Demo Video People Actually Watch cover capture and pacing in more depth than this post does. This one is just about the number of seconds.
App Store and Play Store previews: the platforms set a hard number
This is the one place length isn't a judgment call. Apple's App Store preview specification requires exactly 15 to 30 seconds — nothing shorter, nothing longer gets accepted (the full rules are in What Apple Actually Requires in an App Store Preview Video).
Google Play doesn't enforce a hard cap the same way, but its own promo video guidance is just as clear about what matters: "only the first 30 seconds autoplays," and at least 80% of the video should be actual in-app experience, not branding or intro animation. Practically, that puts a Play Store promo video in the same neighborhood as an App Store preview even without a hard rule forcing it.
Landing page hero videos: long enough to finish, short enough to loop
A hero video on a landing page isn't fighting a feed algorithm — it's fighting the scroll. Most visitors decide whether to keep watching in the first couple of seconds, so the video needs to earn the rest of its runtime rather than assume it. In practice this means: show the product doing the thing immediately, and keep the whole clip short enough that someone can watch it end-to-end without losing the thread of what they were looking at the page for in the first place.
If the video loops (autoplay, muted, no controls — the common landing-page pattern), a shorter loop that plays twice reads better than a longer one that plays once and stalls on a static end frame.
Social feeds: built for vertical, built to be skipped
Feed placements (Reels, Shorts, TikTok, a vertical post on X) are the least forgiving format for length, because the cost of losing someone is one swipe, not a closed tab. The practical rule here isn't a specific second count — it's that every additional second needs to still be earning attention, because the viewer is actively deciding whether to keep watching on every frame, not just the first one.
This is the same "sound off, hook is the opening frame" logic covered in How to Make a Product Demo Video People Actually Watch — it just applies with less slack in a feed than it does anywhere else.
Product Hunt and launch-day listings: room to be longer, still shouldn't be
A gallery video on a Product Hunt listing or a launch page has more patience built in — someone who clicked through is already curious, not scrolling past. That earns you more runtime than a feed post, but not unlimited runtime. How to Make a Product Hunt Launch Video That Doesn't Get Skipped covers what that specific placement rewards; the short version is that "more room" isn't the same as "no reason to be tight."
A practical way to pick a number
Instead of starting from a length, start from the destination and work backward:
- Does the platform enforce a hard limit? (App Store: yes, 15–30s. Play Store: soft, via the 30-second autoplay window.) If so, that's your number — don't fight it.
- Is it autoplay/muted in a feed, or clicked-into on a page? Feeds earn the least patience; a clicked-into listing or landing page earns more.
- Cut to the shortest version that still shows the result, then check if anything past that point is adding understanding or just adding runtime.
The mistake isn't picking a number that's "too short." It's assuming one master edit can serve every destination at once. A version cut for a feed and a version cut for an App Store preview are usually two different exports of the same footage, not one video reused everywhere.
Where MobileStudio fits
MobileStudio is currently in early access, built around exporting the same recording at the framing and length a specific destination actually needs, rather than one fixed cut stretched or squeezed to fit everywhere. Join the waitlist to try it as it opens up, or look through real demo videos made with it at a range of lengths for comparison.
There's no universal right answer to "how long should this be." There's only "how long does the destination actually give me," answered honestly before you start cutting instead of after.
