How to write a Product Hunt tagline
How to write a Product Hunt tagline that earns the click: six formulas, good and weak examples, mistakes to avoid, and how it fits with your listing.
Updated
Your Product Hunt tagline is one line of up to 60 characters, and it does more work than anything else on the listing. Product Hunt's own launch preparation page calls it “typically the main element that drives someone to click on a product from the homepage”. This guide is about writing one: a process, six formulas, examples, the mistakes to avoid, and how the tagline fits with the rest of your launch. Already have a tagline? Paste it into the free Product Hunt tagline checker for a live count and a checklist.
What Product Hunt asks for
- 60 characters at most. Both the Launch Guide and the launch preparation page give the same limit.
- A very short description, with no gimmicks or over-the-top language. Product Hunt's good example is “Send your friends a voicemail meow from a real cat.” Its not-allowed example is “The most ameozing app in the app store”.
- The name field takes only the name. No description or emoji unless they are part of the name, according to the help center. So the tagline is where the description goes.
- Plain words. The Launch Guide asks makers to skip the marketing gloss and “say what the product does so someone gets it on the first read”, with the Mom test as the bar.
The checker's rules section covers the mechanical checks. The rest of this page is about the writing.
Start from a one-sentence brief
Most weak taglines come from writing the tagline first. Write down three facts before you write any tagline:
- Who it is for, as specifically as you can honestly say. “Shopify store owners” beats “businesses”.
- The job it does for them, as a verb and an object: “find duplicate orders”, “turn a CSV into a dashboard”.
- What is different: the input it takes, the step it removes, or the constraint it works under, such as offline, open source or no account.
Then write ten versions without editing, and only then start cutting. Read the best three aloud and keep the one a stranger could repeat back to you. If you built your app with an AI builder, write the brief from what the app actually does, not from the prompt you gave it; how to launch a vibe-coded app explains why.
Six formulas that work
The checker page already covers [Outcome] for [who] and [Action] without [pain]. Here are six more. Treat them as starting points, not templates. Each example is for a made-up product and fits in 60 characters.
[Verb] your [thing] [how or when]
Example: “Back up your Notion workspace to GitHub every night”. Use it when one action is the whole product. The verb does the work, so pick a precise one: back up, find, merge, translate.
[Input] to [output]
Example: “Figma frames to clean React components”. Use it when your users already have the input. People see their own file or data on the left and the result they want on the right.
[Familiar category] for [narrow audience]
Example: “Invoicing for freelance translators”. Use it when the category is well understood and your edge is fitting one group closely. It falls apart with wide audiences like “teams” or “creators”.
[Job] by [familiar action]
Example: “Plan a week of meals by dragging recipes onto a calendar”. Use it when the interaction is the new part. Naming a gesture people already know makes an unfamiliar product feel easy.
[Output] written from your [existing source]
Example: “API docs written from your OpenAPI file”. Use it when the product removes manual work by reusing something people already maintain. It answers “where does the content come from?” before anyone asks.
[Category] with [the constraint people want]
Example: “A habit tracker with no account and no cloud”. Use it when the constraint is the reason to switch: offline, open source, self-hosted, no account. It works best in crowded categories.
Good vs weak tagline examples
Every line below fits the 60-character limit, and every product is made up. The weak versions are the kind of line that gets written in the submit form at the last minute.
WeakNext-gen invoicing for the modern freelancer
BetterInvoices that chase late payments for you
“Next-gen” and “modern” are filler. The better line names the painful part of invoicing and says the product handles it.
WeakYour all-in-one workspace
BetterDocs, tasks and a wiki behind one search box
“All-in-one” never says which things. Name the ones that matter, or lead with the main one.
WeakBuilt with Next.js, Supabase and GPT
BetterTurn bank CSV exports into a monthly budget
Your stack matters to you, and makes a good detail for your maker comment. People scanning the feed want to know what the product does for them.
WeakTired of messy meeting notes?
BetterAction items pulled from your meeting recordings
A question makes the reader do the work. Answer it instead.
WeakThe Uber for dog walking
BetterFind a dog walker who lives on your street
“X for Y” borrows another company's story and leaves out what makes yours different. Say the job directly.
WeakSupercharge your workflow with AI
BetterDraft replies to support tickets from your help docs
Every word of the weak line could describe thousands of products. The better one names the input, the output and the user.
WeakThe fastest database GUI ever made
BetterA keyboard-first database GUI for Postgres and SQLite
A superlative is a claim you can't prove in one line, and Product Hunt asks for no over-the-top language. A concrete trait is easier to believe.
Common mistakes
The tagline checker flags the mechanical problems as you type: going over 60 characters, a trailing full stop, all caps, emoji, hype words and repeating the product name. These are the ones a checker can't catch:
- Describing the technology instead of the result. Model names and frameworks belong in the maker comment.
- Writing for investors. “The operating system for” and “reimagining” describe ambition, not a product someone can use today.
- Insider words. Your internal feature names and acronyms mean nothing to someone scrolling the homepage.
- A feature list. “Notes, tasks, calendar, chat and docs” gives the reader five things to forget. Lead with one.
- A slogan that needs context. A pun that only lands once you know the product won't earn the click that would give people the context.
- Claims you can't back up. “#1”, “fastest” and “best” invite doubt, and break Product Hunt's no over-the-top language rule.
- An audience of everyone. “For teams” or “for creators” tells nobody it is for them.
- Repeating the tagline in the description. You have 60 characters plus 260 more. Don't spend the second allowance saying the same thing.
How the tagline works with the rest of the listing
People meet your launch in stages, and each field has its own job. Make them add to each other rather than repeat each other.
- Name: just the name, per Product Hunt's rules. It tells people what to call you, nothing more.
- Thumbnail: the square image next to your name and tagline in the feed. The help center recommends 240×240. Together, name, thumbnail and tagline are everything people see before they click.
- Tagline: what it does, and for whom. Its one job is the click.
- Description: the next level of detail on your launch page. The Launch Guide and help center cap it at 260 characters (the older launch preparation page still says 500, so write to 260). Cover the problem, how the product works and one detail only you can claim.
- Gallery: at least two images, with 1270×760 recommended, according to the help center. Make the first image show the tagline's promise happening. If the tagline says “CSV to dashboard”, image one is a CSV becoming a dashboard.
- First comment: the story. The Launch Guide calls it the Maker comment, says it sets the tone for the whole conversation, and suggests covering your product, your team, what makes it unique and the story behind the build.
A worked example
Here is how the fields fit together for a made-up product:
- Name: Gridcast
- Tagline: Turn a CSV into a dashboard you can share by link
- Description: Drop in a CSV or paste a Google Sheets link. Gridcast picks a chart for each column and gives you a dashboard at a public or password-protected link. No SQL and no setup, and nothing leaves your browser until you publish.
- First gallery image: a spreadsheet on the left, the finished dashboard on the right.
- First comment: why it was built (tired of pasting spreadsheet screenshots into Slack), what is free, and the feedback the maker wants.
The tagline promises the outcome, the description explains how, the image proves it, and the comment makes it personal. None of them repeats another.
Test it before launch day
- Try the Mom test the Launch Guide suggests. Read the tagline to someone outside tech and ask what the product does. If they can't say, rewrite it.
- Cover the name and thumbnail. The tagline should still make sense on its own.
- Read it next to today's Product Hunt homepage. Would yours stand out, or blend in with the lines around it?
- Run it through the tagline checker for the length and the mechanical checks.
- Reuse it. A good tagline also works as your landing page subheadline, your Open Graph title and your X bio. If it doesn't fit there, it probably isn't clear enough yet.
Next steps
With the tagline settled, the rest of the launch gets easier. The Product Hunt launch checklist covers timing, images and launch-day steps. Launching on Hacker News too? It works differently, so follow the Show HN launch checklist.
LaunchLoop reads your repo and live site and drafts your tagline, description, maker comment, X thread, LinkedIn post and launch images, all inside each platform's limits. The free preview includes the tagline; see pricing for the full kit.
Tagline writing FAQ
How many characters can a Product Hunt tagline have?
60, including spaces. Product Hunt's Launch Guide and its launch preparation page both give 60 characters as the maximum. You don't have to use all of them: a short line people read in one glance is usually stronger.
What is the difference between a Product Hunt tagline and the description?
The tagline is one line of up to 60 characters that sits under your product name in the feed and earns the click. The description, up to 260 characters according to Product Hunt's Launch Guide and help center, is the next level of detail on your launch page: the problem, how the product works and what makes it different.
Should I mention AI in my Product Hunt tagline?
Only if it tells people something they need to know. Product Hunt asks for plain language without gimmicks, and “AI” on its own describes how a product is built, not what it does for someone. Name the job in the tagline and explain the AI part in the description if it matters.
Can I use a formula like “Uber for X”?
It is better to avoid it. “X for Y” leans on another company's story and only works if the reader knows that company and sees the link straight away. Saying the job directly, such as “Find a dog walker who lives on your street”, is clearer.
Can LaunchLoop write my Product Hunt tagline?
Yes. Generate mode in the free tagline checker writes three options from your GitHub repo or live site, and the free LaunchLoop preview includes a tagline too. Check each option against the formulas and mistakes in this guide before you pick one.
Sources
- Launch Guide, Product Hunt Help Center
- How to post a product, Product Hunt Help Center
- Preparing for launch, Product Hunt