Evergarden Font Manager

Evergarden started as a side project born out of a pretty simple frustration.

I spend a lot of time designing and building interfaces, which means I'm constantly trying out different typefaces. Over the years, my font collection grew larger and larger, and eventually managing it became a chore.

Windows has a built-in font viewer, and while it works fine for basic previews, I always felt like it stopped just short of being truly useful. I could see what a font looked like, but I couldn't easily explore its OpenType features, inspect glyphs, compare it with other typefaces, or experiment with it the way I wanted to.

Because of that, I found myself bouncing between different tools and websites just to answer simple questions:

• ➔Does this font support the stylistic alternates I need?
• ➔What OpenType features does it include?
• ➔How well does it pair with another typeface?
• ➔Is it actually the right choice for the project I'm working on?

It wasn't a terrible workflow, but it felt scattered and slower than it needed to be.

Around the same time, I wanted to learn Electron and get more experience building desktop applications. Instead of creating another tutorial project, I decided to build something I would genuinely use myself.

Evergarden is a local-first font manager designed around the way I actually work with typography.

Rather than treating fonts as files sitting in a folder, the goal is to make it easier to explore, understand, and evaluate typefaces before using them in a project.

Some of the features currently include:

• ➔Visual browsing for large font collections
• ➔Real-time font previews and custom text testing
• ➔Glyph and character inspection
• ➔Font metadata and metrics exploration
• ➔OpenType feature discovery and testing
• ➔Fast local search and indexing

The idea is to bring the most common typography tasks into a single place so there's less context switching between different tools.

Evergarden is built with Electron, React, and SQLite.

Everything is indexed and stored locally, which keeps the application fast and fully functional offline. Since most font management happens on a single machine anyway, a local-first approach felt like the simplest and most practical solution.

SQLite handles indexing and search, making it easy to work with large font libraries without introducing unnecessary complexity.

Evergarden is still very much a work in progress.

Lately, I've been exploring ideas that push it beyond being just a font manager, including:

• ➔Typography playgrounds with curated font pairings
• ➔Starter kits that combine typography and color palettes
• ➔Icon testing and comparison tools
• ➔Better font discovery workflows
• ➔More advanced OpenType exploration

The long-term vision is to create something that sits between a traditional font manager and a typography workspace—a tool that helps designers not only organize fonts, but actually experiment with and use them more effectively.