Choose Google Font families and weights to generate @font-face CSS, a WOFF2 file list, and a download script. Upload the files to serve those fonts from your own host.
Serving fonts from fonts.gstatic.com requires the browser to contact Google. Hosting those font files yourself lets the browser request them from your host instead.
Serving font files from your own host can reduce external connections and gives you control over their cache settings. Test loading on the finished pages to assess the effect.
Foundry hits Google's real css2 endpoint with a modern-browser UA, gets the exact WOFF2 blocks, and rewrites the URLs to your self-host path — preserving weights, styles, and unicode-range subsets. No hand-editing CSS.
Search a family, tick the weights, and see it rendered in the actual font before you commit — headings, body, and italics side by side. Pick what you'll really use so you ship fewer bytes and a sharper page.
Along with the CSS, Foundry hands you the list of WOFF2 files and a copy-paste bash/curl script. Run the script to create a /fonts folder, then upload it to your host.
Not sure what goes with what? The paid pairing engine ships 42 hand-picked heading + body combinations — each with a category, a mood, and the rationale — so you can start from a pairing that already works instead of guessing.
Type a Google Font family — Inter, Fraunces, Space Grotesk — tick the weights you need, add italics, and choose your font-display.
It requests font CSS from Google's css2 endpoint and rewrites matching fonts.gstatic.com font URLs to your chosen self-host path. Download and upload the listed files to complete the setup.
Grab the WOFF2 file list, or run the generated curl script. Filenames carry the weight and subset — inter-400-latin.woff2 — so nothing collides.
Paste the @font-face CSS, upload the /fonts folder, and delete the old Google <link>. Now the browser fetches type from your origin — zero Google calls.
The free generator provides CSS and downloads for single families. Pairing data is license-gated; variable-font controls, subsetting hints, multi-family bundles, custom upload, and edge hosting are planned.
In v1, Foundry generates the @font-face CSS, file list, and download script. Upload the /fonts folder to your own host. Edge hosting is planned and is not included in the current workflow.
Hosting the files yourself changes where font requests go. Privacy: browsers normally contact fonts.gstatic.com for Google-hosted font files. Self-hosted files are requested from your host instead. Performance: serving fonts from your own origin can reduce external connections. Test the finished pages to assess the result.
It requests Google's modern css2 endpoint with a current-browser User-Agent, which returns ready-made WOFF2 @font-face blocks. Foundry rewrites those fonts.gstatic.com URLs to your chosen self-host path and names each file by family, weight, and subset — preserving unicode-range so subsets never collide. The output is guaranteed to contain zero gstatic references.
Yes. The whole self-host workflow for single families — search, specimen preview, CSS output, download script, and the optional fonts.js loader embed — is free, no card required. Pairing data is license-gated. Variable-font controls, subsetting hints, multi-family bundles, custom upload, and edge hosting are planned and are not included in the current workflow.
If you'd rather not paste CSS, drop one <script> tag with a data-families attribute and the loader injects the self-hosted @font-face CSS for you. It still points at self-hosted woff2 paths — it does not proxy Google's binaries — so you self-host the files; the loader just saves you the copy-paste. See the embed docs for the full syntax.
Depends on the plan: Single = 1 domain, Agency = 10, Unlimited = unlimited. The free generator itself is open to anyone — a license unlocks the paid features. Domains bind automatically the first time a key verifies, and an invalid or expired key silently degrades to the free tier rather than breaking your page.