Web fonts for a small business website: Fontsource and three self-hosting alternatives
Fontsource is our pick for a site with a bundler: its font package keeps visitor requests on your site. Google’s files, google-webfonts-helper and Font Squirrel offer local delivery with more manual integration.
Fontsource Open Sans
One open-licensed package puts the font files in your own build, so visitors’ browsers contact no font provider, and the licence travels with the files.
Narrow lead: 4.70 against 4.60 for both self-hosted Google files and google-webfonts-helper. Needs a bundler and someone to update the package.
Why Fontsource is our PickTeam behind Fontsource Open Sans? Get your award badge
No Rising Star selected
Two public hosted services lack a verified first-release date, and one also lacks an identifiable responsible operator. Another service remains invite-only.
No checked newcomer met all our availability, launch-date and safety requirements; some candidates could not be checked.
Who is this article for? Owners and developers of a small business website with a build step who want a font in regular and bold without an account. Covers German privacy rulings; not legal advice.
About 20 min read
What Preferred Pick, Rising Star and Ready to Rock mean
The quick list
Start with Fontsource for a site with a bundler. These four free routes keep font delivery on your site; compare the package, file preparation, licence and update work.
These four routes cost $0 for the fonts; website hosting is separate. Google and Fontsource supply OFL editions of Open Sans; Font Squirrel lists an Apache 2.0 edition. We could not confirm prices for OpenFont or Fontlay.
The comparison at a glance
Compare who visitors’ browsers contact, what German courts and a regulator have said, what each licence allows and how much each route depends on a provider.
Fontsource leads narrowly for a small business site with a bundler. Self-hosted Google files and google-webfonts-helper tie next, with Google’s files ahead on independence from a provider; Font Squirrel is fourth.
Hides matching answers for the selected tools. Unknowns and unverified claims stay visible.
| Feature | Fontsource Open Sans | Self-hosted Google Fonts files | google-webfonts-helper | Font Squirrel Open Sans |
|---|---|---|---|---|
| Best fit | Preferred Pick: a site with a bundler that wants its fonts served from its own files | Also consider: no extra package in the build, or no bundler | Ready-made WOFF2 and CSS without a package in the build | A downloadable kit if its older edition and manual setup suit you |
| What a visitor’s browser contacts for the font | Only your site | Only your site | Only your site after local integration | Only your site after local integration |
| German rulings and regulator guidance | Local hosting, the option Lower Saxony’s regulator recommends | Local hosting, the option Lower Saxony’s regulator recommends | Local hosting, the option Lower Saxony’s regulator recommends | Local hosting, the option Lower Saxony’s regulator recommends |
| Price and licence for the example family | $0; Open Sans under SIL OFL 1.1 | $0; Open Sans under SIL OFL 1.1 | $0; Open Sans under SIL OFL | $0; this Open Sans edition under Apache 2.0 |
| Main drawback | Needs a bundler and someone to update the package; avoid the malicious look-alike “fontsource” package | Most manual work: conversion, CSS and updates | Manual integration and updates; deployed dependencies and generated kit not inspected | Kit lists WOFF rather than WOFF2; different edition and licence from current Google files |
Fontsource is our pick for a small business site with a bundler. All four routes can serve Open Sans from your site. Font Squirrel publishes a different edition under Apache 2.0; do not assume its files match current Google or Fontsource files. Prices for OpenFont and Fontlay could not be confirmed. We did not rank appearance or speed. German legal guidance is not advice for a particular site.
All features and sources 12 criteria
Open the groups that matter to you. They compare the same selected tools. “Planned” means future work, not an available feature. Sources include the published conditions.
Getting regular and bold onto the site
Show 4 criteria
| Feature | Fontsource Open Sans | Self-hosted Google Fonts files | google-webfonts-helper | Font Squirrel Open Sans |
|---|---|---|---|---|
| Account needed | No; public npm package | No; public repository or download | No; public download helper | Public download and kit controls; no sign-in shown |
| How the font reaches your site | npm install and one CSS import; the bundler copies the WOFF2 files into your build | Download the TTF files, convert or subset them, and write your own @font-face rules | Select family, weights and subsets; download WOFF2 and CSS; copy both into your site | Choose regular/bold and a kit subset; add files and CSS to your site; kit lists WOFF, not WOFF2 |
| Regular and bold for the example family | Variable face, weights 300–800; italic is a separate import | Variable TTF with weight and width axes, plus a separate italic | Family/variant selection supports regular and bold; italics separately selectable | Static regular, bold and other weights with italics listed |
| After setup | Pinned; you update the package when you choose | Fixed; you replace the files by hand | Fixed local files; repeat selection and copy replacements yourself | Fixed local files; replace them yourself |
These selected tools have matching answers in this group. Turn off “Show differences only” to see them.
Sources for getting regular and bold onto the site
Fontsource installation and package evidence, Google repository and OFL licence: checked October 19, 2026. Additional documentation read November 6, 2026: google-webfonts-helper, Font Squirrel Open Sans and FAQ. Documented behaviour, not a speed or quality test.
Visitor data and the law
Show 2 criteria
| Feature | Fontsource Open Sans | Self-hosted Google Fonts files | google-webfonts-helper | Font Squirrel Open Sans |
|---|---|---|---|---|
| What a visitor’s browser contacts for the font | Only your site | Only your site | Only your site after local integration | Only your site after local integration |
| German rulings and regulator guidance | Local hosting, the option Lower Saxony’s regulator recommends | Local hosting, the option Lower Saxony’s regulator recommends | Local hosting, the option Lower Saxony’s regulator recommends | Local hosting, the option Lower Saxony’s regulator recommends |
These selected tools have matching answers in this group. Turn off “Show differences only” to see them.
Sources for visitor data and the law
Local hosting guidance: Lower Saxony data-protection authority, November 24, 2022, checked October 19, 2026. German, fact-specific guidance; not legal advice or a compliance guarantee for your site.
Licence, handoff and continuity
Show 6 criteria
| Feature | Fontsource Open Sans | Self-hosted Google Fonts files | google-webfonts-helper | Font Squirrel Open Sans |
|---|---|---|---|---|
| Price and licence for the example family | $0; Open Sans under SIL OFL 1.1 | $0; Open Sans under SIL OFL 1.1 | $0; Open Sans under SIL OFL | $0; this Open Sans edition under Apache 2.0 |
| Licence terms that matter | OFL licence file ships in the package; keep it with the files | OFL file sits beside each family; Open Sans has no reserved font name | Font licence applies; Open Sans under OFL; helper code MIT-licensed | Family page publishes Apache 2.0; retain required notices with files |
| Subsetting and format conversion | Allowed by the OFL; the package is already split by character range | Allowed by the OFL; you do it | WOFF2 and subsets provided by the helper under the family licence | Kit offers subset selection; Apache 2.0 permits modifications subject to its notices |
| Handing font files to a developer or agency | Allowed with the licence and copyright notice | Allowed with the licence and copyright notice | OFL files may be shared with their licence and copyright notice | Apache 2.0 permits redistribution subject to its licence and notices |
| Provider dependence and terms | None at page load; the build depends on an npm package with two maintainer accounts | None | No provider at page load or in the site build; future kits depend on helper upkeep; legacy client code documented | No provider at page load or in the site build; current upstream edition not established |
| Main drawback | Needs a bundler and someone to update the package; avoid the malicious look-alike “fontsource” package | Most manual work: conversion, CSS and updates | Manual integration and updates; deployed dependencies and generated kit not inspected | Kit lists WOFF rather than WOFF2; different edition and licence from current Google files |
These selected tools have matching answers in this group. Turn off “Show differences only” to see them.
Sources for licence, handoff and continuity
Current Google Open Sans OFL and Fontsource package terms, checked October 19, 2026. Font Squirrel Apache 2.0 edition, helper documentation and helper change history, read November 6, 2026. Existing website hosting is separate; no paid font plan is required for these four routes.
What matters when choosing
Fontsource is our Practical Pick for a small business website built with a bundler such as Vite or Webpack. You install one free package, such as @fontsource-variable/open-sans, import it once, and your build copies the font files into your own site. Visitors’ browsers then fetch the font from your site and contact no font provider. The package carries the font’s Open Font License, so the terms stay with the files, and Google’s own font repository names Fontsource as a popular way to self-host the fonts it serves. The compromise is upkeep: someone has to add a build dependency, update it when they choose and install the correct scoped package, because a malicious look-alike called fontsource has been flagged on npm. Its lead is narrow. Fontsource scores 4.70 against 4.60 for both hosting Google’s files yourself and using google-webfonts-helper. Its 0.10 lead rests on the balance between setup work and dependency risk, rather than a measured difference in font delivery. Fontsource installation guide, Google Fonts repository, malware advisory
If you would rather not add a package to your build, or your site has no bundler, host Google Fonts files yourself. Google’s repository publishes the files under their open licences, and the Open Font License lets you convert and subset them. You do that work, write the CSS and replace the files by hand when the font changes. Next.js and Astro sites can let the framework do this at build time. Open Sans licence, Next.js fonts, Astro fonts
The hosted links are quicker but send every page view to a third party. The Google Fonts API is the shortest setup, and it is the route German courts have examined: in 2022 the Munich Regional Court found that loading it without the visitor’s consent unlawfully passed the visitor’s IP address to Google, partly because the site could have hosted the fonts itself. Google’s own privacy FAQ says the Fonts API does not set or log cookies and does not use collected information for profiling or targeted advertising (updated July 23, 2024; July 3, 2026 archived copy checked October 19, 2026). Bunny Fonts swaps Google for an EU company with a one-line change and says it stores no logs, but it is still a third-party request, no court has ruled on it, and we found no terms specific to the font service. Choose Fontshare only if you want its typefaces, such as Satoshi. Its free licence allows self-hosting on your own sites but forbids subsetting or converting the files and handing them to a contractor, and it lets the publisher withdraw its API without notice. Munich ruling, Bunny Fonts, ITF Free Font License
Our comparison assumes one sans-serif family in regular and bold, free commercial use and no account, checked October 19, 2026. The four routes below cost $0 for the fonts; you still supply the website hosting. Two conditions would change our recommendation. A site without a bundler, or a wish to keep third-party packages out of the build, points to hosting Google’s files yourself. A design that needs Satoshi points to Fontshare, self-hosted under its licence. Adobe Fonts is not compared because its web fonts need a Creative Cloud subscription, are served only from Adobe and stop working if you cancel. If any clean typeface will do, a system font stack downloads nothing at all, though the face differs by device. The legal points below summarise German decisions and one regulator’s guidance; they are not legal advice. Adobe web-font licensing FAQ, November 14, 2025, Modern Font Stacks
No Rising Star selected. We found no newcomer with both a documented first public release in the past two years and enough evidence to meet our availability and safety requirements. Two hosted services lack a verified first-release date; another is still invite-only. That does not mean no suitable newcomer exists.
We could not confirm prices for OpenFont or Fontlay.
Fontsource Open Sans
Preferred Pick · local delivery with a bundler
Choose Fontsource when your site has a bundler and you want fonts served from your own files, with the licence in the package.
Reasons to choose it
- Visitors contact no font provider
- Licence file and WOFF2 subsets ship in the package
- One install and one import; version stays pinned
What to watch
- Needs a bundler and someone to update the package
- Install the scoped @fontsource packages, not the malicious look-alike “fontsource”
- Narrow lead over self-hosted Google files and google-webfonts-helper
Fontsource repackages open-source fonts, including the Google Fonts catalogue, as npm packages. The @fontsource-variable/open-sans package, version 5.3.0, published July 19, 2026 and still current on October 19, contains the Open Font License file, CSS that splits the font by character range and WOFF2 files. Its default face covers weights 300 to 800, so regular and bold come from one file per character range, and the browser downloads only the ranges a page uses. Since version 5.1, Fontsource packages are published with an npm provenance attestation that links each release to its build. The two Open Sans packages were downloaded more than 530,000 times in the week to October 18. Installation guide, Open Sans on Fontsource, package record, changelog
Choose another route if your site has no build step. Fontsource’s guide says you need a bundler such as Vite or Webpack to handle its CSS imports; otherwise you download its files and write the CSS yourself. Italic is a separate import. Packages stay at the version you pinned, which protects your layout from surprise changes but means someone must update them. Fontsource’s README warns that Google often updates fonts without notice. In March 2024 a user reported that Open Sans releases kept adding and removing files; the maintainer traced it to an update-job bug that had gone unnoticed for about a year and had already pushed a fix. Fontsource also offers CDN links; those send visitors’ requests to the CDN, so use the package if local delivery is your reason for choosing it. Fontsource repository, issue 948
Read the full Fontsource Open Sans analysis and sources
Install the scoped package names that start with @fontsource/ or @fontsource-variable/. An unrelated, unscoped npm package called fontsource was flagged as malware in February 2025; its advisory says any computer that installed it should be considered fully compromised. Fontsource’s code is MIT-licensed and actively maintained, with commits on October 14, 2026, but npm lists only two maintainer accounts for the Open Sans package. Advisory GHSA-2xwx-2g4x-h7px, OSV record MAL-2025-1361
In an earlier hands-on check on October 1, 2026, before we adopted our research-only method, a test page built with version 5.3.0 displayed regular and bold Open Sans from its own WOFF2 file while every outside request was blocked. That was one browser session with one package version, and it did not measure speed or uptime. Earlier check record, October 1, 2026
Used Fontsource Open Sans? Share your experience to help other readers choose.
Self-hosted Google Fonts files
Also consider · no extra package or no bundler
Host Google’s font files yourself when you would rather not add a package to your build, or your site has no bundler.
Reasons to choose it
- No provider at page load or at build time
- Route recommended by Lower Saxony’s regulator
- OFL allows subsetting and conversion
What to watch
- Repository files are TTF; you convert and subset them
- You write the CSS and replace files by hand
Google publishes the font files it serves in a public repository, each family with its licence. Open Sans is under the SIL Open Font License, with copyright held by the Open Sans Project Authors and no reserved font name, so you may subset, convert and redistribute it with your site as long as the licence and copyright notice go with it. Google’s privacy FAQ says that when a font is loaded from your own server, Google does not receive any data about the visit. The Lower Saxony data-protection authority recommends this local hosting as the privacy-compliant option. Open Sans licence, Google Fonts repository, privacy FAQ, Lower Saxony guidance, November 24, 2022
The cost is your time. The repository holds TrueType files, here a variable OpenSans[wdth,wght].ttf with weight and width axes and a separate italic. For small, fast files you convert them to WOFF2, keep only the characters you need and write the @font-face rules, then repeat when the font changes. Google’s FAQ lists larger files, weaker browser compatibility and manual updates as drawbacks of self-hosting; converting to WOFF2 and subsetting answer the first, and the third is the upkeep just described. The free google-webfonts-helper site produces WOFF2 files and CSS for you, but its author’s README describes much of its code as legacy with deprecated dependencies, so treat it as a convenience, not a dependency. Next.js and Astro download fonts at build time and serve them from your site, which gives the same result inside those frameworks. google-webfonts-helper, Next.js fonts, Astro fonts
Used Self-hosted Google Fonts files? Share your experience to help other readers choose.
google-webfonts-helper
A font kit without a build dependency
Choose google-webfonts-helper to get WOFF2 files and matching CSS without adding a font package to your build.
Reasons to choose it
- Visitors contact only your site
- Choose weights and character ranges
- No package needed in the site build
What to watch
- Copy files and CSS into your site yourself
- Updates remain manual; the helper has legacy client code
- Generated kit contents and deployed dependencies not verified
google-webfonts-helper is Mario Ranftl’s public tool for downloading Google Fonts as a set of font files with matching CSS. Choose the family, character range and regular/bold variants, then copy the files and CSS into your site. Its documentation lists WOFF2 output, so it removes the conversion work involved in starting with Google’s repository TTF files. Visitors then request fonts from your site. The font’s own licence still applies; Open Sans is available under the Open Font License. It scores 4.60, narrowly behind Fontsource and level with the manual Google-files route. Documentation and source, read November 6, 2026; Open Sans licence, checked October 19, 2026.
Choose it when you want a ready-made font kit without adding an npm dependency to the site. You still integrate the CSS, keep the licence with the files and replace the files yourself when you want an update. The author describes the client as legacy Angular code; the project has received dependency updates, including one on October 1, 2026, so that wording does not mean it is abandoned. Local copies keep working if the helper disappears, but future downloads depend on the service or finding another source. We have not verified a particular generated kit or its current deployed dependencies. Repository, change history, read November 6, 2026.
Used google-webfonts-helper? Share your experience to help other readers choose.
Font Squirrel Open Sans
A downloadable font kit
Consider Font Squirrel for its Open Sans kit interface when you accept an older edition and manual file integration.
Reasons to choose it
- Visitors contact only your site when self-hosted
- Regular and bold listed
- Family page publishes the Apache 2.0 licence
What to watch
- Kit lists WOFF rather than WOFF2
- Different edition and licence from the current Google files
- Integrate CSS and replace files yourself
Font Squirrel’s Open Sans page offers regular and bold, a downloadable TTF family and a webfont-kit interface with character-range choices. Unlike the current Google and Fontsource copies described above, this page publishes the Apache 2.0 licence and credits Ascender Fonts. Follow the licence supplied with that edition; do not assume every Open Sans download contains the same files or terms. Its score is 4.40. Open Sans and licence, Font Squirrel FAQ, read November 6, 2026.
This route suits an owner who wants local files and a kit interface without a build dependency. The kit lists WOFF, TTF, EOT and SVG rather than WOFF2; use google-webfonts-helper or Fontsource if ready-made WOFF2 is the reason you are choosing. You add the files and CSS to your site and handle replacements yourself. The page does not establish that its edition matches the current upstream font. Font Squirrel also warns readers to check each family’s licence: a directory’s free-commercial-use description is not permission for every kind of embedding. We did not download or inspect a generated kit. Open Sans, FAQ, read November 6, 2026.
Used Font Squirrel Open Sans? Share your experience to help other readers choose.
Which product are we missing?
Know a product that belongs in this article? Tell us what it does differently and why it deserves a closer look. Newcomers welcome.
Readers and product teams can suggest candidates. Suggestions inform our research; they do not guarantee inclusion or a recommendation.
Opens an email draft with this article attached as a link. Nothing is sent until you send it.
No email app? Send the product name, website, and this article’s title to admin@practicalpicks.guide.
What people are saying
Public discussion is a check on vendor claims, not evidence of legal safety or speed. When Bunny Fonts launched in June 2022, several commenters on Hacker News asked why a site would move from one font host to another instead of hosting the files itself, and one argued that browsers no longer share cached fonts between sites. A July 2022 post on Birchtree argued that there is “not a real tangible privacy advantage” in switching from Google to Bunny and suggested self-hosting for anyone who wants to avoid third parties. These are opinions from 2022, before the 2023 and 2025 decisions discussed here. Launch discussion, Birchtree, July 1, 2022
Field data shows the direction of travel. The 2025 Web Almanac, published in January 2026, found Google Fonts on about 54% of desktop and 47% of mobile pages, and about a third of sites hosting all their fonts themselves; its authors attribute the shift toward self-hosting partly to performance and privacy. Fontsource’s issue tracker shows the kind of upkeep problem a package can bring, such as the 2024 Open Sans release churn described above, which the maintainer had already fixed when it was reported. Web Almanac 2025, fonts, issue 948
How we researched
This is public-source research. We did not create accounts, install packages, download fonts, build pages or contact any provider for this review, and no provider supplied access or payment. We first compared Fontsource, the Google Fonts API and Fontshare on October 1, 2026, using a small hands-on check run before we adopted our research-only method on October 3. That check is retained as dated evidence for Fontsource; the earlier Fontshare download difficulty remains a limitation. On October 19, 2026 we rechecked every package version, licence, privacy statement and term, read the German court decisions, the prosecutors’ statement and the Federal Court of Justice referral in their official texts, and re-decided the recommendation from public evidence. Google’s privacy FAQ now loads only in a full browser, so we read its July 2024 text from an archived copy of July 3, 2026. Fontshare’s licence and FAQ were read from the text its own site serves.
We wrote this for the owner or developer of a small business website with a build step who wants one font in regular and bold, free for commercial use and without an account, and who needs to take EU privacy rulings into account. Before scoring, we fixed five criteria and their weights: what visitors’ browsers send to whom, and how that stands with the German rulings and regulator guidance (30%); licence clarity and rights (20%); setup and upkeep with a bundler (20%); dependence on a provider and its terms (20%); and choice of typefaces (10%). Fontsource led self-hosted Google files by 0.10 on those weights, less than one step on our five-point scale. Giving more weight to independence from any package, and less to setup effort, puts the self-hosted files first, which is why we name them as the alternative.
On November 6, 2026 we compared the additional delivery routes named in our earlier research, and checked newer services against dated launch evidence and current documentation. The four routes above scored highest for the same small business site. Fontsource leads narrowly; giving more weight to avoiding a build dependency would favour self-hosted files. Font delivery context, read November 6, 2026.
The Google Fonts API (3.60), Bunny Fonts (3.65), coolLabs Fonts (3.65) and Fontsource through jsDelivr (3.75) offer hosted links, but still send visitors’ font requests to another provider. Bunny’s no-logs statement and coolLabs’ equivalent claim are provider statements, not audits. Bunny was affected by a domain incident on May 21, 2026. Our October 19 assessment of Google’s API also considered the Munich Regional Court’s 2022 finding against loading fonts without consent, the 2023 ruling against a deliberately provoked claim, and the Federal Court of Justice’s August 2025 referral to the EU Court of Justice. We had not established an answer by October 19; the later EU-US transfer framework does not settle the separate question of avoiding unnecessary requests. These are fact-specific German decisions, not a universal ban on hosted fonts. Bunny FAQ, coolLabs, jsDelivr terms, read November 6, 2026; Bunny incident, Munich 2022, Munich 2023, Federal Court referral, checked October 19, 2026.
Fontshare Satoshi scores 3.30. Choose it for Satoshi’s design rather than delivery flexibility: its licence allows own-site self-hosting but forbids subsetting, conversion or handing files to a contractor, and permits withdrawal of the API without notice. Whether its download kit requires an account and its privacy policy remain unverified. Font Library’s local Open Sans route scores 4.10; its page names OFL and offers regular/bold downloads, but its CSS example names another family and the downloaded formats/current edition are unclear. Mixed directory licences are a reason to check a particular family, rather than to dismiss the entire directory. Fontshare licence, Font Library Open Sans, read November 6, 2026.
Next.js next/font, Nuxt Fonts and Astro’s Fonts API each score 4.30 for this reader. They serve fonts locally and are attractive if your site already uses the corresponding framework; adopting an entire framework simply to add a font is more work than Fontsource on a generic bundler site. Their platform ownership also means a recently added font feature is not an independent newcomer. Next.js fonts, Nuxt Fonts, Astro fonts, read November 6, 2026.
OpenFont documents working public CSS routes, but its release identifier does not establish its first public release, and we could not establish a responsible named operator or inspect its processing code. Fontlay names Farid Nizam and documents its proxy, but its first public release remains unverified. We did not reject either merely for a small audience or a lack of independent reviews. Fontstack remains in private beta behind an invitation. We could not read CDNFonts’ pages or the Font Free Downloads launch document, so those candidates remain unchecked. The available discovery material does not support a newcomer recommendation. OpenFont, documentation, Fontlay, Fontstack, read November 6, 2026.
| Tool | Public sources | What remains uncertain |
|---|---|---|
| Fontsource Open Sans | Installation guide, npm registry record, package file list, changelog, repository, issue tracker, malware advisory, earlier check record (October 1, 2026). | How often updates change layout; continuity with two maintainer accounts; future changes to package structure. |
| Self-hosted Google Fonts files | Google Fonts repository and licence files, Google privacy FAQ, regulator guidance, google-webfonts-helper README, Next.js and Astro documentation. | Effort for your own build; how well a hand-made subset covers your text. |
| google-webfonts-helper | Repository documentation, format/variant examples, change history, security overview; read November 6, 2026. | Generated kit contents, deployed dependency versions and future service maintenance. |
| Font Squirrel Open Sans | Family page, Apache 2.0 text, kit options, FAQ; read November 6, 2026. | Current upstream edition and kit contents; the privacy URL returned terms instead. |
| Newer services | OpenFont documentation, Fontlay proxy page, Fontstack availability and their homepages; read November 6, 2026. | First-release dates and some operator/pricing evidence; unreadable candidates could not be cleared. |
None of this establishes page speed, rendering quality or legal compliance for a particular site. Next substantive review is due December 18, 2026, or sooner if the EU Court of Justice answers the German referral or a licence changes. Found a changed term or ruling? Contact the editors.
Sources and evidence
Incumbent sources were checked October 19, 2026 unless another date is given; the additional source pages linked in the product and research sections were read November 6, 2026. Provider pages establish documented offers and terms, not performance. Court decisions are German and fact-specific.
- Fontsource: installation guide; Open Sans page; npm package record (read through the npm registry; the web page blocks automated access); repository; changelog; issue 948, March 14, 2024; advisory GHSA-2xwx-2g4x-h7px, February 13, 2025 and OSV MAL-2025-1361, both on the unscoped
fontsourcepackage; earlier check record, October 1, 2026. - Google Fonts: repository; Open Sans licence; OFL FAQ; CSS API; API terms; privacy FAQ, last updated July 23, 2024, read from an archived copy of July 3, 2026; statement, November 18, 2022, modified March 2, 2023; google-webfonts-helper.
- Bunny Fonts: about; FAQ; Open Sans; bunny.net terms; incident, May 21, 2026.
- Fontshare: Satoshi; ITF Free Font License, version 2.0, August 17, 2026; FAQ; about.
- Courts, prosecutors and regulators: Munich Regional Court, January 20, 2022, 3 O 17493/20; Berlin police and prosecutors, release 2422, December 21, 2022; Munich Regional Court, March 30, 2023, 4 O 13063/22; Federal Court of Justice, order of August 28, 2025, VI ZR 258/24; EU General Court, T-553/23, press release of September 3, 2025; Lower Saxony data-protection authority, November 24, 2022.
- Alternatives and context: Adobe web-font licensing FAQ, November 14, 2025; Next.js fonts; Astro fonts; Modern Font Stacks; Web Almanac 2025, fonts.
- Discussion: Hacker News, Bunny Fonts launch, June 19, 2022; Birchtree, July 1, 2022.
This is a researched comparison, not a product review. Method: evidence standard, editorial picks.