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): 66.0.3359.181 (540276) • Tuesday, 15 May 2018


Sync • WebRTC • Widevine • 66.0.3359.181 (540276) • Wednesday, 16 May 2018

No syncNo WebRTCNo Widevine • 66.0.3359.181 (540276) • Wednesday, 16 May 2018

  • The Portable version uses the free and open-source chrlauncher to install, update and launch Chromium.
  • sha1: 3395959efd9400a96f6add0e3b64b66ad78c2fc1 - chromium-sync.exe
  • sha1: 43740c0a7806509a016c4fdee8ed210678a4f6fb -
  • sha1: f1bc0bbf1b46867324527e7d1003a05dad18910d - chromium-nosync.exe
  • sha1: ee0c4b5ca44137709af4df12f7917b6a993d7649 -
  • List of changes
  • #source-code: follow the Nik guide
  • Source: Github repository (mirror: Zippyshare)


Sync • WebRTC • Widevine • 68.0.3435.0 (559848) • Friday, 18 May 2018

No syncNo WebRTCNo Widevine • 68.0.3424.0 (556419) • Monday, 21 May 2018

Last build with "No WebRTC"
No syncNo WebRTCNo Widevine • 68.0.3424.0 (556419) • Monday, 21 May 2018

  • The Portable version uses the free and open-source chrlauncher to install, update and launch Chromium.
  • sha1: cb040574b31e5a91dd693dbc400dd6ff2b872865 - chromium-sync.exe
  • sha1: 106df03081d92ec5656791451d0408e7ef631ae3 -
  • sha1: 57fa7b761a8085ff4891ff994018b23e2d6e3d25 - chromium-nosync.exe
  • sha1: 1e3f12153b593878b43f0b38642f2ae79fb5b1d0 -
  • Previous versions (win64)
  • #source-code: follow the Nik guide
  • Source: Github repository (mirror: Zippyshare)


No sync • WebRTC • No Widevine • 68.0.3437.0 (560197) • Sunday, 20 May 2018

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

The Chromium Authorsclangdev64-bitwindows

No sync • WebRTC • No Widevine • 68.0.3440.0 (561493) • Thursday, 24 May 2018

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!



No sync • WebRTC • No Widevine • 68.0.3434.0 • Friday, 18 May 2018

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!



No sync • WebRTC • No Widevine • 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 64-bit and 32-bit Windows

Reference: Current stable version (Google Chrome): 66.0.3359.181 (540276) • Tuesday, 15 May 2018


Sync • WebRTC • Widevine • 66.0.3359.181 (540276) • Wednesday, 16 May 2018

No syncNo WebRTCNo Widevine • 66.0.3359.181 (540276) • Wednesday, 16 May 2018

  • The Portable version uses the free and open-source chrlauncher to install, update and launch Chromium.
  • sha1: f2ef9fdbc021085029a8abb0a78891bd2629118e - chromium-sync.exe
  • sha1: 7eb06103f89736ba3bee0bcf004c3d6fba0512bd -
  • sha1: 1516da0527a1949840651e9609ca382fb07d2e7e - chromium-nosync.exe
  • sha1: d70ec1a71463b152c051d2e847663ca9bfd0c0db -
  • List of changes
  • #source-code: follow the Nik guide
  • Source: Github repository (mirror: Zippyshare)


Sync • WebRTC • Widevine • 68.0.3439.0 (560956) • Thursday, 24 May 2018

No syncNo WebRTCNo Widevine • 68.0.3424.0 (556419) • Monday, 21 May 2018

Last build with "No WebRTC"
No syncNo WebRTCNo Widevine • 68.0.3424.0 (556419) • Monday, 21 May 2018

  • The Portable version uses the free and open-source chrlauncher to install, update and launch Chromium.
  • sha1: 226be6b166bddc7ad0a5eb9daedfd67335e03371 - chromium-sync.exe
  • sha1: 250b7d2561f79349929a579b895d5b0049f67b36 -
  • sha1: 57fa7b761a8085ff4891ff994018b23e2d6e3d25 - chromium-nosync.exe
  • sha1: 5bc5d83b690057d1f7ee014c37a9f934cf243948 -
  • Previous versions (win32)
  • #source-code: follow the Nik guide
  • Source: Github repository (mirror: Zippyshare)


No sync • WebRTC • No Widevine • 68.0.3437.0 (560197) • Sunday, 20 May 2018

  • The Portable version uses the free and open-source chrlauncher to install, update and launch Chromium.
  • sha1: 6898f9e545bbed67462466dc04c66ba5553e03a4 - mini_installer.exe
  • sha1: 986205864171dcd94f9bfa80a0672977c0d934e4 -
  • Previous versions (win32)
  • #source-code
  • Source: Github repository

The Chromium Authorsclangdev32-bitwindows

No sync • WebRTC • No Widevine • 68.0.3440.0 (561486) • Thursday, 24 May 2018

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



No sync • WebRTC • No Widevine • 68.0.3434.0 • Friday, 18 May 2018

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



No sync • WebRTC • No Widevine • 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


1. Chromium for 64-bit macOS only

Reference: Current stable version (Google Chrome): 66.0.3359.181 (540276) • Tuesday, 15 May 2018


WebRTC • No Widevine • 66.0.3359.181 (540276) • Wednesday, 16 May 2018

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 • 66.0.3359.181 (540276) • Sunday, 20 May 2018

No syncNo WebRTCNo Widevine • 66.0.3359.181 (540276) • Sunday, 20 May 2018

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



Sync • WebRTC • No Widevine • 68.0.3429.0 (558128) • Saturday, 12 May 2018

No sync • WebRTC • No Widevine • 68.0.3429.0 (558128) • Saturday, 12 May 2018

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

  • sha1: 6e3dc1b349314dbe382fdc29c7e566e6863535d5 -
  • sha1: 46ff3844af1bc2ed8e83f90c7581900cfa87a167 -
  • Previous versions
  • Source: Github repository

The Chromium Authorsdev64-bitmac

No sync • WebRTC • No Widevine • 68.0.3440.0 (561486) • Thursday, 24 May 2018

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): 66.0.3359.181 (540276) • Tuesday, 15 May 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:



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-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




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



Linux Mint

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




Available in the official #arch-linux repository.




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 (since Chromium v52)




Available in the official repository.




Available in the official repository.



Arch Linux

Available in the official repository.



Gentoo Linux

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)

Info: Slackware is an independent distribution


Reference: Current stable version (Google Chrome): 66.0.3359.181 (540276) • Tuesday, 15 May 2018



Available in the official repository.




Available in the official repository.



Reference: Current stable version (Google Chrome): 66.0.3359.158 (540276) • Monday, 7 May 2018

There is no stable Chromium version for Android:

The Chromium Authorsdev32-bitandroid

No sync • WebRTC • No Widevine • 68.0.3440.0 • (561486) • Thursday, 24 May 2018

This ZIP archive contains 2 packages:


Reference: Current stable version (Google Chrome): 66.0.3359.122 • Friday, 20 Apr 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), 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! However, as a primary investor, Google gives a consistent guidance and provides all free tools and services related to the web browser.

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 66.0.3359.181. In this version, there are 181 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 (66.0.3359.181) from the official Git repository and compile it!

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

The Chromium stable version 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 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 (2 years 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 (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 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, MP3, H.264) (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 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 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! ;)


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:
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, 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:
- 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, 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.

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 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. But you can protect your privacy against user tracking tools. These tracking and profiling 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:
Info: CompareDNS Performance

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


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)
  • Info: WOT privacy issues fixed

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 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:

On Windows

On macOS

On Android

Discontinued projects

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

@Mumu Curious, what processor is in your system? If Intel and Win10, have you deployed the Windows microcode update (if needed)?

Assuming you have Win10 April 2018 Update:

Just covering bases here. I manually installed the microcode update earlier tonight, and no Chromium crashes.... yet?
Likewise, I just updated the microcode on my Opteron build box's Win10 install using the latest AMD mircocode extracted from Debian and VMware's CPU Microcode Update Driver. Fingers crossed.
Hi RobRich,

that´s smart, I did not even know of that driver from VMWare, they have some nice tools as usually! A bit off-topic: can you possibly post the latest AMD microcode updates? I would like to update my Threadripper 1950x too, or at least check if I have the latest one. Is there another source where to download the latest microcode updates to use with this driver, beside from installing Linux?

Thanks so much :-)
I’m off computer until Monday late, but promise to come back with all details and response in 36 or maximum 48h. (event, system, updates, microcode, log, etc.) to help on investigation.

But I think you are right, the problem come probably from (my/our) system and not Chromium…

See ya soon and thank you for your help and patience !
With a Threadripper, I suspect your motherboard manufacturer already has the (near) latest microcode available in a BIOS update. Definitely check there first. I resorted to the VMware utility because my Opteron motherboard is a few years old and probably beyond support.

That said, and for the curious....

I get my AMD microcode from the Debian archive.

7z can unarchive the deb, then unarchive the tar, then ya' have the files.

IIRC, you might have to have the Intel microcode files as well to get the VMware utility to run without errors. This one has a microcode.dat file:

To verify, you can access the CPU MSR registers to view the patch ID of the microcode using RW.

Regardless of how the microcode is updated, and assuming everything is right, a currently modern system ideally should show mitigations for Meltdown and Spectre. If so, you should be good to go.

As for my Opteron box, I am still waiting on Spectre mitigation; probably in a future Debian AMD microcode update.


Speaking of Linux.

The LLVM instruction import limit for ThinLTO is back to default. Compiler optimizations are stock since I am using a provided PGO/AFDO profille, but ThinLTO linker optimization is pushed up to O3.

I am currently cooking a Windows build using similar compiler optimizations as the default Linux config, while relying on ThinLTO at O3 to do the heavy lifting on extra performance optimization.
Just hit the bug reports.

Suppose we might actually see if its Chromium, Windows, or whatever.
Widevine still doesnt work with last nik build
@Anon3426: true, for widevine you can user latest stable build.
I don't know why in dev build the widevine isn't work, because config arguments is the same. I still try to figure it out.
@RobRich: thanks a lot, worked like a charm! Yes, you´d think they are updated by the BIOS maker, but they haven´t issued an update since November 2017 and since then there have been 2 new microcode revisions for the 1950X CPU (as I see now after the update). Thanks again :-)
@Lorenz Welcome. :)


IIRC, only one crash since last night.


The build box has churned out multiple Windows builds today. Been comparing optimization options. Fun.

It probably is more of a waste of file space than a serious increase over -O2 for most tasks, but I am back to -O3 for all optimized targets for Windows builds based upon Basemark Web scoring. ThinLTO is at -O3 and its default instruction import limit, so even more file space, plus rolled back in some LLVM compiler options as well.

"-mllvm", "-enable-local-reassign",
"-mllvm", "-enable-deferred-spilling",
"-mllvm", "-enable-implicit-null-checks",

I have some things to do right now, so I will push the build to the regular listings this evening. :)

Next up is probably seeing about getting new pass manager and maybe even NewGVN back into the mix.
Hi Rob,

Thank you for your help and your heavy investment!

I'll be honest, it become a bit too technical for me when I study links you provide.

From what I understand:

I got a Intel Core i7-4710HQ on a windows 8.1 (sorry).

My CPU ID is 000306C3 with a Microcode Revision number 1C.

You are right, there is a Microcode Update (version 0x23) for my Haswell (including H, S), Xeon E3 on

But this one seems to concern only Windows 10.

I confirm that I am not up to date in my windows update. I have not done the update against Spectrum and Meltdown to avoid impacting the performance of my device too much (but it seem there is no or little impact on my modern hardware)

I'm not sure of the link between Spectrum and Meltdown and Microcode CPU updates.

However, I noticed that you crashed too with the same version as me (68.0.3436.0-r560190-exp-win64 ➜ No optimization mods / Compiled with the Clang / Linked vs VS2017 bundle) and you have no more crash until today having updated your microcode.

In short, I must for starting eliminate all parasitic causes on my side like using a RAM disk, clean the cache or start from a blank profile, update my window and repair what I broke in Windows 8.1 for make it operate like a windows 7, etc.

In fact what we miss the most is the return of other anons!! Is it only you and me who crash or is it everyone?
I do not even know if it comes from Chromium, Windows, or whatever for now :(

If there is really nothing to do, I will either switch to Windows 10 or beg Nik to compile a version with the bookmarks modification only for me :$
@RobRich thank you for all your 32bit build.
But don't take offence Portable by Versatile Apps, works more fast of your 68.0.3434.0 or your 68.0.3437.0
I don't understand why ?
@Mumu It is a Chromium or Windows issue, so do not spend too much time digging IMO. There have been at least two Chromium cluster fuzz reports generated about ntdll crashes in recent days.

@Anon3431 Could be revision changes, though I am thinking perhaps memory usage. It has been an issue previously with my 32-bit builds. I have been reusing my 64-bit config for recent 32-bit builds, so I will revisit the optimization levels for the next public build.
Anon3431 @RobRich
Ok !
Thank you :)
In fact I just realize that your last clang version ( 68.0.3437.0 - 560197 ) works flawless and get the bookmarks modification, so I has stopped digging and I’m using this version waiting others resolve the issue for me ;)
I updated the codecs comparison ➜

What is interesting?

-------- [1] --------

The stable version of Nik { Nik @ stable-codecs-nosync - 66.0.3359.170 / 540276 } works perfectly with all codecs.
But with the next update { Nik @ stable-codecs-nosync - 66.0.3359.181 / 540276 } we lost some codecs…

I inform the community:
« […] Here a quick comparison of how codecs works with different Nik, Marmaduke, Rob or Squalus […] » ( #comment-3362 )

Nik reacts 48 hours later with the following message:
« […] i did not notice that they change some configuration. The next build will have codecs enabled. […] » ( #comment-3387 )

The following versions are corrected.
Well done Nik!

It seem to only remains a problem with WidevineCdm according to Anon3426 ( #comment-3426 ) which I can not test because I can not find a video with Widevine…
If someone has a link or a technique…

-------- [2] --------

The codecs functioning of { Squalus @ ungoogled-chromium 66.0.3359.139-1 / 540276 } is exactly the same as { Nik @ stable-codecs-nosync - 66.0.3359.181 / 540276 }
Is Squalus @ ungoogled-chromium based on Nik @ stable-codecs-nosync?

-------- [3] --------

This will interest RobRich: I encountered a crash while testing the codecs with the version of { Nik @ stable-codecs-nosync - 66.0.3359.181 / 540276 } and also 2 crash with the version { RobRich @ - clang - 68.0.3437.0 / 560197 }…
But I have less more crash (only two in 12h usage) after a full windows soft/hard/firm-ware update and using last clang (not exp).

-------- [4] --------

We notice a curious detail:

The { Nik @ stable-codecs-NOSYNC - 66.0.3359.181 / 540276 } version has a DLL (widevinecdmadapter.dll) in the version of the previous release (66.0.3359.170)
While the version { Nik @ stable-codecs-SYNC - 66.0.3359.181 / 540276 } does have this DLL in the same version (66.0.3359.181)

See snapshoot here ➜

-------- [5] --------

Marmaduke seemed to have the best technique for embedding codecs as he describes in this post #comment-3246
Where he explains that he followed the tutorial of… Nik !!


Morality, Nik you seem to be the codecs master.

Are you still using this tutorial to integrate all codecs ➜ ?

If not, would it be possible for you to briefly explain (If you want and when you will have an instant) how you are doing so that other devs (if they want) can learn from your skills?

I confess to also doing this in a personal perspective because I reunite informations to try one day to compile the Holy Grail ➜ Chromium ungoogled version + modified bookmarks + full codecs + Widevine!

We can not let Nik, Rob, Marmaduke and occasionally Squalus forever do all the work!

Sorry for the long post, I will try to be more quiet for the future.
HRH The Duchess of Sussex

Widevine test page:

Marmaduke's latest Mac sync stable build incorporates full CODECs (including mpegts) and Widevine support.

Ungoogled is version specific (and tends to lag behind the stable build); and can be difficult to incorporate into DEV builds: there are certain generic patches that can be used.

An "Ungoogled build" can be approximated by the judicious use of flags and plugins.

Widevine support tends to be limited to Stable builds; it is sporadic in DEV builds.
No sync • No WebRTC • No Widevine • 66.0.3359.181 (540276) running perfectly, as usual. ;-)
Can we have a 32 bit of Sync • WebRTC • Widevine • 68.0.3435.0 (559848)
Please ?
Anon3440 @Nik
Or Sync • WebRTC • Widevine • 68.0.3438.0
It woulb be great !!!
Please ?

Stop taking the piss. Learn how to compile chromium.
Annon3440 @Annon3442

Stay polite silly ; and respect me !!!!

And your name is not Nik.
@HRH The Duchess of Sussex

Thank you for the Widevine test page.

I added a line at the beginning of my table with tool-tips on hover ( ) for Widevine tests.

It seem that to get a Widevine / Netflix functional browser you need a SYNC (Dev or Stable) Chromium version and to visit URL « chrome://components/ » to be sure to have latest version of « Widevine Content Decryption Module » ( at 2018 may,23)
A Chromium relaunch may be necessary.

Thank to Nik for updated this page to explain how to codecz’ ➜ (As an aside, is Nik and Henry++ the same guy?)

Finally I confirm that with a judicious use of flags + µBlock Origin + µMatrix + #extensions you can make a serious privacy browser.

For @Anon344x : don’t fight. I’m actually learning how to compile Chromium and as soon as I success to it I will compile whatever Anons here ask for.

I got a Windows® and a Debian in a VirtualBox but because of the amount of RAM needed I think I will could compile only in Windows®

I try to follow this link ➜

But it’s long because I’m not a developer originally…

I don’t know how to get a « » formatted to match the « chrome-win32 » archive format used by Nik / Chrlauncher ; I don’t know how to make a Sync or NoSync, etc.

To be continued…
Anon 3440 @Mumu

Thank you.
No sync • WebRTC • No Widevine
It's enough for me.
I want just the better optimisation for OS 32bit. 4G Ram on 1G is reserved for the OS.
I can't compile if needed OS 64 bit and 8G Ram
Long story, short: extract the chrome.7z archive, move files around, then compress to the archive.
@Mumu: I have added your links to #news-found-on-the-web (on the right-hand side). Thank you.

> It seem that to get a Widevine/Netflix functional browser you need a SYNC version .
Yes. WebRTC and sync must be enabled.

> Is Nik and Henry++ the same guy?
No. Henry++ is the developer of chrlaucher and other excellent tools. Nik is a developer of stable/dev Chromium on Windows. He simply uses the Github repository of Henry++.

> I'm actually learning how to compile Chromium
Good luck! ;) You need time and a recent computer (ex: 64-bit OS, i7/i9/Xeon/Opteron/Ryzen processor, 16GB+ RAM, 1To SSD discs).
- Official instructions:
- Nik instructions:
- Eloston instructions about "ungoogled-chromium":
- For more: #source-code
Thank you for 32bit 68.0.3439.0

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!