Chromium browser main logo


The free and open-source project behind Google Chrome


Here, you see your Chromium version.
Works only if your 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 (stable and portable) works fine.

1. Chromium for 64-bit Windows only

Reference: Current stable version (Google Chrome): 56.0.2924.87 (433059) • Wednesday, 1 Feb 2017


Sync • WebRTC • Widevine • 56.0.2924.87 (433059) • Thursday, 2 Feb 2017

No syncNo WebRTCNo Widevine • 56.0.2924.87 (433059) • Thursday, 2 Feb 2017

Advice about these builds
Use the free and open-source chrlauncher to install, automatically update and launch Chromium. It is also possible to do a portable version, with included Flash plugin ^^

  • sha1: efe561aa87fcb460f58cde56d8d40098120379b1 - chromium-sync.exe
  • sha1: 5eb041faa112a7526cca0bfac86e5f7f2167b6dc -
  • sha1: 0ec2c75ab83054d9d72e9e39eb1f3377851cad7d - chromium-nosync.exe
  • sha1: 33ef813f457cd9e931857eb613a6320ca6d39cc2 -
  • List of changes
  • Source: Github repository (mirror: Zippyshare)
  • #source-code: follow the Nik guide


Sync • WebRTC • Widevine • 58.0.3016.0 (451385) • Friday, 17 Feb 2017

No syncNo WebRTCNo Widevine • 58.0.3016.0 (451385) • Friday, 17 Feb 2017

  • sha1: f46729d1e974ccc64662ca3302ab0aeb539ae55b - chromium-sync.exe
  • sha1: 22eefb3f517542c023310e344cce0fa2b550c2e2 -
  • sha1: 05d32bdb4b2206172578146177550bf36b1f3705 - chromium-nosync.exe
  • sha1: b1511c0ee3073621218f22acac800d9040e97032 -
  • Source: Github repository (mirror: Zippyshare)
  • #source-code: follow the Nik guide


No syncNo WebRTC • Widevine • 58.0.3015.0 (450943) • Thursday, 16 Feb 2017

  • sha1: 3dd3aa0f66479f3a2744ecf66eb77c314fcace56 - mini_installer.exe
  • sha1: 4279b4ee6e7ab4af1f8ee7f0f15a39ab54bbcc65 -
  • Source: Github repository
  • #source-code


No syncNo WebRTC • Widevine • 58.0.3010.0 (449857) • Saturday, 11 Feb 2017

  • sha1: fd0e7cbfe67f82ddaddda88bb664879650dd51b8 - mini_installer.exe
  • sha1: 52932fd8677955d2453dcb2b473dd92d6544c804 -
  • Source: Github repository
  • #source-code

The Chromium Authorsdev64-bit

58.0.3019.0 (451661, 9cff5cc) • Monday, 20 Feb 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!



58.0.3004.3 • Saturday, 11 Feb 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 AluisioASG (Aluísio Augusto Silva Gonçalves), 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!

Sources: official website and SourceForge directory


58.0.3013.0 • Tuesday, 14 Feb 2017

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

Sources: official website and SourceForge directory


58.0.3019.0 • Monday, 20 Feb 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
Info: this official package uses my #api for updates:

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

Reference: Current stable version (Google Chrome): 56.0.2924.87 (433059) • Wednesday, 1 Feb 2017


Sync • WebRTC • Widevine • 56.0.2924.87 (433059) • Thursday, 2 Feb 2017

No syncNo WebRTCNo Widevine • 56.0.2924.87 (433059) • Thursday, 2 Feb 2017

  • sha1: 8b382dec1280efabd014f9c47bc395ae85de8930 - chromium-sync.exe
  • sha1: d4d32c0cbcfa502be6c3625dde5d7e23f3a8ddae -
  • sha1: 1daf593be1c4abb46414be12055780c6d42667a0 - chromium-nosync.exe
  • sha1: 189285a82ae44f3347147f5cd0d288f9a1270bee -
  • List of changes
  • Source: Github repository (mirror: Zippyshare)
  • #source-code: follow the Nik guide


Sync • WebRTC • Widevine • 58.0.3003.0 (448156) • Saturday, 4 Feb 2017

No syncNo WebRTCNo Widevine • 58.0.3010.0 (449849) • Saturday, 11 Feb 2017

  • The Portable version uses the free and open-source chrlauncher to install, update and launch Chromium.
  • sha1: 084601dcc75906945352180e316724ca50c9410a - chromium-sync.exe
  • sha1: c665a8018416536f22bf5e3b5267a732a9ce70e0 -
  • sha1: a552002c5375480ce4d33f3425365c3358ea3ff7 - chromium-nosync.exe
  • sha1: 6e67e7437052d2ede497952e4c90f298b1ca50fa -
  • Source: Github repository (mirror: Zippyshare)
  • #source-code: follow the Nik guide


No syncNo WebRTC • Widevine • 58.0.3015.0 (450943) • Thursday, 16 Feb 2017

  • sha1: 985cf8d1f26925075ac001574c1d6c4cdabdb4cb - mini_installer.exe
  • sha1: bd339c40dc1d223fc1c767b4d7d96c9051f1a363 -
  • Source: Github repository
  • #source-code

The Chromium Authorsdev32-bit

58.0.3019.0 (451662, a4b3b0b) • Monday, 20 Feb 2017



58.0.3004.3 • Saturday, 11 Feb 2017

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

Sources: official website and SourceForge directory


57.0.2965.0 • Thursday, 29 Dec 2016

Packaged in the winPenPack format, it can work as standalone software.

How to update it with an alternative update system?
Use the simple free and open-source cpf-update-win batch script to automatically update both Chromium and PepperFlash. The Chromium version will be 58.0.3019.0 because this update system (based on my #api) uses the #windows-32-bit-official ^^

Sources: official website and SourceForge directory


58.0.3019.0 • Monday, 20 Feb 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
Info: this official package uses my #api for updates:


1. Chromium for 64-bit macOS only

Reference: Current stable version (Google Chrome): 56.0.2924.87 (433059) • Wednesday, 1 Feb 2017


56.0.2924.87 (433059) • Thursday, 2 Feb 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


The Chromium Authorsdev64-bit

58.0.3019.0 (451666, f6f56fb) • Monday, 20 Feb 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): 56.0.2924.87 (433059) • Thursday, 2 Feb 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 the 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
(PPA info)

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


Cub Linux

Originally called Chromixium OS, Cub Linux, based on a custom Ubuntu LTS, is a #chromium-os like.

Info: Wikipedia page



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): 56.0.2924.87 (433059) • Thursday, 2 Feb 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): 56.0.2924.87 (433059) • Thursday, 2 Feb 2017

There is no stable Chromium version for Android:

The Chromium Authorsdev32-bit

58.0.3019.0 (451666, f6f56fb) • Monday, 20 Feb 2017

This ZIP archive contains 2 packages:


Reference: Current stable version (Google Chrome): 56.0.2924.79 • Wednesday, 1 Feb 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), LKGR, 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, Nvidia, Adobe, Hewlett-Packard, BlackBerry... So Chromium is not made 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 56.0.2924.87. In this version, there are 87 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 (56.0.2924.87) 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.

Snapshots (known as "Nightly" or "Dev" builds) builds are compiles 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.

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 (11 months ago). The Chromium team has removed few LKGR builders (407399, 576253 and chromium-dev) but other ones still work (status, list, 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 LKGR build tested and improved by the Chromium team.

In resume:
  • dev: Untested and may be unstable versions (known as "Snapshots" or "Nightly" builds). Official download page
  • LKGR: Tested and more stable versions. Also used by Google Chrome channels: Canary, Dev, Beta and Stable.
  • stable: The most stable versions.

4. Finally

Except for stable and LKGR versions, this site uses the official Snapshots repository.

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 sandboxed processes as Google Chrome
  • the similar UI and settings as Google Chrome
  • the built-in Chrome PDF Viewer, on Windows OS (known as PDFium)
  • 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 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


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 PepperFlash (PPAPI) from Adobe
  2. Check chrome://plugins
  3. 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] Adobe Flash Player (32/64-bit)
  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 (Firefox: info about plugins, NPAPI deprecation)
  • 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.

  • On #windows, use Nik builds. 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.

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. About official builds, 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 disable plugins: chrome://plugins
- 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 is used to create another web browser.

Proprietary browsers:
  • Chrome (based on Chromium • by Google)
  • Vivaldi (based on Chromium • by Vivaldi Technologies)
  • Opera (based on Chromium • by Golden Brick Silk Road/Qihoo 360, since July 2016)

I do not recommend:
Why not recommended?
Because all of these browsers are closed-source, outdated and 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.

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 may expose user to a number of security 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 which respect your privacy:
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.

For Chromium (and Firefox):
  • WOT (Web Of Trust): Do not share your data! (Settings → Real-time Protection → Set to Off)
  • Browser VPN: Do not use Hola! or ZenMate. Hola! is a botnet (more info on 8chan). 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.
  • µBlock Origin (wiki) is pattern-based filtering, while µMatrix (wiki) is matrix-based filtering which gives you more control over the filtering process.
  • µBlock Origin and ScriptSafe can also protect against WebRTC IP leak.

7. Tools

8. Guides

9. Tests

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


You have downloaded Chromium and your antivirus detect a malicious software like a virus or trojan. 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:
  • Make sure you download Chromium from reliable sources (like on this site ^^)
  • Prefer an open-source #updater

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:

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

Anonymous (1863)
@1842 @1848 @1850 Switched to this ppa, and happy with it. Thank you all for the helpful information.
Donald Retard Trump

This is the error messasge (Trying to build Version 58.0.3005.0 (64-bit)):

C:\depot_tools\src>ninja -C out/LKGR_x64 mini_installer.exe
ninja: Entering directory `out/LKGR_x64'
[641/773] CC obj/third_party/ffmpeg/ffmpeg_internal/error_resilience.obj
FAILED: obj/third_party/ffmpeg/ffmpeg_internal/error_resilience.obj
ninja -t msvc -e environment.x64 -- "C:\Program Files (x86)\Microsoft Visual Studio 14.0\VC\BIN\amd64/cl.exe" /nologo /showIncludes /FC @obj/third_party/ffmpeg/ffmpeg_internal/error_resilience.obj.rsp /c ../../third_party/ffmpeg/libavcodec/error_resilience.c /Foobj/third_party/ffmpeg/ffmpeg_internal/error_resilience.obj /Fd"obj/third_party/ffmpeg/ffmpeg_internal_c.pdb"
c:\depot_tools\src\third_party\ffmpeg\libavcodec\error_resilience.c(405): error C2220: warning treated as error - no 'object' file generated
c:\depot_tools\src\third_party\ffmpeg\libavcodec\error_resilience.c(405): warning C4047: '=': 'int (*)[2]' differs in levels of indirection from 'uint8_t *'
c:\depot_tools\src\third_party\ffmpeg\libavcodec\error_resilience.c(406): warning C4047: '=': 'int (*)[2]' differs in levels of indirection from 'uint8_t *'
[650/773] CC obj/third_party/ffmpeg/ffmpeg_internal/h264_loopfilter.obj
ninja: build stopped: subcommand failed.

The error is caused by the addition of the the "blocklist" macro to "error_resilience.c"

I've tried to solve the problem but have failed. So I've reverted to using the previous version of ffmpeg.

I'd like to try and build Chromium using LLVM to see if that would solve the problem. Since the Mac Chromium build uses LLVM and latest version of ffmpeg with all codecs enabled compiles cleanly and works.
@Donald Retard Trump: hmm, try to add "#pragma warning(suppress: 4047)" before the line 405 and 406 within error_resilience.c
I use pretty much the same setup and build process as nik. The args are as specified with my builds, though I do sometimes build with an external LLVM install instead of the one provided with the Chromium build tools - either way should be okay.

If building LKGR, it could be lagging behind trunk by tens to hundreds of commits. Try building master to see if a fix for the issue recently has been implemented.
Donald Retard Trump
Thanks Nik, that solution works!

RobRich, I will continue to experiment.
Hurrah!!! At leat one webpage on the Internet that doesn't load dozens of external javascript, fonts, css, that consume my CPU and bandwith to send all my info to third-party tracking websites. Yeah! Thank you. And don't forget that you website doesn't use all that new stupid design rules: infinite scrolling, flat design, minimalist icons, grey text, toggleable elements, social buttons, tablet-oriented giant buttons, autoplay video background, popups onexit begging to stay, and so on.
Quick FYI for those checking about:version details. I have started setting "is_official_build = true" for my Clang LKGR builds.
Anonymous (1870)
From time to time github looks strange, dont know why (it works fine in chrome with the same setup) Im on win10 x64 and stable branch of chromium.
@Anon870 Looks like perhaps a CSS loading issue. Have any ad blocking or similar extensions installed?


I have been occasionally poking at the LLVM build process, including resolving a runtime libraries issue and now locally building LLVM for the needed Clang and LLD binaries.

I just completed a working internal test build of Chromium compiled with Clang and linked with LLD instead of the Visual Studio linker. It is a component instead of static build, which is not a big deal for now. Component builds *might* be *slightly* slower to load. :shrug:

If the Clang+LLD internal builds look stable, I likely will migrate my public builds tonight or tomorrow, too. I will have to roll back the "is_official_build = true" argument until my Clang+LLD static build issue is resolved, as "official" does not support component shared library building. Again, not really a concern right now for Clang+LLD builds either IMO.
Anonymous (1872)
@RobRich I use Ublock, but at that time it was disabled. Since today github is working fine again....i dont get it,maybe something 3rd party filtering.
No go on my hopeful Clang+LLD migration, yet. My successful x86 test build works enough.... for testing. Not stable enough for me to release IMO. So back to Clang + MSVS linker for at least awhile longer.
Some interesting changes to Control Flow Guard within Chromium today.
See here:

RobRich, Specifically notice "Also disabling compilation of CFG with MSVC compiler. Preparing for clang CFI instead." Since you are more familiar with clang, that may signify more to you. If you have a look at that link, does that change any for the way in which you or Nik build Chromium to still achieve CFG mitigation?

From a basic standpoint, CFG and CFI are essentially different names for the same concept.

Looking at the comments and changed build files, it appears CFG still will be invoked by the MSVS linker regardless if the compiler is Clang or MSVS.

AFAIK, it is the linker that generates the security checks in the LoadConfig table of an executable. If my understanding is correct, CFG in the compiler stage is more about security auditing at build time, while CFG in the linker stage is more about security auditing at run time.

On a side note, I am not entirely sure where the LLD linker currently stands on CFI support for Windows executables.
I am now getting the dreaded ERR_SSL_PROTOCOL_ERROR for all Google sites (and only Google sites). I checked firewall, clear cache, disable QIUC. nothing works. help! I am a long time Chromium user and this has only happened sporadically before.
Mark - you should add launch flag "--ignore-certificate-errors", i have ssl errors too, like 1/3 https websites are broken - twitch, microsoft, apple, kaspersky, nvidia... Seriously, fuck https and certificates, it was supposed to increase security, not to make websites unusable... Of course, i'm on chromium v54, i dont know if this flag will work on newer versions, and im staying on this version for a long time, until google and chromium will fix their shit, but then again, they will probably just introduce more bugs....
Shot in the dark, but try manually updating your browser components, that way you should have the latest CRLSets, EV whitelists, etc.

Go to the browser URL: chrome://components

Check all components for updates for good measure.
Anonymous (1879)
Downloaded new version from @nik - 58.0.3016.0. Settings page is now in full Material Design.

Thanks for the fresh builds as usually, @nik & @RobRich.
Anonymous (1880)
Are there any disadvantages when using lkgr compared to stable one?
@Anonymous (1880), Disadvantages to LKGR would be sometimes random bugs show up and you would have to revert to a previous build. Not always too critical, but sometimes some glitchy behaviour. Advantages to LKGR would be testing out new the latest and greatest bleeding edge features before they reach stable. chrlauncher makes it quite easy to switch between builds/channels and so on.
The Chromium Authorsdev64-bit, last few days. Interface dark, dark website. In other browsers, everything is fine. So the fault is not in the settings screen or the video card drivers. NVIDIA GT 740, latest 64 bit driver.

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!