The Show HN Playbook for 2026

Most Show HN posts die in new/. The team posted, got 12 upvotes and 3 comments, watched the position drift down, and concluded that HN doesn't work for their category. HN works. The post was unprepared.

A successful Show HN is not a moment. It's a sequence with at least three weeks of work in front of it, the post itself in the middle, and 90 critical minutes after submission that decide whether you make front page or not. This is the sequence I've used and watched work, multiple times, across multiple companies.

Three weeks before: the pre-launch

Most of the work happens here. By the time you submit, you should have:

1. A landing page that survives the front page. Cache aggressively. Pre-load everything. Test it under load. The HN hug-of-death is a real thing and a slow-loading landing page on the front page of HN is a tragedy in real time.
2. A working five-minute quickstart. By "working" I mean: you've watched five non-technical friends and three engineers try it cold, and all eight got to a successful Hello World without DMing you. Anything less and your conversion will hemorrhage at the docs page.
3. A first-comment draft, polished. The first comment by the OP is the single highest-leverage piece of writing in the entire launch. We'll get to the template. Write it three days ahead and edit it twice.
4. A FAQ document for likely critiques. Read three similar Show HNs in your category. Note every critical comment. For each, draft a thoughtful, non-defensive 2-sentence response. You'll thank yourself at hour 1.
5. An onboarding flow that captures email at the right moment. Not too early (kills trial) and not too late (you lose 80% of the spike). For most devtools the right moment is after the first successful command, not before signup.

If you're missing any of these, postpone the launch. The cost of waiting two weeks is much lower than the cost of a Show HN that flops because your quickstart broke under load.

The submission mechanics

Title format: Show HN: [Product] – [what it does in 8 words]. The em-dash is convention. Note the verb-first description after the em-dash: "Show HN: Levo – Generate test data from your DB schema" reads better than "Show HN: Levo – A test data generator." Verb-first feels active; noun-first feels like a press release.

URL: link to the product, not a blog post about the product. HN moderators will sometimes re-route blog post submissions; Show HN is for the actual thing.

Day and time: Tuesday-Thursday morning, US Pacific, between 6am and 9am PT. This is when the HN audience is heaviest and the post has the longest runway. Mondays are flooded with weekend submissions. Fridays die over the weekend. Avoid both.

Don't ask for upvotes. Don't pre-arrange upvote rings. Both will get you de-ranked or banned. HN's flag system is sensitive to coordinated voting and the penalties last forever.

The first comment

This is the most important paragraph of your launch. Post it within 60 seconds of submitting. Format:

"Hi HN — I'm [name], built [Product] with [co-founder] over the last [time]. We made it because [specific personal pain in 1-2 sentences]. The thing it does that nothing else does well is [one specific capability]. Known limitations: [2-3 honest limitations]. Free tier is generous, no signup required to try the demo at [link]. Happy to answer anything — what would you want it to do that it doesn't?"

Why this works:

• The personal pain earns trust faster than any feature list.
• Known limitations pre-empt the top three critical comments and demonstrate self-awareness — HN respects this enormously.
• "What would you want it to do" invites engagement. The comments section is now a feedback gathering, not a defense.
• No signup demo link removes the friction that kills HN traffic at the door.

The first 90 minutes

The HN ranking algorithm weights early engagement heavily. The first 90 minutes determine whether the post climbs from new/ to the front page or dies in obscurity. Treat this window as work — block your calendar, sit at your desk, no meetings.

The rule: reply to every comment within five minutes, for the first hour. Even one-liners. Even ones you find annoying. Especially ones you find annoying. Length doesn't matter; latency does. The HN crowd watches whether the OP is engaging and weights that into both upvotes and the meta-perception of the launch.

When critics arrive (they will), engage substantively. Don't defend; thank them for the critique, acknowledge what's right about it, explain your reasoning where you disagree. The hardest comment to handle gracefully is the one that's partly right. Practice that one. The HN crowd is calibrated to detect defensiveness and rewards intellectual honesty disproportionately.

If a comment is unfair or factually wrong, correct it once, calmly, with evidence. Don't argue twice. Move on.

What to do if you make the front page

If you hit the front page (top 30), you'll get 5,000-50,000 visitors in 24 hours, depending on position and dwell time. The hard part isn't getting them; it's converting them.

1. Monitor your infra. If anything breaks, fix it fast or post an update comment ("Sorry — we've had a small outage at the docs page, fixed in ~5 min"). HN forgives if you communicate.
2. Capture email on the home page. One field, one button, no friction. Phrase it as "Want updates as we ship?" not "Sign up for our newsletter."
3. Post hourly status comments in your own thread. "Update: 8am PT, we just shipped a fix for [bug X]. Thanks for catching it." Keeps the thread active, signals authenticity, gets you re-surfaced.
4. Take the most-asked feature request and ship it within 48 hours. Then post about it in the comments. This is the secondary spike. People love seeing a team that responds.

The day after

The spike fades within 36 hours. What you do during the fade decides whether you have something durable or just had a good Tuesday.

• Email everyone who signed up with a personal, non-templated message. Not a marketing email. A 4-sentence thank you with one question: "What problem were you hoping to solve with us?" Half will reply. Those replies are your roadmap.
• Write a post-mortem of the launch and ship it 7-10 days later. Include the metrics (signups, conversions, peak traffic, top criticisms), what you'd do differently, and one prediction about what comes next. This is the second piece of compounding content from the launch.
• Reach out to the 3-5 commenters who engaged most thoughtfully. Ask if they'd be open to a 20-minute call to talk about their use case. The first 2-3 customer interviews after a launch are gold; you'll learn more about your ICP from these than from a quarter of analytics.

If you don't make the front page

Most launches don't. This is fine. You still have the post, the comments, the signups, the lessons. Wait six months. Ship something genuinely new. Do another Show HN. Many companies whose second or third Show HN went viral had a quiet first attempt nobody remembers.

The thing to NOT do: a "Show HN: [Product] (v2)" three weeks later. The community will downvote it. You get one Show HN per product unless you have a meaningfully new thing to show.

A note on honesty

The biggest mistake new founders make on HN is posturing. Pretending to be a user discovering your own product. Coordinating upvotes through team Slack. Hiding the fact that the post is by the founder of the company.

Don't. HN's community is small and the moderators are exceptional. The penalty for being caught isn't a single post being killed — it's permanent shadow-banning. And the upside of honesty is significant: a clearly-flagged Show HN by a founder asking for feedback is exactly what the community is set up to reward. The "Show HN" tag is a guarantee that this is the maker showing their thing. Lean into it.