PRACTICAL WORKFLOWS

Name exported mockups so the right file gets published

Useful filenames identify destination, version and content. A simple convention reduces mistakes during handoff.

Put it into practice

  1. Include a short feature name and destination.
  2. Add dimensions or version when they distinguish files.
  3. Separate drafts from approved assets.

What this looks like

WORKED EXAMPLE

calendar-launch-square-v2 is easier to identify than final-final-new.

A detail to keep clear

Filenames help organization but do not replace checking the file's actual contents and dimensions.

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