Install Fira Code on Windows by downloading the .ttf files, opening them, and clicking Install for all weights; if VS Code still ignores it, the editor is usually pointing at the wrong font family name. If you skip the family name or restart step, VS Code falls back to another monospace font. This guide shows the exact install path, how to confirm Windows registered the font, and why VS Code may still not render it.
Pick the right font files and install them
Start with the standard font package, then verify that Windows lists it before you touch VS Code. If you want ligatures in the editor, the font alone is not enough; you still need to select the font family in VS Code and turn ligatures on there.
What you'll need
- A trusted Fira Code download in TTF or OTF format.
- Windows 11 or Windows 10 with access to the Fonts page.
- VS Code, if you want the font in the editor.
- Optional: the Nerd Font variant if you need patched icon glyphs in a terminal.
Choose the right font file
- Download the standard package. Choose the regular Fira Code files if you only need a coding font with ligatures. Use the Nerd Font variant only when you also want extra icon glyphs for terminals and prompts.
- Prefer TTF for Windows. Windows can install both TTF and OTF files, and both work through the same font installer flow. If a package includes multiple weights, install each file you plan to use so the editor can switch between regular, bold, and other styles.
- Open the font folder. Extract the archive first if the download arrived compressed. Windows cannot install the font from inside a zip file. (Microsoft)
Install it on Windows 11
- Right-click the font file. Select the install option from the context menu. On Windows 11, that is the fastest path for a single file.
- Use Settings when needed. Open Settings, go to Personalization, then Fonts, and drag the font file into the install area if you prefer the desktop font list workflow.
- Choose scope before confirming. Use the per-user option if you only need the font for your account. Choose the all-users option only when you want it available to every account on the PC and you have permission to install for all users.
Install it on Windows 10
- Double-click the font file. Windows opens a preview window where you can inspect the face before installation.
- Click Install. Use the button in the preview window to register the font with Windows. If you have admin rights and want a machine-wide install, use the all-users option from the context menu instead.
- Check the Fonts list. Open the Windows Fonts settings page and confirm the font appears in the installed list. That confirms Windows registered it, even if VS Code has not picked it up yet.
Fira Code troubleshooting matrix
This matrix covers the common failure points after installation. It separates Windows 10, Windows 11, standard Fira Code, and Fira Code Nerd Font so you can verify the right place at each step.
| Symptom | Likely cause | Exact fix | Where to verify it |
|---|---|---|---|
| Windows 10 shows the font in preview but VS Code still uses another face | The font was installed, but VS Code still points at a different family name | Open VS Code Settings, search for the editor font family field, enter the exact Fira Code family name, then reload the window | Windows Fonts list and VS Code editor appearance |
| Windows 11 installs the font, but it does not appear in the editor list | The file was installed for the wrong scope or the app has not refreshed its font cache | Reinstall using the Windows 11 context menu or drag-and-drop into Settings > Fonts, then restart VS Code | Settings > Personalization > Fonts and VS Code after restart |
| Standard Fira Code appears in Windows but ligatures do not show in code | Ligatures are off in the editor settings | In VS Code Settings, search for ligatures and turn them on, then reopen the file | Any code line with characters that should combine in the editor |
| Fira Code Nerd Font appears, but terminal icons still look wrong | The terminal is still using the standard font, not the Nerd Font version | Set the terminal font family to the Nerd Font variant, then reload the terminal panel | Terminal settings and the icon glyphs inside the terminal |
How do you make Fira Code work in VS Code?
Two VS Code settings are typically needed: the editor font family should be set to Fira Code, and ligatures should be enabled if the combined glyphs are desired. After changing either setting, reload or restart the app, because VS Code may keep the old font until the window refreshes.
Set the editor font
- Open Settings. Use the VS Code settings screen, then search for the editor font family field.
- Enter the exact family name. Type the installed font name exactly as Windows shows it. If the name is even slightly off, VS Code may fall back to another monospace font.
- Save and reload. Reload the window or restart VS Code so the editor can re-read the installed fonts.
Turn on ligatures
- Search for ligatures. In VS Code Settings, find the ligatures option for the editor.
- Enable the setting. Turn it on only if you want the programming ligatures that the font supports. If you leave it off, the font can still render normally, just without those combined glyphs.
- Check a code sample. Open a file that includes characters the font combines, then confirm the editor shows the ligature forms rather than separate symbols.
Reload or restart VS Code
- Reload the window first. If the new font is installed but the editor has not changed, use the reload command inside VS Code.
- Restart if needed. Close and reopen VS Code when reload does not update the font. This clears stale font state more reliably than changing settings alone.
- Recheck the family name. If the editor still shows another font, return to the font family field and confirm the spelling matches Windows exactly.
Say your Windows Fonts list shows Fira Code, but VS Code still displays another monospace font after a restart. The usual miss is a slightly wrong family name in the editor settings. Correct the name, reload the window, and then verify the font changes on a file that uses ligatures.
Why doesn't Fira Code appear after install?
If the font does not appear, Windows may not have registered it, the file may still be inside a zip archive, or the app may be holding an old font cache. Start by checking the Windows Fonts list, because that tells you whether the install succeeded before you troubleshoot VS Code.
Check the Windows Fonts list
- Open the Fonts page. Go to Windows Settings, then Fonts, and search for the font name.
- Confirm the face name. Make sure the installed entry matches the exact family you downloaded. Standard Fira Code and the Nerd Font variant are different families.
- Open a preview. Use the installed-font preview to confirm Windows can display the face outside VS Code.
Confirm the exact font name
- Match the family label. Use the family name shown in Windows, not a shortened label from the download page.
- Check each weight. If you installed only one file, the editor may still list a fallback when bold or italic is requested.
- Try the rename-free path. Do not rename font files before installation; let Windows register them as shipped.
Decide whether to reinstall
- Remove the bad install. If the font list shows a broken or duplicate entry, uninstall it from Windows first.
- Install again from the extracted files. Open the font file directly, then use Install or Install for all users as needed.
- Restart the target app. Relaunch VS Code or the terminal after reinstalling so it can refresh its font list.
A common first-timer mistake is installing only the archive file, not the extracted .ttf or .otf files. Windows cannot register the font from the compressed package, so the family never appears in the installed list.
Should you use Fira Code Nerd Font?
Use standard Fira Code for coding in the editor when you only need ligatures. Pick Fira Code Nerd Font when you also want patched icon glyphs in a terminal, prompt, or shell theme. The two are not interchangeable, because the Nerd Font variant adds extra symbols that the standard package does not include.
Standard Fira Code for coding
- Choose the regular package. Install the standard font when your main goal is readable source code with ligatures.
- Use it in the editor. Set the VS Code editor font family to the standard family name, then turn on ligatures if you want them.
- Keep terminals separate. If the terminal does not need icon glyphs, you do not need the patched variant.
Nerd Font for terminals and icons
- Install the patched variant. Choose the Nerd Font package when your terminal theme depends on symbol glyphs.
- Point the terminal at it. Use the terminal font setting so the shell uses the patched family instead of the editor font.
- Verify the symbols. Open a prompt with icon-heavy output and confirm the glyphs render correctly.
When to pick each one
- Use standard for the editor. If you want a clean coding font and nothing else, the standard package is the simpler choice.
- Use Nerd Font for mixed use. If you want one font family for code plus terminal icons, install the Nerd Font variant and set it only where the icons matter.
- Keep both installed if needed. Many setups use the standard family in the editor and the Nerd Font variant in the terminal.
Common mistakes
- Downloading the font but not installing the extracted .ttf or .otf files.
- Installing the font, then forgetting to restart VS Code.
- Using the wrong family name in the editor font field.
- Turning on the font family but leaving ligatures off.
- Picking the Nerd Font variant when only the standard coding face is needed.
- Expecting Windows to install a font from a zip file without extraction.
Frequently asked questions
How do I install fira code on Windows 11?
Open the extracted font file, right-click it, and use the install option from the context menu. You can also go through Settings, then Personalization, then Fonts, and use the desktop font list there. After installation, confirm the family appears in the Windows Fonts list.
Where do I download Fira Code safely?
Use the project’s official release package or another trusted source that provides the font files directly, not a random repack. Download the standard package if you only need coding ligatures. Choose the Nerd Font package only when you need patched symbols for a terminal.
How do I make Fira Code show up in VS Code?
Install the font in Windows, then set the editor font family in VS Code to the exact registered name. Turn on ligatures if you want them, and reload the window after saving the setting. If it still does not appear, check the Windows Fonts list for the installed entry.
Why isn't Fira Code appearing after I install it?
Most often, Windows has not registered the extracted font file, or VS Code has not refreshed its font cache. Check Settings, then Fonts, and confirm the family name appears there. If it does, restart VS Code and verify the spelling in the editor font field.
Do I need admin rights to install a font on Windows?
No, not for a per-user install. You only need elevated rights for an install that should apply to all users on the PC. If you lack admin access, install the font for your account, then confirm it appears in your Windows Fonts list.
Should I use fira code or fira code Nerd font?
Use the standard font for code editing when you want ligatures and a plain coding face. Use the Nerd Font version when your terminal or prompt needs extra icon glyphs. Many setups use both: standard in the editor, Nerd Font in the terminal.