ClearType
ClearType is Windows’ subpixel font-smoothing for displays with horizontal RGB or BGR stripe geometry. It paints antialiased glyph edges using the individual color stripes inside each pixel so text can look sharper than grayscale antialiasing alone—when the assumed stripe order matches the panel.
In plain language: ClearType bets on your subpixels. Wrong bet → colored fringing. No bet (grayscale) → softer edges, no stripe-order dependency.
Core claim
ClearType is a contract between renderer geometry and panel geometry. Windows exposes that contract through several setting planes and APIs that do not all share the same scope. The inbox tuner UI often narrates a simpler story than GDI, WPF, and DirectWrite actually implement—especially across multiple monitors.
That is product representation: product representation is the bug.
What users are choosing
-
On / off — ClearType vs grayscale smoothing (or smoothing disabled entirely)
-
RGB vs BGR — which horizontal stripe order the filter assumes
-
Contrast / sample pages — how heavy filtered stems look (some wizard pages have been dead weight on modern Windows)
Engineering detail and citations: Dev-Centr — ClearType.
Why it is an HCI topic
Reading text is a first-class daily job. Subpixel filtering is invisible when correct and loudly wrong when mismatched. The settings surface must not imply capabilities the text stack does not deliver.
-
Honest global tools (for example Better ClearType Tuner) expose one RGB/BGR dial for the session.
-
Partially honest wizards (
cttune.exe) offer a monitor picker while GDI orientation remains session-global and DirectWrite monitor params remain app-opt-in.
When monitors disagree
Covered fully in the engineering article; short form here:
If an RGB laptop and a BGR external share a desk, no stock path gives every app two independent GDI orientations. Avalon per-display PixelStructure values can differ; many apps never consume them per HMONITOR. Forcing BGR in a global tuner “fixes” one panel and fringes the other.
Essay: ClearType Tuner in Windows.
Evidence map
| Claim | Sources |
|---|---|
WPF documents per-display |
|
DirectWrite can load defaults per |
How to Add Support for Multiple Monitors; |
GDI orientation is a single SPI value |
|
Inbox tuner page → registry mapping |
|
Better ClearType Tuner sets all monitors the same on purpose |
See also
-
Open-with interrupt — another first-class gesture / honesty pattern