BROWSER & DESKTOP VISUALS

Use an empty-state screenshot intentionally

An empty state works when the product's setup or onboarding is the subject. For feature demonstrations, a populated state usually communicates more.

Put it into practice

  1. Decide whether the image explains starting or using the feature.
  2. Capture the appropriate state.
  3. Use a headline that matches what is visible.

What this looks like

WORKED EXAMPLE

A first-project walkthrough shows the create button, while a product hero shows a sample project.

A detail to keep clear

Do not imply a full workflow is visible when the screenshot only shows its entry screen.

Using MockupX

Browser framing communicates that the image shows a web product. Choose the browser appearance and adjust image sizing in MockupX, but use the original screenshot to decide which content matters. Decorative browser chrome does not make the underlying interface interactive.

Check the result

Keep the original screenshot, then review the exported file at the size where people will see it. Check the message, the visible interface and the final crop separately. For a handoff, record the destination and the approved file so another person can distinguish the final version from a draft.

Try it in the editor ↗Explore the related tool or guide →

References and further reading

Use the official references for format behavior and current destination requirements. The composition advice above is a practical design approach, not a promise of platform approval.

MDN image formats