How to Launch on Hacker News: A Show HN Guide for 2026

Here is how to launch on Hacker News in one line: post a "Show HN" with a link people can actually use, add a first comment explaining what it is and why you built it, then stay in the thread and answer everyone. Don't ask a single person for an upvote. That's the whole method.

The rest of this is detail, because the details are where people get it wrong. A Show HN is one of the few places a solo builder can put a project in front of thousands of sharp, technical people in an afternoon. It's also blunt, allergic to marketing tone, and mostly a lottery. All three things are true at once.

What a Show HN actually is

A Show HN is a specific kind of submission, not a normal link with a label on it. It's for something people can try. "Something you've made that other people can play with," in HN's own words. Software they can run, a site they can use, a thing they can hold.

That rules out a lot. HN's guidelines are explicit that blog posts, sign-up pages, newsletters, and lists don't qualify. If your link is a waitlist or a landing page with a "request access" button, it isn't a Show HN, and the community will say so. The bar is simple: can a stranger use the thing right now, without you standing next to them?

A normal HN submission is you sharing someone else's link. A Show HN is you sharing your own work and inviting people to poke holes in it. The tone that follows is different, and so are the expectations.

How to launch on Hacker News: the actual mechanics

The title. It has to start with "Show HN:" followed by the name and a short description. Something like "Show HN: Fathom - offline maps for trail runners." Keep it plain. HN caps titles at 80 characters and asks you not to editorialize, so drop the adjectives and the exclamation marks. Say what it is, not how amazing it is.

The first comment. Submit the link, then immediately post a comment as the first reply on your own thread. This is where the story goes: what the thing does, the problem it solves, how you built it, and what you'd genuinely like feedback on. A few short paragraphs. This comment does more work than the title, because it's where a curious click turns into a real reader.

The etiquette, which is the part that bites. Never ask anyone to upvote. HN's guidelines put it flatly: "Please don't ask friends to upvote or comment. That's not ok on HN." They detect voting rings and they penalize them, and the penalty is worse than the quiet launch you were trying to avoid. No "we're live on HN, go smash upvote" in your group chat. Not once.

Then live in the thread. Answer every question, including the harsh ones, especially the harsh ones. The person who tears into your architecture in the first hour is often the one who ends up starring the repo. Reply like you're grateful, because you should be.

The best time to post

There's no magic minute, but there is a clear pattern. Post on a weekday, Tuesday to Thursday, in the US morning. Roughly 6 to 9am Pacific, which is 9am to noon Eastern, catches the technical crowd as they settle in with coffee. Avoid weekends and late evenings, when the site is quiet and good posts slide by unseen.

The reason timing matters is velocity. HN's front page is gated by how fast a post gathers upvotes in its first thirty to sixty minutes. Post into a busy site and a good project can catch that early lift. Post at 2am and even a great one can die in /newest before anyone notices. You're not gaming anything. You're just showing up when the room is full.

One more thing timing buys you: be awake and free for the two hours after you post. If you can't sit in the thread and reply, don't post yet. An unanswered Show HN reads as abandoned.

What kills a Show HN fast

A broken or slow link. If people click through and the demo hangs, times out, or falls over under a little traffic, that's the ballgame. Test it under load before you post. A Show HN can send a real spike, and a project that buckles on its first crowd loses the room in minutes.

Marketing tone. The quickest way to get flamed is to sound like a press release. "Revolutionary AI-powered platform" in your first comment draws exactly the wrong replies. Talk like an engineer telling another engineer what you made.

No context. A bare link with a two-word comment makes people work to understand why they should care, and they won't. Say what problem it solves in one sentence, near the top.

Over-explaining. The opposite failure. Three paragraphs of backstory before anyone can tell what the thing even does. Link to something that works, describe it briefly, and let the product carry the weight.

What to actually expect

Most Show HN posts get almost no attention. A handful of points, a comment or two, then off /newest and into the archive. That is the normal outcome, not a verdict on your work. The front page is a lottery, and the ticket is early upvote velocity you don't control.

So detach from the traffic and post for the feedback. Even a quiet Show HN usually brings a few sharp comments from people who actually opened your thing, and that's worth more than a spike. If you want that kind of honest read before you go anywhere near HN, that's part of what we built Shipyard for: post once, get real builders to use it and tell you what's broken, then launch with the rough edges already filed down.

And if it does hit the front page, clear your afternoon. A strong run can send a few thousand visitors and a hundred comments in a day. That's when the load-testing pays off.

Where it fits

Show HN is one channel, not a strategy. It suits projects with a technical hook: dev tools, something with an interesting build, anything where "here's how I made it" is itself the draw. A consumer app with no technical angle will land softer here than in a community built around its actual audience.

Run it next to the others, not instead of them. A Product Hunt launch rewards two weeks of preparation and a polished thumbnail. Reddit rewards being a genuine member of a narrow community. HN rewards a genuinely interesting thing and a thick skin. Three different rooms with three different sets of manners, and the same generic "check out my launch" post fails in all of them.

If you're deciding where to spend your energy, I've ranked the main launch channels by effort versus payoff elsewhere. Short version: pick two or three that fit your app, HN among them only if you've got a technical story worth telling, and do those properly instead of spraying one link across all of them. It's the rule that runs through everything I write about launching: show up as a builder, not an advertiser.

The hardest part of a Show HN isn't the post. It's arriving with something that survives contact with a smart, skeptical crowd, and knowing which rough edges to fix before they find them. That's the bet behind Shipyard: get honest feedback from real builders first, and have your project distributed to the right rooms the respectful way, so HN meets a version of your project that's already been stress-tested. We're letting in the first 50 founding members now. If Hacker News is on your list but you'd rather not launch cold, come and build with us.