- Official Product Hunt Launch Guide — the main overview for preparing, publishing, and promoting a launch.[1]
- Official: Preparing for launch — the best single reference for gallery images, tagline, description, thumbnail, tags, maker comment, and offers. Product Hunt recommends 1270 × 760 gallery images, requires at least two for the gallery to appear, and emphasizes a concise value proposition.[2]
- Official: How to post a product — current submission-field details, including a 260-character description, 240 × 240 square thumbnail, YouTube video support, interactive demos, pricing, makers, and the first comment.[3]
- Official: Sharing your launch — guidance on bringing an existing community to the launch and communicating the story around it.[4]
- Official: Launch timeline — useful for scheduling, creating the teaser, and planning genuine user outreach before launch day.[5]
- Awesome Product Hunt Launch Guide on GitHub — practical, skimmable advice for structuring the gallery as a visual story: strong opening image, authentic screenshots, proof, and a closing CTA.[6]
- Product Hunt Gallery Examples — visual breakdown of hero, feature, proof, use-case, and CTA slides, with emphasis on one idea per slide and a consistent design system.[7]
- Screenhance Gallery Generator — browser-based 1270 × 760 builder. Its suggested sequence is promise → proof → workflow → differentiation → action.[8]
- BrandBird Product Hunt Graphics — screenshot and promotional-asset creator aimed at launch galleries, thumbnails, social posts, and OG images.[9]
- Dribbble Product Hunt search — broad visual-inspiration gallery; useful for visual directions, but validate all dimensions and platform rules against Product Hunt’s official documentation.[10]
- Product Hunt Assets Guidelines — reusable Figma frames for thumbnail and gallery-image dimensions.[11]
- Five-slide Product Hunt Assets Template — five editable launch-asset layouts for replacing copy and screenshots.[12]
- Product Hunt Template — another editable Figma Community starting point.[13]
- Appcues Product Hunt Launch Guide — explains the roles of title, tagline, description, thumbnail, images, video, and launch-day engagement.[14]
- Swipe Files Product Hunt Playbook — practical guidance for post copy, annotated screenshots, video, launch offer, outreach, and follow-up.[15]
- Product Hunt Tagline Generator — useful for generating alternatives around outcome-led patterns; treat the output as ideation and rewrite it in the product’s actual voice.[16]
- Product Hunt Launch Generator — drafts tagline options, the short description, and the first maker comment from a site URL.[17]
- Launch Description Generator — drafts tagline, description, and first-comment copy from the offer, audience, proof, objections, and founder voice.[18]
A strong default is five to seven slides with one message per frame: promise → product in action → core workflow → strongest differentiator → proof/use case → offer or pricing → CTA. Keep typography, background, framing, and screenshot treatment consistent; show the real interface rather than stock imagery or abstract marketing art.[6][8][7]
- Hero: Product name plus a short outcome-led promise.
- Aha moment: The clearest real-product screenshot.
- Workflow: How the main task happens, ideally in two or three steps.
- Differentiator: The capability competitors cannot match easily.
- Proof: Real testimonial, measurable result, recognizable users, or before/after.
- Offer: Free tier, Product Hunt promotion, or pricing context.
- CTA: The single next action and who should take it.
- Tagline:
[Outcome] for [specific audience], or[Do outcome] without [painful alternative]. Product Hunt’s official preparation guide sets a maximum of 60 characters and recommends avoiding gimmicks and exaggerated language.[2] - Short description:
What it is + who it serves + main outcome + sharp differentiator.The current Help Center states a 260-character limit, while an older official preparation page still shows 500 characters; draft to the stricter 260-character limit and verify inside the live submission form.[3][2] - Maker comment:
Why this was built → the problem observed → what is different → key capabilities → who should try it → offer → specific feedback request.Product Hunt recommends including the story, ideal users and use cases, goals, launch offer, and a request for feedback rather than upvotes.[2]
Before exporting, show the first slide briefly to someone unfamiliar with the product and ask what it does. If the answer describes only the aesthetics, enlarge the product UI or make the benefit more explicit; the gallery should communicate product value before it demonstrates design polish.[8]