# How Long Should a SaaS Product Launch Video Be?

> Length guidance for SaaS launch videos: what 30, 60 and 90 seconds can carry, where attention drops, and how to fit one update into a tight runtime.

Source: https://clipnote.mehyar.us/blog/how-long-should-launch-video-be
Published: 2026-11-17T16:56:02.910Z
Publisher: Clipnote (https://clipnote.mehyar.us), a MehyarSoft product

## Key takeaways

- Pick the length from the number of ideas, not from the platform.
- One change per minute is a reliable ceiling for narrated launch videos.
- Sixty seconds fits roughly 130 to 155 words of narration at a calm pace.
- Cut scenes before you speed up the voice: fast narration reads as an ad.

Most SaaS launch videos should be 45 to 60 seconds. That is long enough to name one change, show what it replaces, and say who it helps, and short enough that a viewer who is mildly curious will still finish it. Go past 90 seconds and you are usually making a demo, not an announcement.

## Why 60 seconds is the default

A launch video has one job: move someone from "another changelog entry" to "I should try that". That is a single idea. Sixty seconds holds one idea comfortably and two ideas tightly.

The format matters less than the count. A polished 60-second narrated video, a screen recording with a voiceover, and a talking-head clip all break in the same place: the moment the viewer realises the video is going to keep going without giving them anything new.

There is a practical production reason too. Sixty seconds of narration is about 130 to 155 words at a pace that does not sound rushed. That is a short script you can actually write from a changelog entry in one sitting. A five-minute script needs a writer, and usually a director.

## What each runtime can carry

| Runtime | Ideas it holds | Best for | Risk |
|---|---|---|---|
| 15 to 20 seconds | One headline claim | Social cutdown, ad hook | Nothing is explained, viewers need context |
| 30 to 45 seconds | One change plus one outcome | In-app announcement, changelog page embed | Little room for proof |
| 45 to 60 seconds | One change, the before state, who it helps | Standard launch announcement | Script must be tight |
| 90 to 120 seconds | Two features or a workflow | Feature deep dive for existing users | Drop-off after the first minute |
| 3 minutes and up | A guided walkthrough | Onboarding, sales follow-up | This is a demo, budget it separately |

The mistake teams make is choosing the runtime first and then stuffing content into it. Choose the number of ideas first, then pick the row in that table.

## How do I fit an update into 60 seconds?

Write the narration as four beats and give each beat a sentence or two:

1. **The problem, in the user's words.** "If you import a CSV, you currently re-map the columns every single time."
2. **The change.** "Saved mappings now remember that layout."
3. **What it saves.** "One less step on every import, for every client file."
4. **The ask.** "It is live for all accounts today."

Read it aloud. If it runs under 35 seconds, you have room for one line of proof (a number from your own product, a customer quote you actually have). If it runs over 65 seconds, you have two ideas and need two videos, or a shorter second beat.

Clipnote renders 40 to 60 second videos from six scenes with roughly 130 to 155 words of narration, so the format pushes you toward this structure whether you plan it or not. The [free script preview](/) shows the draft before payment, which is the fastest way to find out whether your notes fit.

## Does length change by platform?

Less than people think. A video posted on LinkedIn, embedded on a changelog page, and sent in a launch email is the same video. What changes is how much context the viewer already has.

- **In-app or changelog embed:** the viewer is already using the product. They will tolerate 60 seconds and skip to the part about them.
- **Social feed:** the first three seconds decide everything, so the opening line carries more weight than the total runtime.
- **Cold email or paid placement:** shorter usually wins, because you are buying attention rather than borrowing it.

If you need a short cutdown for social, cut the middle, not the end. Keep the problem and the outcome, drop the walkthrough.

## Should there be captions?

Yes, and this is not a stylistic choice. Many viewers watch muted, especially in an office or on a commute, and captions are a documented accessibility requirement for prerecorded video under the [W3C's Web Content Accessibility Guidelines](https://www.w3.org/WAI/media/av/captions/).

Clipnote burns captions into the video from the final narration script, which means the words on screen match the words spoken. That consistency is the part most DIY captions fail at, because the captions were generated from a different draft.

## How many words per second is too fast?

Above roughly three words per second, narration starts to sound like a legal disclaimer. If your script needs to be faster to fit, the script is too long, not the video too short.

Three fixes, in order of preference:

1. Delete an entire beat. Usually the second one, because two of your four beats are saying the same thing.
2. Merge two sentences into one.
3. Extend the video by 15 seconds and accept 75 seconds.

What not to do: raise the playback speed. It reads as a promotion for something you are not confident about.

## Where does length affect whether the video gets found?

If you publish the video on a page you own, length is not a ranking factor, but the page around it is. Google's [video indexing documentation](https://developers.google.com/search/docs/appearance/video) explains that the video needs to be the visible content of a page, with supporting text, for it to be eligible for video results. A 60-second video on an otherwise empty page rarely surfaces.

That is an argument for the changelog page approach: the release notes text and the video sit together, each making the other more useful.

## When a longer video is the right call

Three cases:

- **The change is a workflow, not a feature.** If using it requires four steps, showing the four steps is the honest format, and that is a screen recording.
- **The audience is evaluating, not browsing.** A prospect who has already booked a call will watch three minutes.
- **You are replacing documentation.** A walkthrough that answers the top support question can be long if it is chaptered.

In all three cases, mention that it is a walkthrough in the title or the opening line, so nobody expects a 60-second announcement and gets a tutorial.

## A quick test before you publish

Play your video with the sound off and no captions. If you cannot tell what changed, the runtime is not your problem, the visuals are. Then play it with sound only. If you cannot tell who it is for, fix the script.

Length is the easiest thing to argue about and the least important thing to get perfect. One clear change, 45 to 60 seconds, captions on, published next to the release notes: that gets you most of the way, every week.

## Frequently asked questions

### Is 30 seconds too short for a launch video?

It is tight but workable for a single headline change. You will have to drop the context and the proof, so it suits an in-app announcement better than a cold audience.

### Can I reuse one video across channels?

Yes, and you probably should. The same 60-second cut works in-app, on a changelog page, and in an email. For social you may want a shorter cut that keeps the opening line.

### Do longer videos hurt conversion?

Length alone does not, but unexplained length does. A three-minute video that delivers value for three minutes performs fine. A three-minute video that repeats itself for two of them does not.

### How many words should a 60-second script have?

Roughly 130 to 155 words at a calm, natural pace. If you need more words than that, cut a beat rather than speeding up the read.

---
About Clipnote: Paste your release notes. Get a launch video. SaaS teams ship features weekly and announce them with a wall of text nobody reads. Clipnote turns your changelog into a polished 60-second narrated launch video — AI script drafted from your notes (free preview before you pay)… Pricing: $29/video · free script preview.
