How do I update my browser quickly?

Open the browser's About page, let it download any update, then relaunch. Chrome uses About Google Chrome, Edge uses About Microsoft Edge, Firefox uses About Firefox, and Safari updates through macOS Software Update.

Will updating delete bookmarks, passwords, or extensions?

No. Normal updates preserve your browser profile. An extension may be disabled if it is incompatible, but bookmarks, passwords, history, and saved profiles are kept.

Why does a site still say my browser is outdated after I updated?

The old process may still be running, the site may be reading a spoofed user agent, or your OS cannot install the newer engine. Fully restart the browser, run the Browser Test and User Agent Checker, then check OS requirements.

Can I update Safari without updating macOS?

Usually no. Safari is updated through Apple software updates for macOS, iOS, and iPadOS. Install the latest compatible Apple update shown in Software Update.

Update Your Browser Safely: Chrome, Edge, Firefox, Safari

Direct answer

To update your browser, open its About page, let the update download, and relaunch the browser. Then run the Full Browser Test to confirm the version and feature support changed. If the version does not change, the blocker is usually an unfinished relaunch, old operating system, full disk, network/proxy issue, broken updater service, or managed-device policy.

Fast paths:

Chrome: open chrome://settings/help, wait for the check, click Relaunch.
Edge: open edge://settings/help, wait for the check, click Restart.
Firefox: menu > Help > About Firefox, wait for the download, click Restart to Update Firefox.
Safari: Apple menu > System Settings > General > Software Update, then install the latest compatible macOS update.

Safe browser update path from version check to vendor update, relaunch, Browser Test verification, and policy escalation

Follow this safe update path before reinstalling or deleting browser profile data.

Test before you change anything

Open the Full Browser Test and keep the result open while you update. The practical workflow for this guide is:

Record browser name, version, engine, and missing feature rows.
Update or fix one blocker.
Fully relaunch the browser.
Run the same test again and compare the version and feature rows.

If a site says "unsupported browser" but your version looks current, also open the User Agent Checker. A spoofing extension, compatibility mode, or enterprise override can make a modern browser identify as an old one.

Figure callout: For a help desk ticket, capture the Browser Test result before and after updating. Include the version line, user agent line, OS, and any failed HTML5/CSS/WebGL/media rows.

Update steps by browser

Browser	Desktop update path	Notes
Chrome	Menu > Help > About Google Chrome, or `chrome://settings/help`	Google's Chrome update help says Chrome checks for updates on this page and applies them after relaunch. On Linux, use your package manager.
Edge	Menu > Help and feedback > About Microsoft Edge, or `edge://settings/help`	If the About page says updates are controlled by your organization, check policy instead of reinstalling repeatedly.
Firefox	Menu > Help > About Firefox	Mozilla's Firefox update guide notes that packaged Linux builds update through the distribution repository, and Microsoft Store installs update through the Store.
Safari	System Settings > General > Software Update	Apple's macOS update docs explain that Safari updates arrive through macOS updates and upgrades; Software Update only offers versions compatible with your Mac.
ChromeOS	Settings > About ChromeOS > Check for updates	Restart the Chromebook after the update downloads. Browser and OS updates are tied together.
Android	Play Store > Manage apps and device > Updates	Also update Android System WebView if web content inside apps is failing.
iPhone/iPad	App Store for app updates; Settings > General > Software Update for the web engine	On iOS and iPadOS, Chrome, Firefox, and Edge use Apple's WebKit engine, so engine-level fixes come from iOS/iPadOS updates.

After updating, close every browser window. On Windows and macOS, check the taskbar/dock and system tray/menu bar too; an old background process can keep the old build alive until it exits.

Current OS limits to check

Before reinstalling, check whether your operating system can run the current browser. As of this June 29, 2026 review:

Chrome's support page currently lists Windows 10 or later for Intel Windows, Windows 11 or later for ARM Windows, macOS 12 Monterey or later, and supported 64-bit Linux distributions.
Firefox's update support page flags older Windows and macOS versions and directs unsupported users to Firefox ESR where available.
Safari follows Apple's Software Update compatibility list. If Software Update says your Mac is up to date, your Mac may not support a newer Safari engine without a macOS upgrade or newer hardware.
Edge is available on Windows and macOS, but enterprise update behavior can be controlled by Microsoft Edge Update policies.

If your OS is outside vendor support, installing another browser may help short-term compatibility, but it does not replace an OS security plan.

Fix updates that will not apply

Work through these in order:

Relaunch completely. Quit the browser, reopen it, then check the About page again. If the update is still pending, restart the computer.
Free disk space. Keep at least a few GB free on the system drive so the installer can download, unpack, and replace files.
Check the connection. Disable VPN/proxy temporarily, try a different network, and make sure system date/time are correct.
Let security tools finish scanning. Antivirus or endpoint protection can hold updater files open. Pause only if your organization allows it, update, then turn protection back on.
Check updater services on Windows. Chrome relies on Google Update services; Edge relies on Microsoft Edge Update services and Windows update components.
Use the package manager on Linux. Avoid mixing distro packages, vendor .deb/.rpm packages, Flatpak, and Snap unless you know which install owns the browser.
Install over the existing copy from the vendor. Use Google, Mozilla, Microsoft, or Apple sources. Do not trust random "your browser is outdated" popups or download ads.

Linux examples:

sudo apt update && sudo apt upgrade
sudo dnf upgrade
sudo zypper update
sudo pacman -Syu

Use the command for your distribution; do not run every command.

Managed device and policy blockers

If the About page says updates are disabled by an administrator, document the policy instead of fighting it locally.

Chrome: open chrome://policy and look for update or version-pinning policies such as UpdateDefault, TargetVersionPrefix, or AutoUpdateCheckPeriodMinutes.
Edge: open edge://policy; Microsoft documents policies such as UpdateDefault, per-channel Update, TargetVersionPrefix, and UpdatesSuppressed.
Firefox ESR: check whether your organization intentionally uses the Extended Support Release channel. ESR is valid for enterprises, but it may lag the newest web platform APIs.

Send IT the exact browser version from the Full Browser Test, the policy name, and the site feature that fails. For example, "CSS :has() is missing in the production profile" is more useful than "the browser is broken."

Reinstall safely when the updater is broken

Reinstall only after the About page, restart, disk, network, and policy checks fail.

Download the current installer directly from the vendor:
- Chrome
- Edge
- Firefox
Quit all browser windows.
Run the installer over the existing install.
Reopen the browser and confirm the profile is intact.
Run the Full Browser Test again.

Normal reinstalls preserve bookmarks, passwords, extensions, and profiles. Do not delete profile folders unless you have a backup and you are specifically fixing profile corruption.

When an update does not fix the website

If the browser version changed but the site still fails, move from "update" to the feature that is actually failing:

Layout broken or modern CSS missing: run the CSS Test and use the CSS not working guide.
PWA install or offline mode broken: run the HTML5 Test and Storage Test, then check PWA not installing.
Video playback broken: run the Codec Test and check video not supported.
3D canvas, maps, games, or GPU effects broken: run the WebGL Test and check WebGL not working.
Unsupported banner persists: run the User Agent Checker and check browser not supported.

This keeps you from reinstalling a browser to fix a storage, codec, GPU, or user-agent problem.

Release cadence and security updates

Expect frequent browser updates. Chrome, Edge, and Firefox stable channels normally move on a roughly monthly rhythm, with security fixes sometimes shipping outside the normal cadence. Safari arrives through Apple OS updates and security responses. If you leave a browser open for weeks, an update may already be downloaded but not active until you relaunch.

For security-sensitive work, do not wait for a site to complain. Check the About page after major OS updates, after a security bulletin, and whenever the Full Browser Test shows an outdated or missing core feature.

Verify after updating

Run the Full Browser Test again and confirm:

The version number changed or the About page says the browser is up to date.
The user agent matches your real browser and OS.
Core HTML5 and CSS rows are green for the features your site needs.
WebGL/WebGPU, codecs, and storage are green when the failing app depends on them.
The original unsupported-browser warning no longer appears after a hard refresh.

If the version did not change, go back to the failed-update and policy sections. If the version changed but a feature is still missing, the cause is probably hardware, OS support, a disabled flag, an extension, or site-specific compatibility logic rather than the update itself.