Browser version numbers move fast enough that a static blog post listing a specific number is accurate for a few weeks at most. What stays useful longer is knowing the release cadence for each, and where to check the actual current number at the moment it’s needed.
| Browser | Current stable version | As of |
|---|---|---|
| Google Chrome (desktop) | 156.0.8078.47/.48 | 20 October 2026 |
| Mozilla Firefox | 158.0.1 (maintenance update; major release 158) | 13 October 2026 (major); 20 October 2026 (maintenance) |
| Microsoft Edge | 156.0.4314.42 | 22 October 2026 |
| Apple Safari | 26.6 | Latest version confirmed in Apple’s release notes as of 24 October 2026 — verify for newer stable releases |
Version availability can vary by operating system, device, and rollout stage — a staged or early-stable release doesn’t always mean every user gets it on the announcement date. Check the vendor’s own release-notes page for the number that applies to a specific machine.
Release cadence, by browser
- Chrome — a new major version roughly every 4 weeks, following Google’s rapid release cycle, typically rolled out in stages rather than to all users at once. Minor/security updates ship between major releases as needed, and an early-stable build reaching a small percentage of users isn’t the same as general availability.
- Edge — built on Chromium, generally tracks Chrome’s release cadence closely, often within days of a Chrome major release.
- Firefox — also on a roughly 4-week major-version cycle, independent of Chromium’s schedule.
- Safari — closely connected to Apple’s operating-system releases, with additional point releases between major versions, but not on a strict 1:1 version-per-OS-release schedule — Safari has its own release notes and version history, and beta releases can precede general availability by weeks. Check Apple’s Safari release notes for the current stable version rather than assuming the newest beta or OS version number is already shipping.
Checking your own browser’s version
- Chrome:
chrome://settings/help - Edge:
edge://settings/help - Firefox:
about:support(or Menu → Help → About Firefox) - Safari: Safari menu → About Safari
Why this is worth checking, not just trivia
An outdated browser is both a security exposure (unpatched known vulnerabilities) and a compatibility risk for any site or web app using recent CSS/JS features — a page tested only on the latest Chrome can behave unexpectedly on a Firefox or Safari version that’s several releases behind. Checking actual current versions (rather than assuming “it auto-updates, so it’s fine”) matters especially for enterprise or managed environments where auto-update is sometimes deliberately delayed or disabled.
See also: iOS Version History: Major Releases and Key Updates for the OS-level equivalent of this table, Where Chrome Profiles Are Stored on Windows, Linux & Mac and Firefox about: pages for more on these two browsers specifically.