Skip to content

🎥 Make videos programmatically with React

Docs: Specify the Chromium 157.0.8080.0 build

Jonny Burgeradbfa40c1124
diff --git a/.agents/skills/canvas-capture-extension/SKILL.md b/.agents/skills/canvas-capture-extension/SKILL.md
index 85dec9e94f..350309d83d 100644
--- a/.agents/skills/canvas-capture-extension/SKILL.md
+++ b/.agents/skills/canvas-capture-extension/SKILL.md
@@ -23,7 +23,7 @@ the unpacked copy outside the checkout so deleting a worktree cannot break it.
The script builds with Bun and installs the complete WXT bundle in
`/Users/jonathanburger/Applications/Remotion Canvas Capture Extension`.
Building does not require an installed browser. To use the extension, choose
- Chrome 157 or newer with Canvas Draw Element enabled. If no compatible browser
+ Chrome with major version 157 or newer with Canvas Draw Element enabled. If no compatible browser
is installed, use `$install-canvas-capture-browser` to install one.
3. Confirm that the installed directory contains `manifest.json`,
@@ -45,14 +45,14 @@ the unpacked copy outside the checkout so deleting a worktree cannot break it.
Use the separate development directory only for `bun run dev`. Continue using
the production install directory above for manually loaded builds.
-To select another Chrome 157 or newer browser, set
+To select another Chrome with major version 157 or newer browser, set
`CANVAS_CAPTURE_BROWSER_EXECUTABLE` to its executable path when running
`bun run dev`. Development uses the version-neutral
`~/Library/Application Support/Remotion Canvas Capture` profile.
## Reload in Chrome
-- Launch Chrome 157 or newer with the
+- Launch Chrome with major version 157 or newer with the
dedicated Canvas Capture profile, then open `chrome://extensions` manually.
- Enable **Developer mode** on `chrome://extensions`.
- If **Remotion Canvas Capture** already points to the durable directory, click
diff --git a/.agents/skills/canvas-capture-extension/scripts/rebuild-extension.sh b/.agents/skills/canvas-capture-extension/scripts/rebuild-extension.sh
index 92c436e81f..f4efdfe5dc 100755
--- a/.agents/skills/canvas-capture-extension/scripts/rebuild-extension.sh
+++ b/.agents/skills/canvas-capture-extension/scripts/rebuild-extension.sh
@@ -72,5 +72,5 @@ mkdir -p "$install_dir"
rsync -a --delete "$dist_dir/" "$install_dir/"
printf 'Installed Remotion Canvas Capture in %s\n' "$install_dir"
-printf '%s\n' 'Canvas Capture requires Chrome 157 or newer with Canvas Draw Element enabled.'
+printf '%s\n' 'Canvas Capture requires Chrome with major version 157 or newer with Canvas Draw Element enabled.'
printf '%s\n' 'Open chrome://extensions manually, then click Reload or choose Load unpacked for this directory.'
diff --git a/.agents/skills/install-canvas-capture-browser/SKILL.md b/.agents/skills/install-canvas-capture-browser/SKILL.md
index 7e54d91211..c2aeb8c8e5 100644
--- a/.agents/skills/install-canvas-capture-browser/SKILL.md
+++ b/.agents/skills/install-canvas-capture-browser/SKILL.md
@@ -1,11 +1,11 @@
---
name: install-canvas-capture-browser
-description: Install and verify Chrome for Testing 157 or newer for the private Remotion Canvas Capture extension on Apple Silicon macOS. Use when setting up Canvas Capture or when no compatible Chrome browser is installed.
+description: Install and verify Chrome for Testing with major version 157 or newer for the private Remotion Canvas Capture extension on Apple Silicon macOS. Use when setting up Canvas Capture or when no compatible Chrome browser is installed.
---
# Install Canvas Capture Browser
-Canvas Capture requires Chrome 157 or newer with Canvas Draw Element enabled.
+Canvas Capture requires Chrome with major version 157 or newer with Canvas Draw Element enabled.
Use an existing compatible Chrome browser, or install Chrome for Testing with
the bundled script. The extension also checks the required HTML-in-canvas API
and video encoding configuration before allowing recording.
@@ -22,10 +22,10 @@ and video encoding configuration before allowing recording.
Stable, Beta, Dev, or Canary release from Google's Chrome for Testing metadata,
verifies that the downloaded app matches that release, and
installs the app at `/Users/jonathanburger/Applications/Recorder Chrome.app`.
- It exits successfully without downloading when version 157 or newer is
+ It exits successfully without downloading when the major version is 157 or newer and the browser is
already installed. It does not overwrite an incompatible existing app.
-2. Confirm the script reports the expected installed path and a version of at least 157.
+2. Confirm the script reports the expected installed path and a major version of at least 157.
3. Launch it for Canvas Capture with:
diff --git a/.agents/skills/install-canvas-capture-browser/agents/openai.yaml b/.agents/skills/install-canvas-capture-browser/agents/openai.yaml
index 87f88f1c0f..1c1accb28e 100644
--- a/.agents/skills/install-canvas-capture-browser/agents/openai.yaml
+++ b/.agents/skills/install-canvas-capture-browser/agents/openai.yaml
@@ -1,4 +1,4 @@
interface:
display_name: 'Install Canvas Capture Browser'
- short_description: 'Install Chrome 157 or newer for Canvas Capture'
- default_prompt: 'Use $install-canvas-capture-browser to install Chrome for Testing 157 or newer for Canvas Capture.'
+ short_description: 'Install Chrome with major version 157 or newer for Canvas Capture'
+ default_prompt: 'Use $install-canvas-capture-browser to install Chrome for Testing with major version 157 or newer for Canvas Capture.'
diff --git a/packages/canvas-capture-extension/README.md b/packages/canvas-capture-extension/README.md
index 8422dda435..32e9892743 100644
--- a/packages/canvas-capture-extension/README.md
+++ b/packages/canvas-capture-extension/README.md
@@ -4,7 +4,7 @@ Record an area—or a whole webpage—as a high-resolution H.264 MP4 or VP9 WebM
## Browser setup on macOS
-Canvas Capture requires Chrome 157 or newer on Apple Silicon, with Canvas Draw Element enabled. You can use Chrome, Chrome Canary, or Chrome for Testing as long as the browser meets this minimum. The extension also checks whether the HTML-in-canvas API and video encoding configuration are available before recording.
+Canvas Capture requires Chrome with major version 157 or newer on Apple Silicon, with Canvas Draw Element enabled. You can use Chrome, Chrome Canary, or Chrome for Testing as long as the browser meets this minimum. The extension also checks whether the HTML-in-canvas API and video encoding configuration are available before recording.
To install a compatible Chrome for Testing build, run:
@@ -50,7 +50,7 @@ WXT starts Vite, writes the development extension to the durable
directory, launches Chrome for Testing with the required feature
flags and persistent profile, and loads the extension automatically.
-To use another Chrome 157 or newer executable, set
+To use another Chrome with major version 157 or newer executable, set
`CANVAS_CAPTURE_BROWSER_EXECUTABLE` when starting development:
```bash
@@ -67,7 +67,7 @@ extension, so its path and extension ID remain stable across worktrees.
## Build and install
1. From the repository root, run `.agents/skills/canvas-capture-extension/scripts/rebuild-extension.sh --repo "$PWD"`. This creates the production WXT bundle and installs the complete unpacked extension outside the worktree. Building does not require an installed browser.
-2. In Chrome 157 or newer, open `chrome://extensions`, enable **Developer mode**, and choose **Load unpacked**.
+2. In Chrome with major version 157 or newer, open `chrome://extensions`, enable **Developer mode**, and choose **Load unpacked**.
3. Select `/Users/jonathanburger/Applications/Remotion Canvas Capture Extension`.
4. Enable `chrome://flags/#canvas-draw-element` and restart Chrome if HTML-in-canvas is not already enabled.
diff --git a/packages/canvas-capture-extension/README.public.md b/packages/canvas-capture-extension/README.public.md
index 10fb6bf624..5fb4515628 100644
--- a/packages/canvas-capture-extension/README.public.md
+++ b/packages/canvas-capture-extension/README.public.md
@@ -6,7 +6,7 @@ HTML-in-canvas implementation.
## Install
-Canvas Capture requires Chrome 157 or newer with Canvas Draw Element enabled on an Apple Silicon Mac.
+Canvas Capture requires Chrome with major version 157 or newer with Canvas Draw Element enabled on an Apple Silicon Mac.
Follow the [Canvas Capture installation guide](https://www.remotion.dev/docs/canvas-capture/installation).
diff --git a/packages/docs/docs/canvas-capture/installation.mdx b/packages/docs/docs/canvas-capture/installation.mdx
index abcb9aaab5..85f32f37b7 100644
--- a/packages/docs/docs/canvas-capture/installation.mdx
+++ b/packages/docs/docs/canvas-capture/installation.mdx
@@ -8,7 +8,7 @@ sidebar_label: Installation
> Tip: Copy the URL of this page into an agent to let it install it for you.
-Canvas Capture requires an Apple Silicon Mac and Chrome 157 or newer with Canvas Draw Element enabled.
+Canvas Capture requires an Apple Silicon Mac and Chrome with major version 157 or newer with Canvas Draw Element enabled.
## Download the extension
@@ -23,7 +23,7 @@ The repository contains a production build of Canvas Capture. You do not need to
## Choose a browser
-Use Chrome, Chrome Canary, or Chrome for Testing version 157 or newer. Check your version at `chrome://version`.
+Use Chrome, Chrome Canary, or Chrome for Testing with major version 157 or newer. Check your version at `chrome://version`.
If you need a compatible browser, install Chrome for Testing using the script included with Canvas Capture. The installer selects a release that meets the minimum version:
diff --git a/packages/docs/docs/client-side-rendering/html-in-canvas.mdx b/packages/docs/docs/client-side-rendering/html-in-canvas.mdx
index 4f6d855605..d7371fa4f5 100644
--- a/packages/docs/docs/client-side-rendering/html-in-canvas.mdx
+++ b/packages/docs/docs/client-side-rendering/html-in-canvas.mdx
@@ -17,7 +17,7 @@ On supported Chromium-based browsers, [`@remotion/web-renderer`](/docs/web-rende
Use a recent version of Google Chrome or another Chromium-based browser with `chrome://flags/#canvas-draw-element` enabled. Current Chrome stable releases ship `canvas.requestPaint()` together with [`drawElementImage`](https://github.com/WICG/html-in-canvas#2-drawelementimage-and-webglwebgpu-equivalents), which is required for correct frame capture. See [Compatibility](#compatibility) for details.
:::
-Enabling the option does not guarantee that this path runs. If the browser does not have HTML-in-canvas enabled, or if the composition contains an [`<HtmlInCanvas>`](/docs/remotion/html-in-canvas) in Chrome earlier than 157, it falls back to the [default frame capturing mechanism](/docs/client-side-rendering/how-it-works).
+Enabling the option does not guarantee that this path runs. If the browser does not have HTML-in-canvas enabled, or if the composition contains an [`<HtmlInCanvas>`](/docs/remotion/html-in-canvas) in Chrome with a major version earlier than 157, it falls back to the [default frame capturing mechanism](/docs/client-side-rendering/how-it-works).
## Enabling
@@ -67,7 +67,7 @@ If native capture starts but fails while capturing a frame, a warning is printed
Not using HTML-in-canvas: drawElementImage failed (...); falling back to the built-in DOM composer.
```
-If HTML-in-canvas is unavailable, disabled, or would require a nested capture in Chrome earlier than 157, the built-in DOM composer is selected.
+If HTML-in-canvas is unavailable, disabled, or would require a nested capture in Chrome with a major version earlier than 157, the built-in DOM composer is selected.
## Compatibility
@@ -87,9 +87,9 @@ If HTML-in-canvas is unavailable, disabled, or would require a nested capture in
HTML-in-canvas depends on Chromium flag `chrome://flags/#canvas-draw-element`, which must be enabled explicitly.
-Use a recent Chrome or Chromium version with the flag enabled for full support. Compositions containing [`<HtmlInCanvas>`](/docs/remotion/html-in-canvas) use native capture in Chrome 157 or newer. Earlier versions use the built-in DOM composer.
+Use a recent Chrome or Chromium version with the flag enabled for full support. Compositions containing [`<HtmlInCanvas>`](/docs/remotion/html-in-canvas) use native capture in Chrome with major version 157 or newer. Earlier versions use the built-in DOM composer.
-Server-side rendering also supports nested `<HtmlInCanvas>` compositions from Remotion <AvailableFrom v="4.0.534" inline />, which bundles Chromium 157. See [nested HTML-in-canvas](/docs/html-in-canvas#nested-html-in-canvas).
+Server-side rendering also supports nested `<HtmlInCanvas>` compositions from Remotion <AvailableFrom v="4.0.534" inline />, which bundles Chromium 157.0.8080.0. See [nested HTML-in-canvas](/docs/html-in-canvas#nested-html-in-canvas).
## See also
diff --git a/packages/docs/docs/client-side-rendering/limitations.mdx b/packages/docs/docs/client-side-rendering/limitations.mdx
index d46564587d..cdfa30eb2b 100644
--- a/packages/docs/docs/client-side-rendering/limitations.mdx
+++ b/packages/docs/docs/client-side-rendering/limitations.mdx
@@ -130,7 +130,7 @@ The [`<Audio>`](/docs/media/audio) from `@remotion/media` is <a style={{color: '
[`<ThreeCanvas>`](/docs/three-canvas) from [`@remotion/three`](/docs/three) is <a style={{color: 'green'}}>supported</a>.
[`<SkiaCanvas>`](/docs/skia/skia-canvas) from [`@remotion/skia`](/docs/skia) is <a style={{color: 'green'}}>supported</a>.
[`<AnimatedImage>`](/docs/animatedimage) is <a style={{color: 'green'}}>supported</a> when rendering in Chrome.
-[`<HtmlInCanvas>`](/docs/remotion/html-in-canvas) is <a style={{color: 'green'}}>supported</a> when the component itself is supported, including its [`onPaint`](/docs/remotion/html-in-canvas#onpaint) and [`onInit`](/docs/remotion/html-in-canvas#oninit) callbacks. The optional [HTML-in-canvas capture mode](/docs/client-side-rendering/html-in-canvas) supports nested capture in Chrome 157 or newer and falls back to the built-in DOM composer in older versions.<br />
+[`<HtmlInCanvas>`](/docs/remotion/html-in-canvas) is <a style={{color: 'green'}}>supported</a> when the component itself is supported, including its [`onPaint`](/docs/remotion/html-in-canvas#onpaint) and [`onInit`](/docs/remotion/html-in-canvas#oninit) callbacks. The optional [HTML-in-canvas capture mode](/docs/client-side-rendering/html-in-canvas) supports nested capture in Chrome with major version 157 or newer and falls back to the built-in DOM composer in older versions.<br />
[`<OffthreadVideo>`](/docs/offthreadvideo) is <a style={{color: 'red'}}>not supported</a>.
→ Use [`<Video>`](/docs/media/video) instead.
[`<Html5Video>`](/docs/html5-video) is <a style={{color: 'red'}}>not supported</a>.
diff --git a/packages/docs/docs/html-in-canvas-guide.mdx b/packages/docs/docs/html-in-canvas-guide.mdx
index 533f54c758..5e1b44fc19 100644
--- a/packages/docs/docs/html-in-canvas-guide.mdx
+++ b/packages/docs/docs/html-in-canvas-guide.mdx
@@ -100,7 +100,7 @@ You can also build your own — see [Making a custom HTML-in-canvas presentation
HTML-in-canvas is only available in Chrome 149 and later with the `chrome://flags/#canvas-draw-element` flag enabled.
The API is unstable - Chrome may change the API or even remove it in the future.
-Nesting [`<HtmlInCanvas>`](/docs/remotion/html-in-canvas) components requires Chrome 157 or newer with HTML-in-canvas enabled. See [Nested HTML-in-canvas](#nested-html-in-canvas).
+Nesting [`<HtmlInCanvas>`](/docs/remotion/html-in-canvas) components requires Chrome with major version 157 or newer with HTML-in-canvas enabled. See [Nested HTML-in-canvas](#nested-html-in-canvas).
## Rendering
@@ -108,7 +108,7 @@ From [`v4.0.455`](https://github.com/remotion-dev/remotion/releases/tag/v4.0.455
We compiled a version of Chrome and made it the default, and enabled the flag for you.
-Nested `<HtmlInCanvas>` components are supported during server-side rendering from Remotion <AvailableFrom v="4.0.534" inline />, which uses Chromium 157.
+Nested `<HtmlInCanvas>` components are supported during server-side rendering from Remotion <AvailableFrom v="4.0.534" inline />, which uses Chromium 157.0.8080.0.
If your effect uses a WebGL shader, pass [`--gl=angle`](/docs/gl-options) to make the render work:
@@ -140,11 +140,11 @@ npx skills add remotion-dev/skills
Not directly related, but [`@remotion/web-renderer`](/docs/client-side-rendering/html-in-canvas) can also use this technology to capture frames.
-This is opt-in. In Chrome versions earlier than 157, compositions containing [`<HtmlInCanvas>`](/docs/remotion/html-in-canvas) use the built-in DOM composer because native capture would create a nested HTML-in-canvas subtree.
+This is opt-in. In Chrome versions with a major version earlier than 157, compositions containing [`<HtmlInCanvas>`](/docs/remotion/html-in-canvas) use the built-in DOM composer because native capture would create a nested HTML-in-canvas subtree.
## Nested HTML-in-canvas
-Nesting `<HtmlInCanvas>` components is supported in Chrome 157 or newer with HTML-in-canvas enabled. Use [`HtmlInCanvas.isNestingSupported()`](/docs/remotion/html-in-canvas#htmlincanvasisnestingsupported) to check at runtime. Older versions throw an error. Server-side rendering supports nesting from Remotion <AvailableFrom v="4.0.534" inline />.
+Nesting `<HtmlInCanvas>` components is supported in Chrome with major version 157 or newer with HTML-in-canvas enabled. Use [`HtmlInCanvas.isNestingSupported()`](/docs/remotion/html-in-canvas#htmlincanvasisnestingsupported) to check at runtime. Older versions throw an error. Server-side rendering supports nesting from Remotion <AvailableFrom v="4.0.534" inline />.
## See also
diff --git a/packages/docs/docs/motion-blur/html-in-canvas-motion-blur.mdx b/packages/docs/docs/motion-blur/html-in-canvas-motion-blur.mdx
index 8f01e04e65..2c8155bb1c 100644
--- a/packages/docs/docs/motion-blur/html-in-canvas-motion-blur.mdx
+++ b/packages/docs/docs/motion-blur/html-in-canvas-motion-blur.mdx
@@ -109,9 +109,9 @@ Samples outside the composition are clamped to its first or last frame.
## Nested HTML-in-canvas caveat
-Children of `<HtmlInCanvasMotionBlur>` can contain another [`<HtmlInCanvas>`](/docs/remotion/html-in-canvas) component, or vice versa, in Chrome 157 or newer with HTML-in-canvas enabled. Check [`HtmlInCanvas.isNestingSupported()`](/docs/remotion/html-in-canvas#htmlincanvasisnestingsupported) before nesting them.
+Children of `<HtmlInCanvasMotionBlur>` can contain another [`<HtmlInCanvas>`](/docs/remotion/html-in-canvas) component, or vice versa, in Chrome with major version 157 or newer with HTML-in-canvas enabled. Check [`HtmlInCanvas.isNestingSupported()`](/docs/remotion/html-in-canvas#htmlincanvasisnestingsupported) before nesting them.
-Server-side rendering supports nesting from Remotion <AvailableFrom v="4.0.534" inline />, which uses Chromium 157.
+Server-side rendering supports nesting from Remotion <AvailableFrom v="4.0.534" inline />, which uses Chromium 157.0.8080.0.
## Compatibility
diff --git a/packages/docs/docs/remotion/html-in-canvas.mdx b/packages/docs/docs/remotion/html-in-canvas.mdx
index 1e5672f917..83cf716466 100644
--- a/packages/docs/docs/remotion/html-in-canvas.mdx
+++ b/packages/docs/docs/remotion/html-in-canvas.mdx
@@ -46,9 +46,9 @@ if (HtmlInCanvas.isSupported()) {
Return value: _boolean_
-Returns `true` when HTML-in-canvas is enabled in Chrome or a Chromium-based browser version 157 or newer. Use it before nesting `<HtmlInCanvas>` components. Older versions throw an error when components are nested.
+Returns `true` when HTML-in-canvas is enabled in Chrome or a Chromium-based browser with major version 157 or newer. Use it before nesting `<HtmlInCanvas>` components. Older versions throw an error when components are nested.
-From Remotion <AvailableFrom v="4.0.534" inline />, the bundled server-side browser is Chromium 157, so this method also returns `true` during server-side rendering.
+From Remotion <AvailableFrom v="4.0.534" inline />, the bundled server-side browser is Chromium 157.0.8080.0, so this method also returns `true` during server-side rendering.
## Using WebGL and WebGPU during renders
@@ -848,9 +848,9 @@ const onPaint: HtmlInCanvasOnPaint = async ({canvas, elementImage}) => {
## Nested HTML-in-canvas
-You can nest `<HtmlInCanvas>` components in Chrome 157 or newer when HTML-in-canvas is enabled. Check [`HtmlInCanvas.isNestingSupported()`](#htmlincanvasisnestingsupported) before rendering nested components. In older versions, nesting throws an error.
+You can nest `<HtmlInCanvas>` components in Chrome with major version 157 or newer when HTML-in-canvas is enabled. Check [`HtmlInCanvas.isNestingSupported()`](#htmlincanvasisnestingsupported) before rendering nested components. In older versions, nesting throws an error.
-Server-side rendering supports nested compositions from Remotion <AvailableFrom v="4.0.534" inline />, which uses Chromium 157.
+Server-side rendering supports nested compositions from Remotion <AvailableFrom v="4.0.534" inline />, which uses Chromium 157.0.8080.0.
## Compatibility
diff --git a/packages/docs/docs/shared-memory-capture.mdx b/packages/docs/docs/shared-memory-capture.mdx
index 7d89fecdda..78e5f2f13b 100644
--- a/packages/docs/docs/shared-memory-capture.mdx
+++ b/packages/docs/docs/shared-memory-capture.mdx
@@ -10,7 +10,7 @@ Traditionally, screenshots of webpages are captured using the [Chrome DevTools P
Encoding these images is pure overhead, since FFmpeg later decodes them back into bitmaps. JPEG compression can also reduce image quality.
-From v4.0.534, Remotion uses a special version of Chromium to optimize rendering in some cases. Instead of compressing each image, the bitmap is shared directly with Remotion's FFmpeg binary, which encodes it into a video.
+From v4.0.534, Remotion uses a special build of Chromium 157.0.8080.0 to optimize rendering in some cases. Instead of compressing each image, the bitmap is shared directly with Remotion's FFmpeg binary, which encodes it into a video.
## When it is used