Fonts

Press.js Cloud renderers run headless Chromium on Linux. Linux distributions ship different system fonts than macOS or Windows do. While some open-source fonts are present on Cloud instances, you should never rely on system fonts — their availability is not guaranteed and may change across renderer updates.

For general font handling — how to declare @font-face, best practices, and how @press-js/fonts audits your document — see the Press.js Fonts guide.

Self-host your fonts for Cloud

Every font your document uses must be declared with a @font-face rule pointing to a font file bundled with your deploy. When you deploy, the font file travels with your artifacts and is always available — regardless of what is or isn’t installed on the underlying OS.

See Press.js Fonts for @font-face usage and best practices.

Free plan: no external network access

Free plan renderers have no external network access. Fonts loaded from Google Fonts, Adobe Fonts, or any other CDN will fail to load. You must bundle all font files within your deploy.

Paid plans (Starter and above) do have external network access, but self-hosting is still recommended — CDN fonts add a network dependency to your render, increasing latency and introducing a failure mode you can eliminate entirely.

Font audit on Cloud

The @press-js/fonts audit runs during Cloud rendering as it does in Preview. Audit errors (such as missing font assets) cause the render job to fail. Audit warnings (unmanaged font families, etc.) appear in the render output metadata but do not block the render.

Managed fonts (planned)

We are building a managed font library for Press.js Cloud. A curated set of popular open-source fonts will be served from optimized infrastructure with low-level optimizations and a fast network path — no need to bundle them in your deploy.

Details will be published when the feature launches.