Source Serif: Adobe's OpenType Companion to Source Sans

What Source Serif is, and who the repository is actually for

Source Serif is a typeface, not a library. The README describes it as an open-source typeface designed to complement the Source Sans family, and the package.json describes it as a set of OpenType fonts. That distinction matters because the repository is mostly a delivery vehicle: the top level holds OTF/, TTF/, VAR/, WOFF/ and WOFF2/ directories plus a handful of CSS files, and the actual font sources and build instructions live on a different branch. The README points readers to the repository's main branch for source files and build instructions, while the default branch here is release.

The audience is therefore split. One group is designers and front-end engineers who want files they can drop into a project. The other group is type engineers who want to compile the fonts themselves, and the README sends them elsewhere. If you arrive expecting a build pipeline at the top level, you will not find one.

The family covers Latin, Greek and Cyrillic according to the 2017 release note linked from the README, and italics were added to all styles in 2018. Optical sizes arrived with Source Serif 4 in 2021, which the README describes as including a change of family name. That rename is why search traffic still mixes Source Serif Pro and Source Serif 4: they are the same lineage at different points in time.

How the optical size split and the variable build work

Most serif families ship one design. Source Serif ships several, and the top-level CSS filenames tell you the shape of it: source-serif-text.css, source-serif-subhead.css, source-serif-display.css, source-serif-caption.css and source-serif-smtext.css. Each corresponds to an optical size, meaning the letterforms are drawn differently depending on how large the text will be set. Caption and smtext are tuned for small sizes where hairlines would disappear; display is tuned for headline sizes where tighter spacing and finer contrast read better.

The practical consequence is that you cannot treat Source Serif as a single family you declare once and forget. A page that sets 12px body copy and 48px headings is using two different designs, and the CSS files reflect that. There is also source-serif-variable.css alongside a VAR/ directory, and the package.json keyword list includes cff2 and variable, which indicates the variable build is a first-class artifact rather than an afterthought.

The release notes support the same reading. Release 4.005R is titled Fonts version 4.005 and lists OTF, TTF, WOFF, WOFF2 and Variable as the delivered formats. Every release going back to 3.001R lists the same format set, so the distribution model has been stable across three major version lines.

Installing Source Serif and setting your first paragraph

There is no package manager install documented in the README. The README routes you to the latest release and to the full release list, and the repository ships the font binaries in directories rather than as a published npm package, even though a package.json exists. So the install path is: download the release, then either install the fonts on your system or copy the web formats into your project.

For a local install, the OTF and TTF directories hold the desktop formats. On macOS you open the file and confirm in Font Book; on Windows you right-click and choose Install. The README does not document a command-line install, so there is nothing to quote there.

For the web, the WOFF2 directory is the one you want, with WOFF as a fallback for older browsers. The repository already contains source-serif-text.css and its siblings, so the simplest route is to link the CSS file that matches your optical size rather than hand-writing a declaration. The repository does not list the individual filenames inside WOFF2/, so anything you write by hand would be a guess; use the shipped stylesheets instead. The demo/ directory contains index.html and style.css, which is the fastest way to see the family rendered before committing to it in a real project.

Where Source Serif is the wrong choice

The language coverage is the clearest boundary. The README's own design history says Greek and Cyrillic were added in 2017, and nothing in the README claims CJK, Arabic, Hebrew or Devanagari coverage. If your product ships in Japanese or Arabic, Source Serif covers none of it, and mixing it with a fallback for those scripts means two typographic systems on one page.

The second boundary is the one people hit after adopting it. Because the family is split by optical size, a single @font-face declaration gives you one optical size for everything. Setting a 10px caption and a 40px headline in the same cut is exactly the mistake the split exists to prevent, and the repository does not provide a combined CSS file that resolves it for you.

The third is weight range. The README's design history describes the 2014 release as three weights, with three more added later that same year, and Light appears in search traffic as a named style. If your design calls for a weight outside what a given release ships, the variable build is the answer, and that means adopting the variable CSS rather than the static files. The README does not document what happens if you request a weight the variable font does not carry, so test that before shipping.

Source Serif against Charter, Times New Roman and Roboto

The comparison people actually search for is Source Serif versus Charter, and the difference is in how the projects are packaged rather than in letterform quality. Charter is distributed primarily as a small set of static fonts. Source Serif ships five optical sizes, four web formats plus a variable build, and a CSS file per size. If you want one file and no decisions, Charter asks less of you. If you want a text face and a display face that were drawn as a pair rather than scaled, Source Serif gives you that.

Against Times New Roman the split is licensing and intent. Times New Roman is a system font that arrives with the operating system; you do not ship it, you inherit it. Source Serif is OFL-1.1 and you ship the files yourself, which means you control rendering but also own the subsetting, the loading strategy and the fallback stack.

Against Roboto the difference is classification, not quality. Roboto is a sans; Source Serif is a serif drawn to complement Source Sans. The comparison only makes sense if you are choosing a body face for long-form reading, in which case the relevant question is whether you already use Source Sans. If you do, Source Serif is the intended pairing and the metrics were designed with that in mind.

Maintenance, releases and what OFL-1.1 means for shipping

The release cadence is slow and that is visible in the facts. Version 4.005R was released on 2023-01-20, 4.004R on 2021-01-25, and 3.001R on 2019-10-11. That is roughly one release every one to two years. The repository itself is not archived, and the last push was on 2026-09-13, so there is ongoing activity, but the tagged font releases are infrequent. Plan for a family that changes shape every couple of years, not one that ships monthly.

Upgrade cost is mostly about the rename. The move from Source Serif Pro to Source Serif 4 changed the family name, which the README's 2021 design note confirms. Any CSS that declares font-family: "Source Serif Pro" will not pick up a Source Serif 4 file. That is a search-and-replace in your stylesheet, but it is also a check on any PDF or design file that embedded the old name.

The licence is OFL-1.1, stated both in package.json and in the LICENSE.md at the top level. The Open Font License permits use, modification and redistribution, including embedding in documents and applications, provided the reserved font name rules are respected and the licence travels with the files. If you modify the fonts and redistribute them, the naming restriction is the part to read carefully. This is not legal advice; read LICENSE.md before you rename or subset for redistribution.

Editorial conclusion

Adopt Source Serif if you are setting body text in a Latin, Greek or Cyrillic script and want a serif that pairs with Source Sans under a licence that permits commercial embedding. Do not adopt it if you need a CJK or Arabic companion, or if you expect the repository to be a build system rather than a distribution point. Verify first that the release you download actually contains the optical size you want, because the family is split into separate text, subhead, display, caption and smtext cuts, and a single CSS file will not cover all of them.

Frequently asked questions

Official sources

1. adobe-fonts/source-serif on GitHub
2. License: OFL-1.1
3. Project website
4. README
5. Releases