The Show HN Pattern: Why Top Launches Always Have a Demo Video

Show HN's 24-Hour Window

Show HN posts have a brutal life cycle. A submission ranks based on votes and comments in roughly its first eight hours, with diminishing returns over the next sixteen. After 24 hours, the post is effectively dead — buried under newer submissions, unlikely to gain meaningful traffic again. This means the marketing window is small and the cost of unclear positioning is high. Visitors who don't immediately understand the project move on. Submissions that gain traction are the ones that communicate their value in the first ten seconds.

The Pattern Across Top Launches

Look at any list of Show HN successes from the past year — Preevy, Cal.com, Documenso, Trigger.dev, Linear's early launches — and one element is consistent: a demo video or animated visual at the top of either the linked landing page or pinned in the comments. The pattern is not coincidence. A static product page asks the reader to translate text into mental models of how the product works. A video collapses that translation step. On a platform where readers scan hundreds of submissions, that difference compounds into rankings.

Why Video Outperforms Screenshots

Screenshots are good. Videos are better, specifically because they answer two questions screenshots cannot: how does the product flow, and how fast is it. A screenshot of a code editor does not tell you how the autocomplete feels. A screenshot of a dashboard does not show whether interactions are snappy or sluggish. Video reveals these in seconds. For developer tools especially, the perception of speed and ergonomics is a major buying signal — and video is the only medium that conveys it without the viewer installing the product.

What Makes a Show HN Demo Video Work

Effective Show HN demos share four traits: they run under 90 seconds and often under 45, they start with the problem the product solves rather than a product tour, they show real interaction rather than narrated slides, and they include captions or work without audio entirely. HN traffic peaks during work hours when readers watch on mute, so visual storytelling has to carry on its own. Skip the founder talking-head intro. Skip the architecture diagram. Show the user typing a command or clicking a button, and what happens next.

Where to Place the Video

Two placements work consistently: embedded directly on the linked landing page above the fold, and as a top-pinned comment from the author in the Show HN thread itself. The pinned comment matters because many HN readers click into the discussion before visiting the linked URL — meeting them where they are already reading increases the chance they watch. Some authors do both. The worst placement is below the fold on the landing page or buried in documentation, where readers have to scroll past everything else to find it.

Common Mistakes

The most common mistake is launching without a demo video at all, hoping screenshots and a strong README will carry the post. They occasionally do, but the median outcome is silence. The second most common mistake is a demo video that runs too long — anything over two minutes loses most viewers before the value proposition lands. The third is recording the demo on a noisy desktop with unrelated browser tabs, OS notifications, and dock clutter visible. Use a clean recording environment, crop tightly, and remove anything that distracts from the core flow.

Preparing Your Demo Video Before Launch

Plan your demo video the week before launch, not the night of. If you are recording manually, write a 30-word script first, then record short takes for each beat and assemble them. If you do not have time to record, AI tools like RepoClip can generate a narrated demo from a GitHub repository in minutes — useful as a fallback or for asynchronous launches. Either way, watch your finished video on mute on your phone before you submit. If the value proposition is not clear in that condition, rewrite it. The first ten seconds carry the entire post.