Show HN title formulas that actually work in 2026
The Show HN title formula that earns the front page is boring on purpose. Here is the structure, the data behind it, and the phrasings to avoid.
The Show HN title that works is the one a sales team would reject. Start with Show HN:, name the thing, then say plainly what it is in a noun phrase. No verbs of persuasion, no benefit promise, no exclamation point. The Hacker News crowd treats a marketing title as a signal that the product is thin, and the data backs the instinct: the median Show HN scores 2 points, and the posts that break out read like a man page, not a landing page. Signals runs an aged Reddit account marketplace plus an editorial network for AI brand mentions across Reddit, Quora, Product Hunt, and Threads, and we plan launches across all of them, so we see the same founders write a sharp Show HN title and a hype-soaked Product Hunt tagline in the same week. The HN title is the one that punishes the hype. This is the format that survives, with the evidence for why.
What is the Show HN title formula?
The formula is Show HN: [Name] – [what it is, in plain words]. That is the whole thing, and the discipline is in the second half. The description should name the category and the one concrete detail that makes the project specific, with zero persuasion. "Single-file distributable web server" works. "The fastest way to ship" does not. Hacker News readers are mostly engineers scanning for something they can run in the next five minutes, and the title is the only filter they apply before clicking. A title that tells them exactly what they will get is doing its job. A title that tells them how they will feel is asking them to take your word for it, which on this platform reads as a reason to scroll past. Get the noun right and the rest of the launch has a chance.
What does Hacker News actually require in a Show HN title?
Two things, and both are non-negotiable. First, the official Show HN rules state it plainly: "To post, submit a story whose title begins with 'Show HN'." The thing also has to be real. "Show HN is for something you've made that other people can play with," and "blog posts, sign-up pages, newsletters, lists, and other reading material" are explicitly off topic because "those can't be tried out." A waitlist is not a Show HN.
Second, the general Hacker News guidelines govern the wording: "Please don't do things to make titles stand out, like using uppercase or exclamation points, or saying how great an article is." They also ask you to cut gratuitous numbers, "translate '10 Ways To Do X' to 'How To Do X.'" Moderators enforce this by silently rewriting titles, so a hype title does not even survive to the front page in the form you wrote it.
Why do descriptive titles beat clever ones?
Because the data says clever does not convert, and clear sometimes does. The largest recent study, Daniel King's analysis of 188,085 Show HN posts from 2012 to April 2026, found a median score of 2 points and a mean of 13.5, with the 90th percentile at 24 and the 99th at 263. Most posts simply do not move, which means the title's first job is to avoid the unforced error that gets you instantly skipped.
The pattern in what does break out is consistency. ScrapingBee's analysis of 2.6 million submissions found that "almost 66% of all posts don't manage to have more than 2 points" and that absolute length barely matters; what correlates is directness, not word count. Matter-of-fact titles that state what the project is, without hype, are the ones that earn the click from an audience that has seen ten thousand "revolutionary" tools and trusts none of them.
The format that works, with examples
Here is the structure applied. The good column uses a category noun and a specific detail; the bad column reaches for a benefit or a story. These are real-world patterns drawn from front-page Show HN posts and the title teardowns in Lucas F. Costa's launch guide and Markepear's dev-tool launch breakdown.
| Works (descriptive) | Fails (marketing or vague) |
|---|---|
| Show HN: Redbean – Single-file distributable web server | Show HN: The world's most comprehensive Python library |
| Show HN: Layerform – Open-source dev environments using Terraform | Show HN: Layerform – A staging environment for each engineer |
| Show HN: OpenAPI DevTools – Chrome extension that generates an API spec | Show HN: I made a boilerplate to speed up development |
| Show HN: Heynote – A dedicated scratchpad for developers | Show HN: Revolutionize how you take notes |
The left column passes the man-page test: read it aloud and it describes a tool. The right column is selling a feeling or burying the product behind "I made." Hacker News overindexes on open-source and privacy-first projects, so if either is true, say so in the description; it is a credibility signal, not hype.
Why "I built X to solve Y" belongs in the first comment
Because the title is for identification and the comment is for story. The most common founder mistake is compressing the whole launch narrative into the title: "Show HN: I built X because I was frustrated with Y." It reads as personal and it buries the product behind your motivation. The title should answer "what is this." Your first comment, posted within the first minute, answers "why does it exist and what did you learn building it."
That first comment is where you put the origin story, the technical tradeoffs, the stack, and the honest limitations. Hacker News rewards that candor in the thread, not the headline. As the Indie Hackers front-page write-ups repeatedly show, comment depth is what keeps a post alive after the initial votes, and engaging substantively with critics outperforms defending your title. Save the narrative. The title is not the place.
How long should a Show HN title be?
Short enough to be scanned, long enough to be specific, and never past 80 characters because that is the hard platform cap. Length itself is not a lever. ScrapingBee's conclusion was blunt: "no matter your title length, your post won't perform well, but in the case it does, you'd want your title to be as short as possible," yet the reason short titles win is that they tend to be direct, not that brevity is magic. A vague 40-character title loses to a precise 72-character one every time.
The n-gram work in Peercy's analysis of 165,448 titles shows the recurring prefixes and suffixes that define the house style, and almost all of them are functional, not decorative. The practical rule: write the clearest description you can, then cut every word that does not change the meaning. Stop when removing the next word would make it ambiguous. That is your length.
Title mistakes that get you flagged or ignored
Most failures are self-inflicted and predictable. Below is the short list we check before any client submits a Show HN, drawn straight from the platform rules and what we have watched sink otherwise good launches.
The deeper point is cultural. Hacker News is not Product Hunt, where a polished tagline and a coordinated upvote push are the game. The two launches reward opposite instincts, which is why we treat them as separate disciplines when a founder runs both in the same week. If you want the timing and threshold mechanics for the Product Hunt side, our Product Hunt launch strategy pillar and the 12 AM PT timing breakdown cover that channel. For the Reddit side of a coordinated launch, the six-week pre-launch warmup guide is the companion. Show HN punishes the polish those channels reward. Write the boring title.
Frequently asked questions
What is the correct Show HN title format?
Begin the title with Show HN:, then the project name, then a plain description of what it is. The Hacker News rules require the "Show HN" prefix and that the project be something people can actually try. Keep the description factual: name the category and one specific detail, and avoid any persuasion. A title like "Show HN: Redbean – Single-file distributable web server" is the model.
How long can a Show HN title be?
The hard limit is 80 characters; titles longer than that are truncated by the platform. But length is not the optimization. Analysis of millions of submissions found that directness, not brevity, predicts performance. Write the clearest possible description, then cut any word that does not change the meaning. A precise 72-character title beats a vague 40-character one.
Should I put my product's benefit in the Show HN title?
No. Benefit and persuasion language read as marketing to the Hacker News audience and correlate with weak performance. State what the product is, not what it does for the reader emotionally. Put the origin story, the problem you solved, and the technical detail in your first comment, which you should post within the first minute of submitting.
What gets a Show HN flagged or removed?
Submitting something that cannot be tried out, such as a landing page, waitlist, blog post, or newsletter, because the rules require a working thing. Asking friends to upvote or comment, which counts as vote manipulation. And titles with uppercase, exclamation points, or self-praise, which moderators rewrite or penalize. Keep it real and keep it plain.
What score is good for a Show HN post?
Across 188,085 Show HN posts since 2012, the median score is 2 points and the mean is 13.5. Hitting 50 points puts you in the top 6%, the 90th percentile is 24, and the 99th is 263. Most posts never break out, so a few dozen points already places you well above the typical launch.
:::
