Versions on the shared fleet
Our workers that service plans such as the Starter and Scale plans are updated every so often, here are the versions that the hosted version currently has for certain libraries, global timeout and CLI flags supported.
Current versions used in usage based workers
Last update: February 24, 2025.
- Puppeteer:
24.2.1 - Playwright:
1.50.1,1.49.1,1.48.2,1.47.2,1.46.1,1.45.3,1.44.1,1.43.1,1.42.1,1.41.2 - Chromium:
133.0.6943.16 - Chrome:
133.0.6943.127 - Firefox:
134.0 - Webkit:
18.2
If your code is mysteriously crashing, try using the exact version mentioned above, as some older but especially more recent versions than the above may cause conflicts.
Global timeout
By default, the global timeout is set to 15 minutes for usage-based and cloud unit-based API Keys, if you need your sessions to run longer than that, you'll want to consider upgrading to a dedicated account in order to modify this setting.
CLI flags supported
--proxy-server,
--window-size,
--disable-web-security,
--enable-features,
--disable-web-security,
--disable-setuid-sandbox,
--lang,
--font-render-hinting,
--force-color-profile,
stealth,
ignoreDefaultArgs,
headless,
token,
blockAds,
ignoreHTTPSErrors,
slowMo,
Supported browser versions on sites
Some websites require certain codecs to be supported for proper functionality. This is particularly common with streaming sites such as Twitch, Netflix, or other video platforms that rely on specific media codecs for content delivery.
When you encounter a "browser is not currently supported" message on a website, this is typically a good indicator that the site requires codecs or features that may not be available in the current browser binary you're using.
Browser binary differences
By default, Browserless uses Chromium binaries when you connect to the standard endpoint. However, you can switch to Chrome binaries by adding /chrome to your connection path, which often includes additional codec support that some sites require.
Default path (Chromium):
wss://production-sfo.browserless.io?token=YOUR_TOKEN
Chrome path (with enhanced codec support):
wss://production-sfo.browserless.io/chrome?token=YOUR_TOKEN
When to use Chrome binaries
Consider switching to the Chrome binary path when:
- You see "browser not currently supported" error messages
- Working with streaming platforms (Twitch, YouTube, Netflix, etc.)
- Sites that require proprietary codecs
- Video conferencing platforms that need specific media capabilities
The Chrome binaries typically include additional proprietary codecs and features that may be required by certain websites, especially those dealing with media streaming and playback.
Playwright's versioning
It is important to note that Playwright's connect method is tightly version-coupled. Your client version must be either one of the ones listed above.
Playwright's connectOverCDP doesn't always need to match the same playwright version on our usage based workers. This method is generally backwards/forwards compatible since it communicates directly through CDP, with the caveat to be slightly slower due to having more communication over the devtools protocol.