Which browser still runs well on an old Mac

Advice about the best browser for an old Mac usually starts with which one is lightest, which is the wrong question first. On a machine several years old, the deciding factor is not how a browser performs. It is whether that browser still ships updates for the version of macOS the machine can run. A browser that stopped receiving security patches two years ago is not a lightweight option. It is a liability that happens to open quickly.

So the order matters. Establish what macOS the machine can reach, then narrow to the browsers that still support it, then tune the one that is left. Doing it in the other order produces the familiar result where a new browser feels better for a week and then the machine feels exactly as it did before.

Start with the macOS version, because it removes options

Chrome's requirement is stated plainly in Google's own documentation, and it rules out a large number of otherwise working Macs.

To use Chrome browser on Mac, you'll need: macOS 13 Ventura and up Source: support.google.com

A Mac stuck on macOS 12 Monterey or earlier does not lose Chrome. It keeps whichever build was the last one compatible, and that build stays where it is. No new features arrive, and more importantly, no new security fixes arrive either. For a browser used to sign into email and banking every day, that is the point where the decision stops being about speed.

Firefox reaches further back. Mozilla's published system requirements for the current release list macOS 10.15 or later, with recommended hardware of an Intel x86 or Apple silicon processor, 512 MB of RAM and 200 MB of disk space. Those numbers are met by essentially every Mac that can still boot. On a machine where Chrome has frozen, Firefox is frequently still installing current versions, and that difference is the single most useful fact for anyone keeping older hardware in service.

Mozilla also publishes an Extended Support Release, described as the option for long term stability with regular security updates and annual major releases rather than a feature release every four weeks. On an old machine, a browser that changes less often is not a compromise. It is a feature, because each major change is an opportunity for something to get heavier.

Safari is not chosen, it is inherited

Safari works differently from the other two and the difference is structural. It is not installed and updated on its own schedule. It arrives with the operating system.

Each macOS includes the latest built-in apps available for that macOS, including Safari, Notes, Messages, and Apple Music. Source: support.apple.com

The consequence runs in both directions. On a Mac that can still take the newest macOS, Safari is current with no action required, and it is the browser Apple tunes for battery life on laptops, which matters on hardware whose battery is already several years old. On a Mac that has reached the end of its macOS support, Safari is frozen at that version along with everything else.

This makes the software update screen the first thing to check, not the last. The Apple menu shows the current version under About This Mac, and Software Update shows only the upgrades that machine is eligible for. If nothing newer appears there, the machine has aged out, and the browser decision becomes a question of which third party still supports that version.

The shortlist, side by side

Laid out together, the options separate by how updates reach the machine rather than by performance.

Option	macOS supported	How updates arrive	Position on an older Mac
Safari	Whatever the machine's macOS is	Bundled with macOS updates	Current for free if the machine can still upgrade
Chrome	macOS 13 Ventura and up	Automatic, by the browser	Frozen on machines at macOS 12 or earlier
Firefox	macOS 10.15 or later	Automatic, by the browser	Widest reach, usually still current
Firefox ESR	Long term support track	Annual major release plus security fixes	Useful where a stable configuration matters

Read down the third column rather than across. A browser that cannot update is the only genuinely disqualifying condition on this list, and everything else is preference. Once the machine's macOS version is known, this table usually reduces the decision to two rows, and the remaining choice comes down to whether the web applications used for work behave correctly in the one selected.

That last test is worth running deliberately rather than discovering later. Open the three or four services used daily, sign into each, and use them normally for an afternoon. Business web applications are frequently tested against Chromium first, and an incompatibility found on day one is a minor inconvenience while the same one found in week three means migrating a working setup twice.

Where the slowness actually comes from

Once the shortlist is settled, it is worth separating the slowness caused by old hardware from the slowness caused by how the machine is used, because only the second one responds to browser settings.

Old hardware shows up as memory pressure. With too little physical memory, macOS starts swapping to disk, and at that point every application slows down together, the fans run, and switching windows takes seconds. Activity Monitor answers this in under a minute: open the Memory tab and read the memory pressure graph at the bottom. Green means the machine has headroom and the browser is a real variable. Yellow or red means macOS is already rationing, and every browser will behave similarly under those conditions.

Usage patterns show up differently. Tabs reloading when returned to, notifications arriving late, and time lost scanning a strip of identical favicons for a screen that was already open. These occur on new machines too. They are not symptoms of age, and replacing the browser rarely changes them, because every browser handles them in roughly the same way.

The reason this distinction matters is that the two problems have opposite fixes. Memory pressure is relieved by having fewer things loaded. The other three are relieved by having the important things stay loaded. Tuning for one makes the other worse, which is why a single setting cannot solve both.

Heat is the third possibility and it looks like neither. On a Mac several years old, dust in the vents and dried thermal paste raise operating temperatures, and macOS responds by reducing processor speed to keep the machine within limits. The signature is different from memory pressure: the Mac starts the day at normal speed and degrades over an hour or two of sustained use, with the fans audible throughout. No browser setting affects this, and no amount of tab management will either. If that pattern matches, the useful step is having the machine cleaned internally, which is often cheaper than any of the alternatives being considered.

The settings that actually help on limited memory

Chrome documents its behaviour most thoroughly, so it serves as a useful reference for how all of them work. Memory Saver deactivates unused tabs and reloads them automatically on access, with three levels: Moderate, where tabs go inactive after a longer period, Balanced as the recommended default, and Maximum, where tabs go inactive sooner.

The valuable part is the published list of conditions under which a tab will not be deactivated: active audio or video playback or a call, screen sharing, page notifications, an active download, a partially filled form, a pinned tab, or a connected USB or Bluetooth device. There is also a manual list of sites to always keep active.

That gives a precise lever. Pin the one or two tools that must never miss a message, and let everything else sleep aggressively. On an old Mac, set the level to Maximum and use the exception list sparingly, because each exception is memory permanently spent. The trade is explicit and cannot be avoided: a lighter machine means slower returns to idle tabs.

Extensions accumulate, and old machines notice

The other thing worth auditing is the extension list, which on a Mac owned for several years is usually longer than its owner expects. Each extension runs its own process with its own memory footprint, whether or not it was used this month.

A password manager, a translator, a screenshot tool, an ad blocker, a grammar checker and a tab organiser is six pieces of always running code. On current hardware the total disappears into the noise. On a machine already short on memory, it is measurable. The audit takes a few minutes: open the extension list, remove anything not used in the last month, and disable rather than delete anything uncertain so it can be restored.

The same duplication happens at the application level. Running a chat tool both as a native Mac application and as a browser tab is common and invisible, and consolidating to one of the two removes a resident process immediately. The usual sign is receiving the same notification twice, which is easy to dismiss as noise rather than read as evidence that two copies of the same service are running.

Login items deserve the same treatment. Applications that launch at startup are resident for the whole session whether or not they get used, and the list grows because installers add to it quietly. It sits in System Settings under General and Login Items, and pruning it is the one change that benefits every application on the machine rather than just the browser.

What to do when the shortlist is still too slow

If the machine is still struggling after all of that, the remaining variable is how many things stay loaded at once, and that is a structural choice rather than a setting.

One approach is to stop treating everything as a tab. The handful of web applications used every hour get a persistent space each, and everything else is opened in a tab and closed when finished. The number of resident things becomes fixed and predictable rather than growing through the day, which is the specific behaviour that makes an old Mac deteriorate between morning and afternoon. The Features page describes how those spaces work.

Two conditions apply before this is worth trying on older hardware. The services used daily need to be ones the approach supports, which the Supported apps list settles in a minute. And persistent spaces do consume memory, so the number of them has to be kept small on a constrained machine, which means being honest about which tools are genuinely hourly rather than merely open. Cost belongs in the comparison too, since the money involved sits against the price of replacing the machine. The pricing page gives the figures.

What to change first

Open Software Update and find out how far the machine can go, because that single answer eliminates most of the options and turns a long comparison into a short one. Then check the memory pressure graph, prune the extension list, and only after those two steps consider changing tools. If the remaining problem is that too much stays loaded all day, giving each daily app its own space is the change worth testing, and SpaceDeck is built around that model.