Rendering environment
The Chromium build and fonts available inside the rendering worker for website capture jobs.
Browser engine
Website capture jobs run inside a current stable Chromium release on Linux. The exact major version moves with upstream as we update workers. If you depend on a specific Chromium feature for your output, test that feature on a recent stable build before relying on it in production.
Modern CSS works the way you’d expect: Flexbox, Grid, @layer, :has(), Container Queries, variable fonts, color-mix(), nested CSS, print-color-adjust. JavaScript is full ES2024.
Installed fonts
The renderer ships with a standard system font set. You can also load any web font via @font-face (and many free fonts are available from Google Fonts).
System fonts installed:
- Andale Mono
- Arial
- Arial Black
- Comic Sans MS
- Courier New
- DejaVu Sans
- DejaVu Sans Mono
- DejaVu Serif
- Georgia
- Impact
- Lato
- Liberation Mono
- Liberation Sans
- Liberation Sans Narrow
- Liberation Serif
- Roboto
- Roboto Condensed
- Times New Roman
- Trebuchet MS
- Verdana
- Webdings
- Noto (covers most scripts)
- Takao (Japanese)
Font loading caveat
If you’re loading custom web fonts via @font-face, give Chromium time to finish loading them before snapshotting. The most reliable trigger is wait_css_selector pointing at an element that only renders after document.fonts.ready, or a CSS class your page applies once fonts have loaded. See Parameters.
Network and resources
Each render worker has:
- Outbound HTTPS to fetch the page and any subresources (images, fonts, scripts).
- ~250 MB of memory per render.
- 60-second hard timeout for the whole render.
If your page genuinely needs longer than 60 seconds to render, look at trimming heavy subresources, deferring non-essential JavaScript, or moving to a static pre-render before submitting.