Exporting assets looks like the final mechanical step, but inconsistent export decisions create visible problems: blurry icons, oversized images, unexpected backgrounds, duplicate filenames, and assets that are difficult to replace later. A short shared standard makes handoff faster and production output more predictable.
Choose formats by content. Use SVG for simple vector icons, logos, and patterns. Use WebP or AVIF for most web photography and complex raster artwork when the delivery environment supports them. Keep PNG for transparency when lossless raster output is genuinely needed, and JPEG for broad compatibility with photographic images.
Export at the size the interface needs. A huge source image should not be shipped merely because it looks sharp in the design file. Prepare responsive variants for large editorial images and avoid manually enlarging small raster assets. For app assets, follow the platform’s density and naming conventions.
Agree on filename rules. Lowercase kebab-case names are easy to use across systems: pricing-dashboard-dark.webp is more useful than Screen Shot 2026 Final 2.png. Include meaningful variants such as theme or size, but avoid encoding every design decision into the name.
Check the bounds of vector exports. Invisible layers and oversized frames create unexpected whitespace. Outline strokes only when the production workflow requires it, and avoid converting editable text unnecessarily when the asset is maintained as source.
Compression should be evaluated visually. Icons need precise edges; photographs can tolerate more reduction. Compare the final asset at its actual display size rather than judging only at 400% zoom.
Document these decisions in a small export guide and include a few approved examples. The standard does not need to cover every possible file. It needs to make the common path clear enough that different designers produce interchangeable, production-ready results.
