Cascadia Code: Microsoft's ligature font for coding
/cascadia-code
Cascadia Code is Microsoft's monospaced coding font, bundled with Windows Terminal and set as the default face in Visual Studio. The ligatures render cleanly, the variable weight range from 200 to 700 gives real flexibility, and the Mono/PL/NF split means you're not stuck with Nerd Font glyphs you don't want. It's competent, not exciting: a well-executed font that plays it safe rather than trying anything new.
What is Cascadia Code
Cascadia Code is a monospaced font family Microsoft built for code editors and terminals, shipped with Windows Terminal and used as Visual Studio's default typeface. It adds OpenType programming ligatures for sequences like arrows and comparison operators, plus stylistic sets that swap in alternate glyph shapes such as a cursive italic. Cascadia Mono drops the ligatures. PL/NF builds embed Powerline or Nerd Font icons into the file.
Cascadia Code variants and font features
- ✓Cascadia Code and Cascadia Mono give you the same design with or without programming ligatures, so turning the ligature look off entirely just means picking Mono instead of a settings toggle.
- ✓PL and NF builds embed Powerline or Nerd Font glyphs straight into the font file, skipping the separate patching step those glyph sets normally require.
- ✓The variable ttf format covers weights from 200 to 700 in one file, rather than shipping separate static files per weight.
- ✓Stylistic sets ss01, ss02, ss03, ss19, and ss20 swap in alternate glyph shapes, including a cursive form of the italic through ss01.
- ✓Ligature support (the calt OpenType feature) renders sequences like arrows and comparison operators as single joined glyphs instead of separate characters.
- ✓WOFF2 builds are provided for web use, in both variable and static form, alongside the desktop TTF/OTF formats.
Downloading and installing Cascadia Code
Download the release you want from the GitHub releases page — Cascadia Code ships as ttf variable (the recommended default, especially on Windows, since it covers the full weight range and gets proper TrueType hinting), ttf static, otf static, or WOFF2 for the web. Unzip the archive, right-click the font file, and choose "Install for all users." If you have an older Cascadia Code installed, uninstall it first — the README warns that skipping this step can cause improper rendering. App-specific installation notes live in the project's wiki rather than the main README.
Enabling ligatures and stylistic sets in your editor
Enabling ligatures and stylistic sets depends on the editor — Cascadia Code doesn't turn them on by itself in every app. In VS Code, add a line to settings.json: "editor.fontLigatures": "'ss01', 'ss02', 'ss03', 'ss19', 'ss20'" to pick specific stylistic sets. To get the cursive italic variant instead of the standard one, use "editor.fontLigatures": "'calt', 'ss01'". If your app doesn't support the ss01 OpenType feature at all, the README points to opentype-feature-freezer as a workaround for baking a stylistic set permanently into the font file.
Strengths
- ✓Ships and updates alongside Windows Terminal and Visual Studio, so it's already installed for a large share of Windows developers.
- ✓PL and NF builds embed icon glyphs directly, skipping the separate font-patching step other icon fonts require.
- ✓One variable ttf file covers the full 200-700 weight range instead of needing individual static files per weight.
- ✓The cursive italic accessible through ss01 is a distinct look most ligature fonts don't offer as a built-in alternate.
Known limitations of Cascadia Code
- △Font feature and stylistic-set support depends entirely on the app you're using — VS Code needs a settings.json entry, and other editors and terminals vary in whether they expose OpenType features at all.
- △The README doesn't document a license for the project in the material reviewed here, so check the repository's license file yourself before using it commercially.
- △Reinstalling over an older version without uninstalling first can cause rendering problems, per the project's own installation note.
- △The OTF format is only offered as static instances — there's no variable-font OTF build if that's what your workflow needs.
- △Detailed per-app installation steps live in a separate wiki rather than the README, so first-time setup on less common terminals may take extra digging.
Best alternatives to Cascadia Code
Frequently asked questions about Cascadia Code
The GitHub repository for Cascadia Code doesn't state its license terms in the README, so there's no confirmed answer here — check the repository's license file directly before using Cascadia Code in a commercial product.
Cascadia Code's ligatures depend on your editor supporting the OpenType calt feature and, for extra stylistic sets, entries like ss01 through ss20. In VS Code, add "editor.fontLigatures": "'ss01', 'ss02', 'ss03', 'ss19', 'ss20'" to settings.json to turn them on.
Cascadia Code and Cascadia Mono share the same underlying design, but Cascadia Code includes programming ligatures while Cascadia Mono ships without them, for developers who prefer separate characters over joined ligature glyphs.
The README's step-by-step install instructions ("Install for all users") describe the Windows flow specifically; macOS- or Linux-specific steps aren't documented in the material reviewed here. Cascadia Code does ship as standard OTF and WOFF2 files alongside TTF, formats those systems can generally install through their own font tools.
The Cascadia Code variable ttf format covers weights from 200 to 700 in a single file, per the project's README — that's the full range the design offers, rather than a fixed set of individually named weights.
The README documents the settings.json approach for VS Code specifically, since stylistic-set support varies by application. It links to a general guide for enabling OpenType features in other editors but doesn't list every supported app by name — check your editor's font-feature documentation directly.
The problem it solves
Before Cascadia Code, getting a ligature-capable monospaced font with embedded Powerline or Nerd Font glyphs meant patching an existing font yourself with a separate tool, or picking a community font with less predictable maintenance. Cascadia Code packages ligatures, a cursive italic alternate, and pre-patched PL/NF builds into one family that ships and updates alongside Windows Terminal and Visual Studio, so Windows and VS Code users get a matched, ready-to-install option instead of assembling one.
Best use cases
- •Setting Windows Terminal or Visual Studio's font back to its shipped default after experimenting with something else.
- •Running a Powerline-style prompt theme without patching a separate font, by installing the PL build.
- •Getting file-type and git-status icons in a terminal file manager or prompt framework via the NF build's embedded Nerd Font glyphs.
- •Wanting operator and arrow ligatures in VS Code without installing a font extension, just a settings.json change.
Who should try it — and who should skip
Windows developers who live in Windows Terminal or Visual Studio get this font the moment they install either, so trying it costs nothing extra. Anyone who wants Nerd Font or Powerline icons without manually patching a font should grab the NF or PL build directly. Skip it if you've already built your setup around a different ligature font and have no complaint with it — Cascadia Code doesn't do anything those fonts don't, it's just Microsoft's version wired into its own tools.
Still deciding about cascadia-code?
One click hands the question to an AI along with this page — see what it says about cascadia-code.