Skip to main content

Image Versions and Upgrades

This page covers how to check your current image version, match client library versions, and coordinate upgrades.

Checking Your Current Version​

Your current image version is shown in the dashboard under your cluster settings. Hover over the version label for full details. If a newer version is available, the dashboard displays a notification.

Why Versions Matter​

The image version determines:

  • The bundled Chromium binary (used by both Puppeteer and Playwright)
  • Continuous improvements: each version brings performance gains, stability fixes, and expanded dashboard visibility

Matching Client Library Versions​

Both Puppeteer and Playwright connect to the same Chromium binary bundled with your image. For best compatibility, match your client-side library version to what the image bundles.

The dashboard shows the Puppeteer version for your current image. For example, an image tagged enterprise:2.5.0_chromium-124.0.6367.29_firefox-124.0_webkit-17.4 displays as Puppeteer v22.6.4 in the dashboard. Use that version in your project: npm install puppeteer@22.6.4. Mismatched versions can cause connection failures, unexpected behavior, or protocol errors.

Contact Browserless support if you need the exact library version for your current image.

Upgrade Process​

Coordinate upgrades with Browserless support. The general process:

  1. Request a test environment from Browserless, with a separate API key pointing to a worker running the newer image (same machine profile as your production fleet).
  2. Run your integration tests against the test environment. Verify that connection URLs work, that your launch parameters are compatible, and that screenshots and PDFs render correctly.
  3. Coordinate production upgrade with Browserless. The production fleet is updated via a Relaunch onto new workers running the newer image. IP addresses will change. Update any firewall allowlists after the upgrade.