The WAYSCloud Fonts /css2 surface mirrors the Google Fonts CSS2 API where it matters for day-to-day use. In most projects the migration is a hostname change.

Start by inspecting your site

Not sure which fonts your site actually loads? Paste your URL into Inspect a site — it’ll show which families and weights are in use, which are available on WAYSCloud Fonts, and a ready-to-paste replacement snippet.

The simple case

Before:

<link
  href="https://fonts.googleapis.com/css2?family=Inter:wght@400;700&display=swap"
  rel="stylesheet"
/>

After:

<link
  href="https://fonts.wayscloud.eu/css2?family=Inter:wght@400;700&display=swap"
  rel="stylesheet"
/>

That’s it for most sites.

Supported parameters

• family=Inter:wght@400;700 — family name and weights
• family=Inter:ital,wght@0,400;1,400 — include italic
• display=swap — font-display behavior
• subset=latin,latin-ext — explicit subset filtering (when upstream subsets are available)

Parameters NOT supported

• text=... — text-subset generation is not available in v1
• effect=... — text effects are not supported and will not be

If your Google Fonts URL uses unsupported parameters, the CSS response will either omit them or return an error. Request surfaces supported upstream typically work; effect-based URLs need manual conversion.

What stays the same

• @font-face CSS output shape is compatible
• font-family declarations in your CSS need no changes
• font-display: swap behavior is identical

What is different

• No tracking. WAYSCloud does not log your visitors’ IP, User-Agent, or Referer at the edge.
• EU-resident delivery. All requests are served from European infrastructure.
• Font selection is curated. Only redistributable fonts are available. If a specific Google Fonts family isn’t on our catalog, it either wasn’t selected for v1 or its license doesn’t permit our redistribution model.