diff --git a/src/content/docs/browser-rendering/platform/chromium-version.mdx b/src/content/docs/browser-rendering/platform/chromium-version.mdx
new file mode 100644
index 00000000000000..f5eb964cb3162f
--- /dev/null
+++ b/src/content/docs/browser-rendering/platform/chromium-version.mdx
@@ -0,0 +1,48 @@
+---
+pcx_content_type: reference
+title: Chromium version
+sidebar:
+  order: 7
+---
+
+import { TabItem, Tabs } from "~/components";
+
+Cloudflare Browser Rendering currently uses **Chromium version 124.0.6367.257**.
+
+Browser Rendering allows developers to programmatically control and interact with a headless browser instance and create automation flows for their applications and products. Once configured, the service provides access to a WebSocket endpoint that speaks the [DevTools Protocol](https://chromedevtools.github.io/devtools-protocol/). This protocol is what allows Cloudflare to instrument a Chromium instance running in the Cloudflare global network.
+
+If you want to programmatically confirm the version in your environment, you can retrieve it using either [Puppeteer](/browser-rendering/platform/puppeteer/) or [Playwright](/browser-rendering/platform/playwright/).
+
+<Tabs syncKey="workersExamples"> <TabItem label="Puppeteer">
+
+```javascript
+import puppeteer from "@cloudflare/puppeteer";
+
+async fetch(request, env) {
+	const browser = await puppeteer.launch(env.MYBROWSER);
+	const version = await browser.version();
+	console.log("Chromium version:", version);
+	await browser.close();
+})().catch(console.error);
+```
+
+</TabItem> <TabItem label="Playwright">
+
+```javascript
+const { chromium } = require("playwright");
+
+(async () => {
+	const browser = await chromium.launch();
+	const version = await browser.version();
+	console.log("Chromium version:", version);
+	await browser.close();
+})().catch(console.error);
+```
+
+</TabItem> </Tabs>
+
+Example output
+
+```
+Chromium version: HeadlessChrome/123.0.6312.86
+```
diff --git a/src/content/docs/browser-rendering/workers-binding-api/index.mdx b/src/content/docs/browser-rendering/workers-binding-api/index.mdx
index e90b1edc3feb37..e36a56008573aa 100644
--- a/src/content/docs/browser-rendering/workers-binding-api/index.mdx
+++ b/src/content/docs/browser-rendering/workers-binding-api/index.mdx
@@ -5,9 +5,15 @@ sidebar:
   order: 2
 ---
 
-import { DirectoryListing } from "~/components";
+import { DirectoryListing, TabItem, Tabs } from "~/components";
 
-The Workers Binding API allows you to execute advanced browser rendering scripts within Cloudflare Workers. It provides developers the flexibility to automate and control complex workflows and browser interactions. The following options are available for browser rendering tasks:
+The Workers Binding API allows you to execute advanced browser rendering scripts within [Cloudflare Workers](/workers/). It provides developers the flexibility to automate and control complex workflows and browser interactions.
+
+Browser Rendering allows developers to programmatically control and interact with a headless browser instance and create automation flows for their applications and products. Once configured, the service provides access to a WebSocket endpoint that speaks the [DevTools Protocol](https://chromedevtools.github.io/devtools-protocol/). This protocol is what allows Cloudflare to instrument a [Chromium instance](/browser-rendering/platform/chromium-version/) running in the Cloudflare global network.
+
+## Browser Rendering options
+
+The following options are available for browser rendering tasks:
 
 <DirectoryListing />