Organizing, storing, and distributing design assets effectively.
Asset management is the operational foundation of design work. Every project generates files—logos, images, documents, source files. Without systematic management, assets become unfindable, outdated versions proliferate, and time is wasted searching. Good asset management makes the right file available to the right person at the right time.
Why Asset Management Matters
Findability
Can you find that file?
- The logo in EPS format
- The latest version of the guidelines
- That photo from the campaign
- The editable source file
Without management: hunting, guessing, recreating. With management: search, find, use.
Consistency
Which version is current?
- Multiple versions create confusion
- Outdated assets get used
- Brand consistency suffers
Management ensures the right version is available.
Collaboration
How do others access assets?
- Team members need files
- Partners need brand assets
- Clients need deliverables
Management enables appropriate access.
Protection
What happens if files are lost?
- Hardware fails
- Services shut down
- People leave
Management includes backup and continuity.
File Organization
Folder Structure
Consistent hierarchy across projects:
/Brand-Name
/00-Admin
- Brief.pdf
- Contract.pdf
- Timeline.xlsx
/01-Research
- Audit/
- Inspiration/
- Competitive/
/02-Strategy
- Positioning.pdf
- Brand-Strategy.pdf
/03-Identity
- Logo/
- Source/
- Exports/
- Colors/
- Typography/
/04-Applications
- Stationery/
- Digital/
- Social/
/05-Guidelines
- Brand-Guidelines.pdf
- Source/
/06-Delivered
- [Final client deliverables]
/07-Archive
- [Old versions, unused concepts]
Naming Conventions
Consistent, descriptive naming:
Elements:
- Project/brand name
- Asset type
- Version or variant
- Format indicator
Examples:
BrandName_Logo_Primary_RGB.svgBrandName_Logo_Primary_CMYK.epsBrandName_Logo_Reversed_White.pngBrandName_Guidelines_v2.1.pdf
Avoid:
final.ailogo_FINAL_v3_REALLY-FINAL.epsNew Folder (2)/stuff
Version Control
Track iterations:
Simple versioning:
- v1, v2, v3 for major versions
- v1.1, v1.2 for minor revisions
- Date stamps when relevant (2024-01-15)
Keep versions:
- Don't overwrite—save new versions
- Archive old versions, don't delete
- Document what changed
Design file versioning:
- Figma: Built-in version history
- Adobe: Manual saves with naming
- Git for code-like version control (for some)
Storage Solutions
Local Storage
Your computer:
Pros:
- Fast access
- Full control
- Works offline
Cons:
- Limited to one device
- Backup responsibility
- No collaboration
Best for: Working files, drafts
Cloud Storage
Dropbox, Google Drive, iCloud, OneDrive:
Pros:
- Access anywhere
- Automatic sync
- Basic sharing
- Built-in backup
Cons:
- Sync conflicts possible
- Storage costs at scale
- Internet required
Best for: Project files, collaboration, backup
Design Tool Storage
Figma, Adobe Cloud:
Pros:
- Native integration
- Collaboration features
- Version history
Cons:
- Tool-specific
- Subscription dependent
- Export for portability
Best for: Design source files
Digital Asset Management (DAM)
Specialized systems: Brandfolder, Frontify, Bynder, Canto
Pros:
- Built for brand assets
- Permission controls
- Search and metadata
- Usage tracking
- Distribution features
Cons:
- Additional cost
- Setup and maintenance
- May be overkill for small teams
Best for: Large organizations, multi-team, partner distribution
Asset Types
Source Files
Editable originals:
- Figma files
- Illustrator AI files
- Photoshop PSD files
- InDesign INDD files
Management:
- Keep organized and backed up
- Clear naming
- Never distribute to end users
- Archive completed projects
Production Files
Print and web ready:
- Vector: EPS, SVG, PDF
- Raster: PNG, JPG, TIFF
- Motion: MP4, MOV, GIF
Management:
- Generate from source files
- Organize by use case
- Include specifications (size, color space)
- Distribute as needed
Guidelines and Documentation
How to use assets:
- Brand guidelines PDF
- Usage documentation
- Specifications
Management:
- Keep current
- Version control
- Easy to find and share
Reference Materials
Research and inspiration:
- Competitor materials
- Mood boards
- Reference images
Management:
- Organize by project
- Note sources and licenses
- Archive after project
Distribution
Internal Distribution
Team access to assets:
Simple: Shared folder with organized structure Better: Design tool libraries (Figma teams) Best: DAM with permissions and search
Client Delivery
Final asset handoff:
Contents:
- All deliverable files
- Organized folders
- Read-me with contents
- Guidelines if applicable
Methods:
- Direct download link (Dropbox, Drive)
- Packaged zip file
- DAM portal access
Partner/Vendor Access
External parties needing brand assets:
Considerations:
- What do they need?
- What shouldn't they access?
- How to keep current?
Solutions:
- Limited folder access
- Brand portal (DAM)
- Packaged brand kit
Search and Metadata
Making Assets Findable
Beyond folder organization:
File naming: Descriptive names enable basic search
Tags/keywords: Additional searchable attributes
Metadata: Embedded information (creator, date, keywords)
DAM Features
Advanced systems offer:
- Full-text search
- Tag taxonomies
- AI-powered tagging
- Filter by attributes
- Saved searches
Backup Strategy
The 3-2-1 Rule
- 3 copies of important data
- 2 different storage types
- 1 offsite location
Backup Methods
Cloud sync: Automatic, continuous (Dropbox, Drive) Time Machine (Mac): Local versioned backup External drives: Manual periodic backup Cloud backup services: Backblaze, Carbonite
What to Backup
Priority:
- Source files
- Final deliverables
- Documentation
Less critical (can regenerate):
- Exports derived from sources
- Cached files
- Application preferences
Maintenance
Regular Tasks
Weekly:
- Organize working files
- Move completed work to proper folders
- Clear downloads and desktop
Project completion:
- Final file organization
- Archive project folder
- Verify backup
Quarterly:
- Review folder structure
- Clean old files
- Verify backup integrity
Fighting Entropy
Asset management degrades without attention:
- Files accumulate in wrong places
- Naming conventions drift
- Versions proliferate
- Backups fail silently
Schedule maintenance. Stay disciplined.