PRACTICAL WORKFLOWS

Build an email design preview for client review

An email preview can communicate visual direction before implementation. Label it as a concept or screenshot so reviewers understand what has been tested.

Put it into practice

  1. Capture or prepare the approved email design.
  2. Place it in a simple browser or screenshot frame.
  3. Document which parts still need email-client testing.

What this looks like

WORKED EXAMPLE

A client reviews the hero image and typography before HTML email development.

A detail to keep clear

A polished preview does not prove compatibility with Gmail, Outlook or mobile email clients.

Using MockupX

These workflows describe ways to use the editor, not separate automated services. Keep original images and delivery notes outside the editor when a repeatable handoff matters. For paid work, check rights to screenshots, brand assets and stock imagery before publishing.

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