Overview
This is the full offline installer for the current stable browser build, which is the version to have when setting up a machine that is not connected yet or a room of machines from one copy. The usual download is a small stub that fetches everything at install time and fails without a working connection.
The browser itself needs little introduction. Site isolation puts every site in its own process, the sandbox keeps a compromised tab away from the rest of the system, and the rendering and script engines are the reference implementation that most of the web is tested against first. Profiles keep separate bookmarks, extensions, history and settings, which is the practical way to keep work and personal browsing apart on one machine.
The developer tools are a large part of why it stays installed even on machines that browse elsewhere. Element inspection with live style editing, a network panel with throttling and request replay, performance and memory profiling, device emulation with touch input, and a console with full runtime access. Alongside them sits the extension platform, the built in password and payment handling, tab grouping, and a task manager that shows exactly which tab is eating the processor.
What it does well
Offline installer
The complete package rather than the downloader stub, so it installs on a machine with no connection.
Process isolation
Every site runs in its own sandboxed process, so one bad page cannot reach another tab or the system underneath.
Profiles
Separate profiles with their own bookmarks, extensions, history and settings, switchable from the toolbar.
Developer tools
Element inspection, network throttling and replay, performance and memory profiling, device emulation and a full console.
Extension platform
The largest extension ecosystem on the desktop, with per-profile installation and per-site permission control.
Changes in this build
- Rendering engine updated with faster paint on long scrolling pages.
- Memory saver reworked so background tabs release more without losing state.
- Tab groups gained saving and restoring across sessions.
- Password manager moved into its own settings section with a checkup pass.
- Reduced installer size and faster first launch on cold profiles.
What is in the package
- Chrome offline installer, 64-bit
- Per-machine and per-user install modes
- Group policy templates for managed deployment
- Multilingual interface support, 52 languages
- Update service disable switch
System requirements
| Processor | Intel Pentium 4 or later with SSE3 |
| Memory | 2 GB minimum, 8 GB for heavy tab use |
| Graphics | Any GPU with a current driver for hardware acceleration |
| Storage | 500 MB free plus profile space |
| Display | 1024 x 768 minimum |
| System | Windows 10 or Windows 11, 64-bit |
Installation
- Extract the archive to a local folder.
- Choose per-machine or per-user install depending on how many accounts need it.
- Run the installer, no connection is needed.
- Set the default browser association if you want it to own web links.
- Disable the update service afterwards if the version should stay fixed.
Before you start
The update service reinstalls itself on some paths, check it again after a major system update.
Hardware acceleration causes artefacts on some old integrated graphics, it can be turned off in settings.
Profiles live under the user folder and can be copied to another machine wholesale.
Questions about this title
Why the offline installer?
It installs without a connection, which the standard downloader stub cannot do.
Can I stop it updating?
Yes, disable the update service after install if you want the version pinned.
Does it support managed deployment?
Yes, group policy templates are included in the package.
Is it 64-bit?
Yes, this is the 64-bit build.
About this listing
This entry was checked on a clean install of Windows 10 / 11 (64-bit) before it was published, and it is rechecked whenever the package is rebuilt. The figures on this page come from the site index rather than from the publisher, so the download count is what people here have actually pulled.
If a mirror stops answering, use the contact form and it gets replaced. Reports about a specific title are handled faster than general messages because they name the file, the mirror and the point at which the transfer stopped.
Requests for a different version, a different language build or an older release go on the requests page. Older versions of a title are usually still held even when only the current one is listed.