Font preferences and editor scheme settings

Apply the theme first#

Choose a registered palette in Appearance → Theme. Check Editor → Color Scheme for its matching scheme before changing font settings. This gives you a known baseline for separating color and typography changes.

Use the Absolutely font preference#

Open the Absolutely settings page and select its Editor font preference. Applying it sets the selected scheme’s editor and console font choices. The options prefer installed Styrene B or Source Serif 4 where selected, with available fallbacks; default uses JetBrains Mono.

If a preference appears to do nothing, check whether the font is actually installed and available to the IDE. Selecting a font option does not download or license that font.

Avoid competing overrides#

Editor → Font and scheme-specific font preferences also influence typography. Inspect which setting is active before changing several controls. A console font may intentionally differ from source, and a custom scheme can retain earlier font choices.

Set size/line spacing deliberately and compare source at the same zoom. A serif preference can change the reading character substantially even when all colors stay identical.

Customize colors independently#

Duplicate the supplied editor scheme before changing language categories, comments, diagnostics, or selection. The copy affects the editor; it does not create a thirty-seventh registered UI theme.

Restore a baseline#

Choose the supplied palette and matching scheme, then the default font preference when you want the default typography. Inspect another appearance provider or Settings Sync if choices unexpectedly return after restart. Include palette, actual available font, selected scheme, and IDE version in a visual report.