Does Playwright run on Ubuntu 26.04 LTS yet

Ubuntu 26.04 LTS has been out since April 2026. If you’re running a fleet of headless browsers for AI agents on 24.04 or 22.04 boxes right now, the pull to jump onto the new long-term-support release is obvious: newer kernel, newer glibc, five more years of security patches on the clock. But there’s a gap between “Canonical shipped a new LTS” and “Playwright has validated it,” and that exact gap is what’s being asked in a still-open GitHub issue on the Playwright repo, issue #40117, which is close to word-for-word this post’s title.

Here’s the direct answer, since that’s what the issue is actually asking. Going by the pattern of the last two LTS cycles, where it took Microsoft’s Playwright team a few months past each Ubuntu release to validate the new base and add it to the docs, I would not expect 26.04 to show up as officially supported the day it shipped, or even in the first month after. I haven’t personally run a production fleet on a 26.04 box yet, only 22.04 and 24.04. Check the live system requirements page and the issue thread itself before you plan a migration date around it, both get updated the moment the real answer changes, and I’d rather point you at the source than hand you a snapshot that’s stale by the time you read this.

Don’t take my word for it.

what it is

Playwright publishes a short, explicit list of operating systems its team validates the bundled browser builds against. That list currently centers on Ubuntu 22.04 and 24.04, Debian 11 and 12, Windows 10 and 11 plus Windows Server, and the last few macOS releases, all documented on the system requirements page. It updates on Playwright’s release schedule, not on Ubuntu’s.

“Supported” means two concrete things here. First, the Chromium, Firefox and WebKit builds Playwright ships are built and tested against that specific OS in Microsoft’s own CI. Second, running npx playwright install-deps actually knows which apt packages to pull for it. Anything off that list isn’t banned, it’s untested. It might run today. Nobody’s promised it keeps running after the next Chromium security patch.

It’s also worth checking by chip, not just by OS name. arm64 Linux support for some of these browser builds has historically lagged x86-64 by a release or two, so if your fleet runs on Graviton or similar arm hardware, check that column separately rather than assuming it tracks the x86-64 status.

how it works

Canonical has shipped a new Ubuntu LTS every two years in April since 2006, that’s the cadence documented on Ubuntu’s release cycle page, and it’s why 22.04, 24.04 and 26.04 exist on a predictable schedule. Playwright’s release cycle doesn’t line up with that at all. It ships new npm versions roughly every few weeks, tracking Chromium’s own release train.

When a new Ubuntu LTS lands, someone on the Playwright team has to go add it by hand: update the install-deps package list for whatever the new distro renamed or reversioned, rebuild the bundled browsers against the new glibc, run the CI matrix, then flip the docs. That process took a few months after Ubuntu 24.04 shipped in April 2024, not because anything was actually broken on 24.04, more because validating a new base image wasn’t first in anyone’s queue. There’s no particular reason to expect 26.04 moves faster.

Part of why this isn’t just a glibc version check: Chromium’s sandbox leans on kernel namespace and seccomp features that can behave differently across kernel versions, not only library versions. Two Ubuntu releases can share a glibc version and still sandbox a browser differently if the kernel underneath changed. That’s why Playwright validates actual OS builds end to end instead of publishing a minimum glibc number and calling it done.

The other way around this whole question is Docker. Microsoft publishes prebuilt images at mcr.microsoft.com/playwright, each one tagged to a specific Playwright version against a specific Ubuntu base, jammy for 22.04, noble for 24.04. Run your fleet in containers instead of directly on bare metal or a VM host, and the host OS mostly stops mattering, you’re picking an image Microsoft already tested instead of gambling on your host’s glibc. It also forces a second decision worth making on purpose rather than by default, whether you actually want Playwright’s bundled Chromium or Google’s Chrome for Testing binaries, a separate tradeoff from what OS is underneath.

why it matters

CI and production need to agree on OS, and that’s far easier to enforce against a documented list than against “it worked when I tried it once.”
security lifecycle. Ubuntu 22.04 gets standard support through April 2027, 24.04 through April 2029. If your fleet’s lifespan runs past those dates you’ll need 26.04 or paid Ubuntu Pro extended support eventually, so the real question isn’t whether you move, it’s whether Playwright is ready when you do.
misdiagnosed flakiness. A missing or renamed shared library on an unsupported OS rarely crashes loudly. More often the browser launches fine and then drops frames, hangs on navigation, or fails intermittently under load, which reads exactly like an agent logic bug. If you’re already pulling traces and replays to debug agent behavior, ruling out an OS mismatch first will save you a wasted afternoon.
fleet consistency. Half your workers on 24.04 and half jumped early to 26.04 means you’ve added a variable that makes bugs non-reproducible machine to machine, which is a worse position than being uniformly a year behind.

I don’t move a production fleet’s host OS in the same quarter a new LTS ships, official support or not. That’s volunteering for a debugging session nobody budgeted for.

common misconceptions

“It launched, so it’s fine.” A browser launching on an unvalidated OS tells you it works right now, not that it survives your next apt upgrade or the next Playwright release that patches a Chromium CVE. Unsupported means untested, not flagged as broken.

“Playwright uses whatever Chrome is already on the box.” Only if you explicitly set channel: 'chrome' or channel: 'msedge' against a system install. By default it downloads its own patched Chromium, Firefox and WebKit builds into a local cache, so the OS question is really about whether those specific binaries can find the shared libraries they were compiled against, nothing to do with what browser Ubuntu ships out of the box.

“LTS to LTS is always a safe jump.” glibc, OpenSSL and other base libraries can shift enough between two LTS releases to break a precompiled sandboxed binary even though both are technically “just Ubuntu LTS.” That’s the actual reason Playwright keeps an explicit allowlist instead of claiming any modern Linux works.

“Someone’s already answered this on Stack Overflow.” Maybe, for last year’s version of the question. The answer to this one specifically decays fast because it’s tied to a moving support list. The GitHub issue and the live system requirements page are the two places that get updated when the real status changes, a two-year-old forum thread won’t.

where to go from here

Start with the two things that actually move the needle: the live system requirements page for today’s supported OS list, and issue #40117 itself, which is where the Playwright team will confirm 26.04 support the moment it lands.

Past that, a few related decisions worth making before or alongside the OS call.

the browser agent production checklist covers everything else worth locking down before a fleet-wide upgrade, not just which OS it runs on
if part of your fleet drives mobile surfaces too, the same validated-versus-it-just-happened-to-work question shows up again in Android emulator vs real phone for phone-use agents
and if agents on your fleet are getting flagged or blocked regardless of what OS or browser they’re running, that’s a separate problem covered in why AI browser agents get blocked

None of that replaces actually running your real workload on a 26.04 test box before touching production. Cheapest test you’ll run all quarter, and it tells you more than any support list will.

More explainers like this one live on the blog index.

Written by Xavier Fok

disclosure: this article may contain affiliate links. if you buy through them we may earn a commission at no extra cost to you. verdicts are independent of payouts. last reviewed by Xavier Fok on 2026-09-14.