The 8 Best Fonts for Coding in 2026 (Free, for VS Code and Terminals)
The best fonts for coding are monospaced, keep look-alike characters such as 0 and O or 1, l and I clearly apart, and stay readable for hours at 13 to 15 pixels. Every font on this list is free under the SIL Open Font License, and works in VS Code, JetBrains IDEs and most terminals.
We make ExodeUI and the free Exode fonts mentioned here. Every font on this list is free under the SIL Open Font License.
JetBrains Mono is the best all-round coding font: free, very readable and built into JetBrains IDEs. Pick Fira Code if you want the best-known ligatures, Cascadia Code on Windows, Monaspace to mix code voices, and Iosevka to fit more code on screen. There is no single best font for everyone, so try two or three for a day each.
Quick picks by job
| If you need | Use |
|---|---|
| Best overall | JetBrains Mono |
| Best ligatures | Fira Code |
| Best on Windows | Cascadia Code |
| Most flexible | Monaspace |
| Fits the most code | Iosevka |
| No ligatures, no fuss | Source Code Pro |
Side-by-side comparison
| Font | Ligatures | Variable | License |
|---|---|---|---|
| JetBrains Mono | Yes (NL version without) | Weight | OFL |
| Fira Code | Yes | Weight | OFL |
| Cascadia Code | Yes (Cascadia Mono without) | Weight | OFL |
| Monaspace | Yes, plus texture healing | Weight, width, slant | OFL |
| Iosevka | Yes (calt) | Many static cuts | OFL |
| Geist Mono | — | Weight | OFL |
| Source Code Pro | No | Weight | OFL |
| IBM Plex Mono | No | Static | OFL |
How we compared them
- Monospaced and readable at 13–15 px
- Clear 0/O, 1/l/I and similar pairs
- Free under an open license
- Works in VS Code, JetBrains IDEs and terminals
- Actively maintained
The best fonts for coding
1. JetBrains Mono
Best for: Code, logs and terminal views
- Platforms
- Google Fonts, GitHub
- Price
- Free, SIL Open Font License
- Output
- Variable: weight; optional code ligatures
JetBrains Mono was drawn for reading code for hours: a tall x-height and clearly different look-alike characters. In a dashboard it works for log views and IDs.
Pros and cons
- Very clear look-alike characters
- Variable weight
- Ligatures can be turned off
- Looks like code, which is wrong for ordinary labels
2. Fira Code
Best for: Code ligatures in the most editors and terminals
- Platforms
- Google Fonts, GitHub
- Price
- Free, SIL Open Font License
- Output
- Variable: weight; code ligatures
Nikita Prokopov extended Mozilla’s Fira Mono with programming ligatures, so sequences such as =>, != and >= draw as single symbols. It is the font that made code ligatures popular, and almost every editor that supports ligatures has been tested with it.
Pros and cons
- The best-known set of code ligatures
- Variable weight
- Actively maintained
- Ligatures are not for everyone; some readers find them confusing
3. Cascadia Code
Best for: Windows developers and terminal work
- Platforms
- Google Fonts, GitHub; bundled with Windows Terminal
- Price
- Free, SIL Open Font License
- Output
- Variable: weight 200–700; versions with and without ligatures and with Nerd Font symbols
Microsoft’s coding font ships with Windows Terminal and is the default in Visual Studio. Cascadia Mono is the same design without ligatures, and the NF versions add Nerd Font symbols for shell prompts.
Pros and cons
- Comes with Windows Terminal
- Ligature and no-ligature versions
- Nerd Font versions for prompts
- A friendly, rounded tone that not everyone likes
4. Monaspace
Best for: Mixing several code voices in one editor
- Platforms
- GitHub
- Price
- Free, SIL Open Font License
- Output
- Five metrics-compatible variable families; weight, width and slant axes
Monaspace from GitHub Next is five monospaced families with the same metrics, so you can, for example, set comments in one and code in another without breaking alignment. Its “texture healing” evens out the spacing of wide and narrow letters when the calt feature is on.
Pros and cons
- Five interchangeable families
- Texture healing for more even spacing
- Variable weight, width and slant
- Texture healing and ligatures depend on editor support
5. Iosevka
Best for: Fitting more code on screen, and building a font to your own taste
- Platforms
- GitHub
- Price
- Free, SIL Open Font License
- Output
- Narrow sans and slab families; many weights, widths and slopes; custom builds
Iosevka is a narrow monospaced family, so more columns fit side by side. Its customizer lets you choose the shape of individual characters and build your own variant, and its ligatures live in the calt feature.
Pros and cons
- Narrow, so split panes fit more code
- Deeply customizable
- Sans, slab and quasi-proportional versions
- Narrow letters feel cramped to some readers
- Many packages to choose from
6. Geist Mono
Best for: A modern, crisp look that matches Geist sans
- Platforms
- Google Fonts, GitHub
- Price
- Free, SIL Open Font License
- Output
- Variable: weight
The monospaced half of Vercel’s Geist family. It looks sharp at editor sizes and matches Geist in docs and dashboards where prose and code sit together.
Pros and cons
- Matches Geist sans
- Variable weight
- Clean, current look
- Newer, with fewer editor-specific variants than JetBrains Mono or Cascadia
7. Source Code Pro
Best for: A calm, classic coding font without ligatures
- Platforms
- Google Fonts, GitHub
- Price
- Free, SIL Open Font License
- Output
- Variable: weight; italics
Paul D. Hunt drew Source Code Pro for Adobe as the monospaced member of the Source family. It is plain and well spaced, with no ligatures, and matches Source Sans when code sits in documentation.
Pros and cons
- Clean and unfussy
- Pairs with Source Sans and Source Serif
- Variable weight
- No ligatures, if you want them
8. IBM Plex Mono
Best for: Numbers, IDs and code in a dashboard that already uses Plex Sans
- Platforms
- Google Fonts, GitHub
- Price
- Free, SIL Open Font License
- Output
- Static weights from Thin to Bold, with italics
Every character in Plex Mono has the same width, so columns of numbers, logs and IDs line up without extra work. It pairs naturally with Plex Sans.
Pros and cons
- Fixed width for perfect alignment
- Matches Plex Sans
- Static styles rather than a variable font
- Too wide for running text
You have read the list. The one we make is one click away.
Free Community plan. One open .exode file that runs in React, Vue, Svelte, Angular, Solid, React Native, SwiftUI and Flutter.
Also worth a look
How to change the font in VS Code
Install the font on your computer first. Then open Settings, search for “font family” and put the font’s name first in Editor: Font Family, for example ‘JetBrains Mono’, Consolas, monospace. To turn ligatures on, set "editor.fontLigatures": true in settings.json. The terminal has its own Terminal › Integrated: Font Family setting.
Should you use ligatures?
Ligatures draw sequences such as => or != as one symbol. Some people find code easier to scan with them; others find that they hide which characters are really in the file. They change only how the code looks, never the code itself, so try them for a day and keep whatever you prefer. Most fonts here ship a version without ligatures too.