Unlike literally any other platform or OS, Windows never had flag emojis, and that always irked me a little bit. Having to guess what flag someone else is trying to send by just two letters isn't a great user experience, you know. And I always just kinda sighed at it, helplessly.

But not today... Today I woke up, and the absence of flag emojis in Windows has triggered me like never before, and so I've spent over 14 hours hyperfocused on this task of bringing flag emojis to Windows (without replacing all the emojis, that is, like some other projects did).

And now you too can say "No!" to Windows, "I want the flag emojis that everyone else has!", download and install this font, restart your PC, and finally get to enjoy the full emoji experience on Windows!

This font is based on Segoe UI Emoji v1.60 (3D Fluent 16.0; Win11 25H2; 2025-08-29) and contains 262 flags from Twemoji v17.0.3 (jdecked/twemoji@b6b55fe 2026-06-01). You can build it yourself, if you'd like (see the "How to build from scratch" section in the end).

• 🔨 Remade the entire build process with Make.
• 📸 Now includes new 17.0 emojis that aren't yet in Fluent 3D.
• 🔳 Added black-and-white rendering support for older apps (see #12).
• 🔧 A partial fix for rendering in VSCode's xterm.js terminal (see #13).
• ⚡️ Optimized the assets with SVGO, and upgraded build scripts API.

• ✨ Added support for COLRv0 rendering! Now works on Windows 8-10 too.
• 💚 Now compiled with the emojis directly from jdecked/twemoji repository.
• ⚡️ Removed unnecessary SVG table, decreasing the font's size from 13.1 to 12.1 MB.
• 📏 Fixed the relative width and size of the emojis. Now they're the same size as others.

1. Installation
2. Screenshots
3. Similar projects & comparison
4. How to build from scratch

Also, you can read my blog post! (a bit outdated now)

Regular "Install" will only affect a few certain apps: Chromium-based browsers (Chrome, Opera, Vivaldi, etc), and Electron-based apps (Discord, VS Code, etc), so if that's enough for you, you can do this type of install.

"Install for all users" will attempt to render country flags in the system and many other apps too. Sometimes with mixed results though, since the system renders fonts inconsistently (more on that in the next section).

Recover the original Segoe UI Emoji file: Copy-Item "C:\Windows\Fonts\seguiemj.ttf", and install it for all users.

Go to Settings > Personalization > Fonts, and find and select Segoe UI Emoji in the list. In the Metadata section, find the font file that you installed. Press the "Uninstall" button, and restart your PC.

In a Microsoft Word document:

Fonts preview in "Settings > Personalizations > Fonts":

In the system Start menu:

In the system task bar:

Country flags are uncolored in the Explorer, but so are the rest of the emojis. It must be some sort of a limitation in the system itself, if it doesn't even color Windows's own original emojis.

When the country flags appear invisible, you can see that the rest of emojis "downgrade" to lesser-quality versions. And when country flags are uncolored, the rest of emojis are uncolored too. So it's not something that any font can fix, — it's a limitation of the system itself. Maybe in future versions Windows will be able to render emojis consistently everywhere, but at the moment, it's the best that can be done.

• perguto/Country-Flag-Emojis-for-Windows replaces Segoe UI Emoji with Google's Noto Color Emoji.

• quarrel/broken-flag-emojis-win11-twemoji replaces Segoe UI Emoji with Twemoji emojis.

Here are the emojis that you get in all projects, for comparison:

I personally prefer the original Fluent 3D set. A touch of 3D shading looks really nice and it brings some life to the emojis. Fluent 3D's people emojis have actual eyes, while others' have creepy dot eyes and blank stares. Also, as someone with entomophobia, Fluent 3D's bug emoji is the easiest to look at, and as a developer I have to look at it pretty often. And look at Fluent 3D's animals! So cute!

And here's a comparison of flags as well:

I decided to use Twitter's flag emojis, since Noto's wavy ones just look weird — straight lines become curves, circles become ovals, there's a weird gray glow around the flags, and they also don't downscale well.

The project's build process is pretty complicated and takes a long time (full run = 5 mins on 20-core CPU), so I put it all in a Makefile, to cache and reuse intermediate results. If you're on Windows, you'll need WSL to run Make and all the Unix commands.

• git for cloning jdecked/twemoji's SVG assets,
• .NET SDK 10+ for running scripts and merging fonts,
• Python/pip for nanoemoji and fonttools, [de]compiling fonts,
• pip install nanoemoji fonttools[lxml]
• Node.js/npm for svgo, optimizing SVG assets,
• npm install -g svgo
• Inkscape for rasterizing SVGs into PNGs,
• ImageMagick for converting PNGs into BMPs,
• Potrace for tracing BMPs into single-color SVGs,
• HarfBuzz ≥14.2.0 (Apr 2026) for font render tests,
• 7z for packaging the font into a zip file,
• And don't forget to update your PATH.

sudo apt-get update
sudo apt-get install make git dotnet python3 nodejs npm inkscape imagemagick potrace p7zip-full
sudo pip install nanoemoji fonttools[lxml]
sudo npm install -g svgo

After installing everything, you can run these Make commands (if you're on Windows, run them in WSL):

• make build (default) builds the font (build/merged.ttf).

• make package builds and then copies to Segoe.UI.Emoji.with.Twemoji.Flags.{ttf,zip}.

• make test-vars prints the commands for the tools that will be used.

• make test renders PNGs with all of the flags (build/tests/; configurable make test FLAGS_PER_LINE=8).

• make clean cleans the build cache (simply rm -rf build).

• make rebuild is a combo of clean followed by build.

The C# merge script I wrote is a bit janky and disorganized, since I've had to try so many different things to finally get it to work... And it probably won't work with any other fonts, despite all my attempts to keep it as generic as possible.

If you want to add emojis to Segoe UI Emoji from some other font, here's a list of resources that I found useful:

• fontTools ttx can decompile TTF into a readable and editable XML, and recompiles it back losslessly.
• OpenType's spec on Microsoft Learn explains the overall structure of a TTF file and its tables, and what different type ids mean, and etc.
• GSUB docs on FontForge clarifies some stuff about substitution lookups.
• HarfBuzz brought the project to the finish line! It not only renders font characters into the terminal, but also shows the entire textshaping process (run with option -V). I was stuck for a while on script and feature switches, not realizing that they disable rendering the ligatures in some places.