How to truetype hinting vs modern subpixel rendering
- Step 1Identify your audience's renderer — Windows 10+ (DirectWrite): mostly ignores hints. Windows 7 (GDI/ClearType): respects hints. macOS/iOS (CoreText): always ignores TrueType hints. Linux freetype: respects hints if compiled with bytecode interpreter.
- Step 2Match strategy to audience — Mostly modern Windows + Mac + mobile: strip hints (no visible loss). Significant Windows 7 GDI traffic: keep hints (renders worse without). Linux-heavy server traffic: irrelevant (servers don't render fonts).
- Step 3Measure both — A/B test with and without hinting on a representative page. Most teams discover the difference is invisible to users — only a side-by-side pixel diff at 12px reveals it.
Frequently asked questions
Does Apple ever respect TrueType hints?+
No — CoreText (the macOS/iOS text engine) has never used TrueType bytecode hints. Apple uses its own glyph rasterisation tuned for retina displays. Stripping hints from fonts shipped to Apple users is always safe.
What does ClearType do?+
ClearType is Microsoft's subpixel rendering technology. It uses TrueType hints to align glyphs to the LCD subpixel grid. Without hints, ClearType falls back to grayscale antialiasing — slightly less crisp at small sizes on Windows 7.
Are hints ever useful in 2026?+
Niche cases: bitmap-emulating display fonts, technical drawings where pixel-perfect alignment matters, legacy Windows-only enterprise UIs. For 99% of consumer web typography, strip them.
Privacy first
Every JAD Font tool runs entirely in your browser using opentype.js and the wawoff2 WASM Brotli encoder. Your fonts never leave your device — verified by zero outbound network requests during processing.