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

Chromium is not available on XP and Vista since version 50. For help, version 49 works fine.

1. Chromium for 64-bit Windows only

Reference: Current stable version (Google Chrome): 62.0.3202.94 (499098) • Monday, 13 Nov 2017


Sync • WebRTC • Widevine • 62.0.3202.94 (499098) • Tuesday, 14 Nov 2017

No syncNo WebRTCNo Widevine • 62.0.3202.94 (499098) • Tuesday, 14 Nov 2017

  • The Portable version uses the free and open-source chrlauncher to install, update and launch Chromium.
  • sha1: 2d46af32240756de296f889e1e01f9c7e0e476a3 - chromium-sync.exe
  • sha1: 7667097f4896b0a504c4c08c7f6369382536c1f6 -
  • sha1: aa0b548f2e07661f0d7be86922ad31505dac6141 - chromium-nosync.exe
  • sha1: dfc97673ef8107fd8c6629cf1f108b29259f7676 -
  • List of changes
  • #source-code: follow the Nik guide
  • Source: Github repository (mirror: Zippyshare)


Sync • WebRTC • Widevine • 64.0.3259.0 (514062) • Sunday, 5 Nov 2017

No syncNo WebRTCNo Widevine • 64.0.3259.0 (514062) • Sunday, 5 Nov 2017

  • The Portable version uses the free and open-source chrlauncher to install, update and launch Chromium.
  • sha1: 092475c66c4f8721ec291edd326720a4abb93148 - chromium-sync.exe
  • sha1: ce4f6657082838d1a722d1a58ef9c92a6fd08665 -
  • sha1: 4674c96e29268f8b35129d563dac610143acd9dc - chromium-nosync.exe
  • sha1: 274eaf404f70a5ae41f37d3859a65eb348902dd5 -
  • Previous versions (win64)
  • #source-code: follow the Nik guide
  • Source: Github repository (mirror: Zippyshare)


No syncNo WebRTCNo Widevine • 64.0.3268.0 (515942) • Monday, 13 Nov 2017

  • The Portable version uses the free and open-source chrlauncher to install, update and launch Chromium.
  • sha1: 52df47ff7848212e99dd433e8dc451d4ea2ed1d0 - mini_installer.exe
  • sha1: a5114ae1e4d5815871e0aa96b745bbe6799d89b5 -
  • Previous versions (win64)
  • #source-code
  • Source: Github repository


No syncNo WebRTCNo Widevine • 64.0.3263.0 (515088) • Thursday, 9 Nov 2017

  • The Portable version uses the free and open-source chrlauncher to install, update and launch Chromium.
  • sha1: 8b54e48657b7fbbd9537a6a273d779ea1a099792 - mini_installer.exe
  • sha1: 0348d819ba4544f31cdda2c304f0921ff7c17972 -
  • Previous versions (win64)
  • #source-code
  • Source: Github repository

The Chromium Authorsdev64-bitwindows

64.0.3274.0 (517848, ac08508) • Monday, 20 Nov 2017

How to update it?
All of your settings, bookmarks, extensions, history, cookies will be saved. Do not worry!

Update with Installer:
  1. Download mini_installer.exe
  2. Close Chromium browser if opened
  3. Execute mini_installer.exe
  4. Wait for 2 or 3 seconds (Installation is silent)
  5. Open Chromium browser. It is updated!

Update with Archive:
The name of this archive is "" but it is really the 64-bit version!
  1. Download
  2. Close Chromium browser if opened
  3. Unzip
  4. Delete all the files from your installation directory
  5. Move the files from the unzipped chrome-win32 directory to your installation directory
  6. Open Chromium browser. It is updated!

Update with Portable:
  1. Download and unzip
  2. Execute chrlauncher.exe
  3. Close Chromium browser if a notification displays a new version
  4. Open Chromium browser. It is updated!



64.0.3264.0 • Thursday, 9 Nov 2017

This is an open-source and custom-built version of Chromium optimized for portable use. So, you can run it from an iPod, 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!



64.0.3250.0 • Wednesday, 25 Oct 2017

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
To update it: choco upgrade chromium

2. Chromium for 64-bit and 32-bit Windows

Reference: Current stable version (Google Chrome): 62.0.3202.94 (499098) • Monday, 13 Nov 2017


Sync • WebRTC • Widevine • 62.0.3202.94 (499098) • Tuesday, 14 Nov 2017

No syncNo WebRTCNo Widevine • 62.0.3202.94 (499098) • Tuesday, 14 Nov 2017

  • The Portable version uses the free and open-source chrlauncher to install, update and launch Chromium.
  • sha1: 209a3e54686df65a534034952c6e8aaa59016760 - chromium-sync.exe
  • sha1: 311a6b1998a12d0757f56ba0203f361030cdc413 -
  • sha1: 9a38c52cb44e73dddb8b9676abb23e767c21683e - chromium-nosync.exe
  • sha1: 4073b0663a897cb252a3bf66286e54e60af455a5 -
  • List of changes
  • #source-code: follow the Nik guide
  • Source: Github repository (mirror: Zippyshare)


Sync • WebRTC • Widevine • 64.0.3259.0 (514062) • Sunday, 5 Nov 2017

No syncNo WebRTCNo Widevine • 64.0.3259.0 (514062) • Sunday, 5 Nov 2017

  • The Portable version uses the free and open-source chrlauncher to install, update and launch Chromium.
  • sha1: 30fbbcef35fe9bbcd011faac9697c3811de5b205 - chromium-sync.exe
  • sha1: 062f024f15c8801c99d358b2cac60af7de053d53 -
  • sha1: deeca4e51b475eee0b4b3917cea27c4ef26efa44 - chromium-nosync.exe
  • sha1: ed751ca21efa8dfb4824d172a560d7191dd042a3 -
  • Previous versions (win32)
  • #source-code: follow the Nik guide
  • Source: Github repository (mirror: Zippyshare)

The Chromium Authorsdev32-bitwindows

64.0.3274.0 (517849, e9192c1) • Monday, 20 Nov 2017

Follow the same instructions as #windows-64-bit-official.



64.0.3264.0 • Thursday, 9 Nov 2017

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



64.0.3250.0 • Wednesday, 25 Oct 2017

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
To install it on a 64-bit Windows: choco install chromium --x86More info about options and switches

To update it: choco upgrade chromium


1. Chromium for 64-bit macOS only

Reference: Current stable version (Google Chrome): 62.0.3202.94 (499098) • Monday, 13 Nov 2017


62.0.3202.94 (499098) • Tuesday, 14 Nov 2017

To install it, double click on Chromium_OSX.dmg file you have downloaded. Then drag its icon on Applications folder. You may then "Eject" and throw away this disk image.

How to update it?
  • Use command Chromium → Check for Updates...
  • or install an extension created by the FreeSMUG team: Chromium Updater



Sync • No WebRTCNo Widevine • 64.0.3268.0 (515892) • Monday, 13 Nov 2017

No syncNo WebRTCNo Widevine • 64.0.3268.0 (515892) • Monday, 13 Nov 2017

Feedback appreciated - if demand will update once a month. Do no hesitate to write #comments ;)

  • sha1: 9be3a8676470a5958b5d7ca7cd9c87cba4407ffc -
  • sha1: 401fa47249e8d1c64970772944f4047280440867 -
  • Previous versions
  • Source: Github repository

The Chromium Authorsdev64-bitmac

64.0.3274.0 (517848, ac08508) • Monday, 20 Nov 2017

Unzip it on your computer. Double click on the unzipped folder to open it. Drag its icon on Applications folder.

How to update it?
Use a free and open-source #updater tool.


2. Chromium for 64-bit and 32-bit macOS

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


Reference: Current stable version (Google Chrome): 62.0.3202.94 (499098) • Monday, 13 Nov 2017


Chromium OS

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

Free and open-source releases:



To install the stable Chromium version:
  • use the Ubuntu Software Center and Update Manager
  • or type these commands about this PPA:
sudo add-apt-repository ppa:canonical-chromium-builds/stage
sudo apt-get update
sudo apt-get install chromium-browser

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

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

Info: Chromium on Ubuntu packages and source archives



To install and auto-update Chromium, use these commands:
sudo apt-get update
sudo apt-get install chromium chromium-l10n
(chromium-l10n is only used for localization and is optional)

Info: Chromium on Debian wiki and Debian packages


Linux Mint

There are different ways to install the stable Chromium version.

Based on Ubuntu:
Based on Debian (LMDE):



Available in the official repository.

Info: Chromium on Mageia Application Database



Available in the official repository since Chromium v52

Info: Chromium on Fedora Project wiki and Fedora cloud



Available in the official repository: Installer

Info: Chromium on openSUSE wiki and RPM resource chromium


Arch Linux

Available in the official repository.

Info: Chromium on Arch Linux wiki



Available in the official repository.

Info: Chromium on Gentoo packages



Available in the official repository.

Info: Chromium on PuppyLinux wiki and Puppy Linux Discussion Forum



Unavailable in the official repository. But you can install it! ^^
Check this article of Eric Hameleers to download and install the stable Chromium version.


Reference: Current stable version (Google Chrome): 62.0.3202.94 (499098) • Monday, 13 Nov 2017



Available in the official repository.

Info: Chromium on FreeBSD wiki and FreeBSD packages



Available in the official repository.

Info: Chromium on OpenBSD ports and OpenBSD packages


Reference: Current stable version (Google Chrome): 62.0.3202.84 (499098) • Thursday, 2 Nov 2017

There is no stable Chromium version for Android:

The Chromium Authorsdev32-bitandroid

64.0.3274.0 (517848, ac08508) • Monday, 20 Nov 2017

This ZIP archive contains 2 packages:


Reference: Current stable version (Google Chrome): 62.0.3202.70 • Thursday, 26 Oct 2017

Chromium on iOS is a big fake!

Check the official build instructions to understand that Chromium cannot use the existing content/implementation, which is based on V8/Blink and is multiprocess. Go your way! ^^


Obviously, you know this site is not the Chromium official website. As a regular user (not an expert), I created it 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 "Nightly" builds (using the official Snapshots repository).
  • This site gives to users a choice of builds: "Nightly" (also on its simplest download page), LKCR, 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, Opera, Yandex, Samsung, Intel, Facebook, Hewlett-Packard... and external contributors. Chromium is not designed by Google!

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 62.0.3202.94. In this version, there are 94 patches which correct many issues (bugs, feature requests, enhancements...). Because Chromium is open-source (#source-code), anybody can build it. You must be a developer to do this. Just get the current stable version (62.0.3202.94) from the official Git repository and compile it!

The stable version is used in:

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 (known as Snapshot, "Nightly" or "Raw" build) is compile of the Chromium code whenever there are submitted code changes. 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 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 (1 year ago). 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! ^^

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

In resume:
  • dev: Untested and may be unstable version, downloadable on the official site and my alternative webpage.
  • LKCR: Similar to "dev" version but for third-party build.
  • stable: The most stable version.

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
  • 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 built-in Chrome PDF Viewer (known as PDFium), on Windows OS
  • 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 (Solutions: Use an #updater • Use PPA on #linux)
  • no Google API keys (Solution: Check the #google-api-keys part)
  • no built-in Flash player (Solution: Check the #flash part)
  • no support of proprietary codecs (AAC, MP3, H.264) (Solution: Check the #html5-audio-video part)
  • 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 forks of Chromium 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

A yellow disclaimer message appear as a doorhanger:
Google API keys are missing. Some functionality of Chromium will be disabled. Learn More
Sometimes you need to use Google API keys to talk to some Google services (Sync, Speech, Hotword, Translate, Now, Hangout...). And then you Google a bit and follow all the instructions. But the Chromium Project's API keys page does a not-so-great of explaining how to do this, so I will.

1. Without your own Google API keys

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

Now launch Chromium. Enjoy! ;)

2. With your own Google API keys

(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 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. In the shell, type:
launchctl setenv GOOGLE_API_KEY yourkey
launchctl setenv GOOGLE_DEFAULT_CLIENT_ID yourclientid
launchctl setenv GOOGLE_DEFAULT_CLIENT_SECRET yourclientsecret

On #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! ;)


There is 1 type of Flash plugin for Chromium:
  • The PPAPI plugin: PepperFlash
  • The NPAPI plugin: Flash Player (#npapi)

PepperFlash is secure because it works in a sandbox. In short, it executes in its own process, separate from the browser's rendering engine.

The simplest way:
On Windows and macOS, Chomium find PepperFlash itself (= without #command-line-flags)

  1. Install Chromium (WebRTC must be natively enabled in Chromium. Check Nik builds on #windows or Marmaduke builds on #mac)
  2. Install PepperFlash (PPAPI) from Adobe.
  3. Check chrome://flash
  4. Disable "Ask first" in the chrome://settings/content/flash page (screenshot)
  5. Test if animation works on the Flash Player versions page.
  6. Enjoy!

Now, the 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

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)

Solutions to still use NPAPI plugins:
  • Switch to another browser like Firefox (Plugin roadmap, NPAPI deprecation) or Waterfox still supporting NPAPI plugins.
  • or install an older Chromium version (Ex: 331982, 331959, 331938, 331935...)
  • or install the IE Tab addon which allows users to view pages using the IE layout engine

More info on site archives:

HTML5 audio/video

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

  • Use Nik builds on #windows or Marmaduke builds on #mac. All codecs are enabled ^^
  • or compile Chromium from #source-code
  • 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:

1. Check HTML5 audio/video support

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 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, 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 install an older Chromium version:
  1. Uninstall your actual version
  2. Destroy the main folder, the #user-data-directory (and the registry entries, on Windows)
  3. Get your older version from the → download/ page or the Snapshots repository
  4. Install it. Enjoy!

8. Browser crash

You have encountered a browser crash or issue :/

Few ways to help you:
- To disable hardware acceleration: - To disable/enable a browser feature: chrome://flags
- To check for conflicting software: chrome://conflicts
- To disable extensions/add-ons: chrome://extensions

Also you can use #command-line-flags: --disable-extensions, --disable-gpu, --disable-accelerated-video-decode...
Note that 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, an add-on... Read my #notes.

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

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 Opera)... 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 (and security ≠ privacy). But, 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 easy for developers to find malicious code (Ex: Chromium downloads a Chrome extension as a binary without source code). Only an open-source code allows such defense. This is better for secure browsing and user privacy. While I recommend Firefox as the most reliable browser for privacy enthusiasts (cf. about:config settings), Chromium is probably a reasonable alternative for everyday web browsing.

My way (but do as you want ^^):
  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 #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. But you can protect your privacy against tracking tools. These user tracking tools are everywhere today. You can find them both in software 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. Free alternative Internet DNS services for personal use:

5. Search engines

Choose a web search/metasearch engine:
If you are a web developer, do it 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. Add-ons 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

Control the HTTP Referer on a per-site basis

Referer Control

Prevent canvas fingerprint

Canvas Defender

Emule locally CDN


Prevent WebRTC IP leak

WebRTC Network Limiter removed

Remove UTM tracking tokens from URLs

Tracking Token Stripper
  • Download: store, amo
  • Alternatives: Link Cleaner, Clean Links
  • Info: UTM

Display sites quality

WOT (Web of Trust)

Unblock websites with a browser VPN/proxy


Stop link redirection in Google and Yandex search pages

Google search link fix
  • If you use WOT (Web of Trust), do not share your data. (WOT settings → Real-time protection → Set to off)
  • About WebRTC: Extension can only blocks the leak of your IP address. It does not blocks WebRTC in the "core" of Chromium.
  • Browser VPN/proxy: Do not use Hola! or ZenMate. Hola! is a botnet. ZenMate needs a free user registration. (Prefer to pay for a safe and secure VPN service... or use a free VPN service without registration)
  • If you use Adblock Plus or AdBlock, disable "Acceptable Ads" option.
  • uBlock Origin (wiki) is pattern-based filtering, while uMatrix (wiki) is matrix-based filtering which gives you more control over the filtering process.
  • uBlock Origin can also protect against WebRTC IP leak.
  • Add filters to your ad-blocker via FilterLists website.

7. Tools

8. Guides

9. Tests

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


Your antivirus detects 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 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! More on #privacy...

These reports are known for few years ago:

Authentic malware?

Yes, it is 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, Fusion, MyBrowser, Olcinium, Palikan, Qword, Torch, Tortuga...).

Check files on your OS

Free tools to check your OS:
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:

For Windows:
For macOS:
For Android:
Browser extensions:
Discontinued projects:
Thanks a lot for developers!
I do not support these tools. Please, contact the developers for thank, 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

20 latest comments

@Warren Great feedback as usual, and appreciate you sharing benchmark data with the community.

Not sure what is happening with Speedometer. Could be a revision regression. Will consider it an outlier for now.

@Anon2660 Excellent!

@Aargl Do you have a direct link to the extension? It might just need a version compatiblity range patch, which I (or even you! :) probably could resolve. Then you could notify the developer to update with a quick fix.
@Marmaduke do you think we could get a new stable build for the release yesterday? No rush, just curious :)

I intend to maintain the MacOS stable build. At the moment I'm refining the build process. Give me a few days. The intention is to build (ALL CODECS):

(I) No sync, No Widevine, No WebRTC
(ii) Sync, Widevine, WebRTC


I've built an Apple LLVM (with polly)

- cmake -G Ninja -C /volumes/disk1/clang/llvm/tools/clang/cmake/caches/Apple-stage1.cmake ../llvm
- ninja stage2-distribution

When building Chromium, where do I place the Polly Clang flags: "-O3 -mllvm -polly"?

I've tried //build/config/mac/

# Without this, the constructors and destructors of a C++ object inside
# an Objective C struct won't be called, which is very bad.

cflags_objcc = [ "-fobjc-call-cxx-cdtors","-O3","-mllvm","-polly", ]

cflags_c = [ "-std=c99" ]
cflags_objc = cflags_c
cflags_objc += [ "-O3","-mllvm","-polly", ]

But I'm not sure the polly parameters are being used.
@marmaduke See the optimization section of:


You will need to edit the Clang cflags with the "-O3","-mllvm","-polly", parameters as in your above comment. Start with the optimize_max and optimized_speed subsections, as those are the hottest code sections. Get them working with O3+Polly, then move to the standard optimize sections later if desired. If you want to watch what Polly is doing, add "-Xclang", "-Rpass-analysis=polly", to the cflags.

Note that ThinLTO currently does not support auto vectorization, so Polly does not work with it. As it stands ThinlTO is much more likely to generate better results anyway for a standard build. You still can pass -O3, though, which is a good starting point for compiler optimization assuming you do not care about output file sizes.

Conversely, FullLTO supports autovec, plus I am modifying LLVM and Polly parameters to perform additional optimizations, increase SCoP rates, etc. I have kept the Polly public builds rather conservative. My Polly internal builds currently pass something like 50-60 custom cflags parameters. Hopefully more details to follow in the future.


The Apple flavour of LLVM does not appear to support ThinLTO.
@marmaduke No prob. If you need further help with setting the cflags, just let me know. Get the basic cflag modification working, and I can toss some other potential LLVM optimization ideas your way. :)

I know there are ThinLTO conditions for Mac in \build\config\compiler\, but as with some things in the Chromium build config, that does not mean it works as expected.

Are you explicitly using the LLD linker in the gn build args? I suppose the better question is does LLD even link on Mac?


LLD does not link on the Mac.

Read this guy's thesis, then settled on the following parameters:

[ "-O3",
"-mllvm", "-polly",
"-mllvm", "-polly-ast-use-context",
"-mllvm", "-polly-opt-fusion=max",
"-mllvm", "-polly-opt-maximize-bands=yes",
"-mllvm", "-polly-run-dce",
"-mllvm", "-polly-dependences-computeout=0",
"-mllvm", "-polly-dependences-analysis-type=value-based",
"-mllvm", "-polly-position=after-loopopt",
"-mllvm", "-polly-run-inliner",
"-mllvm", "-polly-rtc-max-arrays-per-group=40",
"-mllvm", "-polly-register-tiling" ]

I'm not really sure of the benefits of Polly: the greatest gain seems to come from compiling a bespoke LLVM. The Apple influenced version
of LLVM (and the default Chromium LLVM) produces efficient code and does vectorization by default.

(Thin)LTO is poorly supported and appears not to be a concern on the Apple Chromium platform.

Well, I've learnt a bit more about the Chromium build process, and reached the conclusion that Google/Chromium/Chrome should stop being so
frivolous: less time designing emojis; and more writing legible and valid documentation.

Polly works with the LLVM autovec, plus Polly has its own stripmine auto vectorizer if you want to try it. Big YMMV on stripmine, though.

If doing a local build, look into setting the tiling values for cache size, cache associativity, fma latency, etc. to match your processor. If doing a public build, you can explicitly disable tiling if desired so you are not tiling for a specific chip. IIRC, the defaults in the source are for a Sandy Bridge i7.

You can remove position and early inliner statements IMO. Polly now runs before the LLVM autovec stage by default, which is supposed to be the "preferred" position. The early inner was for when it ran at the front-end of LLVM.

Take care with computeout=0 as it could take awhile or even run away due to not being bound. The default is 500000, which I have found to be generally okay for most Chromium builds.

For a general Polly build, I tend to lean towards something like the following:

"-mllvm", "-polly",
"-mllvm", "-polly-unprofitable-scalar-accs=false",
"-mllvm", "-polly-detect-profitability-min-per-loop-insts=40",
"-mllvm", "-polly-ignore-aliasing=true",
"-mllvm", "-polly-tiling=false",
"-mllvm", "-polly-stmt-granularity=scalar-indep",
"-mllvm", "-polly-invariant-load-hoisting=true",
"-mllvm", "-polly-enable-polyhedralinfo=true",
"-mllvm", "-polly-check-parallel=true",
"-mllvm", "-polly-check-vectorizable=true",
"-mllvm", "-polly-prevect-width=32",
"-Xclang", "-vectorize-loops",
"-Xclang", "-vectorize-slp",
"-Xclang", "-Rpass-analysis=polly",
"-Xclang", "-Rpass=loop-vectorize",

Prevectorization width has a moderate impact here. I drop minimum loop instruction profitability to 40, which Polly devs suggest in the source for "interesting" interchange and transform opportunties while still preserving some profitability analysis.

The rpass switches show you what autovec and Polly are doing. Can be helpful for monitoring changes, plus you can log the terminal output if desired. I use wtee on Windows. I suspect Mac has the similar tee command like Linux.

BTW, I forgot before but ignore my Xclang statements. I deal with clang-cl on Windows versus you dealing with native clang on Mac. clang-cl is more about MSVC switch compatibilty, thus the need for Xclang to pass some of clang's own switches on Windows.
@beast-usa: I copy you!
Still have to switch to FF in order to run NetFlix
Would really appreciate a fix
I have an experimental FullLTO build to share. No Polly this time, but I am leaning heavy on potentially breaking compiler optimizations, plus FullLTO is allowing me to use autovec. I have not found anything broken, though I might should add "yet" to that statement. ;)

No formal numbers, but I did toss a couple of JavaScript benchmarks at the build. I noted minimal to possibly modest gains on my modern Core i5 notebook, while the gains looked more impressive - at least IMO - on my older Opteron build box.

Chromium 64.0.3271.0 (Official Build) (64-bit)
Revision 9fb91d70045741cdcbfad8df694abb5845000fbb-refs/heads/master@{#517198}
Compiler clang (+lld + fulllto +extended_compiler_optimizations) | sha1: ab8c0fe9074d1e46be006c14119cde5b41ba7e93

mini_installer.exe | sha1: 1b0280c5bc641273e07ca31fe873cbb8b2d70a0f

ThinLTO currently does not support autovec, but I might eventually roll a couple of the other optimizations into my ThinLTO build.


@Fred + beast-usa I will do a local build with Widevine to try maybe seeing what is happening with Netflix. Might be a day or two assuming how I feel.
Jimmy Savile

Widevine tends to work best with the stable builds.



+#include "third_party/widevine/cdm/widevine_cdm_common.h"

+#define WIDEVINE_CDM_VERSION_STRING "undefined"
+#define WIDEVINE_CDM_VERSION_STRING "" //find current version from json file.


Obtain current Widevine files from Chrome stable and place in respective position in the equivalent Chromium stable. (For testing purposes!)

Should work, but might require a revised browser header.
= RobRich's Experimental FullLTO build - Chromium 64.0.3271.0 (64-bit) [17th Nov 2017]

Basemark Web 3.0 (higher is better): 1203.19 -
Peacekeeper (higher is better): 7015 -
JetStream 1.1 (higher is better): 264.01 ± 4.1280
Octane 2.0 (higher is better): 51314
Kraken 1.1 (lower is better): 753.6ms +/- 0.8%
Dromaeo V8 (higher is better): 2449.42runs/s -
SunSpider 1.0.2 (lower is better): 168.1ms +/- 1.0%
Speedometer 2.0 (higher is better): 127.3
ARES-6 (lower is better): 17.88 ±0.28ms
MotionMark 1.0 (higher is better): 790.37 ±25.87%

Performed with default fresh profile no add-ons, previous benchmark & PC specs here: #comment-2658
@Warren As always, thanks Warren! :)

Figured it would be a mixed bag, especially on a modern processor. I noted better percentage improvements in informal SunSpider, Kraken, and SunSpider testing on my older Opterons than my Kaby Lake i5. I should dig up my old Pentium T-whatever notebook to see about performance on older Intel processors.

I am going to roll in Polly next to see about maybe improving some of the more intensive operations. Wish ThinLTO supported autovec and Polly, as waiting on a FullLTO build can be annoying. Not as bad as PGO, but still time consuming.
@RobRich, thanks for trying to figure out what's happening with NetFlix!
Chromium for 64-bit macOS - All Codecs - Saturday, 18 November 2017

Chromium 62.0.3202.94 (Official Build) (64-bit) - Stable

Revision 937db09514e061d7983e90e0c448cfa61680f605-[refs/heads/master@{#499098}]


- only for macOS 64
- with codecs (h264, h265, flac, xvid, etc..)
- official build
- stable build
- O3 Optimised (including ffmpeg)

No Sync • No WebRTC • No Widevine
SHA1 25F829FD765CFA1CB558894FE8C638B31FCA4593

Sync • WebRTC • Widevine
SHA1 3C4273A708940DED78FC4AD2F8E92AEAAE1F097A

If demand will update. The "stable" branch will always be built with the default development tools.

The "dev" branch will be built with SDK 10.13, a custom built compiler, and experimental optimisations; this branch might not be compatible with OSX 10.9.x: use the stable branch or the earth/browser shattering lump of lard known as Firefox 57 (RIP).
Anonymous (2676)
Thank you guys: Nik, Robrich and Marmaduke! ;)
@Jerry: It could be nice if you add the LiberKey build ;)
Anonymous (2677)
There hasn't been an update for the RobRich build in quite a while now. Was the support for it dropped maybe?
@Anon ThinLTO is my primary build, and it was updated last week. :)

If referencing PGO, it is more or less an occasionally update - like once a month - performance comparison build. Most likely will find ThinLTO to be the more performant of the two builds.
Anonymous (2679)
Ah I see. Been using the experimental FullLTO build I think it's called? Been performing just about the same for me on a 7700k and gtx 1060. Still the annoying chrome/chromium bug on YouTube where if you rewind the video it freezes but i think that's just a bug that might get fixed soon.
No prob, and yeah, I definitely recommend Nik's WPO or my ThinLTO on Windows. Both are generally proven to be stable.... and probably as soon as I say that, my latest ThinLTO build will crash and burn. lol

Polly+FullLTO is an experimental build at best. I like trying out various permutations in Polly to find optimization opportunities and hopefully performance improvements, but as for now, my Polly build is more of a personal interest. I use FullLTO for link time optimization as ThinLTO currently does not support building with Polly.

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)

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