Show HN: how to launch on Hacker News without getting flagged

A Show HNis Hacker News's post format for something you built that other people can try right now — software they can run, a site they can click into, hardware you demonstrate on video. You launch by prefixing your submission with Show HN:. Almost everything that goes wrong afterwards comes down to three things: posting something nobody can actually try, writing a title that reads like an ad, and asking people to upvote you.

Hacker News is the launch surface founders fear most and prepare for least. It has no submission fee, no scheduling, no hunter, and no way to buy your way onto the front page — which makes it the most level launch platform available to a solo founder, and the least forgiving. This guide is the version I wish I'd had: grounded in what Hacker News actually publishes about its own rules rather than in the folklore that gets recycled between marketing blogs.

What is a Show HN — and what gets flagged?

The rule is narrower than most founders assume, and it's written down. Hacker News's official Show HN rules define the format as being for “things people can run on their computers or hold in their hands” — and explicitly rule out blog posts, sign-up pages, newsletters, lists, and other reading material. If a reader can't interact with the thing at the end of your link, it isn't a Show HN, and the community will tell you so before the moderators do.

Two conditions sit alongside those lists and catch people out. The project has to be yoursand you have to be around to discuss it — a Show HN posted by a marketer on behalf of a team that's asleep reads exactly like what it is. And the rules ask you to lower the barrier to entry as much as you can, which in practice means the email wall is the single most complained-about thing in Show HN threads. A demo, a sandbox, or a video that shows the whole product working will do more for you than any amount of copy.

The last constraint is about substance: new features and point releases generally aren't Show HN material, though a major overhaul probably is. Rough and early is fine — the rules say a Show HN needn't be complicated or look slick. Half-finished and unusable is not.

Why do boring titles win on Hacker News?

Because Hacker News's site guidelines treat editorializing as a defect, not a skill. They ask you to use the original title unless it's misleading or linkbait, to not editorialize, and to strip gratuitous numbers and number-adjective constructions — “10 Ways To Do X” becomes “How To Do X” unless the number carries real information. Every technique that works on a landing page works against you here.

The convention that survives is dull and reliable: Show HN: Name – plain description of what it does. Here are the patterns I see get killed next to the ones that get read. (These are composites of common patterns, not quotes from specific posts.)

Read the left column out loud and the rule becomes obvious. The titles that work sound like something an engineer would say to another engineer at a desk. The titles that fail sound like something a company would say to a market. Hacker News is a room full of people who spend their working lives detecting the difference.

The first comment is your real launch post

Your title gets the click; your first comment decides whether the thread lives. Post it yourself, immediately after submitting, as a top-level reply — this is where the context that doesn't fit in eighty characters goes, and where readers decide whether you're a builder worth talking to or a founder running a campaign. Five things belong in it:

What doesn't belong: pricing tiers, a roadmap, a testimonial, the word “excited,” or any sentence you'd also put in a press release. The comment should read like the README you'd write for a friend. If you've already run your product past people who ship — the sort of structured pre-launch feedback that names specific objections — you'll already know which rough edges to declare here, because someone will have hit them first.

When to post — and what happens if nobody sees it

Post when you can sit with the thread for the next three or four hours. That single constraint outranks every timing chart on the internet. Hacker News ranking decays with a story's age, so attention in the first hour counts for far more than the same attention spread across a day — but the only thing you personally control in that hour is whether you're there to answer questions. A quieter slot you can staff beats a busy slot you sleep through.

US weekday mornings bring the most readers to /newest, and also the most competition for their attention. Weekends are quieter in both directions. Treat that as a mild preference, not a formula, and be suspicious of any guide that hands you a precise upvote target for your first thirty minutes — hitting a number like that on purpose is the behavior that gets launches killed.

If the post sinks without a trace, you have two legitimate options. The first is patience: Hacker News runs a second-chance pool, where moderators and reviewers comb /newestfor stories that were overlooked and re-up them onto the front page at a random position. You can't apply to it; you can only give it something worth rescuing.

The second is a resubmission. Hacker News's FAQ allows a story to be posted again if it hasn't had significant attention in roughly a year, but repeatedly deleting and reposting the same link is not okay and duplicates get buried. If you want the mechanics behind the rest of the site's unwritten behavior — flag thresholds, the flamewar detector, the two-hour edit window — Max Woolf's Hacker News Undocumented is the most careful public catalog of it.

How do you survive the comments?

Candor beats defense, every time. The comment that stings — “why not just use a cron job and forty lines of Python?” — is usually the most valuable one in the thread, and the whole room is watching how you take it. Answer the strongest version of the objection, concede the part that's true, and explain the case where your thing is actually better. That exchange converts more skeptics than the product page ever will.

The site guidelines ask for the same posture from everyone: be kind, avoid snark, and respond to the strongest interpretation of what someone said. They also now state plainly that Hacker News is for conversation between humans and ask you not to post AI-generated text — which, in 2026, is worth reading twice before you paste a polished reply into a thread. A slightly awkward answer in your own voice reads better on HN than a fluent one that isn't.

Two practical habits. Reply to everything for the first few hours, including the terse ones. And when someone finds a real bug, fix it live and say so in the thread — “good catch, deployed” is the single highest-return comment a founder can make on Hacker News.

What is a Hacker News front page actually worth?

Honestly: nobody credible publishes a number, and we're not going to invent one. You'll see “5,000–30,000 uniques in 24 hours” repeated across launch roundups; we tried to trace it to a primary source and couldn't, so it doesn't appear in this guide as a fact. Traffic from a front page varies by an order of magnitude depending on position, hour, and how long you hold — plan for the possibility that it's modest.

What's reliable is the composition and the residue. The composition: the people arriving are developers, technical founders, and infrastructure buyers, which is why a Show HN converts unusually well for developer tools and unusually badly for consumer apps. The residue: the thread itself becomes a permanent, indexed page carrying your product name, your link, and a public technical discussion of your work — which keeps earning long after the spike. That last part matters more in 2026 than it used to, because community discussion is one of the source types answer engines lean on most heavily; Reddit and Wikipedia together account for over a quarter of US ChatGPT citations (Similarweb). A substantive HN thread about your product is exactly the kind of durable, attributed material that gets pulled into answers.

Which reframes what “arrive with momentum” means here. On Product Hunt you can legitimately line up a crowd to show up on the day. On Hacker News you cannot — and shouldn't try. The only momentum that transfers is preparation: a product that survives contact with strangers, because people who ship already found the bugs; a first comment you've stress-tested; and a clear head on the day because the rest of your launch-day checklist is already done. Where HN sits in the broader sequence — before the directories, after the quiet beta — is covered in the startup launch directories guide.

That preparation is the part a solo founder can actually buy with effort instead of money, and it's the reason Favors.dev exists. It's a marketing co-op where founders trade verified help — real testing, honest feedback, reviews from people who used the thing — metered by a points economy so you can't spend what you haven't earned. Nobody there will upvote your Show HN. What they will do is find the broken onboarding step on the Tuesday before you post it, which is worth considerably more.

Frequently asked questions