---
title: "Chromium Renderer · Nuxt OG Image · Nuxt SEO"
canonical_url: "https://nuxtseo.com/docs/og-image/v5/guides/chromium"
last_updated: "2026-08-16T10:00:27.731Z"
meta:
  description: "Learn how, when and why to use the Chromium renderer."
  "og:description": "Learn how, when and why to use the Chromium renderer."
  "og:title": "Chromium Renderer · Nuxt OG Image · Nuxt SEO"
---

Nuxt SEO on GitHub

You're viewing **OG Image v5** documentation. For the latest, [~~switch to v6~~](https://nuxtseo.com/docs/og-image/getting-started/introduction).

](https://nuxtseo.com/docs/og-image/v5/getting-started/introduction)

](https://nuxtseo.com/docs/og-image/v5/api/define-og-image)

](https://nuxtseo.com/docs/og-image/v5/releases/v5)

Switch to OG Image](https://nuxtseo.com/docs/og-image/getting-started/introduction)Switch to Nuxt SEO](https://nuxtseo.com/docs/nuxt-seo/getting-started/introduction)Switch to Robots](https://nuxtseo.com/docs/robots/getting-started/introduction)Switch to Sitemap](https://nuxtseo.com/docs/sitemap/getting-started/introduction)Switch to Schema.org](https://nuxtseo.com/docs/schema-org/getting-started/introduction)Switch to Link Checker](https://nuxtseo.com/docs/link-checker/getting-started/introduction)Switch to SEO Utils](https://nuxtseo.com/docs/seo-utils/getting-started/introduction)Switch to Site Config](https://nuxtseo.com/docs/site-config/getting-started/introduction)Switch to Skew Protection](https://nuxtseo.com/docs/skew-protection/getting-started/introduction)Switch to AI Ready](https://nuxtseo.com/docs/ai-ready/getting-started/introduction)

**Core Concepts**

# **Chromium Renderer**

Nuxt OG Image comes with two ways of rendering your images, the non-default way is using Chromium to take screenshots.

Using Chromium is only recommended when you are prerendering all of your images.

```ts
export default defineNuxtConfig({
  // sets the default renderer to chromium
  ogImage: {
    defaults: {
      renderer: 'chromium'
    }
  }
})
```

## Pros

- Much easier to create complex designs
- Render JPEGs without using `**sharp**`
- Page screenshots are simple and saves time

## Cons

- Requires a Chromium binary to be installed
- Much slower than Satori, using it at runtime is not recommended
- Doesn't work on most hosting providers

## Development Chromium

When running in a development environment, a local Chrome / Chromium binary will be used, if available.

If it's not, then the Chromium renderer will be disabled.

## Prerenderer / CI Chromium

When prerendering your images in a CI environment, the module will automatically install a Chromium binary for you.

If you'd like to opt-out of this, you should disable the binding.

nuxt.config.ts

```ts
export default defineNuxtConfig({
  ogImage: {
    compatibility: {
      prerender: {
        chromium: false
      }
    }
  }
})
```

## Runtime Chromium

Chromium will only be enabled by default in runtime environments if you have explicitly included the `**playwright**` dependency in your project and the target environment is compatible.

```sh
pnpm i -D playwright
```

Check the [**~~compatibility~~**](https://nuxtseo.com/docs/og-image/guides/compatibility) guide for more information.

**Was this page helpful?**

[**Satori Renderer** Learn how to use the Satori renderer.](https://nuxtseo.com/docs/og-image/v5/guides/satori) [**Zero Runtime** Create OG Images without the server runtime overhead.](https://nuxtseo.com/docs/og-image/v5/guides/zero-runtime)