Chromium browser main logo


The free and open-source project behind Google Chrome


Here, you see your Chromium version.
Works only if your web browser is based on Chromium like Google Chrome, Chromium browser, Opera, Vivaldi...

Windows 10, 8, 7

How to install, update and remove Chromium, on Windows?
About updates: your settings, bookmarks, extensions, history, passwords, cookies... will be saved. Do not worry!
For automated updates, use a Chromium #updater

  1. Download the EXE executable file (This is a 7-zip archive file. So you can unzip it to see its content)
  2. Close Chromium browser if opened
  3. Execute this EXE file
  4. Wait for 2 or 3 seconds (Installation is silent)
  5. Open Chromium browser. It is updated!
  6. To remove it definitively: use the standard way or a software like CCleaner.

  1. Download the ZIP archive file
  2. Close Chromium browser if opened
  3. Unzip this ZIP file
  4. Delete all the files from your installation directory
  5. Move the files from the unzipped directory to your installation directory
  6. Open Chromium browser. It is updated!
  7. To remove it definitively: delete your installation directory

Note: Chromium has "Secure Preferences" feature based on the machine SID. So extensions, certificates and passwords are not portable. The only way to migrate these data is to synchronize your data.
  1. Download and unzip ""
  2. Execute chrlauncher.exe (chrlauncher is a free and open-source Chromium launcher/updater)
  3. Close Chromium browser if a notification displays a new version
  4. Click on the "Download" button
  5. Wait for download and automatic installation
  6. Open Chromium browser. It is updated!
  7. To remove it definitively: delete the chrlauncher folder

  1. Install Chocolatey (A free and open-source package manager) in command-line
  2. Chromium will be automatically updated via Chocolatey
  3. To remove it definitively: use the "uninstall" command-line via Chocolatey
Windows XP, Vista
Since version 50, Chromium is not available on XP and Vista. For help, version 49 works fine (installer, archive, portable). In addition, if you have an old CPU without SSE2 support, version 34 is the last one (portable, build before 253860).

1. Chromium for 64-bit Windows

Reference: Current stable version (Google Chrome): 70.0.3538.67 (587811) • Tuesday, 16 Oct 2018


70.0.3538.67 (587811) • Wednesday, 17 Oct 2018
  • The Portable version uses the free and open-source chrlauncher to install, update and launch Chromium.
  • sha1: 70ada7710dbca85316898a54f20173e341b4026a - chromium-sync.exe
  • sha1: 734ecd03d20c2504cd86f3345cb62f6612f95e81 -
  • List of changes
  • #source-code: follow the Nik guide
  • Source: Github repository


71.0.3576.0 (597978) • Wednesday, 10 Oct 2018
  • The Portable version uses the free and open-source chrlauncher to install, update and launch Chromium.
  • sha1: 5742a9455a26a88b4a36badba1148602adaeed8b - chromium-sync.exe
  • sha1: c851cdb64484dd76a6b50f7d821d5044e28244b2 -
  • Previous versions (win64)
  • #source-code: follow the Nik guide
  • Source: Github repository


72.0.3581.0 (599540) • Sunday, 14 Oct 2018
  • The Portable version uses the free and open-source chrlauncher to install, update and launch Chromium.
  • sha1: 47e02340d71972f8c178d52e1713017a194580d9 - mini_installer.exe
  • sha1: aa15ae6489d85dbdcaf6a779091cb73ba5a8517a -
  • Previous versions (win64)
  • #source-code
  • Source: Github repository


71.0.3567.0 • Monday, 1 Oct 2018
This is an open-source and custom-built version of Chromium optimized for portable use. So, you can run it from an USB flash drive, portable hard drive, CD or any other portable media. You can take your bookmarks, extensions, themes and plugins with you. This portable version will leave no personal information behind on the machine you run it on.

Packaged in the format by Versatile Apps, it can work as standalone software.

How to update it?
Nothing is written to the Windows registry. This version uses a specific subfolder (named "Data") directly in the main folder, for all user data. So, take care when you update it!


The Chromium Authorsno-syncdevwin64

72.0.3585.0 (600920) • Thursday, 18 Oct 2018


64.0.3282.168 • Saturday, 17 Feb 2018
Install and update Chromium with Chocolatey, a free and open-source package manager. It works like apt-get or yum on Linux.

To install it: choco install chromium-stable
To update it: choco upgrade chromium-stable

2. Chromium for 32-bit Windows

Reference: Current stable version (Google Chrome): 70.0.3538.67 (587811) • Tuesday, 16 Oct 2018


70.0.3538.67 (587811) • Thursday, 18 Oct 2018
  • The Portable version uses the free and open-source chrlauncher to install, update and launch Chromium.
  • sha1: 36ec7baf34cf9293010a145dcd2024f097a8fe33 - chromium-sync.exe
  • sha1: 7c5089d9dbc59d531ff6ac26f953c1dce5ccff30 -
  • List of changes
  • #source-code: follow the Nik guide
  • Source: Github repository


70.0.3518.0 (581881) • Friday, 10 Aug 2018
  • The Portable version uses the free and open-source chrlauncher to install, update and launch Chromium.
  • sha1: 3aa57e8e641e89604790cca27fe79b74633b9dc0 - chromium-sync.exe
  • sha1: 00f9477aec0760640bdcea15e8e279a195982712 -
  • Previous versions (win32)
  • #source-code: follow the Nik guide
  • Source: Github repository


72.0.3581.0 (599540) • Sunday, 14 Oct 2018
  • The Portable version uses the free and open-source chrlauncher to install, update and launch Chromium.
  • sha1: c068f353750cb5b16f1d6d952ce4a9d555c05750 - mini_installer.exe
  • sha1: 8d366a9da701b357f0f4aa3339f9237d10f3b80b -
  • Previous versions (win32)
  • #source-code
  • Source: Github repository


71.0.3567.0 • Monday, 1 Oct 2018
Packaged in the format by Versatile Apps, it can work as standalone software.
Follow the same instructions as #windows-64-bit-thumbapps.


The Chromium Authorsno-syncdevwin32

72.0.3585.0 (600922) • Thursday, 18 Oct 2018


64.0.3282.168 • Saturday, 17 Feb 2018
Install and update Chromium with Chocolatey, a free and open-source package manager. It works like apt-get or yum on Linux.

To install it on a 32-bit Windows: choco install chromium-stable
To install it on a 64-bit Windows: choco install chromium-stable --x86More info about options and switches

To update it: choco upgrade chromium

macOS 10.10+

How to install, update and remove Chromium, on macOS?
About updates: your settings, bookmarks, extensions, history, passwords, cookies... will be saved. Do not worry!
For automated updates, use a Chromium #updater

  1. Download the DMG file
  2. Close Chromium browser if opened
  3. Execute this DMG file
  4. Drag its icon on Applications folder
  5. You may then "Eject" and throw away this disk image
  6. To remove it definitively: drag the app from the Applications folder to the Trash.

  1. Download the ZIP archive file
  2. Close Chromium browser if opened
  3. Unzip this ZIP file
  4. Double click on the unzipped folder to open it
  5. Drag its icon on Applications folder
  6. To remove it definitively: drag the app from the Applications folder to the Trash

1. Chromium for 64-bit macOS

Reference: Current stable version (Google Chrome): 70.0.3538.67 (587811) • Tuesday, 16 Oct 2018


70.0.3538.67 (587811) • Wednesday, 17 Oct 2018
How to update it?
Chromium Updater Extension is included in the .dmg file. (Archive: ZIP)



70.0.3538.67 (587811) • Wednesday, 17 Oct 2018


70.0.3538.67 (587811) • Wednesday, 17 Oct 2018


72.0.3580.0 (599499) • Saturday, 13 Oct 2018
Feedback appreciated - if demand will update once a month. Do no hesitate to write #comments ;)



72.0.3580.0 (599499) • Saturday, 13 Oct 2018
Feedback appreciated - if demand will update once a month. Do no hesitate to write #comments ;)


The Chromium Authorsdevmac

72.0.3585.0 (600848) • Thursday, 18 Oct 2018

2. Chromium for 32-bit macOS

Since version 39, Chromium and Google Chrome are not available in 32-bit version for macOS.


Reference: Current stable version (Google Chrome): 70.0.3538.67 (587811) • Tuesday, 16 Oct 2018


Chromium OS

Chromium OS is the open-source OS designed by Google that primarily runs web applications. Based on Gentoo, it exists since 2009. Chromium is its default web browser. Google Chrome OS (closed-source) is based on Chromium OS.

Free and open-source releases:


Arch Linux

Available in the official repository



Available in the official repository
To install the stable Chromium version:
  • use the integrated software/package manager
  • or type these commands:
sudo apt update
sudo apt install chromium chromium-l10n
(chromium-l10n is only used for localization and is optional)




Available in the official repository (since Chromium v52)


Gentoo Linux

Available in the official repository


Linux Mint

Available in the official repository
To install the stable Chromium version:
  • use the integrated software/package manager
  • or type commands (#ubuntu)




Available in the official repository



Available in the official #arch-linux repository



Available in the official repository


Puppy Linux

Unavailable in the official repository but you can install it!
Follow the main discussion on the Puppy Linux forum.




Unavailable in the official repository but you can install it!
Follow the blog post of Eric Hameleers (developer of Chromium packages)

Slackware is an independent distribution



Unavailable in the official repository but you can install it!
Install Snappy on Solus (if not installed). Then type this command: sudo snap install chromium



Available in the official repository
To install the stable Chromium version:
  • use the integrated software/package manager
  • or type these commands about this PPA:
sudo add-apt-repository ppa:canonical-chromium-builds/stage
sudo apt update
sudo apt install chromium-browser

To add language packages: sudo apt install chromium-browser-l10n
To add only the patent-free (ogg, vorbis, theora and av1) codecs: sudo apt install chromium-codecs-ffmpeg

To add the patent-free codecs + mp3, aac, ac3, mpeg4 (audio/h264), mov: sudo apt install chromium-codecs-ffmpeg-extra



Reference: Current stable version (Google Chrome): 70.0.3538.67 (587811) • Tuesday, 16 Oct 2018



Available in the official repository



Available in the official repository


Reference: Current stable version (Google Chrome): 70.0.3538.64 (587811) • Wednesday, 17 Oct 2018

There is no stable Chromium version for Android:

The Chromium Authorsno-syncdevandroid

72.0.3585.0 • (600898) • Thursday, 18 Oct 2018
This ZIP archive contains 2 packages:


Reference: Current stable version (Google Chrome): 70.0.3538.60 • Tuesday, 16 Oct 2018

Chromium on iOS is a big fake!
Check the official blog post and build instructions to understand that Chromium cannot use the existing content/implementation, which is based on V8/Blink. It is just a skin on top of Safari. Go your way!


Obviously, you know this site is not the Chromium official website. As a regular user (not an expert), I created it in 2013 because I did not find a simple way to download good releases. I try to keep it as safe and fast as possible! ;) This is absolutely a non-profit site. Please, read the #privacy-policy (on the right-hand side).

In short:
  • The official website is development oriented. Users are invited to download Google Chrome.
  • The official download page gives to users only DEV builds (also known as "Snapshot", "Nightly" or "Raw" builds).
  • This site gives to users a choice of builds: DEV (also on its simplest download page), stable and portable builds.

All downloads are from reliable sources only:

1. Project

Chromium exists since 2008. It is the free and open-source project (#features) behind the famous Google Chrome browser. Intrinsically, Chromium is a Google project maintained by many authors (developers, engineers, graphic designers, security researchers...) from Google, Cloudflare, Facebook, Hewlett-Packard, IBM, Intel, Mozilla, Nike, Nvidia, Samsung, Vivaldi, Yandex... and external contributors. There are many avantages of open source for the enterprise (archive: 1). Chromium is not designed by Google! However, as a primary investor, Google gives a consistent guidance and provides all free tools and services related to this project.

Chromium is the project then Google Chrome is the product.

2. Stable Chromium version

Officially, Chromium does not have a stable release. The official developers (aka The Chromium Authors) do not release it to end users. So it is continually in development. Google Chrome is the stable release... but is not open-source.

In fact, Chromium has a stable version. ^^
Example: The current stable version on #linux is 70.0.3538.67. In this version, there are 67 patches which correct many issues (bugs, feature requests, enhancements...). Because Chromium is open-source (#source-code), anybody can compile it. You must be a developer to do this. Just get the current stable version (70.0.3538.67) from the official Git repository and compile it!

All stable versions of Chromium on #windows, #mac, #linux... are always made by third-party developers.

The stable version of Chromium is compiled by:

3. Development

Basically, Chromium has few versions every day, but you can stick with a version for about a month before you need to upgrade.

A DEV build (also known as "Snapshot", "Nightly" or "Raw" build) is compile of the Chromium code whenever there are submitted code changes. Check the buildbot console. A snapshot build will be created as long as the code compiles successfully. Its binary files are stored in the Snapshots repository of Google Storage. This build is really just development tool for checking whether issues are fixed in the latest Chromium code. It can be buggy and unstable.

A stable build is a DEV build tested and improved by the Chromium team.

About lkcr/lkgr development builds
A LKCR build does at least provide some level of guarantee that the particular revision actually should build, which is good for third-party builds for not wasting time on potentially uncompilable builds. As a result, LKCR usually trails the dev trunk by a few revisions (commits).

If building straight off dev, it can be a guess whether a build will compile or not, so a third-party builder could be wasting processor cycles that could otherwise go to a known compilable build (LKCR).

Each snapshot build is then run through the automated tests. If that snapshot build successfully passes the automated tests, it is considered as a good build: LKGR (Last Known Good Revision)... and can become potentially a stable build.

Note LKGR builds were stored in the Continuous repository until Friday, 18 Mar 2016. The Chromium team has removed few LKGR builders (407399, 576253 and chromium-dev) but other ones still work (latest commit, latest builds). Finally, there is no LKGR binary shared by the Chromium team... but any developer can re-compile it! ^^

In resume:

4. Finally

Except for stable versions, the developers use the official Snapshots repository to re-compile their builds.

So I give you the opportunity to download only nice Chromium releases ;)
If you want, check the simplest multilingual page: → download/

This entire website (#news and #api included) is auto-updated each hour by the server itself.

Thanks for your attention.
Have a good time! ;)


Chromium vs Google Chrome.

Chromium browser has:
  • only open-source licenses (BSD license, MIT license, LGPL, MS-PL and MPL/GPL/LGPL tri-licensed code) plus unlicensed files. It is a FOSS project. A full list of software developed by third-parties is available within the browser at chrome://credits (similar to this online page)
  • a blue-colored logo
  • the similar sandbox as Google Chrome (For info, Firefox also uses it)
  • the similar user interface and settings as Google Chrome
  • the similar support for extensions, themes and web apps as Google Chrome
  • the similar user agent as Google Chrome
  • the similar experiments Field Trials (viewable as a list in "Variations" at chrome://version) as Google Chrome
  • the built-in Chrome PDF Viewer (known as PDFium), on Windows
  • the built-in Chromoting Viewer (To use it, you need to first install the Chrome Remote Desktop app)
  • the built-in Google Native Client
  • the built-in Print preview and print system
  • no stable version offered by the official team (aka The Chromium Authors)
  • no digital signature
  • no auto-update system (Solution: Use an #updater • On #linux, use the integrated software/package manager, indeed a PPA)
  • no Google API keys (Solution: Check #google-api-keys)
  • no built-in Flash player (Solution: Check #flash)
  • no unwanted software protection (known as Chrome Cleanup and "software_reporter_tool.exe"), on Windows
  • no support of proprietary codecs (AAC, H.264/MP4) (Solution: Check #html5-audio-video)
  • no user RLZ identifier
  • no user metrics (usage statistics) (opt-in option)
  • no crash report (opt-in option)
  • More details on the official site, focused on Linux.

Some developers maintain #chromium-forks that offer more features and enhancements. Thanks a lot for developers! ;)

And if you want to follow new Chromium features, check the Google+ posts of the Chromium Evangelist at Google

Google API keys

To use Google services (Sync, Translate, Contacts, Hotword...), Chromium needs Google API keys.

Chromium can display a top message if the Google API keys are needed for Google services:
Google API keys are missing. Some functionality of Chromium will be disabled. Learn More
How to create your own Google API keys?
With your own Google API keys, many Google services (Sync, Translate, Contacts, Hotword...) will work.

(Based on an original tutorial wrote by Chris Van Wiemeersch)
  1. Clicking on that yellow disclaimer message takes you to the confusing API keys docs page.
  2. If you aren't already, subscribe to the chromium-dev[at] mailing list. (You can just subscribe to the list and choose to not receive any mail. FYI: the Chromium project restricts the APIs to those subscribed to that group - that is, Chromium devs.)
  3. Make sure you are logged in with the Google account associated with the email address that you used to subscribe to chromium-dev.
  4. Log in to the Google Cloud Platform, and select an existing project or press the "Create Project" button.
  5. From the project's API Manager, select the Credentials tab in the sidebar.
  6. Create a Browser API Key.
  7. You'll see a modal with an API key. Copy and paste that somewhere.
  8. Now create an OAuth Client ID.
  9. After you complete all the steps and the "content screen", you'll be presented with a modal with your Google Client ID and Client Secret.
  10. You'll need to set three environment variables:

On #windows: Launch Command Prompt (cmd.exe) and enter the following commands:
setx GOOGLE_API_KEY yourkey
setx GOOGLE_DEFAULT_CLIENT_ID yourclientid
setx GOOGLE_DEFAULT_CLIENT_SECRET yourclientsecret

On #mac and #linux: Plop these in your ~/.profile file:
export GOOGLE_API_KEY="yourkey"
export GOOGLE_DEFAULT_CLIENT_ID="yourclientid"
export GOOGLE_DEFAULT_CLIENT_SECRET="yourclientsecret"

Now launch Chromium. Enjoy! ;)
How to disable Google API keys?
Without Google API keys, many Google services (Sync, Translate, Contacts, Hotword...) will not work.

On #windows: Launch Command Prompt (cmd.exe) and enter the following commands:
setx GOOGLE_API_KEY "false"

Now launch Chromium. Enjoy! ;)


Flash is a deprecated multimedia software platform. Since 2015, the Flash #npapi plugin is discontinued. So, PepperFlash (PPAPI) is the only one plugin for Chromium. PepperFlash is secure because it works in a sandbox. In short, it executes in its own process, separate from the browser's rendering engine.

How to quickly install Flash?
On Windows and macOS, Chomium find PepperFlash itself (= without #command-line-flags)

  1. Install PepperFlash (PPAPI) from Adobe website.
  2. Check chrome://flash
  3. Disable "Ask first" in the chrome://settings/content/flash page. (screenshot)
  4. Test if animation works on the Flash Player versions page.
  5. Enjoy!
How to manually install Flash?
This is a full manual installation tutorial.
(If Google Chrome is already installed, go directly to the step 3: #add-command-line-flags)

1. Get PepperFlash (PPAPI)

This plugin is a non-free (proprietary) software developed by Adobe, and distributed bundled with Google Chrome. So get it from the official sources: Adobe or Google.

1.1 From Adobe

Different official ways:
After install, the plugin path will be:
- On a 64-bit #windows:
  • C:\Windows\system32\Macromed\Flash\pepflashplayer64_[version].dll (64-bit version)
  • C:\Windows\SysWOW64\Macromed\Flash\pepflashplayer32_[version].dll (32-bit version)
- On a 32-bit #windows:
  • C:\Windows\system32\Macromed\Flash\pepflashplayer32_[version].dll (32-bit version)

1.2 From Google Chrome

Canary channel:

1.3 From an unofficial source

(Use an online service to prevent #malware)
  1. Search "PepperFlash" or "PPAPI" at [RU] or
  2. Download and open the .7z archive
  3. Get "pepflashplayer.dll" (rename it, if needed) and "manifest.json" files.

Optionally, get the Flash version number:
(If you want to see the correct version number on Chromium internal pages)
  • On all platforms, open the manifest.json text file in the PepperFlash folder.
  • On Windows, you can do a right-click → Properties → Details, on the .dll file

2. Change the plugin directory

If you want, prefer a short path for the plugin. It will be easier for the next step. ^^
Example on Windows: Put this .dll file in a path like C:\PepperFlash\ (Create the directory if needed)

3. Add command-line flags

Use these #command-line-flags:
  • --ppapi-flash-path=[plugin path]
  • --ppapi-flash-version=[plugin version]
  • And optionally --allow-outdated-plugins to disable browser notifications about outdated plugins

On #windows, create a Chromium shortcut. Then go to its properties and edit the target field: --ppapi-flash-path="C:\PepperFlash\pepflashplayer.dll" --ppapi-flash-version="" --allow-outdated-plugins
On #mac, you will need to launch it from the command-line (in the Terminal): /Applications/ --ppapi-flash-path=/Library/Internet\ Plug-Ins/PepperFlashPlayer/PepperFlashPlayer.plugin --ppapi-flash-version= The "&" at the end is not a typo. It is there to make sure Chromium is launched in a separate thread. Without the "&", Chromium would exit as soon as you quit the Terminal. Moreover, to simplify the Chromium launch, check How to create simple Mac apps from shell scripts (Archive: 1). Also see the #comment-566 and #comment-344.

4. Restart the browser

Relaunch it to apply changes.

5. Check the installation

6. Enjoy!

Now, even after browser updates, Chromium uses PepperFlash. ^^

NPAPI plugin support

NPAPI is deprecated. Chromium build 45.0.2416.0 (331982) is the last version which still has NPAPI plugin support enabled via chrome://flags or group policy registry. (sourceNPAPI deprecation)

How to still use NPAPI plugins?
Few ways:
More info on site archives:

HTML5 audio/video

By default, Chromium does not support proprietary codecs (AAC, H.264/MP4) in the HTML <audio> and <video> elements.

How to use Chromium with all audio/video codecs?
Few ways:
  • Use Nik builds on #windows or Marmaduke builds on #mac. All codecs are enabled ^^
  • or compile Chromium from #source-code with desired codecs
  • or install an older version having ffmpegsumo file (Ex: 333350, 333334, 333283, 333258...)
  • or choose other #browsers
  • On #linux, you can use Chromium with proprietary codecs

Before 4 June 2015, we used an alternative with the Google Chrome ffmpegsumo file and our Patch HTML5 Media extension. More info on site archives:

Check HTML5 audio/video support at

If there is a video issue, disable hardware acceleration (see #browser-crash).


1. Internal pages

To access to all internal pages, use chrome://about. Copy and paste this special URL directly into the address bar (omnibox).
Obviously, this special URL works only in Chromium and Google Chrome.

About browser plugins
Since version 57, the chrome://plugins page no longer exists. (official source)


Few internal pages:
Note: About configuration settings, there is nothing similar to Firefox's about:config in Chromium.

Example: How to clear DNS cache?
Open chrome://net-internals/#dns and click on the Clear host cache button.

2. Keyboard shortcuts

To use keyboard shortcuts (on Windows, Mac and Linux), check this full list of official shortcuts... and this one if you are developer. Most of the shortcuts are similar to IE, Firefox or any other browser.

3. User data directory

About your bookmarks, profile... it is important to know where is stored your user data.

4. Command-line flags

There are command-line flags (or "switches") that Chromium accept in order to enable particular features or modify otherwise default functionality. Note flags often contain experimental or obsolete code, so they tend not to stick around for long.
Example: How to start Chromium directly in incognito (or private) mode on Windows?
Add flag at the end of the Chromium shortcut and restart the browser. (screenshot)
"C:\{...}\Chromium\Application\chrome.exe" --incognito

5. External extension installation

How to install an external brower add-on?
  1. Get source .crx file of any extension directly from the Chrome Web Store via CRX Viewer, Chrome extension source viewer, Get CRX or via a site like Chrome Extension Downloader, Crx4Chrome
  2. Go to chrome://extensions
  3. Drag and drop the .crx file on the page

If it does not work...
  1. Unzip the .crx file
  2. Go to chrome://extensions
  3. Drag and drop the unzipped folder on the page... or click on Developer mode then Load unpacked extension...

About updates:
  • You have to update manually
  • You can update when you want! ^^
  • If ever a new version sucks, just re-install the previous one

6. Source code

Before all, check the official guide for developers.

Official links to easily get or see the full Chromium source code:
Interesting info:

7. Older version

Never update your browser with a very old version. It even does not start.

To downgrade Chromium installed with the Installer (.exe):
  1. Open Chromium and check its actual version at chrome://version
  2. Close Chromium.
  3. Uninstall Chromium WITHOUT to delete your #user-data-directory. It is an option of its uninstaller. (screenshot)
  4. Get the Installer (.exe) of an older version (from the → download/ page or Snapshots repository about "official" builds)
  5. Execute it to install Chromium.
  6. Open Chromium and check the new installed version at chrome://version

8. Browser crash

You have encountered a browser crash or issue :/

Few ways to help you:

Also you can use #command-line-flags: --disable-extensions, --disable-gpu, --disable-accelerated-video-decode...
Note the incognito mode disables all extensions by default.


This is a free and simple API for developers to update Chromium to the latest good build via a bash (shell) script, a browser extension... Read my #notes.

Please, do not use this API to build other websites. To prevent abuse, the site can audit each API request.

API details
GET request parameters:
  • os(required) windows or mac or android
  • bit(optional • 64 by default) 64 or 32
  • out(optional • json by default) json or string or xml or revision

chromiumwindows or mac or android
  • architecture(string) 64-bit or 32-bit
  • timestamp(integer) Unix time of this release built on the Chromium Buildbot server
  • editor(string) The Chromium Authors
  • channel(string) dev
  • repository(string) snapshots
  • version(string) (like xx.x.xxxx.x)
  • revision(integer) Git revision's commit position
  • commit(string) Git revision's commit hash

Basic examples:
Example to get the latest build with the outrevision parameter:


1. Open-source browsers

2. Chromium forks

In simple words, a fork of Chromium means Chromium engine is used to create another web browser.

Proprietary browsers:
(developed by official contributors of the Chromium #project)
I do not recommend:
Why not recommended?
Because all of these browsers are closed-source, outdated, based on Chromium like Google Chrome... and most of the features they remove don't even exist in Chromium, in the first place. Control your personal info and #privacy yourself ^^

Moreover, InsanityBit explains this very well on his blog: SRWare Iron Browser – A private alternative to Chrome? (2012 • Archives: 1, 2)

Note if a new browser with "better privacy" than Google Chrome is based on Chromium and is fully open-source, it should be ok for me. But... Google is famous. Its private policy and marketing strategy are well known. So you have to ask you some questions. Do you trust in an unknown team more than Google? Is an outdated Chromium fork?
Few free and open-source Chromium forks:


For a better privacy protection, use open-source #browsers like Chromium or Firefox. Do not forget: It is open-source does not mean it is secure and respects user privacy. Moreover, security ≠ privacy. If your browser is fully "open-source", it means that somebody with the capability can review the #source-code. With versioning tools like SVN or Git, it is easier for developers to find malicious code (Ex: Chromium downloads a Chrome extension as a binary without source code → corrected 7 days after the report). Only an open-source code allows such defense. This is better for secure browsing and user privacy. The security of Chromium is very solid. While I recommend Firefox as the most reliable browser for privacy enthusiasts (cf. about:config settings, better content-filtering and ad blocking extensions), Chromium is probably a reasonable alternative for everyday web browsing.

My way (but do as you like ^^):
  1. Modify your #hosts-file to stop "natively" domains who serve ads, spyware and malware
  2. Use a VPN with strong encryption for your whole OS or router (It is better than browser VPN/proxy #extensions)
  3. Use an up-to-date web browser
  4. Change few #browser-settings
  5. Install few #extensions

You cannot be anonymous on web even using a VPN or TOR network. It is a myth that you cannot be tracked online. There a lot of technologies to get user data. Read the #guides for more info. However, you can protect your privacy against tracking and profiling tools. These tools are everywhere today. You can find them in software, app, extensions and websites.

1. Browser update

The reason for updating to the latest version is security. As security threats are found, they are fixed. Using an old version expose user to a number of security holes and privacy issues. Browsers are far more subject to hacking than other software.

2. Browser settings

Adjust all settings and advanced settings in chrome://settings:

3. Hosts file

Modify your hosts file to prevent your OS from connecting to domains who serve ads, spyware and malware. This will increase your OS security and save bandwidth.


4. DNS services

By default you are using the DNS servers of your ISP but you do not have to stick with them. Before to choose one, compare DNS performance. Free alternative Internet DNS services for personal use:

5. Web search engines

Note: Few #extensions exist to protect your privacy on search engines.

Search engines

Metasearch engine

If you are a web developer, use your own metasearch engine yourself ^^

6. Extensions

Note: Extensions hosted on Chrome Web Store are updated via the Chrome update mechanism (cf. Chromium source code) which developers and users do not control. For a manual installation, read the #external-extension-installation part.

Priority to open-source (no code obfuscation) extensions for Chromium and Firefox:

Block ads, trackers, scripts and popups

uBlock Origin + uBO-Extra

Stop everyone from tracking you


Force to use secure connection of websites (https://)

HTTPS Everywhere

Stop link redirection in Google, DuckDuckGo and Yandex search pages

Google search link fix

Control the HTTP Referer on a per-site basis

Referer Control

Prevent canvas fingerprint

Canvas Defender

Emule locally CDN


Prevent WebRTC IP leak

WebRTC Leak Prevent

Unblock websites with a browser VPN/proxy

  • Download: store, amo
  • Alternatives: TouchVPN, HidemanVPN, TunnelloVPN, Hotspot Shield
  • My advice: Prefer to pay for a safe and secure VPN provider protecting your whole OS ; or use a free VPN service without registration.
  • My advice: Do not use Hola!, ZenMate or Betternet in their free version. Hola! is a botnet. Betternet shares/sells user data to third-parties. In its free version, ZenMate needs a registration.

Display sites quality

WOT (Web of Trust)
  • Download: store, amo
  • My advice: Do not share your data. (WOT settings → Real-time protection → Set to off)

7. Tools

8. Guides

9. Tests

Reputable and reliable sites to show or prevent user data tracking:


Your antivirus has detected a malicious software in Chromium files.

False positive?

You have downloaded Chromium from a reliable source (#notes) and maybe also used an open-source #updater. In this case, it is surely a false positive. The detection is generic (heuristic). There is absolutely no backdoor or other malware inside. Remember that the full #source-code is available. You will get a similar result if you compile Chromium yourself.

Note a thing relative to Chromium browser:
  1. Chromium has no digital signature (unlike Google Chrome)
  2. VirusTotal is a Google service which use its Trusted Source project to limit false positives... in Google Chrome (because it is digitally signed), not in Chromium.
  3. So, unsigned Chromium + VirusTotal service = More chance to get an antivirus alert.

False positive reports known for few years ago:

Authentic malware?

Yes. Obviously, it is also possible.
  • The common entry methods for Chromium virus are freeware downloads as bundled software (bundleware) and spam e-mails. It means Chromium has been silently installed via another software. Do not forget Chromium is free and open-source. So malware writers use Chromium to push malicious code on to your system. Remove this "fake" Chromium version or suspicious web browser (like BeagleBrowser, BoBrowser, BrowserAir, Chedot, eFast Browser, Fusion Browser, Mustang Browser, MyBrowser, Olcinium Browser, Palikan, Qword Browser, Torch, Tortuga Browser...).
  • The other way is about a compromised Chromium repository on a reliable source (#notes).

Check files on your OS

Free tools to scan your system:
Free online services (without registration) to check your file:
If you find an issue:
  • Contact your anti-virus or anti-malware support
  • Report it on the official Chromium supports. For links, see my #comment-1 below.

Chromium updater

To update Chromium automatically.

As always, never install a closed-source software especially if you have never heard it before! SearchCode, GitHub (and its Gist service) are good places to find good stuff. So, try these open-source Chromium updaters:

Updater on Windows

Updater on macOS

Updater on Android

Discontinued updaters

Thanks a lot for all developers!
I do not support these tools. Please, contact the developers for thanks, issue, help...


Quick access: #Read the latest comment

Now, you can post anonymously remarks and suggestions about this site. Do not hesitate! ;)

Please, DO NOT report bugs by a review. Use the official issue tracker or chromium-discuss/dev topics:!forum/chromium-discuss!forum/chromium-dev

Also, I prefer direct links. You are not on Twitter ;)

Thank you for your attention!
Reload this page to display older comments

30 latest comments

Apologies about misspelling your name Nik... I keep doing that on accident.
@Dustyn: Nik is probably very busy! ;)
If sync is important for you, create your own #google-api-keys
Any update on chrlauncher?
Nik: Wow, that was a fast response! And I see a new version has indeed been published! Thanks so much Nik for your continuing efforts! It's greatly apricated good sir! Going to install this now. :D
@jerry, no it does - Auto sign in is engraved in Chromium.
Colin Tennyson
I noticed the following:
I'm on a Windows 64-bit system, so I downloaded the 64-bit version

From the .manifest file:


For comparison I tried this version:

From the .manifest file:


So I'm assuming now that only 32-bit versions of Chromium exist, and all the links to 64-bit versions contain a 32-bit version.

That raises the question:
If the link to a 64-bit version contains a 32-bit version anyway, why bother to offer a link that says: '64-bit version?
To placate visitors who would otherwise complain no 64-bit version is available

Is my hypothesis too simple? Is there more to it?

Colin Tennyson
Where is the no-sync for "69.0.3497.100" for x64 Windows? I only see a sync variant for this version, and no-sync is "71.0.3572.0 (597399)" which is a dev version...
If anyone seeking for a stable version on Android that can disable webrtc fingerprinting, Brave browser can do that, which is built on the latest stable Chromium version. After months of searching and trying many browsers, I finally decided to stick with this one. It is basically a stable Chromium Android build with http->https conversion, ad blocking and fingerprinting protection features. It is also an open source project.
@Colin The relatively generic identifier "win32" in the manifest basically just means the build is for "Windows."

Load the browser and point it towards the URL chrome://version to see the bit type of the Windows build. For example:

Chromium 72.0.3580.0 (Official Build) (64-bit)
Revision 683272efae485d924651022da3a76ed6977470f8-refs/heads/master@{#599494}
OS Windows

There are numerous other ways to check as well, ranging from command line utilities to debugging apps to even using notepad.exe to search an executable for its PE type. Take Sigheck for example:

D:\Chromium\Application>sigcheck64 chrome.exe

Sigcheck v2.60 - File version and signature viewer
Copyright (C) 2004-2017 Mark Russinovich
Sysinternals -

Verified: Unsigned
Link date: 1:00 AM 10/13/2018
Publisher: n/a
Company: The Chromium Authors
Description: Chromium
Product: Chromium
Prod version: 72.0.3580.0
File version: 72.0.3580.0
MachineType: 64-bit
I'm really pissed that Chromium devs removed Tab Audio Muting flag from v71+. With this flag we could just click on the speaker indicator, and the site would be muted. Now, we need to right click on the tab and select ‘Mute Site’ option. There's no such keyboard shortcut for this, either.
@Anon3871 I have not used it, so YMMV, but you might take a look at the following tab muting extension that appears to offer keyboard shortcuts, blacklists, whitelists, etc.
The following 64-bit ThinLTO build targets Intel Skylake, Kaby Lake, and later Intel processors. YMMV.
how can I update #windows-64-bit-official portable version?
Chromium for 64-bit Windows - All Codecs - Tuesday, 16 October 2018

Chromium 72.0.3582.0 (Official Build) (64-bit)
Revision ec5ef4854713d5f8eaf67dcef2acad1c67cb925f-refs/heads/master@{#599622
OS Windows

No Sync - WebRTC - No Widevine

SHA1 DE94FEE0FDDB44FAB8883D7413037BF7258024FE

Thin LTO builds and building with the "tip of the tree" clang/LLVM seems to be broken, probably just a temporary problem. Takes 2.5 times longer to build a Full LTO clang/LLVM than it does to build bog standard Chromium!

Regardless, this is the version of Chromium that I'll be using for the next 4 to 6 weeks.
@marmaduke Duplicate symbols perhaps? If so and you are building LLVM separately, try this modification before building LLVM.


Around line 393 to 410, comment out the duplicate symbol reports.

// else
// reportDuplicate(S, F);

// if (!cast<DefinedRegular>(S)->isCOMDAT())
// reportDuplicate(S, F);

Also set 'treat_warnings_as_errors = false' in your Chromium build arguments if not already. There has been a recent change in LLVM -Wshadow reported warnings for enumerators. Devs are working on fixing the warnings' reported code segments, but otherwise, you can ignore those warnings for now.
@marmaduke, @RobRich, @nik: Thank you for your all work, time and sharing! ;)

@Evangelical: Agree. Auto sign-in is engraved in Chromium but works only with the "sync" (or valid #google-api-keys) Chromium version.

@Colin Tennyson: "win32" in the manifest file is a generic identifier (like RobRich said!) This is really a 64-bit version. You cannot install this version on a 32-bit Windows.

@Heyman: It is currently a known issue of chrlauncher. The binaries are placed in a sub folder named after the version. So copy-paste the content and remove the parent folder.


I always do a Full LTO build of the latest LLVM. The Duplicate symbols problem was driving me up the wall, particularly as the problem occurs at the very end of a Windows Chromium build.
Thanks to marmaduke there are new v70.0.3538.67 binaries for macOS!

I have also just updated the homebrew tap, so your next "brew update && brew cask upgrade marmaduke-chromium" should install the new binaries.
@cpbotha - appreciate the support.

@RobRich - What are your recommended polly parameters?

Managed to get Mac Chromium LTO and CFI builds working again.

Chromium for 64-bit macOS - All Codecs - Wednesday, 17 October 2018
Chromium v70.0.3538.67-r587811-macOS

- only for macOS 64
- with codecs (h264, h265, flac, xvid, AV1, etc...)
- official build
- Stable
- SDK 10.14
- Xcode 10 (10A255) GM Seed
- Compiled under macOS 10.14 build 18A389
- Clang/LLVM 8.0.0 342458

No Sync • WebRTC • No Widevine • ThinLTO • CFI (Will probably make this the standard)
SHA1 B74A3AD58CBDBCAB51BC5B23E71B8124F8A875A1

==== Additional configuration ====

NO Swiftshader dynamic libraries! (Who uses them?!)


mv third_party/libsrtp/VERSION third_party/libsrtp/LIBSRTP_VERSION

cflags = [ "-O3","-flto=thin"]
ldflags += ["-flto=thin","-fvisibility=hidden", "-fsanitize=cfi" ]
After re-analysis of various Polly configurations, I have dismissed some of the extra options I previously used as they were not really doing much to help performance and likely increasing build times.

Try starting with:

"-mllvm", "-enable-newgvn",
"-mllvm", "-polly",
"-mllvm", "-polly-delicm-max-ops=10000000",
"-mllvm", "-polly-dependences-computeout=5000000",
"-mllvm", "-polly-invariant-load-hoisting",
"-mllvm", "-polly-vectorizer=stripmine",
"-Xclang", "-vectorize-loops",

I am using NewGVN right now as hoisting for regular GVN currently is disabled due to some reported performance regressions.

You can lower the profitability limit down to 40+ instructions per loop, though YMMV on real-world returns.

"-mllvm", "-polly-detect-profitability-min-per-loop-insts=40",

I also applied a source code mod to Polly to potentially help with loop fusion when configured to max, though it too is a YMMV situation, as I need to do further testing. I will try to let ya' know something about it in the near future.

I also suggest benchmarking your browser build at different optimization levels regardless of LTO optimizations. Depending upon various factors, you might find building the max/speed code targets at the /O2(-O2) defaults to be as fast or faster than -O3. Could be due to code bloat, caching, register pressure, etc.

Likewise, I have dropped the regular optimization targets back to their /O1(-Os) defaults as well. Remembering back to old MSVC PGO build stats, there are only like 300 or so functions even built for speed versus size for a profiled build. ;)

I actually have a internal build from earlier this week with all optimized targets set to -Os, though with a tweaked LLVM configuration plus dramatically increased inlining limits for V8. It is supposedly slightly faster in Basemark Web 3.0 *without LTO* versus a recent ThinLTO build. o.0 "Supposedly" as I really do not put much importance on BW3 scores due to variability in results, at least on my test platform. Anyway.

BTW, you can now set ThinLTO optimization (at lto_opt_level = 2) from the build arguments.

use_thin_lto = true
thin_lto_enable_optimizations = true

If otherwise setting manually on the build config, I suggest also adding "-fwhole-program-vtables" to the cflags or ldflags as appropriate for the target platform to enable whole program devirtualization.
@Anon3882: it's not a bug, it's a feature :)

Thanks. Will do some testing and benchmarking.
Oops. Missed a line or two. ;)

"-mllvm", "-enable-newgvn",
"-mllvm", "-polly",
"-mllvm", "-polly-delicm-max-ops=10000000",
"-mllvm", "-polly-dependences-computeout=5000000",
"-mllvm", "-polly-invariant-load-hoisting",
"-mllvm", "-polly-vectorizer=stripmine",
"-Xclang", "-vectorize-loops",
"-Xclang", "-vectorize-slp",
"-Xclang", "-Rpass=loop-vectorize",
"-Xclang", "-Rpass-analysis=polly",

The rpass lines are optional. I sometimes take a glance to get a general feel for SCoP rates and vector stats when building.
Video playback doesn't work on this site. (a url that always streams something )
Can anybody please do v70.0.3538.67 nosync+nowidevine for Win x64? Thanks
I noticed that with Nik's recent Chromium stable builds for M69/M70, they have all had an extra process (Audio Service) which is running as a 'utility' process, unsandboxed, and running at Medium IL. This is actually an upcoming feature that is expected, where they are taking the Audio Service out of the browser process and running it OutOfProcess and will eventually be sandboxed.

I know that Nik compiles his Chromium builds essentially as default build settings, therefore I assume that Google Chrome devs must be making a switch on their end for official Chrome builds to keep the Audio Service within the browser process currently. They must have some sort of compile time switch for this.

If anyone is concerned about this extra process which is unsandboxed and running at Medium IL, have no fear, there is a working command line argument which will tuck that Audio Service back into the browser process for now. I have confirmed that this command is working successfully, but keep in mind you have to run it everytime and therefore you can add this into your Chromium shortcut. I will be doing this for now until Chrome devs properly sandbox that Audio Service process and that is likely why official Chrome builds still have that kept within the browser process.

chrome.exe --disable-features=AudioServiceOutOfProcess
It is in the fieldtrial build config right now, or at least as of a recent source pull. It appears to be an ongoing project.

Paul Phillips
Is there a way to import Google Chrome data into Chromium (and vice-versa) without using a Google account?

Leave few words !

  • Advice: To prevent errors, copy/paste your comment to the clipboard before to send it. Keyboard shortcuts on Windows: CTRL+C → CTRL+V
  • Your comment will be automatically approved but not editable
  • Your avatar will be automatically created by an internal process (no third-party service)
  • Use a standard BBCode tag for rendering code snippets in a box: [code]***[/code]

Sorry, the form is not available on the mobile version!