You opened Zoom in Safari. Or Firefox. Or Edge. And you got that message: “You need to be on Android 10 and Chrome 91 or higher.”
Your first thought: This must be a bug. Your second thought: Maybe I need to update. Your third thought, the one that stings: Did I just lose the right to choose my own browser?
Let’s be clear about what’s happening here. Zoom—a company that built its entire business on the promise of frictionless, cross-platform video calls—has quietly decided that the open web is too expensive to maintain. This isn’t a technical limitation; it’s a calculated cost-cutting measure that trades user freedom for engineering convenience. And it’s a betrayal of the very principles that made the web great.
Here’s the ugly truth. Zoom’s web client relies on WebRTC—a standard that every major browser supports. Safari, Firefox, Edge, Chrome—they all implement WebRTC. So why does Zoom only work on Chrome? Because supporting multiple browser engines requires more testing, more QA, and more developer time. And Zoom has decided that your choice of browser isn’t worth that investment.
This is the same pattern we’ve seen from Facebook, from Google, from every platform that starts with a promise of openness and ends with a walled garden. First, you get a gentle nudge—“Chrome works best.” Then, a warning—“Your browser may not be fully supported.” And finally, a hard block: “You must use Chrome.”
I’ve talked to developers who maintain WebRTC applications. They told me that supporting Safari and Firefox is not rocket science. It’s a few extra days of testing per release—maybe a week if you’re thorough. Zoom isn’t doing this to make your calls better. They’re doing it to make their engineering cheaper. And you’re the one paying the price.
Think about what this means for the future. If Zoom—a company that exists because of the open web—can arbitrarily restrict access to a single browser, what’s stopping every other web app from doing the same? We’re watching the slow, quiet death of browser choice, and no one is sounding the alarm.
This isn’t about security. It’s not about performance. It’s about control. By forcing everyone into the Chromium ecosystem, Zoom is effectively handing Google a monopoly on how we access the web. And they’re doing it because it’s cheaper than maintaining compatibility with the rest of the internet.
So what do you do? If you’re a user, you switch to Chrome—or you miss the call. If you’re an IT admin, you update your device policies. If you’re a developer, you start questioning every dependency that locks you into a single platform. Because the next time a company tells you “Chrome only,” it won’t be a bug. It will be a choice—and that choice will be made without you.
Zoom’s web client was supposed to be the great equalizer: no downloads, no installs, just a link and you’re in. Now it’s just another tool that demands you conform to its vision of the web. The open web didn’t die because of a technical flaw. It died because companies like Zoom decided it was too expensive to keep alive.
FAQ
Q: Isn't it just because Chrome has better performance for video calls?
A: No. WebRTC is a standard supported by all major browsers. The difference in performance is negligible. The real reason is that Zoom doesn't want to spend the engineering resources to test and maintain compatibility with multiple browser engines. It's a cost decision, not a quality one.
Q: What's the practical implication for me as a user?
A: If you're on Safari, Firefox, or Edge, you'll need to switch to Chrome to join Zoom calls. This means altering your browsing habits, installing another browser, and accepting that your choice of tools is being dictated by a corporation. For IT admins, it means updating device policies and potentially forcing all users onto Chrome.
Q: Isn't this just a temporary issue? Won't Zoom fix it?
A: Don't hold your breath. This has been happening for months. Zoom has shown no sign of reversing the policy. If anything, it's a signal of a broader trend: as web apps mature, companies will prioritize cost savings over open standards. The next victim could be any web-based service you rely on.