---
title: "next/font/google without subsets (perf/font-subsets)"
description: "With preload on (the default), Next.js fails the build when no subsets are given: it can't know which subset files to preload."
url: http://localhost:4173/rules/perf/font-subsets
updated: 2026-11-11
---

# next/font/google without subsets

> `perf/font-subsets` is a vetd rule. It flags: next/font/google without subsets. It runs on every `check`, together with the TypeScript check.

| Fact | Value |
| --- | --- |
| Rule id | `perf/font-subsets` |
| Severity | error |
| Group | Performance: fonts, images, scripts and bundle |
| Tags | nextjs-16, correctness, performance |

## Why it matters

With preload on (the default), Next.js fails the build when no subsets are given: it can't know which subset files to preload.

## How to fix it

Add subsets: ["latin"] (the subsets your text uses), or preload: false.

## Credit

Based on work by:

- [Next.js team](https://nextjs.org): next/font/google needs a subset list so it knows which font files to preload; the build fails without one.

## References

- [Font Module](https://nextjs.org/docs/app/api-reference/components/font), Next.js
- [Font Optimization](https://nextjs.org/docs/app/getting-started/fonts), Next.js

## See it

Demos in the vetd Lab:

- [Load fonts with next/font](http://localhost:4173/lab/nextjs/next-font)

## Related rules

- [`perf/font-module-scope`](http://localhost:4173/rules/perf/font-module-scope.md)
- [`perf/font-weights`](http://localhost:4173/rules/perf/font-weights.md)

## Get this text from vetd

MCP: call `explain` with `{ "diagnosticId": "perf/font-subsets" }`. CLI: `npx vetd explain perf/font-subsets`.

---

[All 92 rules](http://localhost:4173/rules.md) · Previous: [`perf/font-format`](http://localhost:4173/rules/perf/font-format.md) · Next: [`perf/font-module-scope`](http://localhost:4173/rules/perf/font-module-scope.md)