Complete Guide to Font Migration on macOS
Master macOS font migration with comprehensive strategies for safe transfer, Font Book management, system font handling, and troubleshooting
In Simple Terms
User fonts are in ~/Library/Fonts/. Back up this folder before migration. Never modify /System/Library/Fonts/ (protected system fonts).Use Migration Assistant for new Mac setup, or manually copy ~/Library/Fonts/ folder. After migration, open Font Book and run File → Validate Fonts to check for issues.Clear font cache if fonts don't appear: sudo atsutil databases -remove, then restart. Resolve duplicates in Font Book by right-clicking and choosing "Resolve Automatically."
In this article
Font migration on macOS is the process of transferring your font library from one Mac to another, or from an older macOS version to a newer one, while maintaining font organization, activation states, and application compatibility. Whether you're upgrading to a new Mac, migrating to the latest macOS version, or consolidating fonts from multiple systems, proper migration ensures your design workflow continues seamlessly without font conflicts, missing characters, or application crashes.
Unlike simple file copying, proper font migration requires understanding macOS font locations, Font Book collections, system font protection, font validation, and potential compatibility issues. Improper migration can result in duplicate fonts, corrupted font caches, applications failing to recognize fonts, or worse, system instability if system fonts are damaged.
This comprehensive guide covers everything you need to know about macOS font migration, from pre-migration preparation and backup strategies to Font Book management, troubleshooting common issues, and maintaining a healthy font library. You'll learn safe migration methods for both user fonts and system fonts, how to handle font conflicts, validate font integrity, and optimize your font library for maximum performance and reliability.
Why Font Migration Matters on macOS
Common Migration Scenarios
- Upgrading to a New Mac
- Transferring custom font libraries (100s-1000s of fonts)
- Maintaining Font Book collections and sets
- Preserving application-specific font configurations
- Ensuring design project compatibility
- macOS Version Upgrade
- System font changes (San Francisco updates)
- Font rendering engine updates
- New security restrictions on font locations
- Potential font cache rebuilding needed
- Multi-Mac Workflow
- Synchronizing fonts across studio, laptop, home
- Team font library distribution
- Consistent typography across devices
- Project portability between systems
Risks of Improper Migration
Technical Issues:
- • Duplicate fonts causing conflicts
- • Corrupted font cache files
- • System fonts accidentally deleted
- • Font validation failures
- • Applications unable to find fonts
- • Slow application launches
Workflow Impact:
- • Design projects with missing fonts
- • Incorrect font substitutions
- • Lost Font Book collections
- • Hours spent troubleshooting
- • Productivity loss during migration
- • Client deadline impacts
Benefits of Proper Migration
- Seamless Transition: All fonts immediately available in applications
- No Data Loss: Complete font library transferred safely
- Preserved Organization: Font Book collections and activation states maintained
- Optimized Performance: Clean font cache, no duplicates or conflicts
- Time Savings: Proper migration takes 30-90 minutes vs days of troubleshooting
- Project Continuity: Design files open with correct fonts immediately
macOS Font Migration Fundamentals
Understanding macOS Font Locations
/System/Library/Fonts/
- • Purpose: Critical system fonts required by macOS
- • Protection: System Integrity Protection (SIP) prevents modification
- • Examples: San Francisco, Helvetica Neue, system UI fonts
- • Migration: NEVER copy or modify these fonts
- • Restoration: macOS reinstalls automatically if needed
/Library/Fonts/
- • Purpose: Fonts available to all users on the Mac
- • Access: Requires administrator privileges to modify
- • Examples: Company-wide fonts, shared design resources
- • Migration: Copy if you have admin rights and need system-wide access
- • Best for: Multi-user Macs, shared workstations
~/Library/Fonts/
- • Purpose: Personal fonts for current user only
- • Access: Full control without admin privileges
- • Examples: Custom fonts, purchased fonts, design fonts
- • Migration: PRIMARY location to migrate (most user fonts here)
- • Best for: Individual users, personal font collections
~/Library/Application Support/Adobe/Fonts/
- • Purpose: Adobe application-specific fonts
- • Access: Managed by Creative Cloud or manual installation
- • Examples: Adobe Fonts (formerly Typekit) synced fonts
- • Migration: Let Creative Cloud re-sync; manual migration if needed
- • Note: Cloud-synced fonts re-download automatically
Font Book Database
Font Book maintains a database of font metadata and user preferences:
Location: ~/Library/FontCollections/
- • Contains: Custom font collections, disabled/enabled states, favorites
- • File: UserCollections.fcdata (database file)
- • Migration importance: Preserves your font organization
- • Backup recommendation: Always include in migration
- • Restoration: Copy to same location on new Mac
Preparation and Backup
Pre-Migration Checklist
- ☐ Document current setup: Note which fonts are critical for your work
- ☐ Verify font licenses: Ensure you have rights to transfer fonts
- ☐ Update macOS: Latest version on both old and new Mac
- ☐ Free up space: Ensure 5-10 GB free on target Mac
- ☐ Close applications: Quit all font-using apps (Adobe, Office, etc.)
- ☐ Disable font managers: Turn off Suitcase Fusion, FontExplorer, etc.
- ☐ Create full backup: Time Machine or complete system backup
Font Inventory and Audit
Using Font Book to Inventory:
- Open Font Book
- Select "All Fonts" in the sidebar
- Note total font count (shown at bottom of window)
- Review custom collections you've created
- Identify disabled fonts (grayed out)
- Export font list: File → Export Font List
Command Line Inventory:
# Count fonts in user library find ~/Library/Fonts -name "*.ttf" -o -name "*.otf" | wc -l # List all font files find ~/Library/Fonts -type f \( -name "*.ttf" -o -name "*.otf" -o -name "*.ttc" \) # Check font folder size du -sh ~/Library/Fonts
Creating Complete Font Backup
Method 1: Manual Backup (Recommended)
- Create backup folder: "Font_Backup_[Date]"
- Copy ~/Library/Fonts/ to backup folder
- Copy /Library/Fonts/ if you have admin access
- Copy ~/Library/FontCollections/ to preserve collections
- Copy ~/Library/Preferences/com.apple.FontBook.plist
- Store backup on external drive or cloud storage
- Verify backup integrity by checking file count
Method 2: Script-Based Backup
#!/bin/bash # Font backup script BACKUP_DIR="~/Desktop/Font_Backup_$(date +%Y%m%d)" mkdir -p "$BACKUP_DIR" # Backup user fonts cp -R ~/Library/Fonts "$BACKUP_DIR/User_Fonts" # Backup Font Book collections cp -R ~/Library/FontCollections "$BACKUP_DIR/FontCollections" # Backup Font Book preferences cp ~/Library/Preferences/com.apple.FontBook.plist "$BACKUP_DIR/" echo "Backup complete: $BACKUP_DIR"
Font Validation Before Migration
Validate fonts before migration to avoid transferring corrupted files:
Using Font Book Validation:
- Open Font Book
- Select all fonts (Cmd+A)
- File → Validate Fonts
- Review results: Fix "Serious Problems", note "Minor Problems"
- Remove corrupted fonts or re-download from original source
- Re-validate after fixes
Font Migration Methods
Method 1: Migration Assistant (Easiest)
macOS Migration Assistant transfers everything including fonts automatically.
Steps:
- On new Mac: Applications → Utilities → Migration Assistant
- Select "From a Mac, Time Machine backup, or startup disk"
- Connect old Mac (Target Disk Mode or WiFi)
- Choose what to transfer (ensure "Applications and Settings" selected)
- Wait for transfer (30 min - 3 hours depending on data size)
- Verify fonts in Font Book after migration
Advantages:
- • Transfers everything automatically
- • Maintains font organization
- • Preserves Font Book collections
- • No manual file copying needed
- • Officially supported by Apple
Disadvantages:
- • Transfers ALL data (not just fonts)
- • Time-consuming full migration
- • May transfer unwanted items
- • Limited control over what migrates
Method 2: Manual File Copy (Most Control)
Step-by-Step Process:
- On old Mac: Copy ~/Library/Fonts to external drive or network location
cp -R ~/Library/Fonts /Volumes/ExternalDrive/Font_Migration/
- Copy Font Book data:
cp -R ~/Library/FontCollections /Volumes/ExternalDrive/Font_Migration/
- On new Mac: Quit Font Book and all applications
- Copy fonts to new Mac:
cp -R /Volumes/ExternalDrive/Font_Migration/Fonts/* ~/Library/Fonts/
- Restore Font Book collections:
cp -R /Volumes/ExternalDrive/Font_Migration/FontCollections/* ~/Library/FontCollections/
- Clear font cache:
sudo atsutil databases -remove
- Restart Mac to rebuild font cache
- Open Font Book and verify all fonts appear
Important Notes:
- • Never copy /System/Library/Fonts (protected by SIP)
- • Preserve file permissions during copy (use -R flag)
- • Avoid overwriting existing fonts without verification
- • Test with small batch before full migration
Method 3: Font Book Export/Import
Export from Old Mac:
- Open Font Book
- Select fonts or collections to migrate
- File → Export Fonts
- Choose destination (external drive)
- Export creates organized folder structure
Import on New Mac:
- Open Font Book on new Mac
- File → Add Fonts
- Navigate to exported fonts folder
- Select all fonts (Cmd+A)
- Choose installation location (User or Computer)
- Click "Open" to install
- Verify fonts appear in Font Book
Limitations:
- • Doesn't preserve Font Book collections
- • Requires manual reorganization
- • Must recreate custom collections
- • Good for selective migration only
Method 4: Cloud Sync (Modern Approach)
Using iCloud Drive:
- Create "Fonts" folder in iCloud Drive
- Copy fonts from ~/Library/Fonts to iCloud folder
- Wait for sync to complete
- On new Mac, copy from iCloud to ~/Library/Fonts
- Note: Direct font loading from iCloud not recommended
Using Adobe Creative Cloud:
- • Adobe Fonts automatically sync across devices
- • Sign in to Creative Cloud on new Mac
- • Fonts re-download automatically
- • No manual migration needed for Adobe Fonts
- • Custom fonts still require manual migration
Font Book Management
Post-Migration Organization
Rebuilding Collections:
- Open Font Book
- File → New Collection (or Cmd+N)
- Name collection (e.g., "Design Fonts", "Body Text")
- Drag fonts from All Fonts to collection
- Create Smart Collections for automated organization
Smart Collection Examples:
- • Recently Added: Date Added → is in the last → 7 days
- • Sans Serif Fonts: Typeface → contains → Sans
- • Bold Fonts: Style → contains → Bold
- • Problem Fonts: Status → is not → Valid
Resolving Duplicate Fonts
Finding Duplicates:
- Font Book → Edit → Look for Duplicates
- Review list of duplicate fonts
- Font Book shows location of each version
- Choose which version to keep
Resolution Strategy:
- • Keep User fonts (~/Library/Fonts) over System fonts
- • Prefer newer versions (check date modified)
- • Keep fonts from original source over copies
- • Select duplicate → Edit → Resolve Duplicates
- • Choose "Move to Trash" for unwanted versions
Font Activation Management
Disabling Unused Fonts:
- Why disable fonts:
- Faster application launch times
- Reduced font menu clutter
- Lower memory usage
- Fewer potential conflicts
- How to disable:
- Select font in Font Book
- Edit → Disable
- Font grays out but remains installed
- Re-enable anytime: Edit → Enable
Font Validation and Repair
Regular Validation:
- Select fonts to validate (or All Fonts)
- File → Validate Fonts
- Review validation results
- Address serious problems immediately
- Monitor minor problems
Problem Resolution:
- • Serious Problems: Remove font, re-download from source
- • Minor Problems: Often safe to ignore, monitor behavior
- • Duplicates: Use Resolve Duplicates feature
- • Corrupted: Delete and reinstall from backup
Troubleshooting Common Issues
Fonts Not Appearing After Migration
Solutions in Order:
- Clear Font Cache:
sudo atsutil databases -remove sudo atsutil server -shutdown sudo atsutil server -ping
- Restart Mac to rebuild font cache
- Verify file permissions:
ls -la ~/Library/Fonts # Should show your username as owner
- Open Font Book, check if fonts show as disabled
- Re-add fonts manually if still missing
Application Font Menu Issues
Fonts Missing in Adobe Apps:
- Quit all Adobe applications
- Clear Adobe font cache:
rm -rf ~/Library/Application\ Support/Adobe/CoreSync/ rm -rf ~/Library/Application\ Support/Adobe/Adobe\ Fonts/
- Restart Creative Cloud app
- Sign out and sign back in
- Let fonts re-sync
- Launch application again
Fonts Missing in Microsoft Office:
- Quit all Office applications
- Clear Office font cache:
rm ~/Library/Preferences/com.microsoft.office.plist rm ~/Library/Caches/com.microsoft.*/
- Restart Office application
- Fonts should now appear
Font Book Won't Open or Crashes
- Reset Font Book preferences:
rm ~/Library/Preferences/com.apple.FontBook.plist rm ~/Library/Saved\ Application\ State/com.apple.FontBook.savedState
- Restart Mac
- Try opening Font Book again
- If still crashes, boot into Safe Mode (hold Shift during startup)
- In Safe Mode, open Font Book and validate all fonts
- Remove problematic fonts identified during validation
- Restart normally
Performance Issues After Migration
Common Causes and Fixes:
- Too many active fonts:
- Disable unused fonts in Font Book
- Aim for under 200 active fonts
- Use collections to organize fonts
- Duplicate fonts:
- Use Font Book → Look for Duplicates
- Resolve all duplicates found
- Corrupted font cache:
- Clear system font cache (see above)
- Clear application font caches
- Restart Mac
System Font Corruption
Symptoms:
- • System UI showing placeholder boxes (□□□)
- • Menu text appears garbled or missing
- • Finder showing incorrect fonts
- • System preferences display issues
Recovery Steps:
- Boot into macOS Recovery (Cmd+R during startup)
- From Utilities menu, open Terminal
- Run:
csrutil disable(temporarily) - Restart normally
- In Terminal:
sudo rm -rf /System/Library/Fonts/* # DON'T DO THIS UNLESS IN EMERGENCY
- Reinstall macOS (keeps your data)
- System fonts restored automatically
- Re-enable SIP in Recovery mode
⚠️ This is a last resort. Backup everything first!
Best Practices and Maintenance
Ongoing Font Management
- Regular Validation:
- Validate fonts monthly in Font Book
- Remove or replace problematic fonts immediately
- Keep original font files as backup
- Organized Collections:
- Create project-specific collections
- Use Smart Collections for automatic organization
- Name collections descriptively
- Periodic Cleanup:
- Remove unused fonts quarterly
- Check for and resolve duplicates
- Update fonts to latest versions
- Clear font cache if performance degrades
Font Library Organization Strategy
Recommended Structure:
- • Essential Fonts: Always active, core design fonts (20-50 fonts)
- • Project Fonts: Collections per client/project, activate as needed
- • Experimental Fonts: Fonts being tested, keep disabled until validated
- • Archive: Old/unused fonts, stored externally, removed from system
Naming Conventions:
- • Collections: "Client_ProjectName_2025"
- • Smart Collections: "Type_Category" (e.g., "Type_Sans", "Type_Serif")
- • Date-based: "Fonts_Added_2025_Q1"
Backup Strategy
- Automated Backups:
- Time Machine includes ~/Library/Fonts automatically
- Verify fonts in Time Machine backups monthly
- Keep 3 generations of backups minimum
- Manual Backups:
- Monthly backup to external drive
- Include Font Book collections
- Store original font downloads separately
- Document font licenses and sources
- Cloud Backup:
- Consider Backblaze, CrashPlan, or similar
- Ensure fonts included in backup set
- Verify license allows cloud storage
License Compliance
Important Considerations:
- User-based licenses: Some fonts licensed per user/computer
- Check if migration requires new license
- Deactivate on old Mac if license limits apply
- Subscription fonts: Adobe Fonts, Monotype, etc.
- Automatically sync to new Mac via cloud
- No manual migration needed
- Commercial fonts: Keep purchase records and licenses
- Store in secure location separate from fonts
- Include in backup documentation
Migration Checklist
- ☐ Created complete font backup
- ☐ Documented font inventory
- ☐ Validated all fonts before migration
- ☐ Removed corrupted or problematic fonts
- ☐ Migrated ~/Library/Fonts
- ☐ Migrated ~/Library/FontCollections
- ☐ Cleared font cache on new Mac
- ☐ Restarted Mac after migration
- ☐ Verified fonts in Font Book
- ☐ Resolved duplicate fonts
- ☐ Tested fonts in key applications
- ☐ Re-validated fonts on new Mac
- ☐ Recreated or verified Font Book collections
- ☐ Documented any issues and resolutions
- ☐ Created new backup on new Mac
Summary: Successful Font Migration on macOS
Proper font migration on macOS requires careful preparation, understanding of font locations and Font Book management, systematic execution using appropriate migration methods, and thorough post-migration validation. Whether using Migration Assistant for complete system transfer or manual methods for selective migration, the keys to success are comprehensive backups, font validation, duplicate resolution, and font cache management.
Following this guide ensures your entire font library transfers safely to your new Mac or macOS version, maintaining organization, eliminating conflicts, and preserving your typography workflow. Regular font maintenance, organized collections, periodic validation, and proper backups keep your font library healthy and performant for years to come.

Written & Verified by
Sarah Mitchell
Product Designer, Font Specialist
