PRACTICAL WORKFLOWS

Create a screenshot for release notes

Release-note imagery should make a concrete change visible. Match the capture to the exact version described in the text.

Put it into practice

  1. Choose a current screen showing the change.
  2. Crop around the affected control or result.
  3. Include a short description in the release note itself.

What this looks like

WORKED EXAMPLE

A new sorting option is shown in an open menu beside a clear explanation.

A detail to keep clear

Do not reuse an old interface image when the release changes that interface.

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