Update Chrome, Firefox, Edge, or Safari Safely (Run the Browser Test)

Check your version first

Run the Full Browser Test. It reports your browser version and highlights missing APIs (WebGPU, WebGL 2, codec support). Keep the test open so you can confirm the update worked after each step. If the test flags an outdated build or missing security patches, update right away.

Fast update paths by browser

Chrome (Windows/macOS/Linux)

1. Menu ⋮ > Help > About Google Chrome
2. Chrome downloads the update; click Relaunch
3. If the update fails, ensure the Google Update (gupdate) and gupdatem services are running (Windows) and that disk space is available.

Edge (Windows/macOS)

1. Menu ⋯ > Help and feedback > About Microsoft Edge
2. Edge checks and applies updates; click Restart
3. If disabled by policy, the About page will show it. Contact IT or install the latest offline installer from Microsoft.

Firefox (Windows/macOS/Linux)

1. Menu ☰ > Help > About Firefox
2. Firefox downloads updates; click Restart to update
3. For Firefox ESR, updates track the ESR channel. Switch to the regular channel if you need newer APIs.

Safari (macOS)

Safari ships with macOS.

1. System Settings > General > Software Update
2. Install pending macOS updates
3. Major Safari jumps may require a macOS upgrade; check hardware support before upgrading.

Mobile browsers

• Android Chrome/Edge/Firefox: open the Play Store, update the app, then rerun the Full Browser Test.
• iOS/iPadOS Safari/Chrome/Firefox: update through the App Store (Chrome/Firefox are WebKit-based; version is tied to iOS). Install the latest iOS for the newest engine.

Fix updates that keep failing

• Restart the machine to release locked files.
• Free disk space; keep at least 2–3 GB free for download and unpacking.
• Disable antivirus shields temporarily if they block updater executables (re-enable after the update).
• Check proxy/VPN: Updaters may not use your browser proxy. Try on a direct connection.
• Windows services: open services.msc and set Google Update Service (gupdate) and gupdatem to Automatic. For Edge, ensure Microsoft Edge Update Service is running.
• Linux package managers:
  • Debian/Ubuntu: sudo apt update && sudo apt upgrade google-chrome-stable (or firefox/chromium).
  • Fedora: sudo dnf upgrade chromium google-chrome-stable firefox.

Handle managed or locked-down devices

If the About page shows "Updates disabled by administrator":

• Chrome/Edge: run chrome://policy or edge://policy and look for UpdateDefault or AutoUpdateCheckPeriodMinutes. Capture the line and ask IT to allow updates or push a newer build.
• Firefox ESR in enterprises may update on a slower cadence. If a site demands a newer build, request a temporary standard channel install in a separate profile.

Reinstall when the updater is broken

If updates fail repeatedly or the browser is many versions behind:

1. Download the current installer from the official site.
2. Quit all browser windows.
3. Install over the existing copy (bookmarks, passwords, and profiles stay intact). On Linux, use your package manager instead of manual tarballs to keep future updates clean.

Verify after updating

Run the Full Browser Test again and check:

• Version number matches the latest listed on the vendor site
• WebGL 2 / WebGPU status is green (if your hardware supports it)
• H.264/AV1 codec support shows yes
• Security flag no longer says "outdated"

If the version did not change, the update was blocked. Revisit the policy and disk-space steps.

Release cadences

| Browser | Typical cadence | | ------- | ---------------------------------------------- | | Chrome | Every 4 weeks | | Edge | Every 4 weeks | | Firefox | Every ~4 weeks (ESR yearly baseline) | | Safari | With macOS releases and rapid security patches |