How to launch on Hacker News: the Show HN guide for founders

Hacker News has a community of roughly 10 million monthly visitors, most of them engineers, technical founders, and people who work in technology. A well-received Show HN post can generate hundreds of signups in 24 hours, spark media coverage, and give you the kind of high-quality feedback that takes months to collect elsewhere.

It can also generate nothing — or, worse, a long thread about everything wrong with your approach.

Here's how to give yourself the best chance of a strong showing.

What Show HN actually is

Show HN is a convention, not a category. You post with the title prefix "Show HN:" followed by your product name and a brief description. Posts that generate discussion appear on the front page. Most don't.

What the HN community responds well to:

• Products that solve a real, specific problem
• Technical depth or novelty in the approach
• A founder who responds thoughtfully to all comments, including critical ones
• Products that are genuinely live (not vaporware or landing pages)
• Transparency about what's built, what isn't, and what the challenges are

What it doesn't respond well to:

• Marketing copy in place of a real description
• Products that exist primarily to upsell or extract data
• Defensive responses to criticism
• Announcements without something substantive to show

The title formula

Your title is everything. HN users decide whether to click in one second. Titles that work follow a simple formula:

"Show HN: [Product name] – [specific description in plain language]"

The description should be factual, not promotional. Bad: "The best way to manage your invoices." Good: "Invoice tracking and chasing for freelancers, built with [tech], free to start."

Good Show HN title examples:

• "Show HN: I built an open-source tool that converts Figma designs to Next.js components"
• "Show HN: A command-line tool for managing database migrations with rollback support"
• "Show HN: Waitlist builder with referral loops, built for bootstrapped founders"

Notice what they have in common: they're specific, they describe what the thing does rather than what it's for you, and they don't sound like ad copy.

The initial comment (the "first comment" post)

When you submit a Show HN, you should immediately post a comment on your own thread. This comment is your launch statement — it's what people read after the title convinces them to click through.

A good first comment covers:

1. The problem — what specific pain does this solve, and who has it?
2. Why you built it — briefly. Personal motivation is more interesting than "I noticed a gap in the market."
3. What makes it technically interesting — even if the product isn't a technical innovation, the approach or the constraints you chose probably are.
4. What it is and isn't — be explicit about the current state. "This is a v0.1 — it does X and Y but doesn't do Z yet." HN rewards honesty about limitations.
5. What feedback you're looking for — direct the conversation. "I'd particularly welcome feedback on whether the pricing model makes sense and whether the referral mechanism is annoying."

Keep it under 300 words. Long first comments get skimmed.

Handling comments

The comment section is where HN launches succeed or fail. The rule is simple: respond to everything, quickly, and thoughtfully.

Critical comments: Thank them genuinely. If they're right, say so. If they're wrong, explain why — calmly and specifically. Never be defensive. HN upvotes thoughtful responses to criticism because it signals a founder worth rooting for.

Feature requests: Acknowledge them, but don't commit. "That's interesting — we've thought about this. The reason we haven't done it yet is [X]." This is more credible than "great idea, we'll add it."

Off-topic arguments: Don't engage. Let them run. Responding to trolls elevates them.

Simple questions: Answer fully. A one-sentence question gets a full, useful answer, not "check out our docs."

The goal is to make the thread a useful resource in itself — the kind of comment section that HN users bookmark and share.

Where to send the traffic

Your HN post should link to your actual product or, if it's still in pre-launch, your waitlist page. If you link to a waitlist, be transparent about it — say in your first comment that the product is in beta and you're collecting early access signups.

A strong Show HN post can send 500–2,000 visitors to your page in 24 hours. If your waitlist page isn't set up to convert technical, skeptical visitors, most of them won't sign up.

Adjustment	Why it matters for HN traffic
Be specific about what the product does	HN visitors have low tolerance for vague positioning
Show technical implementation details	Engineers want to know how it works
Include a short demo video or gif	Faster than reading a feature list
Have a clear free-tier or open-source component	HN responds better to "try it free" than "book a demo"

After the post

HN traffic decays fast — 80% of your traffic comes in the first 12 hours. After that, the post lives in the archive as a permanent reference. Many founders find that their HN post continues to drive steady low-volume traffic for months via search.

Export your new waitlist signups from the day and tag them as "HN" in LaunchSuite. HN-origin signups are often highly engaged — they've read the thread, they understand the product, and they have specific expectations. Follow up with them as a segment rather than lumping them into your general waitlist outreach.

Summary

A successful Show HN launch requires a specific, jargon-free title, a transparent and technically credible first comment, and thoughtful replies to every comment in the thread. It cannot be manufactured with network upvoting — it has to earn its attention. Post between 9am and noon Eastern on a weekday, link to either your live product or a transparent waitlist page, and spend launch day in the comment section. The HN audience is skeptical but engaged — the founders who do well there are the ones who treat it as a conversation, not a broadcast.