How to Change the Font in Notepad++
Font selection in Notepad++ is a configuration decision with direct consequences for the quality of .dat file editing. A poorly chosen font face, size, or rendering mode increases the cognitive effort required to distinguish structurally similar characters, elevates the chance of a transcription error in a key-value pair, and reduces the legible working duration on high-resolution displays. This reference documents the full font-configuration surface available in Notepad++, explains the rationale behind each setting, and provides the recommended configuration for workstations engaged in Unturned™ mod development.
57 Studios™ maintains this reference as part of the canonical onboarding sequence for new contributors. The font configuration documented here is the configuration applied to every workstation that participates in 57 Studios™ mod releases. Community contributors who work against 57 Studios™ project templates are encouraged to adopt the same configuration so that code-review screenshots, shared screen sessions, and documentation captures share a consistent visual baseline.
Font configuration in Notepad++ is not a cosmetic decision in the context of .dat file editing. The Unturned engine relies on exact key-value pairs, and the editor that produces those pairs must make every character visually unambiguous. This reference treats font selection as a primary operational concern and documents each setting at the level of precision appropriate to that concern.
Prerequisites
Before you begin, confirm the following:
- Notepad++ is installed and the main window opens without errors. If Notepad++ is not installed, refer to How to Install Notepad++ and complete that procedure first.
- The Notepad++ version is current. The Style Configurator dialog documented in this reference matches the layout introduced in Notepad++ 8.x and verified through the current release.
- The display on which the editor will be used is connected and active. Font size recommendations in this reference vary by display resolution and pixel density, and the correct size cannot be determined without the target display active.
- Administrator rights are not required for font configuration. Font settings are stored in the user configuration directory and apply only to the current user account.
Common mistake
Changing fonts on a secondary display and then using the editor primarily on a different display with a different pixel density. Font size decisions are display-specific. The recommended practice is to complete the font-configuration procedure on each display in the workstation's regular display rotation.
What you'll learn
By the end of this reference, you will know how to:
- Open the Style Configurator and navigate its layout.
- Identify the Global Styles section and understand its relationship to per-language styles.
- Select a monospace font face appropriate for
.datfile editing. - Set a font size appropriate for the target display resolution.
- Configure the anti-aliasing mode for the target display type.
- Understand ligature support and when to enable or disable it.
- Apply font configuration changes and confirm they are active in the editor viewport.
- Save the configuration in a state that persists across Notepad++ restarts and updates.
- Evaluate font choices using the cognitive-load criteria documented in the Yamak-cohort research summary.
Background
The Unturned engine reads .dat configuration files at server startup and at item-bundle load. The engine is sensitive to exact key-value syntax, and a misread character during editing is one of the most common sources of a non-loading item. The most frequent misread characters in .dat files are the zero and the letter O, the numeral one and the lowercase letter l, the uppercase letter I and the lowercase letter l, and the colon and the semicolon. A font that renders these character pairs as visually distinguishable reduces the chance that a modder copies an incorrect value without noticing.
The distinction matters most when editing GUIDs, which appear throughout Unturned™ item bundles as 32-character hexadecimal strings. A GUID contains only the characters 0–9 and a–f. The ambiguity between zero and the letter O is the highest-risk ambiguity in this character set. A monospace font with a slashed zero, a dotted zero, or an oval zero that is clearly narrower than the letter O eliminates this risk. Proportional fonts, which are the default in most word processors and general-purpose text editors, render GUIDs in compressed runs of unequal width that are difficult to scan and compare at a glance.
The image above shows the same 32-character GUID rendered in a proportional font and in a monospace font with a slashed zero. The proportional rendering compresses the run of repeated digits at the start of the GUID into a visually ambiguous block. The monospace rendering spaces each character evenly, making the zero-versus-O distinction visible without requiring the reader to pause and inspect individual characters.
The 57 Studios™ workflow treats font configuration as the first post-installation step because every subsequent procedure in the knowledge base assumes the modder can read .dat content accurately. A modder using a poorly configured font is working at a disadvantage that compounds across the length of a session.
Step 1: Open the Style Configurator
In Notepad++, open the Settings menu in the top menu bar and click Style Configurator.
The Style Configurator dialog opens. The dialog has three panes:
- Left pane — A list of language categories. The top entry is "Global Styles," which controls the default font and color settings that apply to every language unless overridden at the language level.
- Center pane — A list of style names within the selected language category.
- Right pane — The configuration controls for the selected style: font name, font size, bold, italic, underline, foreground color, and background color.
Did you know?
Notepad++ applies a two-level style hierarchy. The Global Styles category defines the baseline appearance for all text. Individual language categories (for example, "Normal Text," "INI file," "JSON") can override specific style properties for specific token types. A font change in Global Styles propagates to every language unless the language-specific style explicitly sets a different font.
The Style Configurator dialog also contains a preview pane at the bottom that renders a sample of text using the currently selected style settings. The preview updates in real time as settings are changed and is the primary tool for evaluating font changes before applying them.
Step 2: Select the Global Styles category
In the left pane of the Style Configurator, click Global Styles at the top of the language list.
In the center pane, a list of style names appears. The most important style for font configuration is Default Style. Click Default Style in the center pane to select it.
With Default Style selected, the right pane displays the font name, font size, bold, italic, and underline controls that govern the default appearance of all text in Notepad++. Changes made here propagate to every file type and every syntax-highlighting category that does not override the font explicitly.
Pro tip
After setting the font at the Global Styles / Default Style level, review the per-language style entries for any language you use frequently. Some languages ship with a per-language font override that will take precedence over the global setting. If a specific file type appears in the wrong font after setting the global, check its language category for an override entry.
Common mistake
Configuring the font at the per-language level (for example, under "INI file") instead of at the Global Styles level. A per-language configuration applies only to files that Notepad++ has detected as that specific language. If Notepad++ detects a .dat file as "Normal Text" rather than "INI file," the per-language configuration will not apply. Setting the font at the Global Styles level guarantees consistent rendering regardless of language detection outcome.
Step 3: Choose a monospace font face
In the Font name field in the right pane, click the dropdown and select a monospace font. The recommended font faces for Unturned .dat work are listed in the table below, ranked by the criteria described in the Yamak-cohort research summary in Appendix A.
| Font face | License | Slashed/dotted zero | Ligature support | Recommended use case |
|---|---|---|---|---|
| Cascadia Code | MIT | Slashed zero | Full | Primary recommendation for most displays |
| JetBrains Mono | OFL-1.1 | Slashed zero | Full | High-density displays; slightly more compact |
| Fira Code | OFL-1.1 | Dotted zero | Full | Secondary option; very wide character repertoire |
| Consolas | Proprietary (Windows) | Slashed zero | None | Fallback when open-licensed fonts are not installed |
| Courier New | Proprietary (Windows) | None | None | Not recommended; present only as a last resort |
The four primary recommendations (Cascadia Code, JetBrains Mono, Fira Code, Consolas) are all monospace fonts that include a visually distinct zero. Courier New is listed only for completeness and is not recommended because its zero-versus-O distinction is weaker than the four primary options and its character stroke weight is uneven on modern displays that use subpixel rendering.
Did you know?
Cascadia Code was designed by Microsoft specifically for terminal and code-editor contexts. The design brief explicitly included zero ambiguity as a requirement, and the Cascadia Code zero uses a forward slash through the oval to make it distinct from the letter O at every point size above 9pt. The font ships with Windows 11 and can be downloaded at no cost for Windows 10.
The dropdown in the Style Configurator lists only fonts that are currently installed on the system. If Cascadia Code or JetBrains Mono do not appear in the dropdown, they are not installed. Both fonts are available from their respective project repositories and can be installed by downloading the font files and opening them from File Explorer. Font installation requires no administrator rights when installing for the current user only.
Consolas is installed by default on every Windows 10 and Windows 11 system and is available as an immediate fallback if the open-licensed fonts are not yet installed.
Step 4: Set the font size
In the Font size field, enter or select the size appropriate for the target display. The table below documents the recommended sizes by display configuration.
| Display type | Recommended size | Rationale |
|---|---|---|
| 1080p (1920 × 1080), 24" | 12–13pt | Standard-density display; 12pt is the historical default for terminal work |
| 1080p (1920 × 1080), 27" | 13–14pt | Larger physical screen at the same resolution; characters are physically larger |
| 1440p (2560 × 1440), 27" | 13–14pt | Higher density than 1080p/27"; characters render sharper at the same pt size |
| 4K (3840 × 2160), 27" | 14–16pt with 100% DPI scaling | Very high density; lower pt sizes render at subpixel dimensions that cause blurring |
| 4K (3840 × 2160), 27" | 10–12pt with 200% DPI scaling | At 200% DPI, the OS scales all rendering; lower pt sizes are appropriate |
| Laptop FHD, 15.6" | 11–12pt | Compact display; physical pixel density is higher than desktop 1080p |
| Ultrawide 1440p, 34" | 13–14pt | Wide format; same density recommendation as standard 1440p |
Did you know?
Notepad++ expresses font sizes in points (pt), where one point is 1/72 of an inch. The physical size of a point on screen depends on both the point size and the display DPI. At 96 DPI (the Windows default), 12pt renders at 16 pixels tall. At 144 DPI (150% DPI scaling), the same 12pt renders at 24 pixels tall because the OS multiplies the output.
The most reliable way to determine the correct size for a specific workstation is to open a representative .dat file, set an initial size from the table above, and then read fifteen to twenty lines without adjusting. If the reading feels effortful or if characters appear ambiguous at the end of a focused reading period, increase the size by one point and repeat. If the lines feel excessively sparse and scrolling feels inefficient, decrease by one point. The goal is a size at which a full session of editing does not require a mid-session rest due to visual fatigue.
Pro tip
The keyboard shortcut Ctrl and the plus key increases the font size in the active Notepad++ window in real time, and Ctrl and the minus key decreases it. These shortcuts are useful for testing sizes before committing them in the Style Configurator. Once the correct size is found through the keyboard shortcut, note the size from the bottom-right status bar and enter it in the Style Configurator for persistence.
Step 5: Configure anti-aliasing
Notepad++ delegates text rendering to the Windows DirectWrite stack. The anti-aliasing mode is not exposed as a per-font option in the Style Configurator dialog itself; it is configured through the Settings → Preferences → MISC. dialog under the DirectWrite option.
Open Settings → Preferences, navigate to the MISC. tab, and locate the Use DirectWrite (need to restart Notepad++) checkbox.
| Setting | Effect | Recommended for |
|---|---|---|
| DirectWrite enabled | ClearType and grayscale anti-aliasing via DirectWrite; supports ligatures | All modern displays; required for Cascadia Code and JetBrains Mono ligature rendering |
| DirectWrite disabled | GDI bitmap rendering; no ligature support | Legacy displays; CRT monitors; remote desktop sessions with bandwidth constraints |
Common mistake
Leaving DirectWrite disabled and then observing that ligatures do not render in Cascadia Code. DirectWrite is a prerequisite for ligature rendering in Notepad++. Enabling ligatures in the font does not produce visible ligatures if DirectWrite is disabled. The recommended sequence is: enable DirectWrite first, restart Notepad++, then configure ligatures.
On modern LCD and OLED displays, DirectWrite is the correct setting. On remote desktop sessions, the rendering behaviour depends on the remote desktop client's configuration and the network bandwidth available. High-latency or low-bandwidth sessions may produce sharper visual output with DirectWrite disabled because GDI rendering produces fewer subpixel blending artifacts at standard compression levels.
Did you know?
DirectWrite was introduced in Windows 7 and has been the standard Windows text rendering API for hardware-accelerated displays since then. The main practical difference between DirectWrite and GDI rendering in Notepad++ is that DirectWrite produces smoother diagonal strokes in fonts with angled characters, which affects the readability of characters like k, v, w, x, y, and z at small point sizes.
Step 6: Configure ligatures
Ligatures are typographic substitutions in which two or more adjacent characters are replaced by a single combined glyph. In code-oriented fonts like Cascadia Code, JetBrains Mono, and Fira Code, ligatures are available for common programming symbol sequences. The table below documents the relevant ligature sequences for Unturned .dat editing.
| Sequence | Ligature glyph | Relevant in .dat editing? |
|---|---|---|
-> | Right arrow | No; not a .dat operator |
=> | Double-bar arrow | No; not a .dat operator |
!= | Not-equal glyph | No; not a .dat operator |
== | Double-bar equal | No; not a .dat operator |
>= | Greater-or-equal | No; not a .dat operator |
<= | Less-or-equal | No; not a .dat operator |
// | Unified slash pair | Possible; appears in file-path values |
:: | Unified colon pair | No; colons are not paired in .dat |
Best practice
Ligatures in Cascadia Code and JetBrains Mono are enabled by default when DirectWrite is active. For .dat editing specifically, ligatures have a neutral effect: the common programming ligatures do not appear in .dat content, and the only candidate ligature (// in file paths) presents as a cosmetically different rendering of a sequence that carries no structural ambiguity. Leaving ligatures at their default state (enabled) is the recommended configuration for .dat work. If the editor will also be used for code in a language where ligatures cause confusion, disable them per the instructions below.
To disable ligatures in Notepad++, add the following to the user's stylers.xml configuration file in %APPDATA%\Notepad++\:
Locate the <WidgetStyle name="Default Style" ...> entry in stylers.xml and confirm the fontName attribute matches the selected font. Ligature suppression in Notepad++ is controlled through the font face selection: fonts without a ligature substitution table (such as Consolas) produce no ligatures regardless of DirectWrite mode. If ligature suppression is required for a font that ships with ligatures, the practical option in Notepad++ is to use an alternate version of the font that ships without the ligature table, if the font vendor provides one.
Pro tip
Cascadia Code ships as two separate font families in its distribution archive: "Cascadia Code" (with ligatures) and "Cascadia Mono" (without ligatures). Installing "Cascadia Mono" and selecting it in the Style Configurator produces a rendering identical to "Cascadia Code" except that no ligature substitutions are applied. This is the recommended approach for contributors who want Cascadia Code rendering without any ligature behavior.
Step 7: Apply and verify the configuration
After setting the font face, size, and anti-aliasing, click Close (or Save and Close depending on the Notepad++ version) to apply the Style Configurator changes.
If DirectWrite mode was changed, Notepad++ will prompt for a restart. Allow the restart to complete before evaluating the font rendering.
After the editor reloads, open a .dat file from the project and perform the verification steps in the table below.
| Verification check | Expected outcome | Action if not met |
|---|---|---|
| Font face visible in editor | Characters render in the selected font | Reopen Style Configurator and confirm font is set under Global Styles / Default Style |
| Zero-versus-O distinction | Zero and O are visually distinguishable | Select a font with a slashed or dotted zero from the recommended list |
| Monospace alignment | Characters in a column align vertically | Confirm a monospace font is selected; proportional fonts will not align |
| Font size matches expectation | Characters are legible at reading distance | Adjust size in Style Configurator |
| Ligature rendering (if enabled) | Programming symbol sequences appear as ligatures | Confirm DirectWrite is enabled in Settings → Preferences → MISC. |
| No rendering artifacts | No blurred or doubled character strokes | Adjust DirectWrite setting or reduce point size by one |
Cross-monitor font calibration
A workstation that spans two or more displays with different pixel densities requires independent font calibration for each display. Notepad++ stores a single global font size in the configuration file, which means the same point size applies regardless of which display the Notepad++ window occupies.
The recommended practice for multi-monitor setups is:
- Determine which display is the primary editing display. This is the display where the Notepad++ window will spend the majority of its active session time.
- Configure the font size for the primary editing display using the procedure in this reference.
- Note the point size used.
- Move the Notepad++ window to each secondary display and evaluate legibility.
- If a secondary display produces poor legibility at the primary font size, adjust the Windows DPI scaling for that display (Settings → System → Display → Scale) rather than adjusting the Notepad++ font size. DPI scaling adjustments affect all applications on that display and are preferable to maintaining separate Notepad++ configuration profiles for each display.
| Multi-monitor scenario | Recommended adjustment | Rationale |
|---|---|---|
| Primary 4K + secondary 1080p | Use primary 4K font size; increase secondary DPI scaling | Secondary display DPI is lower; scaling compensates |
| Primary 1080p + secondary 4K | Use primary 1080p font size; decrease secondary DPI scaling | Secondary display density is higher; scaling compensates |
| Two displays with identical resolution | Single font size applies equally | No adjustment needed |
| Laptop display + external monitor | Calibrate for external monitor; laptop display will benefit from its own DPI setting | Laptop displays are typically higher density than external monitors |
Did you know?
Windows 10 version 1703 and later support per-display DPI scaling. Earlier versions of Windows apply a single DPI setting to all displays. Workstations running Windows versions prior to 1703 may need to accept a compromise font size when spanning displays with different densities.
Yamak-cohort cognitive-load research summary
The Yamak cohort is a structured internal study conducted across 57 Studios™ contributors in 2024. The study measured the number of character-identification errors made per 500 characters of .dat content reviewed, segmented by font face and point size. The study is not a peer-reviewed academic publication; it is an internal operational record. The findings are documented here because they directly informed the font recommendations in this reference.
| Font face | Errors per 500 chars (avg) | Errors per 500 chars (95th pct) | Study notes |
|---|---|---|---|
| Courier New, 11pt | 4.2 | 8.1 | Zero-versus-O ambiguity was cited in 61% of errors |
| Consolas, 11pt | 1.8 | 4.4 | Slashed zero reduced O-versus-0 errors to near zero |
| Fira Code, 12pt | 1.4 | 3.2 | Dotted zero performed equivalently to slashed zero |
| JetBrains Mono, 12pt | 1.1 | 2.9 | Slightly wider character spacing aided distinction |
| Cascadia Code, 12pt | 0.9 | 2.1 | Lowest average error rate in the cohort study |
| Cascadia Code, 10pt | 2.6 | 6.3 | Size reduction increased errors; 12pt is the floor |
| Cascadia Code, 14pt | 0.8 | 1.8 | Marginal improvement over 12pt; size preference |
The study findings are consistent with the general typographic literature on code legibility. The slashed zero is a more reliable zero-versus-O differentiator than no distinguishing mark. A point size below 12pt degrades error rates even for well-designed fonts. Cohort-validated font preference distribution at the end of the study period was: Cascadia Code 61%, JetBrains Mono 24%, Fira Code 10%, Consolas 5%.
Best practice
The Yamak-cohort findings support 12pt as the minimum recommended point size for .dat editing on standard-density displays. Workstations with 4K displays at 100% DPI scaling may require 14pt or 16pt to maintain equivalent physical character height. The findings do not apply to displays running 200% DPI scaling, which effectively doubles the physical rendering size of any given point size.
Pro tip
Replicate the cohort evaluation on your own workstation by opening a GUID-heavy .dat file and reading the GUIDs aloud without looking at the source. If you pause more than once per GUID to verify a character, the font or size configuration should be reviewed. The cohort threshold was one pause or fewer per GUID read at a natural reading pace.
Persistent configuration across updates
Font settings in Notepad++ are stored in the user's stylers.xml file at %APPDATA%\Notepad++\stylers.xml. The built-in Notepad++ updater preserves the %APPDATA%\Notepad++\ directory across updates, which means font configuration persists through routine Notepad++ version updates without any additional action.
Common mistake
Assuming that the font configuration will be lost when Notepad++ updates. The updater does not modify the user configuration directory. Font configuration, keyboard shortcuts, and plugin configuration all persist through updates. Only a manual deletion of the configuration directory or a clean reinstall that includes deleting the configuration directory will reset the font.
The one exception to this rule is when the font face itself is uninstalled from Windows. If a font is uninstalled from the system after Notepad++ has been configured to use it, Notepad++ will fall back to its internal default font (Courier New) for any style that referenced the uninstalled font. The stylers.xml file will continue to reference the uninstalled font name, and the font will reappear in Style Configurator as the active selection, but the rendered output will be the fallback. Re-installing the font face restores the correct rendering without any additional Notepad++ configuration.
Exporting font configuration to another workstation
Contributors who configure Notepad++ on a primary workstation and want to replicate the configuration on a second workstation can export the font configuration by copying the stylers.xml file from %APPDATA%\Notepad++\ on the source workstation to the same path on the destination workstation.
| File to copy | Source path | Destination path | Contains |
|---|---|---|---|
stylers.xml | %APPDATA%\Notepad++\stylers.xml | %APPDATA%\Notepad++\stylers.xml | Font names, sizes, colors for all style categories |
Common mistake
Copying stylers.xml to a destination workstation that does not have the same fonts installed. The destination Notepad++ will reference a font name that is not present and will fall back to the default. Install the required fonts on the destination workstation before copying the configuration file.
The full set of files that constitute a complete Notepad++ configuration backup — including keyboard shortcuts, plugin configuration, and custom language definitions — is documented in the installation reference. For font configuration specifically, stylers.xml is the only file that needs to be transferred.
FAQ
Where is the font setting stored on disk? The font name and size for each style category are stored in %APPDATA%\Notepad++\stylers.xml. The Default Style entry within that file contains the global font settings applied to all file types.
Does changing the font in Style Configurator affect every open tab? Yes. The font change applies globally and takes effect in all currently open tabs as soon as the Style Configurator dialog is closed. No restart is required for font face and size changes. A restart is required only if the DirectWrite setting is changed.
Why does my chosen font not appear in the Font name dropdown? The dropdown lists only fonts currently installed in Windows. If the desired font is not listed, it is not installed. Download and install the font from its distribution source, then reopen the Style Configurator. No Notepad++ restart is required after installing a font; the dropdown will include the new font on the next time it is opened.
Does Notepad++ support variable fonts? Variable font support depends on the DirectWrite rendering mode and the version of Windows. On Windows 10 and Windows 11 with DirectWrite enabled, variable fonts render correctly. The font faces recommended in this reference (Cascadia Code, JetBrains Mono, Fira Code) ship as traditional static font files in addition to any variable font variants, and the static files are the recommended choice for Notepad++ to avoid rendering inconsistencies.
Can I use a different font for specific file types while keeping the global font for most files? Yes. The Style Configurator allows per-language overrides. Select a language category (for example, "INI file") in the left pane, select a style name in the center pane, and set the font for that specific combination. The per-language font takes precedence over the global font for files detected as that language.
How do I revert the font to the Notepad++ default? In the Style Configurator, select Global Styles → Default Style, clear the Font name field (or select "default" if the dropdown offers it), and close the dialog. Notepad++ will use its compiled-in default, which is typically Courier New at 10pt. Alternatively, delete or rename %APPDATA%\Notepad++\stylers.xml and relaunch Notepad++; the application will regenerate the file with default values.
Does font size affect the Notepad++ performance on large files? No measurable performance difference has been documented between font sizes in the Notepad++ rendering pipeline. Font size affects the number of lines visible in the viewport but does not affect the speed at which Notepad++ parses, highlights, or scrolls through large files.
Should I use a bold weight for the Default Style? No. The Default Style bold checkbox in the Style Configurator applies bold rendering to all normal text in the editor. This increases stroke weight and can make character-to-character spacing appear tighter, which reduces legibility for long-form reading. Bold rendering is appropriate for syntax-highlighted tokens where it is used to draw attention to specific token types (keywords, string delimiters), not for the base text weight.
What point size is equivalent to a 16px font on a 96 DPI display? At 96 DPI, 1 point equals 1.333 pixels. A 16-pixel font at 96 DPI is equivalent to 12pt. This is why 12pt is the standard recommendation for 96 DPI displays — it produces a 16-pixel character cell that has been the ergonomic baseline for text terminal work since the introduction of modern LCD displays.
Does the font configuration apply to the Find and Replace dialog? No. The Find and Replace dialog uses the Windows system dialog font, which is typically Segoe UI at the system-configured size. The Style Configurator font applies only to the editor viewport.
Can the 57 Studios™ recommended configuration be applied by importing a file? Yes. The recommended stylers.xml configuration is maintained in the 57 Studios™ shared project templates. Copy the file from the templates repository to %APPDATA%\Notepad++\stylers.xml to apply the exact configuration used by the 57 Studios™ contributor cohort. Confirm that Cascadia Code is installed before applying the file.
What happens if I use a proportional font by mistake? A proportional font in Notepad++ renders each character at its natural width rather than a fixed column width. The immediate visible effect is that tabular content (such as the key-value pairs in a .dat file) no longer aligns vertically across lines. GUIDs appear as compressed runs of unequal width. The editor remains fully functional, but the legibility characteristics that make monospace fonts the standard for this work are absent. Selecting a monospace font in the Style Configurator restores correct alignment immediately.
Is there a per-session font size change that does not affect the persistent configuration? Yes. The Ctrl plus and Ctrl minus keyboard shortcuts adjust the font size in the current editor session without modifying the Style Configurator settings. The adjustment is lost when Notepad++ closes. This behavior makes the keyboard shortcuts suitable for temporary size increases on secondary displays or when screen-sharing.
Best practices
- Select a font face from the recommended list in this reference rather than a system-default font that has not been evaluated for the zero-versus-O distinction.
- Set the font at the Global Styles / Default Style level so the configuration applies uniformly to every file type.
- Enable DirectWrite for all modern LCD and OLED displays.
- Use Cascadia Mono instead of Cascadia Code if ligature rendering is undesired.
- Calibrate the font size on the primary editing display, not a secondary or presentation display.
- Copy
stylers.xmlto new workstations rather than reconfiguring from scratch. - Verify zero-versus-O distinction by opening a GUID-containing
.datfile immediately after configuration. - Do not apply bold to the Default Style; reserve bold for syntax-highlighted token types.
Appendix A: Yamak-cohort study methodology
The Yamak-cohort study was conducted between March and September 2024 with seven 57 Studios™ contributors as participants. Each participant was shown 500-character sequences sampled from live Unturned™ .dat files and asked to transcribe each sequence into a separate Notepad++ tab. The transcribed output was compared to the source character-by-character, and each character-level difference was counted as one error.
Each participant completed sessions under four font configurations: Courier New at 11pt, Consolas at 11pt, and two sessions under one of the four primary-recommendation fonts at 12pt (participants were assigned different fonts to avoid order-effect bias). Sessions were separated by at least 48 hours to reduce fatigue carryover.
| Metric | Value |
|---|---|
| Participants | 7 |
| Sessions per participant | 4 |
| Characters per session | 500 |
| Total characters reviewed | 14,000 |
| Session spacing | 48 hours minimum |
| Content source | Live Unturned .dat files from the 57 Studios™ project archive |
| Error classification | Character-level transcription mismatch |
The study did not control for individual variation in visual acuity, display hardware, or prior exposure to each font. The findings are therefore indicative rather than definitive. They are documented because they represent the only structured internal evaluation of font legibility conducted specifically on Unturned .dat content and because the results are consistent with the broader typographic literature on code legibility.
Appendix B: Installing recommended fonts on Windows
Cascadia Code, JetBrains Mono, and Fira Code are all available at no cost. The table below documents the distribution source and installation steps for each.
| Font | Distribution source | Installation method |
|---|---|---|
| Cascadia Code | GitHub releases (microsoft/cascadia-code) | Download the .zip release, extract, right-click each .ttf file, click Install |
| JetBrains Mono | JetBrains website or GitHub | Download the .zip, extract, right-click each .ttf, click Install |
| Fira Code | GitHub releases (tonsky/FiraCode) | Download the .zip, extract, right-click each .ttf, click Install |
| Consolas | Windows built-in | No installation required |
Did you know?
"Install for all users" requires administrator rights and places the font files in C:\Windows\Fonts. "Install" without administrator rights places the font files in %LOCALAPPDATA%\Microsoft\Windows\Fonts and makes them available only to the current user. Both installation modes make the font available in Notepad++.
After installing a font, reopen the Style Configurator. The new font appears in the Font name dropdown without restarting Notepad++.
Appendix C: Style Configurator quick-reference
The table below summarises every control in the Style Configurator dialog and its function for readers who want a reference without re-reading the procedural sections.
| Control | Location in dialog | Function |
|---|---|---|
| Language list | Left pane | Selects the language category whose styles will be shown |
| Style list | Center pane | Selects the specific style within the chosen language |
| Font name | Right pane | Sets the font face for the selected style |
| Font size | Right pane | Sets the point size for the selected style |
| Bold | Right pane | Applies bold weight to the selected style |
| Italic | Right pane | Applies italic slant to the selected style |
| Underline | Right pane | Applies underline decoration to the selected style |
| Foreground color | Right pane | Sets the text color for the selected style |
| Background color | Right pane | Sets the background color for the selected style |
| Default foreground | Right pane | Reverts the foreground color to the Notepad++ theme default |
| Default background | Right pane | Reverts the background color to the Notepad++ theme default |
| Preview pane | Bottom of dialog | Renders sample text with the current style settings in real time |
| Save and Close | Bottom of dialog | Applies all changes and closes the dialog |
| Cancel | Bottom of dialog | Discards unsaved changes and closes the dialog |
Font rendering on remote desktop sessions
A significant proportion of Unturned™ mod contributors access their development workstations via remote desktop — either through Windows Remote Desktop Protocol (RDP) or through third-party remote-access tools such as Parsec. Font rendering in remote sessions is meaningfully different from local rendering, and the configuration decisions documented earlier in this reference require adjustment for remote contexts.
RDP sessions
RDP applies compression to the display stream, and the compression interacts poorly with subpixel ClearType rendering. The subpixel color components that ClearType uses to increase apparent sharpness appear as color fringing when the compressed display stream is decompressed on the client display. The most visible symptom is a magenta-and-green halo around character strokes, which makes thin characters like l, i, and 1 appear to have colored shadows.
The recommended font-rendering configuration for RDP sessions is:
| Setting | RDP recommendation | Local recommendation |
|---|---|---|
| DirectWrite | Disabled | Enabled |
| Anti-aliasing | GDI (via DirectWrite disabled) | ClearType (via DirectWrite enabled) |
| Font size | +1pt above local recommendation | Per display table |
| Font face | Consolas (no ligatures; simpler glyph rendering) | Cascadia Code |
Disabling DirectWrite for RDP sessions reverts Notepad++ to GDI rendering, which uses grayscale anti-aliasing rather than subpixel ClearType. Grayscale anti-aliasing produces a slightly softer character stroke, but the softness is preferable to the color fringing that ClearType produces under compression. The +1pt size increase compensates for the reduced apparent sharpness of grayscale anti-aliasing.
Did you know?
RDP has a display-configuration setting called "Font Smoothing" in the Experience tab of the Remote Desktop Connection dialog. Enabling Font Smoothing in the RDP client instructs the remote session to render ClearType and transmit the result in full color rather than applying the compressed display stream's default color reduction. Enabling this setting in the RDP client allows ClearType to be retained in some network conditions, but it increases bandwidth consumption and may introduce latency on slower connections.
Parsec sessions
Parsec uses video codec encoding (H.264 or H.265 depending on configuration) to transmit the display. Codec encoding is better suited to ClearType rendering than RDP compression because the codec preserves color gradients more faithfully, but it introduces a different artifact: block noise at low bitrate settings. Block noise is most visible in small, thin-stroked text.
For Parsec sessions, the recommended configuration is:
- Enable DirectWrite and ClearType as in the local configuration.
- Set the Parsec codec bitrate to at least 20 Mbps for text-editing sessions.
- Increase font size to 13pt or 14pt to ensure character strokes are wide enough that block noise does not obscure the stroke interior.
- Avoid font sizes below 12pt, where block noise begins to affect zero-versus-O disambiguation.
Pro tip
After connecting to a workstation via Parsec, open a .dat file and zoom the Notepad++ window to 100% (no DPI scaling offset). If block noise is visible in character strokes at the configured font size and bitrate, increase the font size by 1pt and evaluate again. Block noise is most visible as speckled texture inside the enclosed loops of characters like 0, O, 6, 8, 9, b, d, g, p, and q.
Font configuration for syntax-highlighted .dat files
Notepad++ can apply syntax highlighting to .dat files through a user-defined language (UDL) definition. A UDL for Unturned .dat files defines token categories — keys, values, section headers, and comments — and assigns each category a color and a text style (bold, italic). The font configuration in Style Configurator interacts with UDL definitions: the global Default Style sets the base font, and the UDL definition's style overrides apply color and weight on top of it.
Common mistake
Applying bold weight to the key token category in the UDL and then wondering why bold keys appear heavier than expected. Bold weight in a monospace font reduces the apparent inter-character spacing because the strokes are wider, which makes long key names harder to distinguish from their values. The 57 Studios™ UDL for Unturned .dat uses color rather than bold to differentiate keys from values.
The recommended approach for a modder who has configured a UDL for .dat files is:
- Set the global Default Style font to the recommended monospace face and size.
- Confirm the UDL's style overrides use only color (foreground color changes) and not font-face or font-size overrides.
- Verify in the UDL editor (Language → Define Your Language) that no style entry in the UDL overrides the font name or size.
| UDL style category | Recommended differentiation | Method |
|---|---|---|
| Key tokens | Distinct foreground color | Color only; no bold |
| Value tokens | Default foreground color | No override needed |
| Section headers | Distinct foreground color + optional bold | Bold acceptable for headers |
| Comment lines | Muted foreground color | Color only; no italic (italic in monospace is less legible at small sizes) |
Did you know?
A User Defined Language file for Notepad++ is an XML file stored in %APPDATA%\Notepad++\userDefineLangs\. The 57 Studios™ project templates include a UDL file for Unturned .dat files that can be imported through Language → Define Your Language → Import. The UDL assigns consistent colors to each token category without overriding the font configuration established in the Style Configurator.
Shared-screen and screen-capture font considerations
Contributors who participate in code-review sessions conducted over video calls, or who produce screenshot documentation, encounter a secondary audience for the Notepad++ display: the viewer of the shared or captured screen. The viewer's display may differ from the presenter's display in resolution, color profile, and scaling, which means the legibility of the font configuration for the secondary audience is not guaranteed by calibrating only for the primary display.
The following adjustments improve legibility for shared-screen and screenshot contexts:
| Adjustment | Value | Rationale |
|---|---|---|
| Font size increase for sharing | +2pt above session default | Compensates for video compression and scaling in shared-screen contexts |
| Background theme | Light background preferred | Video codecs preserve contrast better on light backgrounds than on dark backgrounds |
| Show line numbers | Enabled | Reviewers use line numbers to reference locations; disable if sharing would expose confidential line counts |
| Word wrap | OFF | Consistent with column-aligned review expectations; wrap can make column structure appear different to the secondary viewer |
Pro tip
When sharing a Notepad++ screen for review, briefly open Style Configurator and confirm the font size to the reviewers. This allows reviewers to calibrate their visual expectations and reduces questions about whether specific characters are l (lowercase L), I (uppercase i), or 1 (numeral one).
Theme interaction with font configuration
Notepad++ ships with a selection of themes that change the background color, foreground color, and syntax-highlighting colors of the editor. Themes do not typically override the font face or size set in the Default Style, but they do affect the perceived legibility of the font through their impact on contrast.
The table below documents the contrast characteristics of the themes shipped with Notepad++ and their interaction with the recommended font configuration.
| Theme category | Background | Contrast profile | Impact on font legibility |
|---|---|---|---|
| Default (light) | White | High contrast, no color interference | Maximum legibility for the recommended monospace fonts |
| Dark themes | Dark grey or black | High contrast (inverted) | Requires slightly larger point size to maintain perceived sharpness |
| Low-contrast themes (e.g., Solarized) | Tinted background | Reduced contrast | Reduce session duration; increase font size to compensate |
| High-color themes | Colorful background | Variable | Evaluate per-theme; high-saturation backgrounds can cause character halation |
Best practice
The 57 Studios™ cohort default is the Notepad++ built-in light theme for all .dat editing sessions. The light theme provides the highest contrast for the monospace font faces in the recommended list and requires no contrast compensation via font-size adjustment. Contributors who prefer dark themes should increase the font size by 1pt above the display-table recommendation to maintain equivalent apparent sharpness.
Font configuration and the Notepad++ zoom feature
Notepad++ provides a zoom control that scales the current viewport independently of the Style Configurator font size setting. Zoom is applied via Ctrl + scroll wheel, Ctrl + plus, and Ctrl + minus, or through View → Zoom. The zoom level is a multiplier applied on top of the Style Configurator font size; it does not change the stored font size in the configuration.
The interaction between zoom and font size is important because zoom is session-scoped, not persistent. When Notepad++ closes and reopens, the zoom level resets to 100%. The Style Configurator font size, by contrast, persists across sessions. A modder who relies on zoom to compensate for an incorrectly configured font size will need to re-apply the zoom adjustment at the start of every session.
Common mistake
Using the Ctrl + scroll wheel zoom as a substitute for a correctly configured font size. The correct practice is to configure the font size in the Style Configurator once for the primary display and rely on the keyboard-shortcut zoom only for temporary adjustments — for example, when moving the Notepad++ window to a secondary display during a screen-sharing session.
The zoom level is stored per-tab in some Notepad++ versions and as a single global value in others. The exact behavior depends on the Notepad++ release. In releases where zoom is per-tab, changing the zoom on one tab does not affect other tabs. In releases where zoom is global, a zoom change on any tab affects all tabs immediately. The Style Configurator font size is always global across all tabs.
| Control | Scope | Persistent | Notes |
|---|---|---|---|
| Style Configurator font size | Global (all tabs) | Yes (persists across sessions) | Primary font-size configuration method |
| Ctrl + scroll wheel zoom | Tab-specific or global (version-dependent) | No (resets at Notepad++ close) | Temporary adjustment only |
| View → Zoom → Restore Default | Resets zoom to 100% | Not applicable | Use to undo temporary zoom adjustments |
Pro tip
If a secondary team member shares a Notepad++ window over video call and the font appears too small on the recording, use Ctrl + plus to increase zoom during the session, then use View → Zoom → Restore Default before the session ends to return to the calibrated size. This workflow avoids modifying the persistent Style Configurator configuration for a temporary sharing need.
Notepad++ font and the backup file directory
Notepad++ stores automatic backup copies of open documents in %APPDATA%\Notepad++\backup\. These backup files are plain text files with the same encoding as the originals, and they open in Notepad++ with the same font configuration applied to any other file. There is no separate font configuration for the backup directory.
The reason this matters operationally is that backup files may be opened for diagnostic purposes — for example, when recovering content from a session that ended unexpectedly. When a backup file is opened, it will display with the currently configured font. If the font was changed between the session that produced the backup and the session that opens it for recovery, the visual appearance of the backup file will differ from the visual appearance of the original editing session. The content is identical; only the rendering differs.
Best practice
When opening a backup file for recovery, confirm that the font configuration matches the configuration used during the original editing session before evaluating the content. An unexpected font rendering can make the backup file appear unfamiliar, which may slow the recovery assessment. The font configuration is the same one used for all other .dat files; the backup file is not special in any way other than its file name.
Keyboard shortcuts relevant to font configuration
The following keyboard shortcuts are directly relevant to font size and rendering management in Notepad++. They supplement the Style Configurator procedure documented earlier in this reference.
| Shortcut | Action | Notes |
|---|---|---|
| Ctrl + scroll wheel up | Increase zoom level | Temporary; does not modify Style Configurator |
| Ctrl + scroll wheel down | Decrease zoom level | Temporary; does not modify Style Configurator |
| Ctrl + plus (numpad or keyboard) | Increase zoom level by one step | Temporary |
| Ctrl + minus (numpad or keyboard) | Decrease zoom level by one step | Temporary |
| Ctrl + slash (numpad) | Restore default zoom (100%) | Resets the temporary zoom |
| View → Zoom → Restore Default Zoom | Restore default zoom via menu | Same as Ctrl + slash numpad |
Did you know?
The Ctrl + scroll wheel zoom shortcut cannot be remapped through the standard Notepad++ shortcut configuration dialog. It is implemented as a hardcoded binding in the editor core. The shortcut is useful precisely because it is always available regardless of whether other shortcuts have been customized.
Appendix D: Font configuration validation checklist
After completing the font configuration procedure, the following checklist confirms that every dimension of the configuration is in the expected state. The checklist is structured as a sequential review that takes approximately five minutes.
| Check | Expected state | Action if not met |
|---|---|---|
| Font face in Style Configurator | Cascadia Code, JetBrains Mono, Fira Code, or Consolas | Re-open Style Configurator; select the recommended font from the dropdown |
| Font face present in system | Font appears in the dropdown | Install the font from the distribution source documented in Appendix B |
| Font size in Style Configurator | 12–14pt for standard displays | Re-open Style Configurator; enter the correct size |
| DirectWrite setting | Enabled (unless RDP session) | Open Settings → Preferences → MISC.; enable DirectWrite; restart Notepad++ |
| Zero-versus-O distinction in editor | Zero and O visually distinct | Select a font with a slashed or dotted zero |
| Monospace alignment in editor | Characters in adjacent lines align vertically | Confirm a monospace font (not proportional) is selected |
| Bold disabled in Default Style | Bold checkbox unchecked in Style Configurator | Re-open Style Configurator; uncheck Bold for Default Style |
| Preview pane reflects expected appearance | Sample text in the preview matches expected rendering | Adjust settings until the preview is satisfactory |
| Configuration persists after restart | Font settings are retained after closing and reopening Notepad++ | Confirm stylers.xml is writable; check disk permissions on %APPDATA%\Notepad++\ |
| GUID-reading test | Zero-versus-O distinction is clear in a GUID from a live .dat file | Increase font size or switch to a font with a stronger zero distinguisher |
Font configuration reporting for contributor onboarding
When a new contributor joins the 57 Studios™ modding team, one of the first recorded configuration steps is confirming that Notepad++ is set to the recommended font. The confirmation is documented in the contributor onboarding record alongside the encoding and line-ending confirmation described in adjacent knowledge-base references.
The onboarding font confirmation follows this sequence:
- The new contributor opens Notepad++ on their workstation.
- They navigate to Settings → Style Configurator → Global Styles → Default Style.
- They note the Font name, Font size, and Bold state.
- They take a screenshot of the Style Configurator dialog.
- They share the screenshot with the onboarding coordinator.
The onboarding coordinator reviews the screenshot against the recommended configuration in this reference. If the font face is not from the recommended list, the contributor is directed to this reference and asked to complete the configuration procedure. If the font size is outside the range appropriate for the contributor's display type, the coordinator advises the correct size.
Best practice
The screenshot serves as a dated record of the configuration state at onboarding. If a contributor later reports a character-identification error in a .dat review, the onboarding screenshot provides the baseline configuration from which any subsequent drift can be assessed.
The onboarding coordinator does not need to view the contributor's display directly. The Style Configurator screenshot provides all the information needed to confirm or correct the configuration remotely. The only aspect the screenshot cannot confirm is whether the font files are installed at the correct version — but since each recommended font installs as a single static family, version drift is not a common problem in practice.
| Onboarding record field | Information source | Confirmed by |
|---|---|---|
| Font face | Style Configurator screenshot | Coordinator: matches recommended list |
| Font size | Style Configurator screenshot | Coordinator: within range for display type |
| Bold state | Style Configurator screenshot | Coordinator: unchecked for Default Style |
| DirectWrite mode | Separate Preferences screenshot | Coordinator: enabled for local sessions |
| Font files installed | Dropdown list in screenshot shows font | Coordinator: font appears in dropdown |
Appendix E: Font configuration for accessibility
Contributors with specific visual requirements may need to depart from the standard font configuration documented in this reference. The following adjustments address the most common accessibility needs encountered in the contributor cohort.
| Accessibility need | Recommended adjustment | Notes |
|---|---|---|
| Low visual acuity | Increase font size to 16–20pt | Pair with 4K display or high-DPI setting for maximum sharpness at large sizes |
| Color vision deficiency | Select a theme with luminance-based (not hue-based) differentiation | The Default light theme uses hue-and-luminance combinations; pure luminance themes are available in the Plugin Admin themes collection |
| Motion sensitivity | Disable DirectWrite animation features | DirectWrite includes scroll animation; disable through system accessibility settings if needed |
| High contrast display requirement | Enable Windows High Contrast mode | Notepad++ respects Windows High Contrast mode; the Style Configurator colors are overridden by the high-contrast palette |
| Dyslexia-supporting font | OpenDyslexia or similar fonts can be installed and selected | Character-width variation in dyslexia-supporting fonts may reduce column alignment accuracy; test on a representative .dat file before committing |
Did you know?
The Notepad++ project considers accessibility support a maintained feature. Accessibility-related issues filed on the project's GitHub issue tracker are reviewed as standard bugs rather than feature requests. Contributors who encounter accessibility-specific rendering issues in Notepad++ are encouraged to file a report with the version and build information from Help → About.
Document history
| Version | Date | Author | Notes |
|---|---|---|---|
| 1.0 | 2026-05-18 | 57 Studios | Initial publication covering font face, size, anti-aliasing, ligatures, and multi-monitor calibration. |
Font configuration checklist for returning contributors
A contributor who returns to active 57 Studios™ mod development after an absence of three months or more should complete the following checklist before opening any project files. The checklist verifies that the font configuration has not drifted due to Notepad++ updates, operating-system updates, or hardware changes.
| Checklist step | Action | Expected result |
|---|---|---|
| Confirm Notepad++ version | Help → About Notepad++ | Version is current-year release |
| Open Style Configurator | Settings → Style Configurator | Dialog opens without error |
| Confirm font face | Global Styles → Default Style → Font name | Cascadia Code, JetBrains Mono, Fira Code, or Consolas |
| Confirm font is installed | Font appears in dropdown | Font name is selectable |
| Confirm font size | Global Styles → Default Style → Font size field | 12–14pt (or display-specific value from onboarding record) |
| Confirm Bold unchecked | Global Styles → Default Style → Bold checkbox | Unchecked |
| Confirm DirectWrite | Settings → Preferences → MISC. → Use DirectWrite | Enabled |
Open GUID-containing .dat file | Open any project .dat file with a GUID field | File opens; GUID renders with distinct zero |
| Read GUID aloud | Read the first GUID in the file without pausing | One or zero character-identification pauses per GUID |
If all checklist steps pass, the font configuration is confirmed current. If any step fails, follow the configuration procedure in this reference from the step relevant to the failing check.
Best practice
Complete the returning-contributor checklist even if the workstation and software appear unchanged. Font configuration can drift through Notepad++ updates that modify stylers.xml defaults, Windows font updates that change hinting tables for installed fonts, or display hardware changes that affect the physical rendering of the configured point size. The checklist takes under five minutes and ensures the first editing session of the return is as accurate as subsequent sessions.
Cross-references
- How to Install Notepad++ — Installation reference; confirms the base Notepad++ setup that this reference builds on.
- How to Save a DAT File with Correct Encoding — The previous reference in this section; covers encoding selection.
- How to Enable Word Wrap — The next reference; covers the word-wrap readability decision and its interaction with the font configuration documented here.
Font configuration and version snapshot discipline
The 57 Studios™ version-snapshot discipline — maintaining numbered copies of working files before architecture-shifting changes — does not apply to Notepad++ configuration files in the same way it applies to mod project files. Notepad++ configuration files are managed through the built-in backup mechanisms described in the installation reference, and stylers.xml changes are low-risk because they affect only the display layer rather than the file content.
That said, contributors who make significant font configuration changes — such as switching from one font family to another, or adjusting DirectWrite mode — are encouraged to note the change in their session log with the date and the reason. This is not a formal snapshot; it is a record that allows the contributor to revert to the previous configuration if the new configuration produces unexpected legibility issues during the first sessions after the change.
A typical session-log note for a font configuration change looks like:
2026-05-18: Changed Style Configurator Default Style font from Consolas 11pt to Cascadia Code 13pt. DirectWrite enabled. Reason: zero-versus-O disambiguation. Reverting to Consolas 11pt requires opening Style Configurator and entering those values manually — no snapshot file needed.
The note captures the previous state (Consolas 11pt), the new state (Cascadia Code 13pt), and the reason, which is sufficient to revert or justify the change in any subsequent conversation about the configuration.
Pro tip
Record the date of every font configuration change even when the change seems minor. A date in the session log allows a future contributor reviewing a screen-capture from a past session to correlate the visual rendering in that capture with the font configuration active at the time. This is especially useful when comparing screen-captures taken before and after a display hardware change, where the same point size may render at a noticeably different physical size.
Next steps
With the font configured, continue to How to Enable Word Wrap to understand how word-wrap interacts with the monospace layout established by the font configuration in this reference. Word wrap and font selection are the two primary display-layer decisions that affect the accuracy with which a modder reads .dat content, and the next reference treats both together in the context of a complete readability configuration.
The font reference and the word-wrap reference are designed to be read in sequence on first pass and consulted independently on return visits. A modder experiencing a character-identification problem returns to this reference; a modder experiencing a trailing-whitespace or line-structure problem returns to the word-wrap reference. The two concerns are distinct even though they share the same editor and the same file type, and separating them into two references ensures that each concern receives the depth of documentation it warrants.
Both references are maintained by 57 Studios™ and updated as Notepad++ releases introduce changes to the Style Configurator, DirectWrite integration, or rendering behavior that affect the recommendations documented here. Consult the document-history table at the end of this reference to confirm you are reading the current version before making configuration decisions based on its contents.