Show HN: How to Launch Your Startup on Hacker News

Show HN is a dedicated Hacker News section where founders post what they have actually built and let the technical community judge it on merit. Launching on Hacker News through Show HN means submitting a real, working product with a plain link and an honest context comment, instead of a marketing pitch. It rewards builders and punishes promotion.

What Is Show HN and How Does It Differ from a Normal Submission?

Show HN is a subsection of Hacker News, the aggregator founded by Y Combinator and read heavily by engineers, founders, and investors. A normal HN submission points to an article, essay, or news item. A Show HN submission points to something you made: a product, a tool, an open-source library, a dataset, even a piece of hardware. The community expects you to be the maker and to engage with people who show up.

The two distinctions that trip up first-time founders are Launch HN and Product Hunt. Launch HN is a special, moderated format available to YC-backed companies that gets a dedicated thread with an "Official YC" tag and a built-in audience. Product Hunt is a separate platform with its own mechanics, gamified upvoting, and a different (often less technical) audience. The comparison table below summarizes the trade-offs.

If you are weighing HN against other organic channels, our guide to reddit organic marketing for startups covers a complementary audience, and our Product Hunt launch playbook walks through that platform's specific mechanics.

What Are the Official Show HN Rules?

The rules are short and enforced by both moderators and the community. The submission title should describe what you built, not why it is amazing. You must be the maker or closely involved. You should link directly to the thing, not to a landing page about the thing. HN's guidelines also prohibit asking for votes, using multiple accounts, or coordinating a vote ring.

Practically, the rules map to a handful of don'ts:

• Don't link to a waitlist or "coming soon" page. Show HN is for finished, usable work.
• Don't put your pitch in the title. "Show HN: I built a tool that does X" is the accepted form.
• Don't submit someone else's project as if it were your own.
• Don't delete and repost after a weak showing. Reposting is frowned upon and looks manipulative.
• Don't run vote rings or ask friends to upvote in coordination.

What Do HN Readers Reward and Punish?

The HN crowd is unusually technical and unusually skeptical. They reward a working demo they can poke at immediately, technical honesty about trade-offs and limitations, and a founder who shows up to answer hard questions. They punish marketing language, hype, paywalled or signup-gated demos, and anything that smells like astroturfing.

Concretely, the behaviors that move a thread in your favor are:

• A no-signup demo. If the first click requires an email, your conversion on HN traffic will be low and the comments will say so.
• Plain, specific titles. "Show HN: a CLI that turns Postgres queries into charts" beats "Show HN: the future of data visualization."
• Technical transparency. Mention what it is built with, what it costs to run, and known limitations.
• Genuine engagement. Answer questions, admit what you don't know, fix a bug someone flagged during the launch.

The punishment is quiet but real: a flagged or downvoted post disappears, and a reputation for astroturfing follows you across future launches.

How Do You Write the Title and the First Comment?

The title is the single highest-leverage element. Keep it literal and descriptive. The accepted template is "Show HN: [short description of what you built]." Avoid adjectives, superlatives, and anything that reads like ad copy. If your product has a memorable name, lead with the function, not the brand.

The first comment is where you add context the title cannot carry. Founders call this the "founder context post," and it should read like a note you would send a smart friend. Cover:

• Why you built it and the problem it solves.
• What is interesting technically (architecture, a clever trick, an open challenge).
• How people can try it right now, with the path of least resistance.
• Honest caveats: it is early, it is rough in places, here is what is next.

Write the first comment before you submit, not after. The early minutes of a thread set its tone, and an empty comment section reads as a drive-by promotion.

How Does Timing and Front-Page Mechanics Work?

Every submission first lands in /newest, where it competes for attention before it can reach the front page. Most launches die in /newest because they never clear the threshold of early upvotes needed to be promoted. There is no fixed formula for timing, but the commonly cited windows are when the US East Coast is awake and at work, avoiding weekends and major holiday lulls when fewer power users are active.

Mechanics that matter more than the clock:

• Early velocity. A few genuine upvotes in the first hour signal quality. Manufactured velocity triggers spam filters.
• Flags. Users can flag submissions; enough flags remove a post regardless of votes. Provocative or deceptive titles get flagged fast.
• Comments drive rank. A lively, substantive comment thread keeps a post alive longer than upvotes alone.
• Reputation. Accounts with history and karma are treated more leniently by ranking than brand-new throwaways.

What Is the Pre-Launch, Launch-Day, and Post-Launch Checklist?

Treat a Show HN like a small engineering release. The ordered list below is the sequence we use with early-stage teams.

1. Confirm the demo works with zero signup and loads fast on a mobile connection.
2. Write the title and the founder context comment, then set them aside and reread them for hype.
3. Make sure your infrastructure can handle a traffic spike without timing out.
4. Set up analytics and a waitlist or signup so the spike is measurable and capturable.
5. Submit from an account with some history, using the literal title, and post your context comment immediately.
6. Stay online for the first two to three hours to answer every substantive question.
7. Fix visible bugs live if users hit them; mention the fix in the thread.
8. After the spike, send a follow-up comment or update to people who expressed interest.
9. Compile what you learned about objections and pricing into your broader venture-backed startup marketing playbook.

How Do You Convert an HN Spike into Durable Results?

A front-page HN post produces a sharp, short traffic spike that decays within a day or two. The mistake is treating that spike as the outcome. The durable value comes from what you instrument and capture during it. Put a clear waitlist, a lightweight signup, or a "star on GitHub" path in front of interested readers, and make sure each is tagged so you can attribute it later.

Be realistic about traffic quality. HN readers are curious and technical, which is excellent for feedback and early adopters, but they are not necessarily your buyer persona at scale. Many will kick the tires and leave. The founders who benefit most are those selling to developers or technical buyers, where the audience overlap is high. For everyone else, HN is a credibility and feedback event more than a lead-gen event. Following up in threads, shipping what people asked for, and posting a "Show HN one month later" update are what turn a spike into a relationship.

How Should You Measure a Show HN Launch?

Measurement starts before you submit. The metrics that actually tell you whether the launch mattered:

• Referral traffic from news.ycombinator.com, broken out by the thread URL.
• Signup or waitlist conversion rate from that referral segment specifically.
• Branded search lift in the days after, a signal that the name stuck.
• Backlinks and domain authority gained as blogs and newsletters cite the thread.

Track these as a cohort. If 10,000 visitors produced 40 waitlist signups and three of them became design partners, that is a defensible result even if the raw traffic number looks like a firework. The backlinks and branded search often outlast the traffic and compound quietly over the following weeks.

What Mistakes Do Founders Make When Launching on Hacker News?

The recurring failures are predictable. Launching too early is the biggest one: a demo that breaks under load or a product with no clear "try it now" path wastes the one shot at the audience's attention. Deleting and reposting after a weak result is the second; it reads as manipulation and the HN algorithm and community both notice. Arguing in comments is the third. Defensiveness reads as insecurity, and the thread will side with the critic.

Smaller but common errors include burying the demo behind a signup wall, writing a title that sounds like a press release, and vanishing after submitting so the comment section goes cold. None of these are fatal in isolation, but together they explain why most launches fade in /newest.

How Does Show HN Fit into an Early-Stage Marketing Strategy?

For a technical founding team, Show HN is one of the few channels where credibility is earned by the work itself rather than by ad spend. It pairs well with founder-led sales because the thread becomes a visible record of how you think and respond under pressure. It is not a replacement for a repeatable acquisition channel, but it is a high-signal event that can seed your first community, surface your sharpest objections, and produce backlinks that help every later campaign.

Key Takeaways

• Show HN is for shipping a real, working thing to a technical audience, not for pitching.
• Literal titles and an honest founder context comment outperform any marketing language.
• Most launches die in /newest; genuine early engagement and a no-signup demo are what survive.
• A HN spike is a credibility and feedback event; instrument it and capture signups while it lasts.
• Measure referral traffic, signup conversion, branded search lift, and backlinks as a cohort.
• Avoid the classic mistakes: launching too early, deleting and reposting, and arguing in comments.

If you are a YC company, the coordinated format differs from a self-serve Show HN: see how YC startups run a Launch HN.

Frequently Asked Questions

Who Is Eligible to Post a Show HN?

Any Hacker News user can post a Show HN as long as they are the maker or closely involved with what they are showing. There is no affiliation requirement, which is what separates it from Launch HN, which is reserved for YC-backed companies. You should link directly to the thing you built rather than to a page describing it.

Is Show HN Better Than Product Hunt for Startups?

Neither is universally better; they serve different audiences. Show HN reaches a technical, skeptical crowd that rewards working demos and honest engineering, while Product Hunt draws product enthusiasts through a gamified, time-boxed format. Technical founders selling to developers often find Show HN produces sharper feedback and more durable backlinks even with lower raw traffic.

Why Did My Show HN Get Flagged or Buried?

Posts are flagged or buried for hype-filled titles, signup-gated demos, deceptive framing, or coordinated voting. The HN ranking also depends on early organic upvotes and an active comment thread; submissions that sit inert in /newest rarely escape. Reread your title and first comment for anything that reads like promotion rather than description.

How Much Traffic Can a Successful Show HN Drive?

A front-page Show HN typically produces a sharp spike of tens of thousands of visitors within a day, followed by a quick decay. The traffic is technically literate and curious but not always your end buyer at scale. The lasting value is usually the backlinks, branded search lift, and early-adopter relationships rather than the raw visitor count itself.