Which design elements should be exported?

Four types of elements to export first

• Brand and complex graphics: logos, textures, fixed-shape icons, and hand-drawn or 3D illustrations.
• Visuals that code cannot reproduce reliably: detailed gradients, layered shadows, and illustrations with fine strokes.
• Graphical controls that need a fixed appearance: special button graphics, campaign badges, and gamified medals.
• Content imagery: product images, posters, photos, and other business media.

Content that is usually better in code

Headings, body copy, prices, form fields, simple dividers, and standard rounded containers should normally be implemented with text and CSS. They need to adapt to screen widths, language length, and changing state. Turning them into images makes adaptation, search, accessibility, and maintenance harder.

Handoff checklist

1. Does every icon have a transparent background and sensible safety padding?
2. Do icons in the same family share canvas dimensions and naming rules?
3. Have editable labels, button copy, or business data been mistakenly exported as images?
4. Are image assets grouped by feature, page, or state so developers can find them?
5. Do complex visuals include implementation notes such as fixed aspect ratio, no-stretch, or light/dark variants?

Use Slice Master for one last asset review

Put the complete design screenshot into Slice Master and use automatic detection as an inventory starting point. Keep the icons and illustrations that need to ship, remove text and decorative noise, then export the selected PNG files. You receive usable assets and a quick completeness check at the same time.