How to Create Product Hunt Launch Visuals That Stand Out

Product Hunt launches are visual competitions. With dozens of products launching every day, your gallery images are often what makes someone stop scrolling and click.

Here's how to create visuals that actually get attention.

The First Image Matters Most

Your first gallery image appears as the thumbnail. It needs to:

• Show what your product does immediately
• Be visually striking
• Work at small sizes
• Stand out from typical SaaS screenshots

This isn't the place for a plain screenshot. Use a mockup with a beautiful background that pops.

What Your Gallery Should Include

A strong Product Hunt gallery typically has 4-6 images:

• Hero shot - Your product in a beautiful device frame
• Feature highlights - 2-3 key features with context
• Before/after - If applicable, show the transformation
• Social proof - Testimonials or user numbers (if you have them)
• Pricing or CTA - Make it easy to understand next steps

Design Tips That Work

Use consistent styling

All your images should feel like they belong together. Use the same:

• Background colors or gradients
• Device frames
• Typography (if adding text)
• Spacing and margins

Add context with device frames

A screenshot of your dashboard is boring. That same screenshot in a MacBook frame with a gradient background? Now it looks like a real product.

Keep text minimal

If you add text overlays, keep them short:

• 3-5 words max per image
• Focus on benefits, not features
• Use a readable font size

Mind the aspect ratio

Product Hunt displays images at roughly 16:9. Design for this ratio to avoid awkward cropping.

Common Mistakes to Avoid

• Using raw screenshots without any styling
• Inconsistent design across images
• Too much text that's unreadable at small sizes
• Low resolution exports
• Outdated device frames (iPhone X in 2025 looks dated)

The Quick Workflow

Here's a fast way to create your launch gallery:

• Screenshot your product's key screens
• Upload each to a mockup generator
• Apply the same device frame and background to all
• Export at high resolution
• Add to Product Hunt in the right order

With a tool like Screenhance, this whole process takes about 10 minutes for 5 images.

Timing Your Visual Prep

Don't leave visuals until launch day. Use the Product Hunt launch checklist to stay on track and prepare them at least a day before:

• Create all your gallery images
• Get feedback from someone who hasn't seen your product
• Make sure they tell a coherent story
• Test how they look at thumbnail size

The First-Image Test

Your first gallery image does 80% of the work. It's what shows on the launch card, on the search result, and inside the timeline feed. If it doesn't stop the scroll, the other four images never get seen.

Hold your first image up against this three-part test before you publish.

The five-second test. Show the image to a stranger for five seconds. Ask "what does this product do?" If they can't tell, the image is too abstract or has too many competing elements. Strip it back to a single clear product moment, ideally with one bold headline overlay (3–7 words). The thumbnail test. Shrink the image to 200×120px. Can you still read the headline? Can you still tell what the product is? If not, your text is too small or your composition is too busy. Headlines on Product Hunt gallery images need to read at thumbnail size — that's how 90% of upvoters will first see them. The competitor test. Open the Product Hunt homepage from the day you plan to launch. Drop your first image into the grid mentally. Does it stand out? If every other launch is using a dark gradient with a screenshot, a similar treatment will get lost. Pick a deliberately different palette — bright, dark, or unusual ratio — to win attention at a glance.

Iterate the first image more than any other in the set. Three to five rounds is normal.

Animated vs Static for the Gallery

Product Hunt supports both static images and short videos in the gallery. The right mix:

• Image #1 — static. Stops the scroll faster than video. Goes everywhere as the launch card.
• Image #2 — animated (optional). A 4–6 second WebM showing one core interaction. Use only if the animation makes the product clearer; otherwise stick with static.
• Images #3–5 — static. Feature breakdowns, social proof, pricing — anything text-heavy is better static so people can read at their own pace.

Animations are evaluated harshly: if it loops awkwardly or runs longer than 6 seconds, viewers will judge the product as unpolished. Export as WebM, not GIF — same quality at a fraction of the size, which matters on mobile data.

Frequently Asked Questions

What dimensions should Product Hunt gallery images be?

1270×760 pixels (the supported max). Product Hunt accepts anything from 1024×576 upwards, but exporting at the largest supported size gives the sharpest result on Retina displays. Use a Product Hunt gallery generator preset to hit the exact dimensions without manual cropping.

How many images do I really need?

Five is the sweet spot. You can upload up to ten, but viewers rarely swipe past the third or fourth. Better to ship five strong images than ten mediocre ones. The five-image template most launches use: hero, key feature, secondary feature, social proof / testimonials, pricing.

Should the headline text be on the image or in the launch comment?

Both — and they should be different. The on-image headline is the visual hook (3–7 words). The launch comment is the longer narrative (the why, the story, the ask). Repeating the same headline in both places wastes attention.

Can I reuse the same images across Twitter, LinkedIn, and Product Hunt on launch day?

Reuse the design, not the export. The first image should be re-cropped for each platform's native aspect ratio (square for LinkedIn feed, 16:9 for Twitter, 1270×760 for PH). A single design exported at three sizes outperforms a one-size-fits-all crop.

When should I start preparing visuals before launch?

Two weeks. One week for design and iteration, one week for feedback, edits, and the inevitable last-minute "we need to swap image #3" panic. Founders who design visuals the night before launch consistently underperform — the work is too important to rush.

Should I A/B test the first gallery image before launch day?

Yes, but not on Product Hunt itself — by the time you'd see meaningful data, the launch window is over. Test ahead of time on Twitter or LinkedIn. Post the same product copy with two different first-image candidates a week apart. The one with higher click-to-profile rate wins. You're not measuring upvotes, you're measuring "does this image stop the scroll." That signal transfers cleanly to the PH thumbnail context.

Do hunter and maker comments need different visuals attached?

The maker comment usually gets the most attention, so put your strongest secondary image there — the one that shows the "aha" moment of the product. The hunter comment can use a more contextual shot (founder photo, team photo, or the problem-statement image). Don't repeat the gallery's first image inside the comments; you'd be wasting prime visual space.

How should multi-product launches handle visuals across the suite?

Pick one visual system — frame, palette, type — and apply it to every gallery in the suite. The reason isn't aesthetic, it's recall. If someone upvotes your first product on Tuesday and your second on Friday, the matching visual language reinforces that they're from the same team. Differentiate inside the system (different accent colors per product), but never break the system.

What visual should I post for the day-after engagement push?

A milestone shot — "#3 product of the day" overlaid on your first gallery image, or a thank-you visual with upvote count. Keep it produced at the same quality as your launch images, not a quick screenshot of the PH page. Founders who post celebratory blurry phone shots undercut the work they just spent two weeks polishing.

Why Launch-Day Visuals Tank When They Were Good Enough in Figma

The most common pattern I see: founders design a gallery they're proud of on a 27-inch monitor, hit publish, and then watch upvote velocity stall in the first three hours. The visuals weren't bad. They just weren't built for the context where they actually show up.

Product Hunt's grid renders your first image at roughly 350px wide on desktop and 180px wide on mobile. Inside that thumbnail, your product is competing against twenty other launches stacked vertically in the feed. The Figma canvas you designed on is six to ten times that size. Everything legible at 1270x760 disappears at 180px — fine details, body text, subtle gradients, secondary UI elements. What survives the shrink is silhouette, contrast, and a single bold focal point.

The fix isn't to redesign at 180px. It's to design at 1270x760 and then constantly preview at 180px throughout the design process. Keep a browser tab open at thumbnail size next to your editor. Every time you push a change, check both. If the change is invisible at thumbnail size, it's not load-bearing — strip it. If a change improves the thumbnail at the cost of the full-size detail, take it. The thumbnail wins the click; the full-size image is bonus material.

The second reason "good enough in Figma" tanks: nobody saw the gallery in launch-day context before launch day. Drop your first image into a screenshot of the actual Product Hunt feed before you publish. You'll spot palette collisions (everyone else used purple gradients that day too) and silhouette overlaps (three other products have a MacBook frame in the same orientation) that are invisible when you view your work in isolation. The Product Hunt gallery generator presets help, but the context check has to happen manually.

Visual Prep Timeline That Survives a Real Launch Week

Most launch checklists tell you to "start visuals two weeks early." That's directionally right but useless as a plan. Here's the day-by-day breakdown that actually holds up under launch-week pressure.

T-14 to T-10: Concept and first drafts. Define your gallery's narrative — what story do these five images tell in order? Sketch each image's purpose as a single sentence before opening a design tool. Draft all five images quickly, lower fidelity, just to validate the sequence. Don't polish anything yet. T-9 to T-7: First-image obsession. Spend three full days on the first image alone. Three variations minimum. Show each to five strangers (not your team — they're biased toward your taste). Pick the version that scored best on the five-second test. The other four images can wait — they don't carry as much weight. T-6 to T-4: Build the remaining four. Now polish images two through five against the styling you locked in for image one. Same device frame, same palette family, same type. This goes faster because the constraints are set. T-3: External feedback round. Show the full set to two trusted advisors who launch on PH themselves. They'll catch issues your team is blind to — the same way authors need editors. Take notes; don't argue. T-2: Final edits and exports. Make the feedback edits. Export everything at the right dimensions. Compress for web (under 500KB each). Stage them in a folder named with launch date. Upload to PH as a draft and check the actual platform rendering. T-1: Buffer day. Do not design today. This day exists for the inevitable disaster — your CDN goes down, your designer is sick, you spot a typo at 11pm. Founders who use T-1 for "one more polish pass" introduce more bugs than they fix. T-0: Launch. Don't touch the gallery during the launch day itself. You'll be tempted to swap an image at hour four when upvote velocity stalls. Resist. The data you'd be reacting to is too noisy to be reliable. Save iteration ideas for the post-mortem and your next launch.

Related Reading

• How to Make a Mockup: Complete Beginner's Guide - Step-by-step mockup tutorial
• How to Create Product Hunt Mockups That Get Upvotes - Detailed mockup guide for Product Hunt
• 7 Screenshot Mistakes That Make Your Product Look Amateur - Avoid these common pitfalls
• Best Screenshot Size: Complete Guide - Optimal dimensions

Conclusion

Your Product Hunt gallery is a visual pitch. A Product Hunt gallery generator can help you create cohesive images quickly. Every image should reinforce why someone should care about your product.

Keep it professional, keep it consistent, and make sure that first image stops the scroll.

Good luck with your launch.