Show HN for a Chrome Extension: Odds from 569 Posts
Originally published on ExtensionLaunch. A Show HN for a Chrome extension can put your work in front of thousands of technical readers in an afternoon, for free. It can also get zero points, so it helps to know the odds
Originally published on ExtensionLaunch.
A Show HN for a Chrome extension can put your work in front of thousands of technical readers in an afternoon, for free. It can also get zero points, so it helps to know the odds and the rules before you post. Here is what a year of extension Show HNs looks like, the objections you will hear, and a text template to fill in.
The odds, with numbers
The ExtensionLaunch team queried the Hacker News Algolia API on October 30, 2026 for Show HN posts matching "chrome extension", submitted between October 1, 2025 and September 30, 2026:
| Result | Posts | Share |
|---|---|---|
| All matching Show HN posts | 569 | 100% |
| Reached 10+ points | 37 | 6.5% |
| Reached 100+ points | 6 | 1.1% |
Plan for the quiet outcome as well as the good one. The six posts that passed 100 points each solved a problem readers already cared about: watching pages for changes, local-first password storage, an in-browser AI model with no API keys, keeping secrets out of chatbot prompts. Three of the six linked straight to a GitHub repo.
"Open source" in a title is not a hook on its own. A clear problem is.
Check you qualify before you post
The Show HN guidelines define it as something you made that people can play with. For an extension, that means:
- It is installable now. Landing pages, waitlists and sign-up pages do not count.
- It is non-trivial and yours. You built it and you will be around to discuss it.
- It is not a minor release. "Foo 1.3.1 is out" is not a Show HN. A major overhaul probably is.
- No vote or comment requests. HN penalizes or bans submissions, accounts and sites that ask friends to upvote.
Remove the hoops
HN readers will install your extension, read its permissions and open the source if they can. Make that easy:
- Let people understand it before installing. Link a live demo, a short video or a repo with screenshots. A bare store link works only if the listing explains itself.
- Skip the account wall. If the core feature needs sign-in, offer a guest mode or a demo account for launch week.
-
Narrow your permissions. The "Read and change all your data on all websites" warning is the objection extension threads hear most. Use
activeTabwhere it fits (it shows no warning, per Google's permission warnings guide) and ask for extra host access at runtime. - Expect "Is there a Firefox version?" Ship one first if you can.
Title: plain words only
Format: Show HN: Name β what it does. HN guidelines ask for no uppercase, exclamation points or claims about how great something is.
| Instead of | Try |
|---|---|
| Show HN: TabZen β The ULTIMATE AI Tab Manager!!! | Show HN: TabZen β Group and search open tabs locally, no account |
| Show HN: I built a Chrome extension | Show HN: A Chrome extension that shows which extensions call home |
| Show HN: ReadLater β 10 reasons you need it | Show HN: ReadLater β Save articles as Markdown files on your disk |
Saying "Chrome extension" lets readers decide in a second whether they can try it.
Text: write it by hand
Moderator dang's Show HN tips, updated in March 2026, say not to use an LLM to generate or edit the text. The community reacts strongly to machine-written copy. Ask for the backstory, what is different, and no marketing language. A skeleton:
I built [name] because [the specific problem you had].
It's a Chrome extension that [what it does, concretely].
How it works: [the interesting technical part: APIs used, where data
is stored, what runs locally and what does not].
Permissions: it asks for [permissions] because [reason]. [What, if
anything, leaves the browser.] Source: [link, if open source].
It's free [or: free with a paid tier for X]. No account needed to try it.
I'd love feedback on [one specific question].
Also: do not use a company or project name as your username, and consider adding an email to your profile so moderators can reach you.
Run the thread
There is no official best time to post. Pick a window when you can stay at the keyboard for hours.
- Answer every good question, especially critical ones. "Fixed in the next version" plus a commit link is the best reply.
- Do not argue about tone. Reply to the substance.
- No booster comments. HN users spot friends' promo comments and treat them as spam.
- Say when a fix will ship. Chrome Web Store updates go through review, so do not rush an untested build.
-
Tag your link, for example
utm_source=hackernews, so you can see installs it brought.
If the post sinks, a small number of reposts is OK when a story has not had significant attention in the last year or so. Do not delete and repost. A new Show HN for a later version needs to be significantly different, with a comment linking the previous one.
Key takeaways
- Of 569 extension Show HNs in a year, 6.5% hit 10 points and 1.1% hit 100.
- Only a published, installable extension qualifies.
- Keep permissions narrow and make it usable without an account.
- Use a plain
Show HN: Name β what it doestitle and write the text yourself. - Never ask for upvotes, and stay in the thread.
For the sources behind each rule and the full FAQ, read the complete guide to planning a Show HN for a Chrome extension. After the thread, give your extension a permanent home by listing it on ExtensionLaunch.
Which objection did your last launch thread raise first: permissions, sign-in or a missing Firefox version?
Originally published by Dev.to WebDev. Aggregated on AIWithGhost for educational purposes β full credit and traffic to the original publisher.