Chromium browser main logo

Chromium


The free and open-source project behind Google Chrome

Version

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): 58.0.3029.81 (454471) • Wednesday, 19 Apr 2017

Nikwpocfgall-codecsstable64-bit

InstallerArchivePortable
Sync • WebRTC • Widevine • 58.0.3029.81 (454471) • Thursday, 20 Apr 2017

InstallerArchivePortable
No syncNo WebRTCNo Widevine • 58.0.3029.81 (454471) • Thursday, 20 Apr 2017

Info:
  • The Portable version uses the free and open-source chrlauncher to install, update and launch Chromium.
  • sha1: e83fc80de9a6c78822a62c5ffc89358927760084 - chromium-sync.exe
  • sha1: 244ba32948f4f617835154e457c2df0aa28ddf65 - chromium-sync.zip
  • sha1: df8cfb73a0ee296c818cfbda78e6e3e3d4483367 - chromium-nosync.exe
  • sha1: abfca5b9e11674593dcc8400c4311c5b935354d1 - chromium-nosync.zip
  • List of changes
  • Source: Github repository (mirror: Zippyshare)
  • #source-code: follow the Nik guide

Nikwpocfgall-codecslkgr64-bit

InstallerArchivePortable
Sync • WebRTC • Widevine • 60.0.3079.0 (466537) • Saturday, 22 Apr 2017

InstallerArchivePortable
No syncNo WebRTCNo Widevine • 60.0.3079.0 (466537) • Saturday, 22 Apr 2017

Info:
  • The Portable version uses the free and open-source chrlauncher to install, update and launch Chromium.
  • sha1: f7561c3cad09eb6c82e9741baaadb9bcc6dcee05 - chromium-sync.exe
  • sha1: c46384fe9a2f329ba4207dd5013e334d69afe6f2 - chromium-sync.zip
  • sha1: 4a174ac8bfb95db1290215513119c3140f5f0ab7 - chromium-nosync.exe
  • sha1: aa1c3cbbea0b390d57e6426edc3492107082f8e7 - chromium-nosync.zip
  • Source: Github repository (mirror: Zippyshare)
  • #source-code: follow the Nik guide

RobRichclangcfglkgr64-bit

InstallerArchivePortable
No syncNo WebRTC • Widevine • 60.0.3079.0 (466580) • Monday, 24 Apr 2017

Info:
  • The Portable version uses the free and open-source chrlauncher to install, update and launch Chromium.
  • sha1: a0a3ed7239d2344ad76ab0023778ad880c0233c1 - mini_installer.exe
  • sha1: 42f966e64ba5f726c2f9888cbd46ad4e27e9f6a0 - chrome.zip
  • Source: Github repository
  • #source-code

RobRichpgocfglkgr64-bit

InstallerArchivePortable
No syncNo WebRTC • Widevine • 59.0.3061.0 (461348) • Tuesday, 4 Apr 2017

Info:
  • The Portable version uses the free and open-source chrlauncher to install, update and launch Chromium.
  • sha1: 834214d02c6aab589f0fe0da390be467cb776cb8 - mini_installer.exe
  • sha1: 224dd504e69cc640f8cf7706dd1efaf3e483733e - chrome.zip
  • Source: Github repository
  • #source-code

The Chromium Authorsdev64-bit

InstallerArchivePortable
60.0.3083.0 (467799, 8ba4e2e) • Thursday, 27 Apr 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 "chrome-win32.zip" but it is really the 64-bit version!
  1. Download chrome-win32.zip
  2. Close Chromium browser if opened
  3. Unzip chrome-win32.zip
  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. Execute chrlauncher.exe
  2. Close Chromium browser if a notification displays a new version
  3. Open Chromium browser. It is updated!

Info:

AluisioASGdev64-bit

Portable
59.0.3071.15 • Sunday, 23 Apr 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 PortableApps.com 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

ThumbAppsdev64-bit

Portable
60.0.3073.0 • Monday, 17 Apr 2017

Packaged in the PortableApps.com 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

Chocolateydev64-bit

Package
60.0.3083.0 • Thursday, 27 Apr 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: chromium::chocolatey.core.team.packages

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

Reference: Current stable version (Google Chrome): 58.0.3029.81 (454471) • Wednesday, 19 Apr 2017

Nikcfgall-codecsstable32-bit

InstallerArchivePortable
Sync • WebRTC • Widevine • 58.0.3029.81 (454471) • Thursday, 20 Apr 2017

InstallerArchivePortable
No syncNo WebRTCNo Widevine • 58.0.3029.81 (454471) • Thursday, 20 Apr 2017

Info:
  • The Portable version uses the free and open-source chrlauncher to install, update and launch Chromium.
  • sha1: 0194a360b8862216df2b429de3b41e41a38ecdc4 - chromium-sync.exe
  • sha1: 786b20ce47f978b00030a75a32f71186c29193df - chromium-sync.zip
  • sha1: b8eff48dc5a955443d8439d4e36820ac875cef2e - chromium-nosync.exe
  • sha1: edcf185572870cad5c23b7569b25ec68c5adfcb7 - chromium-nosync.zip
  • List of changes
  • Source: Github repository (mirror: Zippyshare)
  • #source-code: follow the Nik guide

Nikcfgall-codecslkgr32-bit

InstallerArchivePortable
Sync • WebRTC • Widevine • 60.0.3079.0 (466537) • Saturday, 22 Apr 2017

InstallerArchivePortable
No syncNo WebRTCNo Widevine • 60.0.3079.0 (466537) • Saturday, 22 Apr 2017

Info:
  • The Portable version uses the free and open-source chrlauncher to install, update and launch Chromium.
  • sha1: c9dbda9faf98664c5b8c77ee3bd483255f6d7ef5 - chromium-sync.exe
  • sha1: 6224054feb7e166b8f33175ef5cd31619d8278f0 - chromium-sync.zip
  • sha1: 0cec7d27aeb1e665dff53d19dc5d0f2d07ef98d1 - chromium-nosync.exe
  • sha1: 8115ae8734d857942cba2fb66d8e5acc9907bf30 - chromium-nosync.zip
  • Source: Github repository (mirror: Zippyshare)
  • #source-code: follow the Nik guide

RobRichclangcfglkgr32-bit

InstallerArchivePortable
No syncNo WebRTC • Widevine • 60.0.3079.0 (466580) • Monday, 24 Apr 2017

Info:
  • The Portable version uses the free and open-source chrlauncher to install, update and launch Chromium.
  • sha1: 8a8baadf0fa46eebc2165d86981371fcb4ae0600 - mini_installer.exe
  • sha1: 33a3cd2dd18c0b64b06c49227ce6cb5d1f37ad84 - chrome.zip
  • Source: Github repository
  • #source-code

The Chromium Authorsdev32-bit

InstallerArchivePortable
60.0.3083.0 (467799, 8ba4e2e) • Thursday, 27 Apr 2017

Info:

AluisioASGdev32-bit

Portable
59.0.3071.15 • Sunday, 23 Apr 2017

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

Sources: official website and SourceForge directory

winPenPackdev32-bit

Portable
60.0.3077.0 • Sunday, 23 Apr 2017

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 60.0.3083.0 because this update system (based on my #api) uses the #windows-32-bit-official ^^

Sources: official website and SourceForge directory

Chocolateydev32-bit

Package
60.0.3083.0 • Thursday, 27 Apr 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: chromium::chocolatey.core.team.packages

macOS

1. Chromium for 64-bit macOS only

Reference: Current stable version (Google Chrome): 58.0.3029.81 (454471) • Wednesday, 19 Apr 2017

FreeSMUGstable64-bit

Installer
58.0.3029.81 (454471) • Thursday, 20 Apr 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

Info:

The Chromium Authorsdev64-bit

Archive
60.0.3083.0 (467799, 8ba4e2e) • Thursday, 27 Apr 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.

Info:

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.

Linux

Reference: Current stable version (Google Chrome): 58.0.3029.81 (454471) • Wednesday, 19 Apr 2017

dev

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:

stable

Ubuntu


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
(PPA info)

Info: Chromium on Ubuntu packages and source archives

stable

Debian


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

stable

Linux Mint


There are different ways to install the stable Chromium version.

Based on Ubuntu:
Based on Debian (LMDE):

stable

Mageia


Available in the official repository.

Info: Chromium on Mageia Application Database

stable

Fedora


Available in the official repository since Chromium v52

Info: Chromium on Fedora Project wiki and Fedora cloud

stable

openSUSE


Available in the official repository: Installer

Info: Chromium on openSUSE wiki and RPM resource chromium

stable

Arch Linux


Available in the official repository.

Info: Chromium on Arch Linux wiki

stable

Gentoo


Available in the official repository.

Info: Chromium on Gentoo packages

stable

PuppyLinux


Available in the official repository.

Info: Chromium on PuppyLinux wiki and Puppy Linux Discussion Forum

stable

Slackware


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

BSD

Reference: Current stable version (Google Chrome): 58.0.3029.81 (454471) • Wednesday, 19 Apr 2017

stable

FreeBSD


Available in the official repository.

Info: Chromium on FreeBSD wiki and FreeBSD packages

stable

OpenBSD


Available in the official repository.

Info: Chromium on OpenBSD ports and OpenBSD packages

Android

Reference: Current stable version (Google Chrome): 58.0.3029.83 (454471) • Thursday, 20 Apr 2017

There is no stable Chromium version for Android: chromium::google.play

The Chromium Authorsdev32-bit

Archive
60.0.3083.0 (467799, 8ba4e2e) • Thursday, 27 Apr 2017

This ZIP archive contains 2 packages:
Info:

iOS

Reference: Current stable version (Google Chrome): 58.0.3029.83 • Tuesday, 25 Apr 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! ^^

Notes

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

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 58.0.3029.81. In this version, there are 81 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 (58.0.3029.81) 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.

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

lkgr
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 (list, latest commit, latest builds). Finally, there is no LKGR binary shared by the Chromium team... but any developer can re-compile it! ^^

stable
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! ;)
Jerry

Features

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 similar user agent 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 API keys (Solution: Check the #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

API Keys

(Original tutorial wrote by Chris Van Wiemeersch)

Sometimes you need to use API Keys to use things like the Speech API. 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. Download Chromium.
  2. If you launch it, you'll notice a yellow disclaimer message appear as a doorhanger: Google API Keys are missing. Some functionality of Chromium will be disabled. Learn More.
  3. Clicking on that link takes you to the confusing API Keys docs page.
  4. If you aren't already, subscribe to the chromium-dev@chromium.org 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.)
  5. Make sure you are logged in with the Google account associated with the email address that you used to subscribe to chromium-dev.
  6. Log in to the Google Cloud Platform, and select an existing project or press the "Create Project" button.
  7. From the project's API Manager, select the Credentials tab in the sidebar.
  8. Create a Browser API Key.
  9. You'll see a modal with an API key. Copy and paste that somewhere.
  10. Now create an OAuth Client ID.
  11. 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.
  12. You'll need to set three environment variables:

On #windows: Launch 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.

Flash

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://flash
  3. Test if animation works on the Flash Player versions page.
  4. 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="25.0.0.148" --allow-outdated-plugins
On #mac, you will need to launch it from the command-line (in the Terminal): /Applications/Chromium.app/Contents/MacOS/Chromium --ppapi-flash-path=/Library/Internet\ Plug-Ins/PepperFlashPlayer/PepperFlashPlayer.plugin --ppapi-flash-version=25.0.0.148& 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.

Solutions:
  • 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).

Advanced

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)

Info:
Jerry • Thursday, 23 Feb 2017

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.

API

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

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

Browsers

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 #project official contributors):
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:

Privacy

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.

Note:

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):
Note:
  • If you use WOT (Web of Trust), do not share your data. (WOT settings → Real-time protection → Set to off)
  • Browser VPN: 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.
  • µ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.
  • Add filters to your ad-blocker via FilterLists website. new

7. Tools

8. Guides

9. Tests

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

Malware

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:
Advice:
  • 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...

2043 comments

Quick access: #Read the latest comment

admin
Hello!
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:
https://bugs.chromium.org/p/chromium/issues/list
https://groups.google.com/a/chromium.org/forum/#!forum/chromium-discuss
https://groups.google.com/a/chromium.org/forum/#!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
Anonymous (2024)
@qq Confirm the issue is still present in the VS2017 build (also present in nik's 60.0.3073.0 (464874) build).
I have not tested Flash, as I do not use it, but that is interesting. Could be a compiler/linker option or optimization causing the particular difference.

Update on PGO. Tried a PGO build with VS2017. No go, yet, so PGO will remain VS2015 for now.

Quick FYI while on the topic. My latest Clang compiles here are linked with VS2017, plus I am now building the Clang/LLVM compiler with VS2017, too.
Anonymous
Anonymous (2026)
Interesting. RobRich's 60.0.3074 build will not cause errors due to flash. However, RobRich's 60.0.3075 build causes an error due to flash. What's the big difference between the two builds?
Odd. There are no significant changes in my Chromium build process other than updating my local Clang/LLVM build between those revisions, which I doubt is related, so I suspect any change regarding Flash (not) clashing would be source related.
A summary: (Windows 7) RobRich's Builds
Chromium60.0.3075.0 (Official Build) (64-bit)
Revision929fcfc0778b8848e9a4b2b5c205c1ae43cfa9f9-refs/heads/master@{#465262}
Compilerclang
Flash: Not Working
Jump List: Not Working

Chromium60.0.3074.0 (Official Build) (64-bit)
Revision6d3aa4c52ee23c233ec65f08c0a6ee0cb1aeca6a-refs/heads/master@{#464896}
CompilerMSVC 2017
Flash: Not Working
Jump List: Not Working

Chromium60.0.3074.0 (Official Build) (64-bit)
Revision6d3aa4c52ee23c233ec65f08c0a6ee0cb1aeca6a-refs/heads/master@{#464896}
Compilerclang
Flash: Working
Jump List: Not Working
WildByDesign
@nik Thank you for your continued efforts to keep builds going for Stable branch.

@All Does anyone know yet what the status is with regard to those Flash Player crashes on No WebRTC builds? Is there a specific patch/bug report to reference? Thank you.
Thanks nik for your good work much appreciated - latest stable works all good for me
Thanks jerry for maintaining the site :)
Anonymous
Anonymous (2031)
No sync • No WebRTC • No Widevine • 58.0.3029.81 (454471) • Thursday, 20 Apr 2017
Strange. In this version, uBlock Origin blocked items counter stopped working.
Anonymous
Anonymous (2032)
@2031
I always do clean install instead of updating, to avoid weird stuff like that. Current stable nosync seems to work flawlessly for me so far. Addons: uBO+uBO Extra, HTTPS Everywhere, Privacy Badger.
Anonymous
Anonymous (2033)
60.0.3079.0 win32 nosync lkgr from Nik, updated from some 59 (same channel from from Nik):
uBlock Origin continues to crash from time to time (sometimes after some event, sometimes after several [tens of] minutes)

Made a backup of settings to file (uBO feature).
Tried to remove all uBO settings (Local Storage - .localstorage + .localstorage-journal, also from "Local Extension Settings" and "Managed Extension Settings"), launched Chromium, imported settings from file - continues to crash.
Tried to remove uBO, reinstalled it, imported settings from file - continues to crash.
Currently reinstalled and testing with default settings, will keep you informed.
If someone else has the same problem - please let us know...

P.S. Didn't check on clean profile because don't have much time (sometimes it doesn't crash for a really long time) and RAM, but will try to test it later (maybe some conflicts with other extensions?)
Updated Visual Studio 2017 build. No sync, WebRTC disabled, and Widevine enabled. Compiled with WPO and CFG.

Chromium: 60.0.3080.0 (Official Build) (64-bit)
Revision: c4cb0d38f0bd26578120775e9c09be813b5215c0-refs/heads/master@{#466630}
OS: Windows
Compiler: MSVC 2017

mini_installer.exe | sha1: 86f3d544128f201ed9c101a2a5841de2743f4aeb
https://drive.google.com/open?id=0B4saVuqumZNZNXVEU3Vkem5BNkE

chrome.zip | sha1: 7da3c38b192b672e999fc6c90d1181b05e920041
https://drive.google.com/open?id=0B4saVuqumZNZT1BYcGJPSzMtSE0
WindowsSmellsOfMonopolyAgain
The new version of Windows 10 (Creators Update) now actively blocks the Installer from starting, and does not make it obvious how to get it to run. I just downloaded Nik Stable x64 Sync Installer (as I always do) to update to 58.0.3029.81 (454471) • Thursday, 20 Apr 2017. Prior to updating Win 10 I experienced no problems running the Installer, after updating Win 10 with the newest Installer I get this https://i.imgur.com/Hks1B1f.png

As you can see from the screenshot, the dialogue is not offering an option to Run the exe, only if you click the slightly different words "more info" do you get the option to run it anyway.

Is MS just trying to stomp on your browser as competition for Edge, or does the new Windows Defender Smartscreen need educating about the best open source browser on the planet ?
phuong nguyen
@2017: A question to the devs here: Do you know why while watching videos, if we switch tabs and then come back to the video tab, the video is frozen and takes a couples of seconds to start moving again? This has something to do with the codecs i believe. https://bietthucanho.com/
@RobRich: hey, did you compare the build time of 2015 vs 2017? because vs2013 was faster than vs2015 :)
bitdefendyourself
Is anyone able to run the flash player?

So far what I did was to install the PPAPI plugin from Adobe page, enable flash in the chrome://flags, but everytime I try to load a webpage with flash content the browser crashes and displays the message: "Something went wrong."

Am I doing something wrong? I've been using Chromium 32-bit no Web-RTC builds (unofficial stable channel).

I know in the future Flash will eventually be dropped but for now it's still needed for some livestreaming websites
Anonymous
Anonymous (2039)
@bitdefendyourself: Flash player works only if WebRTC is enabled. Tested with #windows-32-bit-dev-nik portable builds.

My way:
1. Download and install Portable version of Chromium with enabled WebRTC.
2. http://effect8.ru/soft/media/adobe-flash-player-portable.html --> Get "pepflash 25.0.0.148" PPAPI 32-bit version.
3. Unzip pepflashplayer32_25_0_0_148.7z
4. Rename pepflashplayer32_25_0_0_148.dll to pepflashplayer.dll
5. Put pepflashplayer.dll and manifest.json into the "plugins" Chromium folder
6. Launch Chromium
7. Check chrome://flash
8. Manage Flash at chrome://settings/content/flash
9. Normally, animation works on https://www.adobe.com/software/flash/about/ ;)
@Nik I have not actually timed the builds, but from a casual perspective, it seems like 2017 builds slightly faster.

Unless you are doing PGO or serious debugging, 2017 should be good to go for 64-bit Chromium builds IMO. 32-bit building on a 64-bit build box should be okay now, too, from what I am seeing about recent cross architecture compilation updates.

https://bugs.chromium.org/p/chromium/issues/detail?id=683729
Chromium for 64-bit macOS - All Codecs

No sync • No WebRTC • No Widevine 60.0.3082.0 (467367) Wednesday, 26 Apr 2017

https://uploadfiles.io/h3ckm

(Feedback appreciated - if demand will update!)
bitdefendyourself
@Anonymous (2039), You're right, yesterday I ended up trying to run flash in the Web-RTC edition and it works good so far. I'm able to livestream my soccer games again. Thanks anyway.

Is it some sort of a requisite for Flash, to have Web-RTC enabled or it is a bug in the current versions of Chrome/Chromium?

Thanks in advance and keep it up guys.
Hi all.
Using Nik sync 60.0.3079.0 (64-bit). Not sure what build (recent, of course) started it, but now I have to enable the "Offer to translate.." option under settings in order to get the translate option on the right click context menu, but this also implies the annoying offer to translate on the upper right corner. Previously I could disable that option and still get the context menu option.

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!