Google Chrome for Mac Description
Chrome isn't the default browser on a Mac, but it's one of the first apps many people install on a new one. I did exactly that when I switched from a Windows laptop to a MacBook, and Chrome was ready to use within minutes. On this page, I'll cover which Macs can run it, how the installation differs from Windows, and how it performed on our M5 Pro MacBook.
Which Macs Can Run Chrome?
According to Google's help page, you need macOS 13 Ventura or later to use Chrome on a Mac. That covers most Macs from the last several years. If your Mac is stuck on an older macOS, it will keep running an older Chrome build, but you will stop receiving security and feature updates.
Chrome works on both Apple Silicon (M-series) and Intel Macs. It runs natively on both, so there is no Rosetta translation, and you don't have to choose the build by yourself, since Google's download page picks the correct one for your Mac. If you want to double-check your chip, click the Apple menu > About This Mac.
How the Mac Installation Differs
On Windows, you run an installer and it does everything on its own. On a Mac, it's the classic drag-and-drop process. Google's instructions say to open the googlechrome.dmg file and drag Chrome into the Applications folder. You may be asked for your admin password during this step.
This also solves the problem we pointed out in the review. Since you are moving the app yourself, you aren't forced into a fixed install location the way you are on Windows. For the full step-by-step process, check our download and installation guide.
How Chrome Performed on Our Mac
We tested on a MacBook Pro with the M5 Pro chip (15-core CPU, 16-core GPU, 24 GB RAM) running macOS 27 Golden Gate. This is a powerful machine, so I expected Chrome to run comfortably, and it did, but with one catch.
With the same 20-tab test (10 YouTube videos and 10 online games), Chrome used about 8-9+ GB of RAM and 10-20% of the CPU. Even on a 24 GB Mac, that is a large chunk of memory, and it was clearly heavier than what we saw on Windows. So if you buy a MacBook with 8 GB of RAM, I'd turn on Memory Saver from day one.
The speed was decent, though. Chrome scored 39.6 in Speedometer 3.1, which is average. In our head-to-head test on the same Mac, Brave came out ahead at 48.4, while Firefox trailed at 33.7. In JetStream 3, Chrome and Brave were basically tied (488.56 and 488.30). In MotionMark, they were also very close, which means animations and graphics feel just as smooth on Chrome as on Brave.
Using Chrome on a Mac: Things Worth Knowing
- Allow permissions once: The first time a website uses your camera, microphone, location, or screen sharing, macOS will ask you to allow Chrome itself. You can change this later in System Settings > Privacy & Security.
- Switching from Windows is painless: When I moved from my old Windows laptop to my MacBook, I just signed in with my Google account, and my extensions, settings, and passwords came along.
- Memory Saver and Energy Saver help a lot: They are even more useful on a MacBook, where saving battery matters. Just remember they may limit some visual effects and smooth scrolling.
- Set it as your default browser: If you want links from other apps to open in Chrome instead of Safari, you can do it from Chrome's settings.
Should You Use Chrome on a Mac?
If you already use Chrome on other devices, it's an easy choice, because everything follows you to your Mac. Its performance is solid and it works with every website. The downsides on a Mac are the high RAM usage and the fact that Brave was a bit quicker in Speedometer. If battery life or memory is a big concern for you, Chrome's Memory Saver and Energy Saver settings are worth turning on right away.
