The best time to post on Hacker News

People ask this question because Hacker News can feel mysterious.

One post gets 600 points. Another disappears in 20 minutes. The natural reaction is to look for the perfect hour, the perfect day, or the perfect headline formula.

There is some truth to that. Timing helps. But not in the clean, deterministic way people want.

The honest answer is:

good posts can die
average posts can catch a wave
timing helps at the margin
the rules and etiquette count for more than most growth advice admits

If you want the short version, here it is.

The Short Answer

For a normal technical post, I would start with Tuesday through Thursday, roughly 14:00 to 17:00 UTC.

That is 7am to 10am Pacific and 10am to 1pm Eastern. It lines up with when the US technical audience is awake and active, and it lines up with a lot of the practical launch advice that keeps getting repeated in decent HN guides.

But that is not the whole story.

If your goal is maximum raw audience, posting during busy US daytime hours is a reasonable default.

If your goal is lower competition, some analyses argue for Sunday night Pacific, especially around midnight to 1am Pacific, because fewer people submit then even though enough readers are still around to give a strong post an early push.

Those are two different goals:

more readers online
fewer competing submissions

People often treat them as the same thing. They are not.

What The Data Actually Says

The official Hacker News FAQ says ranking is not just votes plus time. It also includes flags, anti-abuse software, overheating penalties, account or site weighting, and moderator action. In other words, even if you knew the best time, you still would not have a guaranteed recipe for the front page. See the HN FAQ.

That is why timing advice is all over the place.

Older large-scale analysis from Max Woolf found that overall activity peaks around 12pm Eastern / 9am Pacific, but also concluded that submission time alone did not strongly determine which posts went viral. See A Statistical Analysis of All Hacker News Submissions.

Recent practical launch guides mostly converge on Tuesday to Thursday morning Pacific. See Smol Launch’s Hacker News launch guide and Calmops’ guide. These are useful, but they are also launch guides written by people who want to help you launch things, so read them as practical heuristics, not revealed truth.

Then you get a more contrarian result. A June 2025 analysis of 23,000 posts argued that the best odds came from Sunday, midnight to 1am Pacific, because competition was lower while engagement stayed decent. See When to Post on HN: Analyzed 23k posts (June 2025).

That sounds contradictory until you separate best chance per post from biggest total audience.

Those are different questions, and different articles answer different ones.

Our Take

If you want one simple recommendation, use this:

Post during US morning for broad technical posts. Try lower-competition windows for niche posts.

Concretely:

Start with Tue-Thu, 14:00-17:00 UTC for technical essays, product writeups, and serious link posts.
Test Sunday night Pacific if your post is niche, weird, or likely to benefit from less crowding.
Treat weekends as viable for side projects, longer reads, and more curiosity-driven posts.

That recommendation is also broadly consistent with our own Top HN stats page, which is useful because it shows when top stories were actually created over the last 365 days.

One important caveat: our page is a top-stories heatmap, not a magical conversion model for all submissions. It tells you when high-scoring stories tend to appear, not your personal odds of success. Over the last year, it points strongly at weekday US morning to early afternoon, especially around 14:00-17:00 UTC. That is a useful factual anchor, even if it is not the whole answer.

Use The Right Submission Type

Before worrying about time, make sure you are using the right kind of post.

Regular link post

Use a normal submission when you are sharing:

a blog post
a research writeup
a news article
a technical tutorial

Show HN

Use Show HN when you made something and people can actually try it.

The official Show HN guidelines are clear about this:

it should be something you worked on personally
users should be able to try it
blog posts, newsletters, sign-up pages, and landing pages do not count
you should be around to discuss it

This is where a lot of self-promotion goes wrong. People post a glossy homepage with no product behind it, call it Show HN, and then wonder why the thread goes badly.

HN is not confused about the difference between “I built this” and “I would like traffic to this.”

Ask HN

Use Ask HN when you genuinely want answers, recommendations, feedback, or discussion.

Do not use Ask HN as a disguised launch.

The Rules That Count

If you only read one primary source, read the official Hacker News Guidelines.

The main rules in practice are:

submit the original source when possible
do not hype the title with ALL CAPS, exclamation points, or marketing language
do not change the title unless the original is misleading or linkbait
do not use HN primarily for promotion
do not solicit upvotes, comments, or submissions
if it is a video or PDF, label it [video] or [pdf]

That last one is more important than people think. A lot of bad HN advice starts from “how do I make my post stand out?” The official answer is almost the opposite: do not decorate it.

HN generally rewards clear, plain, descriptive framing.

Etiquette Counts More Than Timing

This is the part many guides underplay.

The social rules on Hacker News are not cosmetic. They shape whether people give you the benefit of the doubt.

The official guidelines ask people to:

be kind
be curious
avoid snark
reply to the strongest version of what someone said
avoid shallow dismissals
avoid political or ideological flamewars
assume good faith
not post AI-generated or AI-edited comments

That last one is now explicit in the official guidelines: HN is for conversation between humans.

If you post your own work, the etiquette is simple:

be present
answer real questions
admit limitations
do not act like you are above criticism
do not vanish after dropping the link

One small HN thread about how to submit your product put it well: expect unrequested feedback, and read the thread from time to time so people can see the author is around. See How to Submit.

What Usually Does Well

One of the more interesting writeups on this is What gets to the front page of Hacker News?. It is imperfect and the HN comments correctly point out some methodology issues, but the broad conclusion feels directionally right:

personal technical writing does well
useful tutorials do well
thoughtful engineering blog posts do well
naked corporate promotion usually does not

That matches the official rules and it matches lived experience on the site.

If your post teaches something, explains a tradeoff clearly, shares a real build story, or gives technical readers something concrete to react to, it has a chance.

If it reads like demand generation content, it probably does not.

Practical Advice Before You Hit Submit

Here is the checklist I would actually use.

Before posting

make sure the page loads fast
put the real subject in the title
remove hype, slogans, and vague claims
make sure the article itself is worth reading without a sales agenda
decide whether this should be a link post, Show HN, or Ask HN

Right after posting

be around for the first hour
answer early questions clearly
fix obvious bugs or broken links fast
do not argue with every critic
do not ask friends to upvote

If it dies

do not panic
do not immediately repost
do not conclude the article was bad

Sometimes the window is short. Sometimes the timing was wrong. Sometimes the topic just did not match the audience that day. Sometimes HN is random.

The FAQ explicitly says ranking has other hidden factors. That is a polite way of saying you should stay humble about any theory of the system.

The Real Answer

The best time to post on Hacker News is the time when all of these are true:

the relevant readers are awake
you can stick around to answer comments
the post is on-topic for HN
the title is plain and accurate
the thing you are sharing is genuinely interesting

If you force me to give a schedule, I would say:

default window: Tue-Thu, 14:00-17:00 UTC
experimental low-competition window: Sunday night Pacific
best format for your own real product: Show HN, if people can actually try it

But the deeper advice is simpler:

Write something smart. Say plainly what it is. Follow the rules. Show up like a human.

That still beats timing tricks.