📋 Table of Contents
If you have ever tried to set up Chrome on a fresh or offline machine, you have probably hit the same wall: the download button on google.com/chrome hands you a roughly 1–2 MB "web installer" (ChromeSetup.exe) that then tries to pull the real ~100 MB browser from Google's servers during installation. On an air-gapped PC, a locked-down work laptop, or a slow connection that drops mid-download, that stub fails. Google does publish a genuine standalone offline installer that bundles the whole browser — it is just not the default button. This guide shows where the official offline installer lives, how to install it on Windows, macOS, and Linux, and how to verify you got the real thing.
1 Web installer vs. offline installer — what is the difference?
The default ChromeSetup.exe is a downloader stub: it contacts Google during install and fetches the current browser build, so the machine must be online at install time. The offline (standalone) installer is the complete browser packaged into a single file (~100 MB on Windows). You download it once, copy it to a USB drive or network share, and it installs with no further internet access. For one personal PC that is online, the web installer is fine. For deploying to multiple machines, imaging a lab, or any offline scenario, you want the standalone installer — it installs identically every time and does not depend on connectivity.
2 Where Google puts the real offline installer
Google hosts the standalone installer on its own domain at google.com/chrome — but you have to ask for it specifically. On the Chrome download page, look for the link that says "Other Platforms" or append the alternate-installer parameter the page exposes; Google then offers "Chrome for another computer" / the standalone build. The file you want is the larger one (around 100 MB on Windows, a full .dmg on macOS, and a .deb/.rpm package on Linux), not the 1–2 MB stub. Always start from google.com — never a third-party "Chrome offline installer" mirror, which is the most common vector for browser hijackers and bundled adware. Our Google Chrome page links straight to Google's official source so you skip the search-ad traps.
3 Install on Windows
1. On a connected machine, download the standalone installer from Google's official page and save it (for example ChromeStandaloneSetup64.exe). 2. Copy it to the target machine via USB or your deployment share. 3. Double-click the installer. Because the full browser is inside the file, it installs without contacting Google. 4. For unattended/IT deployment, Google also offers the Chrome Enterprise MSI on the same Chrome Enterprise page — run it with msiexec /i googlechromestandaloneenterprise64.msi /qn for a silent install across a fleet. If SmartScreen warns about an unrecognized publisher, confirm the file is digitally signed by "Google LLC" in the file's Properties → Digital Signatures tab before running it.
4 Install on macOS
On macOS the "offline installer" is simply the full googlechrome.dmg. Download it from Google's official page on a connected Mac, copy the .dmg to the target machine, open it, and drag Google Chrome into the Applications folder. No internet is required to complete that copy. For managed Macs, Google provides a Chrome .pkg through Chrome Enterprise that you can push with your MDM. Gatekeeper should accept it because the disk image is notarized by Google; if you see a warning, verify the signature with spctl -a -vv /Applications/Google\ Chrome.app.
5 Install on Linux
Linux is the most genuinely "offline-friendly" of the three. Google publishes a direct .deb (Debian/Ubuntu) and .rpm (Fedora/openSUSE) of Chrome that contain the full browser. Download the matching package on a connected machine, transfer it, and install with sudo apt install ./google-chrome-stable_current_amd64.deb or sudo dnf install ./google-chrome-stable_current_x86_64.rpm. The package also adds Google's apt/yum repo for future updates — on a truly air-gapped box those updates will not run, so plan to re-download the package periodically. Note Google does not ship an official Chrome build for ARM Linux; on ARM, Chromium from your distro is the supported route.
6 Verify you got the official build
Whichever platform you are on, do two quick checks before trusting the installer: (1) confirm the file came from a google.com URL, and (2) confirm the digital signature/notarization names Google (Google LLC on Windows, Google Inc. on macOS). After install, open chrome://version — the build should match the current stable release on Google's release blog. If anything is off (wrong publisher, a much smaller-than-expected file, a non-Google domain), delete it and start over from the official source.
Frequently Asked Questions
Why does the normal Chrome download need internet to install?
The default ChromeSetup.exe is a small web-installer stub. It only contains a downloader; the actual browser is fetched from Google's servers during installation. That is why it fails on offline machines. The standalone installer bundles the full browser, so it does not need a connection at install time.
Is the offline installer the same Chrome as the web installer?
Yes — it is the identical browser from Google, just packaged as a complete file instead of a downloader stub. You get the same version, features, and automatic-update behavior once the machine is back online.
Can I use the offline installer to deploy Chrome to many computers?
Yes. The standalone installer (or the Chrome Enterprise MSI/PKG) installs identically on every machine and is ideal for imaging labs, classrooms, or corporate fleets. The Enterprise package adds silent-install switches and group-policy support.
Where should I download it from to stay safe?
Only from google.com. Third-party "Chrome offline installer" sites are a common source of hijackers and bundled adware. Verify the digital signature names Google before running the file.
Conclusion
Chrome's standalone offline installer is the right choice any time you cannot rely on a connection during setup — air-gapped PCs, fleet deployment, or flaky networks. The key is starting from Google's own domain and choosing the larger full-browser package over the default stub, then verifying the signature. Once installed, Chrome behaves exactly like a normally-installed copy.
