Why you should use product shots on your site

Product shots are real images of what you sell: for software, screenshots of the actual interface; for physical goods, photos of the item. Showing them on your homepage and sales pages lets a visitor see what they would get before they sign up or buy. Use them whenever someone has to understand a product to decide, which is almost always.

How to do it

1. Put one clear product image near the top of the homepage. Place it under the headline and the sign-up button so the visitor sees the promise and the proof together. Show the screen where the main result happens, not a settings page.
2. Use real data in screenshots. Fill the demo account with believable names and numbers. Empty states look unfinished, and nonsense text looks fake.
3. Crop to what matters. A full-window capture at small size is unreadable on a phone. Zoom in on the part that shows the benefit, and add a short caption saying what the reader is looking at.
4. Show the product at each step of the page. A shot beside each feature or step beats one big hero image and a wall of text. Add alt text that describes the screen.
5. For physical products, show the item from several angles and in use, on a plain background for the main image. If you sell through Google Shopping, read the rules below first.
6. Keep them current. Re-shoot after any redesign. Check the page on a phone, where images often load last or get cropped.
7. Test it. Run a two-version test on the homepage with and without the shot, and judge sign-ups, not clicks. See onboarding checklist for what the visitor sees after sign-up.

Examples

• Linear. On linear.app, checked on Oct 8, 2026, a screenshot of the app sits directly under the headline and tagline. It shows an issue open next to the sidebar, with the activity feed and comments. A visitor sees the product's layout before reading any feature copy.
• Nielsen Norman Group eye-tracking. Its research says users skip purely decorative "feel-good" images but scrutinize images of products and real people, and that stock photos of generic people are ignored. The same article found thumbnails of bookcases were studied closely while TV thumbnails were mostly ignored, so a product image has to show something useful.

When it backfires

• Decorative shots. An abstract graphic or stock image of smiling people gets skipped, according to NN/G, and adds weight to the page.
• Misleading images. A mockup showing features you do not have, or a polished render that your product does not match, costs you trust the moment a visitor opens the product.
• Marketplace and shopping rules. Google Merchant Center lists image violations including stock-photo watermarks, copyright symbols and promotional overlays. Check the rules of Google, Amazon or any marketplace you list on before you add text or logos to images.
• Slow pages. Large uncompressed screenshots slow loading, especially on mobile. Resize and compress them.
• Giving away the surprise. If your product's value is a surprise, such as a game reveal, hiding it can be intentional. For most tools, hiding the product only costs sign-ups.
• No guaranteed lift. There is no public benchmark for how much a product image changes conversions. Test on your own page.

Questions people ask

Should I show product screenshots on my homepage? Yes in most cases. Make them readable, current and tied to the headline's promise.

How do I take product shots of clothing? Use even light, a plain background, a flat lay or a model, and several angles. Merchant Center asks for a main image plus extra angles and, optionally, a lifestyle image, at least 500 x 500 pixels (a requirement that Google says applies to all products from January 31, 2027), with about 1500 x 1500 recommended.

Sources

• Linear home page, read Oct 8, 2026
• Nielsen Norman Group: Photos as Web Content, read Oct 8, 2026
• Google Merchant Center help: image link attribute, read Oct 8, 2026