Font Migration on Windows: Complete Guide for Windows Users

Windows Font Landscape

Windows has a unique font ecosystem that differs significantly from macOS. Understanding these differences is essential for successful migration, especially when moving fonts between desktop use and web deployment.

Where Windows Stores Fonts

Font Inventory with PowerShell

# List all installed fonts with details
$fonts = Get-ItemProperty 'HKLM:\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Fonts'
$fonts.PSObject.Properties | Where-Object { $_.Name -ne 'PSPath' -and $_.Name -ne 'PSParentPath' } |
  Select-Object @{N='FontName';E={$_.Name}}, @{N='FileName';E={$_.Value}} |
  Sort-Object FontName | Format-Table -AutoSize

# Find legacy Type 1 fonts (need migration)
Get-ChildItem "C:\Windows\Fonts" -Filter "*.pfm" -ErrorAction SilentlyContinue |
  ForEach-Object { Write-Host "Type 1 font found: $($_.Name)" -ForegroundColor Yellow }
Get-ChildItem "C:\Windows\Fonts" -Filter "*.pfb" -ErrorAction SilentlyContinue |
  ForEach-Object { Write-Host "Type 1 font found: $($_.Name)" -ForegroundColor Yellow }

# Export font inventory to CSV
$systemFonts = Get-ChildItem "C:\Windows\Fonts" |
  Select-Object Name, Extension, @{N='SizeKB';E={[math]::Round($_.Length/1KB,1)}}, LastWriteTime
$systemFonts | Export-Csv -Path "font-inventory.csv" -NoTypeInformation
Write-Host "Exported $($systemFonts.Count) fonts to font-inventory.csv"

# Count fonts by format
$systemFonts | Group-Object Extension |
  Select-Object @{N='Format';E={$_.Name}}, Count |
  Sort-Object Count -Descending | Format-Table

# Find per-user installed fonts (Windows 10 1809+)
$userFontPath = "$env:LOCALAPPDATA\Microsoft\Windows\Fonts"
if (Test-Path $userFontPath) {
  $userFonts = Get-ChildItem $userFontPath
  Write-Host "Per-user fonts: $($userFonts.Count)"
  $userFonts | Select-Object Name, Extension,
    @{N='SizeKB';E={[math]::Round($_.Length/1KB,1)}} |
    Format-Table -AutoSize
} else {
  Write-Host "No per-user font directory found"
}

Migration Planning

Common Migration Scenarios

Converting Fonts for Web Use

Using Python FontTools on Windows

# Install Python and FontTools on Windows
# (requires Python 3.8+ from python.org or Microsoft Store)
pip install fonttools[woff] brotli ttfautohint-py

# Step 1: Auto-hint the TTF (critical for Windows ClearType)
# ttfautohint v1.8.4 (current stable)
ttfautohint input.ttf input-hinted.ttf

# Step 2: Convert hinted TTF to WOFF2
python -m fontTools.ttLib -o output.woff2 input-hinted.ttf

# Batch convert all TTF files in a directory
for %f in (*.ttf) do (
  ttfautohint "%f" "%~nf-hinted.ttf"
  python -m fontTools.ttLib -o "%~nf.woff2" "%~nf-hinted.ttf"
  del "%~nf-hinted.ttf"
)

ClearType & Hinting Considerations

Windows ClearType rendering relies heavily on TrueType hinting instructions to align glyph outlines to the pixel grid. Unlike macOS (which renders outlines faithfully regardless of hinting), Windows can produce blurry or uneven text from unhinted fonts.

# Optimal ttfautohint settings for Windows web fonts
ttfautohint ^
  --stem-width-mode=qqq ^
  --increase-x-height=14 ^
  --hinting-range-min=8 ^
  --hinting-range-max=50 ^
  --fallback-stem-width=100 ^
  input.ttf output-hinted.ttf

# Note: Use ^ for line continuation in Windows CMD
# In PowerShell, use backtick (`) instead

Enterprise Deployment with GPO

For organizations managing Windows fleets, fonts can be deployed centrally using Group Policy Objects (GPO) or Microsoft Intune for modern management.

Method 1: GPO Startup Script

# deploy-fonts.ps1 - Run as GPO Computer Startup Script
$FontSource = "\\server\share\Fonts"
$FontDest = "C:\Windows\Fonts"
$RegPath = "HKLM:\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Fonts"

Get-ChildItem $FontSource -Include *.ttf,*.otf -Recurse | ForEach-Object {
    $fontFile = $_.Name
    $destPath = Join-Path $FontDest $fontFile

    if (-not (Test-Path $destPath)) {
        Copy-Item $_.FullName $destPath -Force
        # Register the font in the registry
        $fontName = [System.IO.Path]::GetFileNameWithoutExtension($fontFile)
        $regValue = if ($_.Extension -eq ".otf") { "$fontFile" } else { "$fontFile" }
        New-ItemProperty -Path $RegPath -Name "$fontName (TrueType)" -Value $regValue -Force
        Write-Host "Installed: $fontFile"
    }
}

Method 2: Microsoft Intune

Package fonts as a Win32 app (.intunewin) for deployment through Intune. This is the recommended approach for modern cloud-managed Windows devices.

1. Place font files and an install script in a folder
2. Package with the IntuneWinAppUtil tool
3. Upload to Intune as a Win32 app
4. Set detection rule: check for font file in C:\Windows\Fonts
5. Assign to device groups

Troubleshooting Windows Font Issues