How to post a Show HN in 2026 without getting flagged
We counted every Show HN of October 2026: the median got 2 points. What gets posts flagged, the new-account limit, and a checklist before you submit.
The numbers below come from every Show HN post in October 2026 and October 2025, taken from Hacker News' public search API on 2026-11-16. Points are as of that day.
The short answer
Post something a stranger can try in under a minute, with no sign-up required. Write the title and the body yourself, in plain language, without marketing phrasing. Use an account that has been a regular member for a while and is under a personal name, not a product name. Do not ask anyone for up-votes or comments, even in a direct message. After posting, stay in the thread for a few hours and answer questions as an engineer, not as a salesperson.
These steps address most of the reasons a Show HN gets flagged or ignored. The rest of the article breaks down each element and shows what the data say about your chances.
The odds, measured
Many Show HN guides omit this, so we counted. In October 2026 there were 4,261 Show HN posts, about 137 per day, from 3,654 different accounts. In October 2025 there were 2,395 posts, about 77 per day.
What happened to them
| Oct 2025 | Oct 2026 | |
|---|---|---|
| Show HN posts | 2,395 | 4,261 |
| Median points | 2 | 2 |
| Reached 10 points | 250 (10.4%) | 300 (7.0%) |
| Reached 100 points | 57 (2.4%) | 66 (1.5%) |
| No comments at all | 63.1% | 67.0% |
Posts increased by roughly 78%. The number that performed well changed little: 57 reached 100 points in 2025, 66 in 2026. So the typical Show HN today gets 2 points and no comments, and many more posts now compete for the same attention.
One note: posts that moderators or flags removed do not appear in the public search index, so they are not counted here. So the true share of posts without traction can only be higher, not lower.
This is why Hacker News made a change. Its Show HN update page states: "We're temporarily restricting Show HNs because of a massive influx, mostly by users who aren't yet familiar with the site or its culture." We saw this ourselves. On 2026-11-15 we created a brand-new account and tried to submit a Show HN; the system rejected it with that message and nothing was posted.
What gets a Show HN flagged
The Show HN guidelines are brief. Read them fully; the following points summarize what they rule out.
It isn't something people can try. "Show HN is for something you've made that other people can play with." Off topic: "blog posts, sign-up pages, newsletters, lists, and other reading material." Also no landing pages or fundraisers. A waitlist counts as a sign-up page. If the product isn't usable yet, make a regular submission or wait until it is.
There is a barrier. The guidelines ask for something easy to try, "ideally without barriers such as signups or emails." Moderator dang's tips for Show HN add that HN users "get ornery if you make them jump through hoops." Provide a demo mode, a sandbox account, or a free tier that doesn't require an email. MaxxMini's checklist built a ?demo link that loads sample data instantly and points the URL directly at the app instead of a landing page.
It's a quick one-off. The guidelines now say: "Don't post quickly-generated one-offs; anybody can do that now." Share something you've built and can explain.
It's a minor update. "Foo 1.3.1 is out" is not a Show HN. A major overhaul may qualify. Dang's tips advise that a repost of new work should link to the previous Show HN and describe what changed, and this "should probably only happen once or twice a year."
It reads like marketing. "Drop any language that sounds like marketing or sales. On HN, that is an instant turnoff." The HN guidelines also ask you not to use all-caps or exclamation points in titles, to omit the site name, and to avoid gratuitous numbers (e.g., "10 Ways To Do X" becomes "Ways To Do X").
The text was written by an AI. This rule is new. In an edit dated 2026-03-28, dang wrote: "Write your text by hand. Don't use an LLM to generate any of it (not even a tiny bit, including to edit or spruce it up)." The main guidelines say the same: "Please don't put generated text in HN posts." If the body sounds like a press release, readers will call it out in the comments.
Someone asked for votes. The guidelines state: "Please don't ask friends to upvote or comment. That's not ok on HN." The general rules add: "Don't solicit upvotes, comments, or submissions." Dang's tips label booster comments from friends as spam and note that HN users are good at spotting them.
You deleted and reposted. "Please don't delete and repost." If the first attempt didn't gain traction, leave it. Dang's tips mention that moderators sometimes send a repost invitation; they suggest putting your email address in your profile so moderators can reach you.
Some older advice now breaks the rules
Many older launch guides still appear in search results, but they were written before the recent rule changes. Onlook's guide from 2024 describes two launches, the first of which made the front page and earned more than 1,000 GitHub stars. The guide also advises keeping a short list of contacts to message on launch day to "get as many upvotes as possible early on" and to ask them for comments. That directly conflicts with the current guidelines.
Flowjam's line-by-line reading of the rules, updated November 5, 2026, points out the problem clearly. If your friends are on X, LinkedIn, or a group chat and you post "we're on Hacker News, come say hi," you have publicly solicited comments with a link. Flowjam writes: "A DM asking for comments is still asking." Leave the HN link out of your calls to action. If someone asks where else you posted, just answer.
Writing the title
The title should state the name and a simple description of what it does. From our October 2026 data:
- The "Name – what it does" format performed about the same as other formats: 6.9% of those posts reached 10 points, versus 7.1% for the rest.
- Short titles performed slightly better. Titles of 60 characters or fewer reached 10 points 8.5% of the time, while longer titles did so 6.3% of the time. October 2025 showed a similar gap (11.6% vs 9.7%).
- Including "open source" in the title correlated with higher scores: 11.5% of the 270 posts that used it reached 10 points, compared with 6.7% of those that did not. In 2025 the numbers were 14.2% vs 10.2%.
- AI-related words did not help. Of the 1,312 posts that contained AI, LLM, agent, Claude, GPT or MCP, 6.4% reached 10 points, versus 7.3% for posts without those terms.
- "Free" in the title performed slightly worse: 5.8% reached 10 points, compared with 7.1% for posts without it.
These are correlations from a single month each year, not hard rules. Open-source projects may do better because readers can inspect the code, not because of the wording. The overall pattern is: state what the project is, keep the title short, and avoid buzzwords.
Examples that topped October 2026: "Show HN: SimCity, but with Permits" (941 points), "Show HN: Guitoro, a virtual guitar you strum with your keyboard", and "Show HN: TitleArt – Make text like it's 1997". Each title tells the reader what to expect in a few words.
Writing the text
Dang's checklist for the post body, paraphrased:
- A clear statement of what the project is or does. Otherwise "the discussion will consist of 'I can't tell what this is'."
- A brief backstory explaining how you arrived at the project.
- What makes it different from existing solutions.
- Links to any earlier Hacker News threads that are relevant.
- Factual, direct language. "Personal stories and technical details are great."
If the text does not appear at the top of the post, add it as the first comment. MaxxMini prepared a maker comment in advance that covered three points: why they built it, the technical choices made, and specific feedback they wanted. They also wrote answers to the five expected questions so they could respond within five minutes during the first two hours.
Write the text yourself, even if it reads rougher than you would like.
Your account
Two aspects of the account matter.
Age and history. Because of the posting restriction mentioned earlier, a brand-new account might not be allowed to submit a Show HN. Create the account well before the launch and use it to comment where you have knowledge.
Username. Dang's tips: "Don't have your username be that of your company or project. It creates a feeling of using HN for promotion." We made that mistake by naming the account after our product. You don't need to use your real name; choose a username that looks like an individual's.
When to post
Views differ, and our data shows only modest variations. In October 2026, Monday had the lowest share of posts reaching 10 points (5.3%); other days ranged from 7.1% to 7.6%. By UTC time, the busiest block (12:00 to 15:59) had 1,404 posts with a 6.9% success rate, while the quiet block (00:00 to 03:59) had 349 posts and a 9.7% rate. The European morning block (08:00 to 11:59) was the lowest at 4.5%.
Onlook observed the opposite in their own launches: their Monday launch performed better than their Thursday launch, and they suggest launching around 9 a.m. Eastern. That observation is based on a single pair of launches in 2024. Our numbers cover one month, and the differences are only a few percentage points. Choose a time when you can stay in the thread for three or four hours. Onlook notes that a post's life is typically 48 to 72 hours, with the first few hours being the most important.
In the thread
- Answer questions directly and concisely. Acknowledge real limitations.
- Avoid becoming defensive. Onlook saw competitors become combative at launch, and it "never lands well."
- Do not reply with long blocks of text each time.
- If a bug is reported, fix it and note the fix in the thread.
A checklist before you click submit
- A stranger can start using it within a minute, without needing an email or signing up.
- The link points directly to the product, not to a waitlist or a landing page.
- The title follows the format "Show HN: Name – plain description", short, no hype, no exclamation mark and no number for show.
- In the body, write in your own words: what the product is, why you built it, what makes it different, and what kind of feedback you're looking for.
- Your Hacker News account is not brand-new, has some regular comments, and does not share the product's name.
- Do not ask anyone to vote or comment, in any channel.
- Be prepared to spend three free hours monitoring the discussion thread.
If the post receives 2 points, you're in the majority. Read the comments you get, improve the product, and if you later create something substantially different, you can submit again. Hacker News is just one of several launch channels; we compare the others in our guide on where to launch a side project.
More for makers
- Is Product Hunt worth it for a tiny product in 2026?
Product Hunt logs up to 1,150 new posts a day. What makers report, what a launch costs, and a 5-question test for whether your small product should launch.
8 min read
- Free launch sites in 2026: the catch on each one
We tried over 25 free launch sites for two products in Nov 2026. Each wanted something: a long wait, a badge, upvotes, a phone number or a paid last step.
10 min read
- Where to launch a side project in 2026: what 40 launch sites asked of us
We tried about 40 launch sites in six days. The dated waits, prices, badge demands and bot checks we hit, and the 8 sites we would submit to first.
9 min read