PRACTICAL WORKFLOWS

Add a product mockup to a proposal

A proposal visual helps describe scope when its status is clear. Label concepts and avoid presenting them as completed functionality.

Put it into practice

  1. Choose the part of the proposed workflow to illustrate.
  2. Create a focused composition.
  3. State whether the interface is existing, proposed or illustrative.

What this looks like

WORKED EXAMPLE

A proposal labels a new reporting screen as a concept awaiting implementation.

A detail to keep clear

An unlabeled concept can create inaccurate expectations about delivery scope.

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