How to Get to the Front Page of Hacker News (Show HN)
What makes a Show HN post land: format, timing, the first comment, and how to handle the thread in the first two hours." target_keyword: "show hn front page
Getting a Show HN to the Hacker News front page comes down to four things: a working demo people can try, a plain factual title, posting in the Tuesday-to-Thursday morning window, and replying to every comment in the first two hours. Front-page placement is decided largely in the first 60 to 90 minutes by early vote velocity, so the work is half preparation and half being glued to the thread the moment it goes live. There is no upvote hack that survives HN's ring detection, so do not try one.
Hacker News sends a concentrated burst of technical, high-quality traffic when a post lands, and it is one of the few places where an unknown founder with a genuinely interesting build can outrank a funded competitor on merit alone. Here is how to give yourself the best shot.
First, qualify: is your thing even a Show HN?
Show HN has specific rules, and breaking them gets your post pulled. It is for something people can actually try, software they can run, a site they can use, hardware you can show in a video. Off topic: blog posts, sign-up pages, waitlists, newsletters, and anything that cannot be tried out. If your work is not ready for people to use, do not do a Show HN yet; come back when it is.
The project should be non-trivial and personal, something you built and are around to discuss. Early-stage and rough is fine; the community is comfortable with work in progress. What it cannot be is a landing page with a "join the waitlist" button.
The title is most of the battle
HN punishes hype. The title format that works is plain and specific:
Show HN: [Product] – [one-line description of what it does]
No adjectives, no exclamation marks, no version numbers, no "revolutionary." Specific digits and concrete results outperform vague claims: "Show HN: I cut my AWS bill 82% with a 200-line Lambda" beats "How I saved money on AWS." State what it is and one thing that makes it interesting. Let the work be the hook.
Timing: when to post
Vote velocity decays with time, and HN's gravity multiplier rises every 45 minutes, so a post that gets 10 upvotes in the first 15 minutes outranks one that gets 50 over six hours. You want to launch when your audience is awake and at their desks.
The community-validated windows:
- Tuesday through Thursday, roughly 8 to 10am Eastern (engineers checking news before stand-up, with the West Coast online by the end of it).
- Sunday evening is a solid second choice: lower competition, a more exploratory audience.
- Avoid Monday mornings (everyone is digging out of backlog) and Friday afternoons into the weekend (no one starts a deep comment thread heading into Saturday).
The launch sequence
- Have the live demo URL ready. Not a waitlist. The link must show the thing working, ideally with no signup barrier, you get far more feedback when people can try it immediately.
- Write your first comment before you submit. The moment your post is live, post a comment: a short "I built this because..." that explains the problem, your technical choices, and honest limitations, plus one specific question to seed discussion. This frames the whole thread.
- Reply to every comment for the first two hours. This is the window that decides front page or obscurity. Answer questions out of genuine curiosity, suggest alternatives instead of getting defensive, and treat every critique as useful. Silence in this window reads as abandonment, and thin engagement gets punished by the algorithm.
- Share the link where your real audience already is and let votes come honestly. Do not message friends asking for upvotes; that is against the rules and HN's ring detection is strong enough to shadowban your URL or ban your domain.
If you miss the front page
Do not delete and resubmit, that behavior gets you flagged. HN has a "second-chance" pool where moderators occasionally re-expose strong posts that did not surface the first time. You get one shot at organic graduation plus that long-tail chance. If it truly did not land, a different, well-prepared submission on another day is fine, but reposting the same thing repeatedly is not.
Handling the comments
The HN comment culture is direct and can feel harsh, but the rules cut both ways: people are expected to be respectful and to ask questions out of curiosity rather than cross-examine. Your job is to be the calm, helpful person in your own thread. When something genuinely is not good, acknowledge it; do not pretend. Founders who answer every comment thoughtfully see the strongest sustained traffic, well beyond launch day.
Where Okara fits
A good Show HN is mostly preparation, the title, the first comment, the timing, the honest framing, and then intense presence in a two-hour window. The preparation is exactly the part founders underinvest in, usually writing the title and first comment in a rush minutes before posting. Okara's Hacker News agent drafts Show HN post variations in a technical, builder's voice, including the title and the "I built this because" first comment, so you go in with framing that fits the community instead of improvising. It is draft-first; you pick and edit before anything goes live, and you still own the live thread. Point it at your site to see the Show HN angles it would draft for your launch.
Frequently asked questions
What time should I post a Show HN? Tuesday through Thursday, about 8 to 10am Eastern, or Sunday evening. The first 15 to 30 minutes of vote velocity largely decide front-page placement.
Can I ask friends to upvote my post? No. HN explicitly prohibits it, and its ring detection can shadowban your URL or ban your domain permanently. Share where your real audience is and earn votes honestly.
My product is just a landing page. Can I still do a Show HN? No. Show HN requires something people can actually try. Landing pages, waitlists, and sign-up pages are off topic. Wait until the product is usable.
What goes in the first comment? A short "I built this because..." explaining the problem, your technical approach, and honest limitations, plus one question to start discussion. Write it before you submit and post it immediately.
What if my post doesn't make the front page? Don't delete and repost the same thing. HN has a second-chance pool that can re-surface strong posts. You can try a different, well-prepared submission another day, but repeated reposting gets you flagged.