Nebula Sans: a free font for your SaaS

Your product has seven screens and five different fonts. Nobody chose that. It just happened: the dev used the framework's default font, the freelance designer brought another one, someone pasted in a library component that came with a third, and the transactional email went out in Arial because nobody looked. Nebula Sans, a free and open source font built for interfaces, solves a good chunk of that with a single decision. And it is exactly the kind of decision most small SaaS teams put off until it turns into rework.

Let me explain why typography matters more than it looks in a digital product, and why a well made free font today delivers what only an expensive license delivered five years ago.

Why your SaaS font is not a detail

A SaaS is 90% text. Field labels, buttons, tables, error messages, dashboard numbers, billing notices. Users spend the day reading what you wrote, on small screens, in a hurry, often on a phone in the middle of something else.

When the font is bad for interfaces, the cost shows up in places nobody connects to design:

• The 1 looks like an l and the customer types the wrong code.
• Numbers in a column don't line up, and the billing table gets hard to compare.
• The 12px text goes blurry, and the person zooms in instead of reading.
• The "semibold" weight doesn't exist, so everything is either too thin or too heavy.

None of this takes the product down. It just makes it look amateur and tire people out faster. Fatigue becomes a support ticket, and a support ticket becomes a cost with a first and last name.

Fonts made for long form reading, the pretty ones you see on marketing sites, were drawn for a different job. An interface needs a font that can be read a hundred times a day without calling attention to itself.

What Nebula Sans brings

Nebula Sans is a neo grotesque sans serif, the family Helvetica made famous. Neutral shapes, no loud personality, built to disappear and let the content show. It is free, open source, and cleared for commercial use.

The parts that matter for a product:

• A full range of weights. You can build real hierarchy: title, subtitle, body, caption, each with its own weight. No "just bold it" workarounds.
• Tabular figures. Every digit takes the same width, so columns align on their own. If you show prices, balances, or metrics, this is the most underrated item on the list.
• Drawn for screens, not for paper. Spacing open enough that small text stays readable.
• A license with no catch. You use it in the app, on the site, in email, in the contract PDF, in the sales deck. No pageview counting, no yearly renewal.

That last one is what a lot of people find out too late. Commercial web font licenses are usually billed by traffic volume. Traffic grows, the bill grows. And it is a bill nobody put in the financial plan, because a font doesn't feel like infrastructure.

A good font is the one you don't notice. If the user noticed the font, it got in the way.

"But isn't a free font worse?"

It was, ten years ago. Free meant three weights, crooked accents, and a ç that looked taped on.

That changed. The best interface fonts today are open, and many of them were born inside product companies that needed to solve their own problem. The model shifted: instead of selling the font, the studio releases it and earns reputation and work.

The test I run is always the same, and you can do it in five minutes:

1. Write the most boring text in your product in that font. Something like "We couldn't process your payment. Check your card details and try again."
2. Set it at 13px, medium gray, white background.
3. Look at it on a phone, with the brightness turned down.
4. Next to it, write a column of values: 1,480.00 / 990.00 / 12,375.50.

If the small text stays clean and the numbers align, the font works. If it doesn't, no price tag saves it. I have seen a thousand real font fail this test because it was drawn for a magazine.

And there is the boring part almost nobody tests: accented characters. Portuguese uses ã, õ, ç, é, ê, à. Plenty of foreign fonts treat those as decoration. If the tilde sits glued to the a or the cedilla vanishes at small sizes, your product will look like it went through Google Translate. Test it with "Informações da assinatura não disponíveis" before deciding anything.

The hidden cost: weight and speed

Here is the part that hits revenue directly.

Every font weight is a file the browser has to download before it can show the text properly. If you load six weights, plus an italic for each, typography alone can go past 500 KB. On a bad 4G connection, the user stares at a blank screen or watches the text jump from one font to another mid sentence.

What I do in practice:

• Load two or three weights, max. Regular, medium, and bold cover 95% of any interface.
• Use woff2, the lightest format, and it works everywhere that matters.
• Host the font on my own domain instead of pulling it from an external service. One less dependency, one less request, and nobody tracking your users for free.
• Set a system font as the fallback, so text shows up immediately while the main one loads.

That usually cuts the time to first readable text in half. This isn't nerd micro optimization: it is what separates the visitor who waits from the one who closes the tab.

One decision, not a project

What I wish more people understood is that standardizing typography is cheap when you do it early and expensive when you do it late.

Early: you pick one family, define five sizes, three weights, and write that down in a file. Half a day of work.

Late: you have forty components with sizes invented on the spot, the transactional email in another font, the PDF in another, the landing page in one more. At that point it isn't typography, it's archaeology. I once took over a project with nineteen different text sizes across twenty screens. Nobody decided that. It was just nobody deciding anything, for two years.

The scale I use almost every time, and it covers any SaaS:

• 12px caption
• 14px interface body
• 16px reading body
• 20px section title
• 28px page title

Five sizes. If you need a sixth, the problem is probably layout, not typography.

How to apply this in your week

If you run a product and you read this far thinking "yeah, mine is a mess", start with the most visible part:

1. Open the screen your customers use most. Just that one.
2. List how many text sizes and weights show up there.
3. Cut it down to four combinations, max.
4. Pick a single family, apply it, and move to the next screen the following week.

You don't need a redesign. Redesigns are expensive, slow, and they scare users. Standardizing is boring, fast, and nobody complains, because people just feel the product got easier without being able to explain why.

This is the kind of cleanup I do on products that are already running: touching what pays off, without stopping operations or throwing away what works. If your SaaS is at that point where everything works but nothing looks like it came from the same place, tell me how things are today and we'll see what to solve first.

Your SaaS has seven screens and five different fonts. Nobody chose that, it just happened.

The dev used the framework default, the freelancer brought another one, the transactional email went out in Arial because nobody looked.

Sounds like a detail, but a SaaS is 90% text. When the "1" looks like an "l", the customer types the wrong code. When the numbers don't line up, the billing table turns into guesswork. That becomes a support ticket, and a ticket has a cost with a first and last name.

The good news: today you can fix it with a free, open source font, like Nebula Sans. Full range of weights, tabular figures, a license with no catch.

Standardizing typography costs half a day if you do it early. Leave it for later and it stops being design, it becomes archaeology.

If your product works but nothing looks like it came from the same place, get in touch and we'll see what to fix first.

#SaaS #Typography #ProductDesign #UX #MicroSaaS