Chrome Download App: How to Install Google Chrome in 2026

Typing “chrome download app” into a search bar usually means one thing: you want Google Chrome on your computer or phone, and you want the file that’s actually safe to run. Good news. There’s exactly one official source, and the whole process takes a few minutes on every platform Chrome supports.

This guide covers downloading and installing Chrome on Windows, Mac, Linux, Android, and iPhone, what a Chrome download app gets you (it’s free, no purchase involved anywhere), what to do without an internet connection on the target machine, and how to spot a fake download page. Near the end we cover the part Google’s own install guide skips: what happens to the tabs you already have open when you install or update, and how a tool like BelayTab keeps that stack of windows from disappearing the moment something goes sideways.

Where Do I Get the Official Chrome Download App?

The official Chrome download app comes from one page: google.com/chrome. There’s no second official mirror, no approved reseller, and no “verified” third-party host — just that page for desktop, and your device’s app store for mobile.

Google’s own install instructions describe the process in plain terms: download the installation file, then look for it in your downloads folder, open it, and follow the instructions. That single sentence covers the Windows path, and Mac and Linux follow a nearly identical shape with a couple of extra clicks along the way.

Chrome itself costs nothing to get. There’s no free trial that expires, no paid tier, and no “Chrome Pro” hiding behind a paywall — every desktop and mobile build is a chrome app download free of charge, and it stays that way after install. If a site asks you to pay for a Chrome installer or hand over a “license key” before you can download it, close that tab. That is not how Google distributes its browser.

Google’s install page doesn’t spell out an explicit warning against third-party download sites, so treat that gap as a reason for caution rather than a green light. The safest habit is still to type google.com/chrome yourself, or search your phone’s app store directly, rather than clicking a download link buried in an ad, a forum post, or a search result on a domain that isn’t Google’s own.

That last row matters more than it looks. Chrome doesn’t carry over open tabs from whatever browser you were using before, and if you’re mid-project (a dozen tabs of contract language, or a research binder for a class due Friday) losing that context on install day is a rough way to start with a new browser. We’ll come back to that near the end.

How Do I Download and Install Chrome on Windows?

You download the installer from google.com/chrome, open it, and approve one Windows permission prompt. From there Chrome installs itself and opens on its own. There’s no wizard full of screens to click through.

For a chrome browser for windows download, Google supports Windows 10 and up on Intel or AMD processors, provided the chip is a Pentium 4 or later with SSE3 support (which describes essentially every PC sold in the last decade). If you’re on an ARM-based Windows machine (the kind of thin, fanless laptop built around a Snapdragon or similar chip) Chrome requires Windows 11 or later rather than Windows 10.

The whole thing usually takes under a minute on a normal broadband connection. If you manage several Windows machines, or you’re setting one up somewhere without internet access, Google also offers a standalone offline installer, which we cover a little further down. It saves you from re-downloading the same file on every computer in a lab or office.

One thing worth flagging early: Windows doesn’t ask you to choose an install location or opt out of any bundled software during this flow, because there isn’t any. If an installer you downloaded shows extra checkboxes for toolbars, a different default search engine, or “recommended” software, you’re not looking at Google’s actual installer, and you should stop and re-download from google.com/chrome directly.

How Do I Download and Install Chrome on Mac?

You download googlechrome.dmg from google.com/chrome, open it, and drag the Chrome icon into your Applications folder. That drag-and-drop step is the whole install. There’s no separate installer program running in the background.

A chrome browser download mac requires macOS 13 Ventura or later. If you’re running an older release of macOS, Chrome’s installer will still open, but the browser itself won’t run, so it’s worth checking your macOS version under the Apple menu before you start.

Dragging Chrome into Applications sometimes asks for your admin password, since it’s writing to a system folder shared by every user account on the Mac. If you don’t have that password handy (a work laptop managed by IT, for instance) you can drag Chrome to your desktop instead and run it from there, though moving it into Applications later is the more normal long-term home for it.

Eject the disk image when you’re done. After dragging Chrome into Applications, eject the mounted googlechrome.dmg from Finder’s sidebar. It’s harmless to leave it mounted, but it clutters your desktop and your list of open volumes for no reason.

Once Chrome is in Applications, launching it for the first time may trigger a Gatekeeper-style confirmation, since macOS flags any app downloaded from the internet. Click through that prompt and Chrome opens normally from then on. If you ever need to reinstall (a corrupted profile, a fresh Mac) the process is identical: fresh .dmg, drag again, done.

How Do I Install Chrome on Linux?

You install Chrome on Linux through your distribution’s package manager, using the .deb or .rpm file Google publishes on google.com/chrome. There’s no tarball-and-symlink route for Chrome the way there is for some other browsers. It’s built around your system’s package tooling from the start.

Debian and Ubuntu-based distributions use the .deb package; Fedora and openSUSE use the .rpm. Either way, installing requires admin access, since the package manager needs permission to place Chrome’s files in system directories and register it with your desktop environment. Minimum supported versions are 64-bit Ubuntu 18.04 or later, Debian 10 or later, openSUSE 15.5 or later, or Fedora Linux 39 or later, running on x86-64 or ARM hardware with SSE3 support.

Once installed this way, Chrome shows up in your applications menu like any native package, and (this is the part that trips people up coming from Windows or Mac) updates don’t come through Chrome’s own updater. On Linux, your system’s package manager is responsible for pushing new Chrome versions, the same way it handles updates for every other installed package.

Chromebooks are a different thing entirely. A Chromebook doesn’t run a separate “Chrome the app” at all — the browser is baked into ChromeOS itself, so on a Chromebook you update the operating system, not a standalone Chrome install. If that’s your device, our Chromebook tabs guide covers how tabs and updates interact there.

If you’re setting up several Linux machines at once (a classroom, a small office) scripting the package-manager install command is faster than repeating the manual download-and-click flow on every box, and it plays nicely with whatever configuration management you’re already running.

Can I Download Chrome for Android or iPhone?

Yes, but not from google.com/chrome — mobile Chrome installs only through your device’s app store. There’s no separate standalone installer for phones or tablets the way there is for desktop operating systems.

For a chrome app download for android, open the Play Store, search “Google Chrome,” and install it. That’s the only supported play store app download chrome route, and it requires Android 10 or later. On most Android phones Chrome comes preinstalled already, so you’re more likely to be reinstalling after a factory reset than setting it up for the first time.

On iPhone and iPad, Chrome installs from the Apple App Store the same way any other app does, and it requires iOS 17 or later. Because Apple restricts what any third-party browser can do at the system level, a handful of Chrome features you might expect from desktop (cookie-setting controls, automatic encoding detection, Do Not Track) simply aren’t available on iOS. That’s a platform limit Google documents rather than a bug in the iOS build.

Neither mobile version behaves like the desktop installer in one other way: there’s nothing to drag, nothing to run as an administrator, and no permission dialog beyond the app store’s own install confirmation. It’s the simplest install path of the bunch, which makes sense given how many people are doing it on a phone with one thumb.

What Are the Minimum System Requirements for Chrome?

Chrome’s minimum requirements vary by platform, but every current desktop OS released in the last several years clears the bar easily. The table below pulls together the numbers Google publishes for each supported system.

If you’re not sure which OS version you’re running, or which Chrome build you already have, a quick check on what browser and version you’re currently using settles that in seconds before you commit to a download. It’s a faster first step than guessing and having the installer refuse to run.

Most people never hit these limits, since they upgrade hardware more often than Chrome tightens its floor. Where it does bite is older Macs stuck below Ventura, or Linux servers running a long-term-support release from several years back. In both cases, the fix is either upgrading the OS or accepting that Chrome on that machine will lag behind the current release — Google doesn’t offer a legacy Chrome build the way some software vendors do for older operating systems.

Is There an Offline or Standalone Chrome Installer?

Yes, Google offers a standalone installer for machines without an internet connection, available under “Other Platforms” on the Chrome download page. It’s meant specifically for installing Chrome on a computer that can’t reach the internet during setup, rather than as a general alternative to the normal download button.

That makes it useful in a few specific situations: air-gapped machines in a secure environment, computers in a location with no reliable connection, or IT departments deploying Chrome to a batch of devices from a single downloaded file rather than pulling it fresh over the network each time. You download the offline package once, on a connected machine, then carry it over (a USB drive, an internal file share) to install it elsewhere.

The standard online installer, by contrast, is a small file that downloads the rest of Chrome during setup, which is why it’s the default choice for a single computer with a normal connection. Unless you specifically need the offline option, the regular google.com/chrome download button is the simpler path — fewer steps, and it always grabs the current release automatically.

How Do I Know a Chrome Download Site Is Official (and Avoid Fakes)?

You know a Chrome download page is official when its address is exactly google.com/chrome, or when you reached the install through the Play Store or App Store search results rather than a link. Anything else (a sponsored ad, a “download now” button on a tech blog, a link shared in a message) should be treated as unverified until you check the address bar yourself.

Google’s own install support page doesn’t include an explicit warning telling users to avoid third-party download sites, which is worth knowing honestly rather than papering over. That absence doesn’t mean unofficial sites are safe; it just means the caution here is general good practice rather than a quote from Google itself.

Watch for fake “urgent update” pages. Mozilla has documented scammers redirecting users to fake pages claiming an “important” or “urgent” browser update, then pushing malware through a fake manual download. The same trick shows up on Chrome-themed copycat pages — a legitimate browser update never needs you to run a downloaded file from a pop-up.

A few practical checks help here: look at the full domain in the address bar, not just the site name shown in a search result; be suspicious of any download page pushing a sense of urgency (“your browser is out of date, update now”); and remember that Chrome, once installed, checks for its own updates in the background. You shouldn’t need to visit a website to trigger one. If something feels off about a download page, closing it and typing google.com/chrome fresh costs you ten seconds and avoids a much longer cleanup later.

What Happens to My Tabs When I Install or Update Chrome?

A fresh install starts with a blank slate, and an update generally preserves your open tabs automatically. Those are two different situations worth separating clearly, because people often assume they behave the same way.

On a brand-new install, Chrome opens with its default new-tab page. There’s nothing to restore, since there was no previous Chrome session on that machine to pull from. If you’re replacing another browser, Chrome’s built-in import tool can bring over bookmarks and history, but it does not import a live set of open tabs from your old browser; that’s a gap you have to close yourself.

Updating an existing Chrome install is different. When you click Relaunch to apply an update, Chrome saves your opened tabs and windows and reopens them automatically once it restarts. You land right back where you were, tab for tab. Google documents this behavior directly, and it’s one of the more reassuring things about how Chrome handles updates.

Checking your version and triggering that update check yourself takes four short steps, and it’s worth doing right after a fresh install to make sure you’re not starting out already a release behind.

1. Open the three-dot menu. Click the icon in Chrome’s top-right corner.
2. Choose Help, then About Google Chrome. This opens the page that shows your installed version.
3. Let Chrome check automatically. Visiting this page starts a background check for a newer release right away.
4. Click Relaunch if one appears. Your tabs and windows reopen automatically once Chrome finishes restarting.

Incognito is the one exception. Your Incognito windows won’t reopen when Chrome restarts after an update, by design. That’s the whole point of Incognito, but it does mean anything you were doing there needs to be somewhere else if it matters.

Where this documented behavior runs out is anything Chrome itself doesn’t control: a full system crash mid-update, a forced restart, a corrupted profile, or simply closing out of Chrome the wrong way before an update finishes. Google’s relaunch feature is genuinely useful, but it only covers the clean path. For what to do when Chrome itself won’t recover cleanly, our guide on a crashed Chrome and restoring tabs in Chrome go into the messier scenarios in more detail, and updating itself is covered step by step in our Chrome update guide.

How Do I Protect My Tabs Before and After Installing Chrome?

You protect your tabs by running a dedicated tab-saving tool alongside Chrome, since Chrome’s built-in recovery only covers the clean relaunch-after-update path, not crashes, wiped profiles, or a browser switch. That’s exactly the gap BelayTab is built to close.

BelayTab is a free browser extension from Pointerflow LLC that saves your open windows as named sessions and restores them later, on Chrome and several other browsers. It runs automatic snapshots of every open window every five minutes, and again the moment you close a window, keeps the last 20 versions of each saved session, and holds deleted sessions in a 30-day trash — all without an account, and without any limit on how many sessions or tabs you keep. Save manually with one click, or press Ctrl + Shift + S (Cmd + Shift + S on Mac) to save the current window on the spot, including tab groups, pinned tabs, and their order.

That matters most exactly around a Chrome install or update, because that’s when things are most likely to go slightly wrong: a relaunch that doesn’t come back cleanly, a new install on a replacement computer, or a profile that gets reset during a reinstall. With BelayTab already running, you have a recent snapshot to fall back on through the single Recovery screen, which brings together snapshots, deleted sessions, and your browser’s own recently closed windows in one place.

If you’re coming from another browser rather than a clean reinstall, BelayTab’s import and export tools read OneTab exports, Session Buddy, Tab Session Manager, Tablerone, and plain URL lists, and write out JSON, CSV, URL lists, or HTML bookmarks — so a browser switch doesn’t mean starting your tab collection over from nothing. BelayTab reads no page content and requests no host permissions; everything stays on your computer unless you turn on the optional paid Sync tier.