How to Make a Product Hunt Launch Video That Explains Your Product

A Product Hunt launch video should show what your product does, why it matters, and what to try next. Choose a customer problem you can demonstrate, record how your product solves it, and remove details that do not help explain that task.

Before animating, decide how the video should look and collect references for the layout, pacing, and sound. Test a short sequence, then use it to guide the rest of the edit.

Start with the change your viewer wants

Before opening an editor, finish this sentence:

For [specific person] who struggles with [specific situation], [product] helps them [visible outcome] by [main action].

For a client-feedback tool, focus on a familiar problem: a designer cannot tell which version the client approved. Show how comments attached to each version remove that confusion.

Record the designer opening a shared design, checking its comments, and finding the approval.

Filmmaker Casey Neistat described his approach in an interview with WITNESS THIS:

I try to tell stories at a 5th grade reading level.

— Casey Neistat, on his storytelling style

Use familiar actions in the script. Explain how a designer checks an approval instead of describing stakeholder alignment. When a technical term is necessary, demonstrate what it means.

Choose the final action at the same time. Do you want viewers to try a sample project, join a waitlist, or visit the launch discussion? Pick the action your product is ready to support. A video promising an immediate trial should not end at an unexplained waitlist.

Turn that promise into a 50-second story

Arrange the scenes in this order: problem → product action → result → next step. Follow the same task throughout, from the initial difficulty to its resolution.

Here is how you could storyboard that client-feedback workflow. Adapt the actions to features your product actually supports.

Split the demonstration into separate shots for sharing, commenting, and approval. Give the viewer time to see the action and then its result.

Include supporting features only when the task needs them. Show permissions if they affect who can approve a design; leave unrelated analytics for another video.

Write the screen text beside each shot before producing anything. Each sentence should describe something the viewer can see. Support any numerical claim, such as weekly hours saved, with evidence.

For a more detailed handoff, use our guide to briefing Claude Code for a product video.

Build a moodboard before you animate

A moodboard collects the images, video excerpts, colors, and type treatments you want to use as references. It helps you agree on the look before animation begins. A request for a premium video is vague; a layout reference and an annotated motion clip give an editor useful direction.

Start with three words that suit the product and audience. For the client-feedback workflow, try calm, precise, reassuring. Those words suggest spacious layouts, readable product details, and controlled movement. A playful consumer app might call for brighter color and more expressive motion.

Collect a small set of stills and short clips. Include your own product screens and brand assets so the board stays connected to what you are launching. Organize the references by the decisions they help you make:

For video references, save a timestamp and describe the action: the cursor arrives, pauses, and clicks before the camera moves. Identify which part you want to use and why it suits your scene.

Keep a note of what you do not want: tiny interface text, constant camera movement, or a different transition for every shot. Credit reference sources on the board and use them to study decisions; create your own compositions and assets.

Review the references together before approving the board. If half the references are quiet and minimal while the others depend on frantic cuts and bright effects, select one direction before proceeding.

Turn references into a design and motion direction

Use the moodboard to choose the type sizes, colors, framing, and transitions for your video. Test those choices in still frames and a short animation before applying them to every scene.

Design three key frames

Create still designs for the opening, the main product action, and the closing card. These are style frames: representative images that establish the finished look before animation.

Use the actual product in the middle frame. Choose a consistent type scale, a small palette drawn from the brand, and a repeatable position for labels. Make the primary message easy to find; make supporting text smaller or less prominent. Check all three frames together to see whether they belong to the same film.

For the client-feedback example, place the two conflicting comments in the opening frame, crop closely around a pinned comment in the demonstration, and give the closing card one invitation to try the product. A light interface on a neutral background can work well here. A darker treatment is also possible if the controls remain readable and the product still feels familiar.

View the frames at phone size. If the design only works when enlarged on your monitor, fix the crop or hierarchy before animating. Check that labels have enough contrast and that decorative elements are not competing with the product.

Test one short motion sequence

Animate a representative five-to-eight-second passage before building the whole film. Choose a passage that includes a product action, a callout, and a transition. This tests the parts you will repeat.

Write a few motion rules beside the style frames:

• Focus: move toward the control the viewer needs to see, then hold the camera steady during the action.
• Timing: let the viewer read the label before the next change; let the result register before cutting away.
• Easing: let interface panels arrive and settle smoothly. Reserve bounce or overshoot for a deliberately playful tone.
• Continuity: keep a shared object in a similar screen position across a transition so the viewer can follow it.
• Restraint: reuse a small set of cuts and transitions. Save the most expressive movement for the main reveal.

In the feedback sequence, you might move from the full design into one comment, pause while it is resolved, then reveal the approval state. Each camera move should reveal the next detail the viewer needs.

Review the sample at normal playback speed. Does it feel hesitant, rushed, or appropriately paced? If a move feels distracting, first reduce its distance or remove it. Adding another effect rarely solves an unclear transition.

Once the sample works, keep it beside the storyboard as the standard for the remaining scenes. Include the moodboard, approved frames, and motion sample in the production brief.

Keep one idea on screen at a time

A viewer should not have to choose between reading a headline, tracking a cursor, and understanding three animated cards at once.

For each shot, decide where the viewer should look first. Reveal the label, show the action, and let the result settle before introducing the next idea. Zoom to make a small control readable; stop zooming when the viewer needs to inspect it.

Film editor Walter Murch describes the timing problem in his conversation with Kiran Ganti:

If the audience is not ready, the cut will feel awkward.

— Walter Murch, on when to cut

For a product demo, that means holding the result long enough to understand it. When a status changes from Needs changes to Approved, hold the shot long enough to read the new label before moving on.

Try these edits on a crowded scene:

• Three feature cards arrive together: show only the feature needed for the current action.
• A full dashboard makes the key detail tiny: crop closer while retaining enough context to identify the screen.
• A paragraph sits over moving footage: reduce it to a short label and split the explanation across shots.
• Every click gets an effect: keep the cues that direct attention and remove the rest.

Watch the cut muted. The text and product actions should explain the sequence without narration. If you use narration, also provide accurate captions; short promotional labels do not replace speech captions.

Choose tools for the scenes you need

Make an asset list from the storyboard before choosing tools. For the example above, the essentials are a sample design, two staged feedback threads, a recording of the actual workflow, a logo, and a closing card. This workflow needs no generated footage.

Before recording, prepare a demo account with sample data, close unrelated tabs, and turn off notifications. Record the workflow in short takes, leaving a pause before and after each action. If you remove loading time, label the shortened sequence when processing speed is part of your claim.

Start with a recorder and an editor. Add another tool only when the storyboard calls for an asset you cannot make with those two.

Connect only the capabilities you will use

CoAnimator’s plugin documentation lists ElevenLabs Audio for narration, effects, and music; Gemini Images for images; and Grok Imagine for images and video. Enable the relevant plugin, complete its key or account setup, and start a new agent session after changing the configuration. Provider usage is billed through your provider account. Check the current license requirements for any premium plugin you select.

Keep credentials in plugin setup. For real product footage, record with a separate screen recorder and import the clip. Website capture and desktop screen recording are different jobs.

Give music a supporting role

For a calm workflow demo, try a restrained instrumental track with room for speech and a clean ending. Preview it against the rough cut before committing. A dramatic build can work for a reveal, but it should not force you to rush the explanation to reach the beat.

If generating music, specify an instrumental track for a 50-second software demo, with no vocals, a steady pulse, and a gentle ending. Review the actual output rather than assuming the prompt guarantees the timing.

Lower the music under narration, listen on ordinary speakers, and leave a moment for the final card. Add sound effects only where they make an action easier to follow.

YouTube’s Audio Library distinguishes tracks that require attribution from those that do not. Copy any required credit into the description. Check the selected track’s terms for your intended uses, including any social or advertising versions; do not assume that a track available in a tool is cleared for every use.

Generate supporting footage only when it explains something

Generated video can illustrate a setting or an abstract transition. Use an actual recording for the workflow that proves what your software does. A generated interface should not stand in for a working feature.

For a supporting shot, establish the look with an approved image, then describe one main motion. Runway’s image-to-video guide separates the image’s composition and style from the prompt’s motion instructions.

For example, ask for a slow camera move toward a notebook while the desk and objects remain still. Generate the shot separately, inspect it, and bring the approved clip into the edit. Add precise text and logos in the editor, where you can control them. If the scene does not help explain the problem or outcome, cut it.

Build the first cut in CoAnimator

Once the story and assets are ready, use the CoAnimator quickstart to connect your agent and open a project. Give it the scene plan and approved files together. Ask the agent to list missing footage before building the scenes.

Step 1: Give the agent a complete brief

Use this as a starting brief, replacing the workflow and assets with your own:

Create a 50-second, 1920x1080 Product Hunt launch video for our client-feedback tool for freelance designers. Use our supplied product name and logo. The promise is keeping feedback attached to the right design version. End with Try a sample project.

Follow this sequence: 0–5s conflicting feedback; 5–10s introduce the product; 10–23s share a design and add a comment; 23–36s resolve the comment and show approval; 36–44s hold on the approved version; 44–50s closing card.

Use my supplied workflow recording, staged feedback screenshots, logo, and brand font. Identify any missing assets before building. Do not invent product controls, results, customer logos, or statistics.

Follow the attached moodboard and approved style frames: calm, precise, reassuring. Use our brand type, one accent color, consistent labels, and the framing from the approved motion sample. Make the story understandable without audio. Keep text separate from footage so it remains editable.

If any creative direction is still missing, propose three style frames and a short motion test before assembling the full video. Build a rough cut from the approved direction. List any provider connection needed before generating assets. Keep approved scenes unchanged while revising a specific shot.

Step 2: Refine the cut in focused passes

Build an animatic first: the storyboard frames held on a timeline, with rough timings and temporary narration or music where useful. Watch it from beginning to end. Fix missing steps, a weak opening, or an abrupt ending while the scenes are still inexpensive to change.

Then assemble the full motion cut and review it in this order:

Use a simple loop: watch → identify one problem → revise → compare → keep or revert. Save the previous version so you can judge whether the edit helped. Review the changed shot in context; extending a pause can improve comprehension but weaken the transition that follows.

Give feedback with a timestamp, an observation, and a specific change:

At 00:28, the approval label appears while the camera is still moving, so it is hard to read. Let the camera settle first, then reveal the label and hold the approved state for two seconds. Keep the surrounding shots unchanged.

If you are unsure which opening works, make two short versions while holding the rest of the cut constant. Ask someone unfamiliar with the product what each opening leads them to expect. Choose the version that creates the right expectation and carries naturally into the demo.

Set acceptance criteria before the final review. Stop when the story is understood on one viewing, the design follows the approved direction, the movement supports the actions, and the export passes the final checks below. Further changes should solve an identifiable problem, not simply make the latest version different.

Step 3: Add audio and export the reviewed version

Replace temporary audio with the approved music and narration, then check the final mix against the finished timing. Check pronunciation and captions against the actual audio.

A 1920x1080, 16:9 master is a practical choice for a readable software demo. Use 30 fps for a straightforward motion-graphics project, or preserve the recording’s frame rate when appropriate. These are production choices, not Product Hunt submission requirements.

Check the current CoAnimator export limits before the final render: the free plan caps exports at 720p with a watermark; paid licensing unlocks higher-resolution, watermark-free exports.

Keep the editable project and approved assets. For future releases, replace changed screens and re-render rather than reconstructing the sequence from an exported file.

Prepare the video for Product Hunt

Product Hunt’s posting guide separates the video field from gallery images and the thumbnail:

The gallery-image dimensions are not the video canvas dimensions. Export the video separately, then add its YouTube URL to the listing.

Upload at least the day before as a practical buffer. Product Hunt’s YouTube troubleshooting guide says a newly uploaded video may need approximately 12 hours before integration works, and sharing or embedding restrictions can also cause problems.

Open the YouTube link while logged out, then test playback inside the Product Hunt draft or preview. A working watch page alone does not confirm that embedding works. Check the actual listing placement before treating the upload as finished.

Review it with someone who does not know your product

Show the exported video once, without introducing the product first. Ask the viewer:

• Who is this for, and what problem does it solve?
• What did the product actually do?
• Where did you need more time or explanation?
• What would you do next?

Ask for specific points of confusion rather than a general opinion about the production quality. If they remember the animation but cannot explain the workflow, simplify the sequence. If they understand the problem but doubt the result, improve the product evidence.

Before launch, check these five things:

1. Comprehension: the muted cut still communicates the problem, action, and result.
2. Readability: screen text and important controls are legible on a phone without pausing.
3. Accuracy: every demonstrated feature exists; staged sample data is appropriate; no private customer information is visible.
4. Sound and assets: speech is clear, captions are correct, and music or footage credits are included where required.
5. Delivery: the exported file plays correctly and the embedded video works in the listing preview.

After launch, look at the action the video was meant to support, such as sample-project starts or signups. Upvotes alone cannot tell you whether the video worked. Launch timing, distribution, the offer, and the rest of the page also affect results. Use viewer feedback and available viewing data to decide what to revise.

Frequently asked questions

How long should a Product Hunt launch video be?

Aim for 45–60 seconds for a single product workflow. That is a starting recommendation, not a platform limit. Allow more time when the demonstration needs it, but cut repeated explanations and unrelated features before making the video longer.

What should a Product Hunt launch video include?

Include the problem, your product’s name, a demonstration of the main action, the result, and one next step. Show the product early enough that viewers understand what they are watching. Save setup instructions and secondary features for a separate tutorial.

Can I make a Product Hunt launch video without editing experience?

Yes. Start with a short screen recording, trim mistakes and waiting time, and add readable labels and a closing card. A template or an agent-assisted editor can help assemble the scenes. Review the exported video yourself, especially the pacing, captions, and accuracy of the demonstration.

How much does a Product Hunt launch video cost?

The cost depends on whether you record and edit it yourself or hire someone to handle scripting, design, animation, and sound. For a DIY version, budget for any editor license, music, and AI usage you need. For commissioned work, ask for a quote that specifies the duration, source footage, custom animation, revision rounds, and delivery of editable files. A screen recording and a fully animated film involve very different amounts of work.

Should I use a screen recording or an animated launch video?

Use a screen recording when viewers need to see how the software works. Animation helps explain a concept, introduce a problem, or connect steps that are difficult to capture. You can combine them: a short animated introduction followed by a real product demonstration. Avoid recreating the interface unless you can keep its appearance and behavior accurate.

What video size and format should I use for Product Hunt?

A 1920×1080 widescreen MP4 is a practical master to upload to YouTube. Product Hunt’s video field accepts a full YouTube URL rather than a direct video-file upload. Its 1270×760 gallery recommendation applies to still images. See the submission requirements.

Why is my YouTube video not appearing on Product Hunt?

Check that you used the full YouTube URL, that the video is not private, and that embedding is allowed. For a new upload, Product Hunt advises waiting approximately 12 hours before retrying integration. Test the listing preview after making changes; the troubleshooting guide explains these checks.