Keep a trusted master
Store the source vector with editable paths and a clearly identified approved version. Preserve live construction separately if outlined delivery files are required. Do not rely on a raster image embedded inside a vector container.
Use a version and approval date so teams know which files are current.
Export by use case
Provide SVG for modern interfaces, PNG at required raster sizes, and print formats when needed. Remove unnecessary metadata, confirm transparent backgrounds, and inspect viewBox bounds so the asset does not carry accidental whitespace.
Favicon and app-icon systems may need optical adjustments rather than mechanical resizing.
- Full-color and one-color
- Light and dark background
- Horizontal and compact lockup
- SVG and required raster sizes
- Color profile
- Minimum-size guidance
Make misuse harder
Use descriptive filenames, a simple folder structure, and a short usage sheet with clear space, minimum size, backgrounds, and deprecated variants. Include contact or ownership for future questions.
Test exported files in the target applications before handoff; a valid file can still render incorrectly in a specific toolchain.
Open every delivered format in a second application, inspect transparency and bounds, and place assets on the actual product surfaces before archiving the package.