Product Hunt Demo Video: What to Show and How to Make It
A Product Hunt demo video should show one complete task in the real product, in 16:9, in under forty-five seconds, with captions, because the gallery plays muted and the visitor is deciding in the first few seconds whether the product does what the tagline says. A trailer with music and taglines belongs further down the gallery, if anywhere. The first slot is for proof.
What does the first gallery slot have to do?
Hunters land on your page from the feed with one question: does it do the thing? The video in the first gallery slot answers it or loses them. So:
- Open on the product, not a title card. A short intro card with the name is fine; a ten-second logo animation is not.
- Show a flow with a visible end state. Create the thing, see the result. Software demo video examples lists six flows that work.
- Caption every step. Sound is off. The captions carry the story: “Paste a URL”, “Pick a format”, “Done.”
- Keep it to five to eight steps. Enough to be convincing, short enough to finish before the scroll. How long should a demo be has the reasoning.
- End on the result and hold it. The last frame is what they remember.
Which format and frame?
16:9 in a browser frame is the safe choice for the gallery: it reads as a screen, the mockup sets it apart from screenshots, and it looks right on the thumbnail. If your product is mobile-first, record it on a mobile device and render the phone in a 16:9 canvas on your brand color; the gallery still gets a landscape asset and the phone frame says “mobile” without a word. Formats and frames by channel has the full table.
Style: smooth. Zoom on the one or two clicks that matter; a snappy zoom on every click reads as frantic at forty seconds.
How do you avoid the night-before recording?
Launch videos get made at the last minute because the product keeps changing until the last minute, and every change invalidates the recording. The usual answer is to record the night before and hope nothing moves. A better answer is to make the recording cheap enough to redo in the morning.
With Klevo connected to Claude or ChatGPT, the recording is a prompt:
Record a demo with Klevo of the main flow on https://staging.acme.app: open a new document, paste a URL, pick the Report format, generate, show the result. Desktop, 16:9, browser frame, smooth. Zoom on Generate. Intro card with the title “Acme turns a URL into a report”. Outro: “Live on Product Hunt today”, acme.app. Brand color #2F6DF6. Log in with DEMO_LOGIN.
The AI opens the app, performs the steps while checking each screenshot, writes a caption per step and finishes; the video renders in about a minute and the steps are saved as a script. If you ship a change at midnight, “render script abc123 again” produces the current version before coffee. Demo videos that never go stale explains why the script, not the video, is the asset.
What goes in the rest of the gallery?
After the proof clip, the gallery can hold the shorter cuts:
| Slot | What | Format |
|---|---|---|
| 1 | The complete flow, captions, 5 to 8 steps | 16:9, browser frame |
| 2 | One feature, 2 to 4 steps | 16:9, browser frame, snappy |
| 3 | The mobile view, if it matters | Mobile device, phone frame in 16:9 |
| 4 and on | Screenshots of the screens the videos did not reach | Static |
All three videos can come from one or two scripts rendered with different options, so the gallery is not three recording sessions.
How do you reuse it on launch day?
The same proof clip goes to the launch tweet as 1:1 with no frame and the snappy style, to the LinkedIn post as 4:5, and to the story as a 9:16 mobile render. Ask for each render by name; the flow does not change. The launch-day checklist in keeping demos current after every release is the same list you will use for the next release.
What should you not do?
- Do not show the login. Save a test login so the recording starts on the first real page. Recording an app behind a login shows how.
- Do not demo with your own account’s data. Make a test workspace with plausible names. Demo videos without real customer data covers it.
- Do not invent claims in the captions or the cards. “Trusted by 10,000 teams” on launch day is a sentence you may have to walk back by lunch.
- Do not record at a resolution the gallery will shrink. 1080p is plenty; what matters is the zoom on the click so the small version is still readable.
FAQ
Can the video have music? Klevo renders a clean MP4 without audio. Add music in any editor if the gallery needs it; the first slot works better without.
How long before launch should I record? Whenever the flow is final, because re-rendering after a change takes a minute. Record early, render late.
Should the video have a title card? A short intro card with the product name and the task is fine; keep it under two seconds and let the flow start.
Does the free plan cover a launch? Twenty videos a month at 720p with a small watermark, in the default look. A launch gallery usually calls for 1080p without the mark, which is Pro: pricing.