Guide5 min read

Show HN Demo Video Guide

Give technical readers one working path worth inspecting.

Choose one technical flow for a Show HN demo video, then review the evidence a Hacker News reader can inspect.

See how it worksYour first 60 seconds of video are free, with a watermark.
Verify your email to download it.

A Show HN demo video should give a technical reader one working path to inspect. Its job is not to create a launch gallery or to compress an entire product into a short clip. A good candidate starts in a prepared state, shows the action that makes the product interesting, and holds on the resulting state long enough for someone to understand what changed. The Show HN post can then explain the technical context, constraints, and questions that the recording cannot prove.

That makes this page different from a Product Hunt demo video. Product Hunt needs an asset that supports a listing promise and gallery. Show HN readers are more likely to ask whether the working thing behaves as described, what boundary the maker chose, and where they can learn more. The video is evidence for one narrow question, not a substitute for a README or a technical explanation.

Reader need	What the video can show	What belongs beside it
Is there a working path?	A prepared route, action, and visible result	The scope and known limitations
Why does the action matter?	The observable product behavior	The technical problem being addressed
Can I inspect the work further?	A bounded browser example	A README, repository, or post context

Choose the question before the route

Begin with the question a technical reader should be able to answer after watching. It might be whether a user can complete one task in the browser, whether an input produces a visible result, or whether a particular interaction is understandable without narration. Do not begin with the app navigation. Navigation is only useful when it establishes the start of the selected proof.

The question must be narrower than “what does the product do?” That question produces a tour, and a tour usually gives a skeptical reader less to examine. A better question names the one behavior that makes the Show HN post worth opening. If the answer needs several unrelated features, the post is asking the video to carry more than a focused on-screen sequence can support.

Use this selection checklist before preparing the route:

State the technical question the chosen flow can answer.
Choose one inspectable route with a prepared starting state.
Show the meaningful action without turning the clip into a tour.
Keep the resulting state visible for a technical reader to inspect.

A README demo GIF serves the repository reader who needs a compact orientation. A SaaS demo video covers the broader buyer-facing URL and flow preparation process. For Show HN, the test is more specific: can the clip make one working technical claim inspectable without asking the viewer to accept an unshown system, result, or future plan?

Prepare a route a reader can trust

Choose a reachable web app route and test it manually with non sensitive seeded data. Confirm the starting state, redirects, consent notices, empty states, modals, and final result. The manual pass creates a concrete review target. It does not establish that every route will render successfully or that the product works for every app.

GogoScreen’s stated workflow uses a URL and one line hint about what to show, then returns an edited MP4. It writes and speaks a voiceover matched to what occurred on screen, and it applies editing such as click zooms, cursor smoothing, dead air cuts, and captions. These are product capabilities, not proof of an unseen result. A render can fail or need a retry, so the maker should leave time to review a candidate before using it in a public post.

If the route needs authentication, use a disposable demo account through the approved product process. Writers and reviewers should never handle or include credentials. Credentials are encrypted, used for a single render, then deleted. When a storyboard is planned first, the credentials are kept encrypted for that session and deleted at most two hours after their last use. Do not show a customer URL, customer data, private document, or personal identifier merely because it makes the flow look more complete.

Write the hint as a testable instruction

A useful hint identifies where the flow starts, the meaningful action, and the visible result. It should give the reviewer a way to compare the candidate with the intended path. “From the prepared project list, create an invoice and show the new entry” names a bounded task. “Show the product architecture” asks a browser recording to explain something that belongs in the post or README.

Keep the wording factual. Do not use the hint to claim performance, scale, security, traction, or future capability. Those claims need their own evidence. The on-screen sequence should only carry what the on-screen sequence can reveal. If the action requires background explanation, provide it in the Show HN text before or after the clip.

A startup pitch demo video also limits itself to product proof, but it supports a founder’s pitch context. An investor update demo video documents progress around one product change. A feature launch demo video announces a newly available capability. Each audience asks a different question, so the same on-screen sequence should not be reused with a new label without another review.

Review for inspectability

Watch the candidate first without relying on narration. A technical reader should be able to locate the starting context, see the meaningful action, and identify the resulting state. Then compare any captions and voiceover with what happened on screen. GogoScreen can create these elements, but the product owner remains responsible for deciding whether the language is accurate and proportionate.

Review the accompanying Show HN copy at the same time. The post should name what the clip demonstrates, what it does not demonstrate, and where an interested reader can inspect more detail. Avoid using a polished cut to imply that a prototype is complete, a result is universal, or a technical constraint has disappeared.

Review item	Decision to record
Route and prepared state	Whether the opening context matches the technical question
Action and result	Whether the visible result follows from the action
Public safety	Whether customer material or credentials are absent
Post wording	Whether claims stay within the observed session

Connect the video to the right next read

A Show HN video works best when it leads to material a technical reader can use. Link the post to a README for setup and constraints, and to the relevant product page for a broader explanation of the user job. The readme demo GIF guide explains how to keep a repository asset short. The software demo video from a URL guide covers URL readiness.

For launch placement, use Product Hunt demo video preparation rather than treating Show HN as a gallery. For a general workflow decision, consult GogoScreen versus Loom, GogoScreen versus Screen Studio, GogoScreen versus Clueso, and GogoScreen versus Guidde. Start with the GogoScreen homepage, review pricing, and check the privacy policy before submitting a render.

Clarifications

Before you start

What should a Show HN demo video show?

Show one working technical flow with a clear starting condition, an observable action, and a result a reader can inspect. The clip should help a technical reader evaluate the working thing, not replace the Show HN explanation.

How is a Show HN video different from a Product Hunt video?

A Product Hunt video supports a listing and gallery. A Show HN video should make the implementation-facing product question easier to inspect, while the post explains technical context, constraints, and what feedback the maker wants.

Should a Show HN video be a full product tour?

No. A full tour hides the decision a technical reader is trying to make. Use one bounded path and link readers to documentation or a README for setup, architecture, and limitations that do not belong in the recording.

What needs review before sharing a Show HN video?

Review the route, prepared data, visible action, result, captions, and any audible voiceover. Confirm that no customer material, credentials, private URL, or unsupported technical claim appears in the clip or accompanying post.

Paste a URL, describe one flow, and get a demo video of your web app.

Your first 60 seconds of video are free, with a watermark. Verify your email to download the video.

View pricing Read the guides