Hacker News Front Page 2026: The Playbook (Timing, Titles + the Ranking Formula)

How to hit the Hacker News front page in 2026: the real ranking formula, the exact timing window, a title good-vs-bad guide, a minute-by-minute launch sequence, a first-comment template, and what gets you banned.
Dark minimalist hero with a rising orange velocity curve, evoking Hacker News ranking
The short version: a Hacker News front-page run is decided in the first 60-90 minutes. Post Tuesday to Thursday, 8-10am ET, with a plain factual title, a working demo people can try in seconds, and a first comment ready to go - then reply to everyone for two hours. No upvote-begging (it gets you banned). Below is the exact playbook, including the real ranking formula.

From the team at Flowjam · Last updated July 2026

Fifty upvotes earned slowly will lose to twenty earned fast. That one fact - not connections, not luck - is what most Hacker News launches get wrong. HN's ranking is mechanical, the community is predictable, and the mistakes that sink a good post are all avoidable. This is the current, tactical playbook: how the algorithm actually works, when to post, the title that gets clicked, and the minute-by-minute of launch day.

A note on grounding: the ranking formula below is HN's public algorithm (see HN's guidelines and FAQ). Timing windows, vote-velocity effects, and the second-chance pool are well-observed community patterns, not secret internal weights - HN deliberately hides the exact anti-abuse and account/domain weighting. Where something is an observed pattern rather than a documented rule, we say so.

How the HN ranking algorithm actually works

Front-page rank is driven by a simple, public formula. Roughly:

score = (upvotes − 1) / (age_in_hours + 2)1.8

Two things fall out of that exponent, and they explain everything:

  • Time is a 1.8-power guillotine. The exponent on age means a post loses rank every hour whether or not it gains votes. A story that stalls drops off fast.
  • Early velocity wins. Because age is small at the start, votes in the first hour are worth far more than the same votes later. Ten upvotes in the first 15 minutes outrank 50 upvotes spread over six hours.

On top of the raw formula, HN layers user flags, anti-abuse software, an "overheated discussion" penalty, account and domain weighting, and moderator action. But the core takeaway is blunt: for most posts, your trajectory is clear within the first 60-90 minutes. Everything in this playbook exists to win that window.

What the formula means in real numbers

Plug in real values and the decay is stark. A post with 20 upvotes gets a very different score depending on how old it is:

Upvotes
Age
Score
Trajectory
20
30 min
~3.7
Climbing
20
1 hour
~2.6
Slipping
40
3 hours
~2.2
Needed double the votes to stay close
20
3 hours
~1.1
Fading
50
6 hours
~1.2
Buried

Read the extremes: 20 upvotes at 30 minutes (~3.7) beats 50 upvotes at six hours (~1.2) by 3x. Slow volume cannot buy back lost time - the 40-at-3-hours row needed double the votes just to stay in the conversation. Concretely, a Show HN posted at 9am ET usually needs its first 15-20 organic upvotes by about 9:30 to break onto the front page while the score is still high.

Step 1: is your post even a Show HN?

Most launches go out as Show HN, and it has hard rules. Get the format wrong and you are dead on arrival.

Post type
Use it for
Rule
Show HN
Something you built that people can try
Must be a working demo. No landing pages, waitlists, or signup walls. Rough and early is fine.
Ask HN
A genuine question for the community
Text post, no link. Works when the question is broadly interesting.
Link
An essay, deep-dive, or original data
No prefix. Blog posts and technical write-ups are the single largest category on the front page.

The Show HN bar: a stranger can click your link and use the thing in under a minute. If they hit a "request access" form, you are not ready. This is exactly why a Show HN lives or dies on the demo - more on that below.

Step 2: the title is most of the battle

On HN, the title is the product. There is no thumbnail, no description - just the words. The rules are strict and the community punishes hype instantly.

Loses
Wins
"Show HN: The revolutionary AI tool that will change how you code"
"Show HN: I built a CLI that turns SQL into typed API endpoints"
Adjectives, hype, exclamation marks
Plain, factual, specific
"How I saved money on AWS"
"I cut my AWS bill 82% with a 200-line Lambda"
Vague claims
Specific numbers and outcomes

Format for a Show HN: "Show HN: [Product] - [plain one-line description]". No version numbers, no "revolutionary," no marketing voice. A concrete number or result is the one lever that reliably raises clicks.

Step 3: timing - when to post

Timing is availability planning, not a magic trick - but posting when your audience is awake and competition is thin genuinely matters, because you need votes fast.

Window
Why
Best: Tue-Thu, 8-10am ET
US engineers check HN before stand-up; peak engaged audience.
Good: Sunday evening
Low submission volume, so less competition for the front page.
Avoid: Fri afternoon
Audience checks out for the weekend; momentum dies.
Avoid: Mon before 7am ET
Inbox overload; your post gets buried before anyone looks.

Step 4: the launch-day sequence (minute by minute)

Because the first 60-90 minutes decide everything, run launch like a countdown, not a click-and-hope.

T-1 day
Make sure the demo works on mobile and can survive a traffic spike (the "hug of death"). Write your title and first comment in advance.
0:00
Submit in the Tue-Thu 8-10am ET window. Post your first comment immediately.
0:00-0:15
The make-or-break window. Organic early votes here are worth 3-4x the same votes later. Do NOT message anyone asking for upvotes - just be present.
0:00-2:00
Reply to every single comment - fast, specific, non-defensive. Engagement signals keep you climbing.
If you miss
Don't delete and repost (that gets flagged). You may still catch the second-chance pool - see below.

Step 5: the first comment (post it immediately)

Your first comment frames the whole discussion. Post it the second you submit, before anyone else comments. Include four things: the problem, your technical choices, honest limitations, and one question that invites discussion.

Hi HN. I built [Product] because [specific problem you hit yourself].

How it works: [1-2 sentences on the technical approach and why you chose it].

What it does NOT do yet: [honest limitation]. [Second limitation].

I'd love feedback on [one specific, open question]. Happy to answer anything - I'll be here all morning.

Honesty about limitations is not a weakness here - it is the single fastest way to earn the room. HN respects "here's what's rough" far more than a flawless pitch.

Why the demo carries a Show HN

Here is the part most guides underweight. A Show HN is a show - the community clicks through to judge the thing, not the pitch. The posts that convert curiosity into upvotes let a skeptical engineer understand the product in seconds. That means two assets matter more than your copy:

  • A demo that works instantly - no signup, fast load, obvious what to click.
  • A short demo video or GIF at the top of the linked page and in your first comment, so people who won't run it still get the "aha" in ten seconds.

A crisp 30-60 second product video is the highest-leverage thing you can add before launch - it is what turns a skim into an upvote, because most front-page traffic will watch ten seconds of video before they will run your code. Record it yourself, or if you want it to look as sharp as the product, a tool like Flowjam turns a raw screen recording into a launch-ready demo video fast. (For the full launch beyond HN, see our product launch playbook.)

Three non-obvious edges most guides miss

  • Front-load the specific number in your title. (observed) "Show HN: I cut cold-start latency 90%..." beats burying the metric at the end - skimmers read the first few words before they decide to click or scroll.
  • Reply speed compounds into rank. (inferred - comments are not in the score formula directly) A thread where the author answers within minutes generates more comments and more repeat visits, which drives the upvotes the formula does reward. Being fast in the first hour beats being clever.
  • Post from an account with a little history. (observed) Karma does not directly boost rank, but a brand-new zero-comment account draws anti-abuse scrutiny. Two to four weeks of genuine commenting first - reply on 10-20 threads, don't just lurk - quietly removes a risk you did not know you had. Same logic for your link: a brand-new domain gets more scrutiny than a GitHub or YouTube URL.

What to do after you hit the front page

Front page is the start, not the finish. Keep replying - the discussion often runs for hours, and a thoughtful thread is what converts a spike of visitors into signups, stars, and follow-on coverage. Do not spam a follow-up post; HN expects roughly one launch per meaningful milestone. A good cadence is a fresh Show HN only after a major new capability, typically 6-12 months apart, never a re-post of the same thing. And make sure whatever you linked can take the traffic - a page that falls over at the top of HN wastes the entire window.

What gets you flagged, killed, or banned

Mistake
Consequence
Asking for upvotes (even a "check out my post" tweet)
Ring detection can shadowban your URL or ban your domain - permanently.
Coordinated voting / paid upvotes
Same - HN's anti-abuse is aggressive and unforgiving.
Delete and resubmit to "try again"
Flags the post and the account. Just don't.
Hype title / marketing voice
User flags pile up fast; the post gets buried.
Getting defensive in the comments
Turns the thread hostile; the "overheated discussion" penalty can demote you.

Tip: enable showdead in your HN profile so you can see flagged/dead posts and learn what tripped the filters.

The second-chance pool: your recovery path

Missing the front page on the first try is not the end. HN runs a second-chance pool: moderators and a small group of reviewers periodically resurface older submissions that seem in the spirit of the site, placing them onto the lower front page with a fresh timestamp. You cannot game it, but two things make you eligible: a genuinely good post that just posted at a bad time, and a clean history (no vote manipulation, no resubmitting). Post once, post well, and let it work.

Quick checklist before you submit

☐ It's a working demo anyone can try in under a minute (no signup wall)
☐ Title is plain, specific, and starts with "Show HN:"
☐ A 30-60s demo video or GIF is on the page and in your first comment
☐ Page loads fast and can survive a traffic spike
☐ First comment written: problem, tech choices, limitations, one question
☐ Posting Tue-Thu 8-10am ET (or Sunday evening)
☐ You have a clear two-hour block to reply to every comment
☐ You are NOT messaging anyone to ask for upvotes

Frequently asked questions

How many upvotes do you need to hit the HN front page?
There's no fixed number - it's about velocity, not total. Because rank is (upvotes-1)/(age+2)^1.8, roughly 10-30 upvotes in the first 30-60 minutes is often enough to break onto the front page, while the same votes spread over hours won't.

What's the best time to post on Hacker News?
Tuesday to Thursday, 8-10am ET, when US engineers check HN before work. Sunday evening also works because submission volume is low. Avoid Friday afternoons and early Monday.

Can I ask friends to upvote my Show HN?
No. HN's ring detection is strong and will penalize the post, shadowban your URL, or ban your domain. Even a public "please check my HN post" can trigger it. Let votes be organic.

Does account karma affect ranking?
Not directly - posts by high-karma users don't rank higher just for that. But brand-new zero-history accounts draw more scrutiny, so a small track record helps.

What if I miss the front page?
Don't delete and repost. Leave it up - HN's second-chance pool may resurface a good post later with a fresh timestamp. A clean history keeps you eligible.

Does a Show HN need a video?
Not required, but it's the highest-leverage add. A 30-60 second demo video or GIF lets skeptical readers get the "aha" in seconds without running your code, which is exactly what converts a visit into an upvote.

Before you post your Show HN: the single asset that converts a front-page visit into an upvote is a demo people grasp in seconds. Flowjam turns your screen recording into a launch-ready demo video - the clip you put at the top of the page and in your first comment. Make the demo undeniable and the votes follow.

Sources: HN guidelines, HN FAQ, Show HN rules, and Paul Graham's essay on HN. The ranking formula is HN's long-documented public algorithm; anti-abuse and weighting details are deliberately undisclosed.

Related reads: How to Announce a Product Launch · Best Startup Launch Campaigns · Best AI Video Generators