Introducing the Cascadia Code Font
Cascadia Code is finally here! You can install it directly from the releases page in our repository on GitHub or automatically get it in the next Windows Terminal update.
Cascadia Code was introduced this May at the Microsoft Build event. This is the latest monospace font provided by Microsoft, which provides a fresh command line experience and code editors. Cascadia Code was developed hand in hand with the new Windows Terminal app. This font is recommended for use with terminal applications and text editors such as Visual Studio and Visual Studio Code.
Cascadia Code supports software ligatures! Software ligatures are most useful when writing code, as they create new glyphs by combining characters. This helps make the code readable and “friendly” for some people.
Note: if you use Visual Studio Code, then to use ligatures you will need to enable Font Ligatures in the settings.
Yes, you heard right! Cascadia Code is available on GitHub under the SIL Open Font License , so you can contribute if you wish!
Note: there is currently no proper testing infrastructure in the repository, so all pull requests must be manually tested and approved by Microsoft. This slows down the coordination of pull requests, so please be sympathetic to this.
The name Cascadia Code comes from the Windows Terminal project. Before it was released, the code name for Windows Terminal was Cascadia. In fact, some of the source files in Windows Terminal still use this name! We liked the idea to name the font by the code name of the project. This is such a tribute to Windows Terminal.
We added “Code” at the end of the font name to indicate that this font is primarily for programming. In particular, it helps determine that it includes software ligatures.
To make sure that Cascadia Code was the right choice for the font name, we did a Twitter survey along with the other names that we considered. We are very grateful to everyone for participating and were very pleased that Cascadia Code was the winner.
Many thanks to Aaron Bell, designer of Cascadia Code. We were fortunate enough to work with him over the past year, and he did a really great job. Aaron Bell, a font designer and owner of Saja Typeworks , has been with Microsoft for many years. For example, back in 2015, he was the designer of Selawik ! You can follow his activities on Twitter ( @aaronbell ), and in our repository on GitHub. We plan to continue working with it to improve Cascadia Code and make it a great font for everyone!
Cascadia Code font version 1909.16 is currently available on GitHub. It will conform to the syntax of Windows versions and will receive updates related to new and improved glyphs.
For information on any updates to the Cascadia Code, feel free to follow our repository on GitHub or the Kayla ( @cinnamon_msft ) and Rich ( @richturn_ms ) Twitter pages . We are very pleased to release our font in the public domain and look forward to when you start using it.
Wait, what's the Cascadia Code?
Cascadia Code was introduced this May at the Microsoft Build event. This is the latest monospace font provided by Microsoft, which provides a fresh command line experience and code editors. Cascadia Code was developed hand in hand with the new Windows Terminal app. This font is recommended for use with terminal applications and text editors such as Visual Studio and Visual Studio Code.
Software Ligatures
Cascadia Code supports software ligatures! Software ligatures are most useful when writing code, as they create new glyphs by combining characters. This helps make the code readable and “friendly” for some people.
Note: if you use Visual Studio Code, then to use ligatures you will need to enable Font Ligatures in the settings.
Did we mention that it is open source?
Yes, you heard right! Cascadia Code is available on GitHub under the SIL Open Font License , so you can contribute if you wish!
Note: there is currently no proper testing infrastructure in the repository, so all pull requests must be manually tested and approved by Microsoft. This slows down the coordination of pull requests, so please be sympathetic to this.
Why is it called Cascadia Code?
The name Cascadia Code comes from the Windows Terminal project. Before it was released, the code name for Windows Terminal was Cascadia. In fact, some of the source files in Windows Terminal still use this name! We liked the idea to name the font by the code name of the project. This is such a tribute to Windows Terminal.
We added “Code” at the end of the font name to indicate that this font is primarily for programming. In particular, it helps determine that it includes software ligatures.
To make sure that Cascadia Code was the right choice for the font name, we did a Twitter survey along with the other names that we considered. We are very grateful to everyone for participating and were very pleased that Cascadia Code was the winner.
Who is the designer of Cascadia Code?
Many thanks to Aaron Bell, designer of Cascadia Code. We were fortunate enough to work with him over the past year, and he did a really great job. Aaron Bell, a font designer and owner of Saja Typeworks , has been with Microsoft for many years. For example, back in 2015, he was the designer of Selawik ! You can follow his activities on Twitter ( @aaronbell ), and in our repository on GitHub. We plan to continue working with it to improve Cascadia Code and make it a great font for everyone!
What will happen next with Cascadia Code?
Cascadia Code font version 1909.16 is currently available on GitHub. It will conform to the syntax of Windows versions and will receive updates related to new and improved glyphs.
stay in touch
For information on any updates to the Cascadia Code, feel free to follow our repository on GitHub or the Kayla ( @cinnamon_msft ) and Rich ( @richturn_ms ) Twitter pages . We are very pleased to release our font in the public domain and look forward to when you start using it.
All Articles