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 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): 67.0.3396.87 (550428) • Tuesday, 12 Jun 2018

Nikwpocfgall-codecsstable64-bitwindows

Installer • Archive • Portable
Sync • WebRTC • Widevine • 67.0.3396.87 (550428) • Wednesday, 13 Jun 2018

Installer • Archive • Portable
No sync • No WebRTC • No Widevine • 67.0.3396.87 (550428) • Wednesday, 13 Jun 2018

Info:
  • The Portable version uses the free and open-source chrlauncher to install, update and launch Chromium.
  • sha1: deab163315644907f1870112b0c98047df80f3fe - chromium-sync.exe
  • sha1: 6815e569290216d60acbfe4a4cf0a9068b901260 - chromium-sync.zip
  • sha1: 267d5b339d2a68d4d8cc437638d46c60411148ca - chromium-nosync.exe
  • sha1: 33905d3b85fdf3cdb783aa27f35097defc001b48 - chromium-nosync.zip
  • List of changes
  • #source-code: follow the Nik guide
  • Source: Github repository

Nikwpocfgall-codecslkcr64-bitwindows

Installer • Archive • Portable
Sync • WebRTC • Widevine • 69.0.3460.0 (567342) • Thursday, 14 Jun 2018

Installer • Archive • Portable
No sync • No WebRTC • No Widevine • 68.0.3424.0 (556419) • Monday, 21 May 2018

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

Info:
  • The Portable version uses the free and open-source chrlauncher to install, update and launch Chromium.
  • sha1: 19976698f00dd12355d041496d3a70001f3589af - chromium-sync.exe
  • sha1: 31078339ee3192d4f677d55edb8588580a2db4e1 - chromium-sync.zip
  • sha1: 57fa7b761a8085ff4891ff994018b23e2d6e3d25 - chromium-nosync.exe
  • sha1: 1e3f12153b593878b43f0b38642f2ae79fb5b1d0 - chromium-nosync.zip
  • Previous versions (win64)
  • #source-code: follow the Nik guide
  • Source: Github repository

RobRichlldwpothinLTOmodifiedlkcr64-bitwindows

Installer • Archive • Portable
No sync • WebRTC • No Widevine • 69.0.3463.0 (567896) • Saturday, 16 Jun 2018

Info:
  • The Portable version uses the free and open-source chrlauncher to install, update and launch Chromium.
  • sha1: cd9e6551483264cc1a4a1ba9ec9e605d3f17bc72 - mini_installer.exe
  • sha1: 35fd858f286c4b9883b69be768e32be1df9bdba3 - chrome.zip
  • Previous versions (win64)
  • #source-code
  • Source: Github repository

The Chromium Authorsdev64-bitwindows

Installer • Archive • Portable
No sync • WebRTC • No Widevine • 69.0.3467.0 (569023) • Wednesday, 20 Jun 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 "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. Download and unzip chrlauncher-win64-dev-official.zip
  2. Execute chrlauncher.exe
  3. Close Chromium browser if a notification displays a new version
  4. Open Chromium browser. It is updated!

Info:

ThumbAppslkcr64-bitwindows

Portable
No sync • WebRTC • No Widevine • 69.0.3456.0 • Wednesday, 13 Jun 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 PortableApps.com 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!

Info:

Chocolateyoldstable64-bitwindows

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

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

Reference: Current stable version (Google Chrome): 67.0.3396.87 (550428) • Tuesday, 12 Jun 2018

Nikcfgall-codecsstable32-bitwindows

Installer • Archive • Portable
Sync • WebRTC • Widevine • 67.0.3396.87 (550428) • Wednesday, 13 Jun 2018

Installer • Archive • Portable
No sync • No WebRTC • No Widevine • 67.0.3396.87 (550428) • Wednesday, 13 Jun 2018

Info:
  • The Portable version uses the free and open-source chrlauncher to install, update and launch Chromium.
  • sha1: 9dff0899ebc4c6b39bdda4939a548eae6efa7ac8 - chromium-sync.exe
  • sha1: 74bab614ec5d1c2eb60ba7e7316306c167d4e53f - chromium-sync.zip
  • sha1: 72051bea1ef2d82a3f188fb4b8cf7a968738635d - chromium-nosync.exe
  • sha1: 9a55e2d31ff4e97deed276b13e8d76725d710300 - chromium-nosync.zip
  • List of changes
  • #source-code: follow the Nik guide
  • Source: Github repository

Nikcfgall-codecslkcr32-bitwindows

Installer • Archive • Portable
Sync • WebRTC • Widevine • 69.0.3461.0 (567505) • Friday, 15 Jun 2018

Installer • Archive • Portable
No sync • No WebRTC • No Widevine • 68.0.3424.0 (556419) • Monday, 21 May 2018

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

Info:
  • The Portable version uses the free and open-source chrlauncher to install, update and launch Chromium.
  • sha1: 6dbe0ae11b69bce66201db930e1e3253723e1d24 - chromium-sync.exe
  • sha1: 090624ca88d91b5c341329d51d024b936f5e8655 - chromium-sync.zip
  • sha1: 57fa7b761a8085ff4891ff994018b23e2d6e3d25 - chromium-nosync.exe
  • sha1: 5bc5d83b690057d1f7ee014c37a9f934cf243948 - chromium-nosync.zip
  • Previous versions (win32)
  • #source-code: follow the Nik guide
  • Source: Github repository

RobRichlldwpothinLTOmodifiedlkcr32-bitwindows

Installer • Archive • Portable
No sync • WebRTC • No Widevine • 69.0.3463.0 (567896) • Saturday, 16 Jun 2018

Info:
  • The Portable version uses the free and open-source chrlauncher to install, update and launch Chromium.
  • sha1: c42a42ecbc22e30dfffd5645d4396aca35d59b82 - mini_installer.exe
  • sha1: f631fc2cb25f60bfda4bb902e70a19e8d70ffe57 - chrome.zip
  • Previous versions (win32)
  • #source-code
  • Source: Github repository

The Chromium Authorsdev32-bitwindows

Installer • Archive • Portable
No sync • WebRTC • No Widevine • 69.0.3467.0 (569025) • Wednesday, 20 Jun 2018

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

Info:

ThumbAppslkcr32-bitwindows

Portable
No sync • WebRTC • No Widevine • 69.0.3456.0 • Wednesday, 13 Jun 2018

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

Info:

Chocolateyoldstable32-bitwindows

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

macOS

1. Chromium for 64-bit macOS only

Reference: Current stable version (Google Chrome): 67.0.3396.87 (550428) • Tuesday, 12 Jun 2018

FreeSMUGstable64-bitmac

Installer
No sync • WebRTC • No Widevine • 67.0.3396.87 (550428) • Tuesday, 19 Jun 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

Info:

Marmadukeall-codecsstable64-bitmac

Archive
Sync • WebRTC • Widevine • 67.0.3396.87 (550428) • Wednesday, 13 Jun 2018

Archive
No sync • No WebRTC • No Widevine • 67.0.3396.87 (550428) • Wednesday, 13 Jun 2018

Info:

Marmadukeall-codecslkcr64-bitmac

Archive
Sync • WebRTC • No Widevine • 69.0.3447.0 (563372) • Friday, 1 Jun 2018

Archive
No sync • WebRTC • No Widevine • 69.0.3447.0 (563372) • Friday, 1 Jun 2018

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

Info:
  • sha1: 6e3dc1b349314dbe382fdc29c7e566e6863535d5 - Chromium.69.0.3447.0.sync.app.zip
  • sha1: 5617a9e0397b0517e0ecc0922c72e7d18f76e56b - Chromium.69.0.3447.0.nosync.app.zip
  • Previous versions
  • Source: Github repository

The Chromium Authorsdev64-bitmac

Archive
No sync • WebRTC • No Widevine • 69.0.3467.0 (569000) • Wednesday, 20 Jun 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.

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): 67.0.3396.87 (550428) • Tuesday, 12 Jun 2018

devlinux

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:

stablelinux

Ubuntu


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

Info:

stablelinux

Debian


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)

Info:

stablelinux

Linux Mint


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

Info:

stablelinux

Manjaro


Available in the official #arch-linux repository.

Info:

stablelinux

Solus


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

stablelinux

Fedora


Available in the official repository (since Chromium v52)

Info:

stablelinux

openSUSE


Available in the official repository.

Info:

stablelinux

Mageia


Available in the official repository.

Info:

stablelinux

Arch Linux


Available in the official repository.

Info:

stablelinux

Gentoo Linux


Available in the official repository.

Info:

stablelinux

Puppy Linux


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

Info:

stablelinux

Slackware


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

BSD

Reference: Current stable version (Google Chrome): 67.0.3396.87 (550428) • Tuesday, 12 Jun 2018

stablebsd

FreeBSD


Available in the official repository.

Info:

stablebsd

OpenBSD


Available in the official repository.

Info:

Android

Reference: Current stable version (Google Chrome): 67.0.3396.87 (550428) • Tuesday, 12 Jun 2018

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

The Chromium Authorsdev32-bitandroid

Archive
No sync • WebRTC • No Widevine • 69.0.3467.0 • (569019) • Wednesday, 20 Jun 2018

This ZIP archive contains 2 packages:
Info:

iOS

Reference: Current stable version (Google Chrome): 67.0.3396.87 • Wednesday, 13 Jun 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!

Notes

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:
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, Facebook, Hewlett-Packard... and external contributors. There are many avantages of open source for the enterprise (archive: 1). Chromium is not designed by Google! However, as a primary investor, Google gives a consistent guidance and provides all free tools and services related to 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 67.0.3396.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 compile it. You must be a developer to do this. Just get the current stable version (67.0.3396.87) 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.

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

lkcr
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).

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 (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! ^^

stable
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! ;)
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 (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"
setx GOOGLE_DEFAULT_CLIENT_ID "no"
setx GOOGLE_DEFAULT_CLIENT_SECRET "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]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.)
  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! ;)

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 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] effect8.ru or patheticcockroach.com
  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="30.0.0.113" --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=30.0.0.113& 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. (source • NPAPI 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.

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

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:

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.

API

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

Response:
chromium → windows 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 out → revision 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 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:

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 easier 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. The security of Chromium is very solid. 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.

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

uMatrix

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

Decentraleyes

Prevent WebRTC IP leak

WebRTC Leak Prevent

Unblock websites with a browser VPN/proxy

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

Display sites quality

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

7. Tools

8. Guides

9. Tests

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

Malware

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

Chromium updater

To update Chromium automatically.

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

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

3567 comments

Quick access: #Read the latest comment

admin
Jerry
7 Jul 2013, 05:52
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

30 latest comments

Aargl
10 Jun 2018, 12:35
@marmaduke
Thanks!
Yes! Disabling the flag did the job! :-)
I've tried downloading the equivalent sync version but it's awfully slow...
I'll try later, if it's useful to you?
marmaduke
10 Jun 2018, 13:23
@Aargl

It's not necessary to download the Sync version. The "auth errors" issue only applies to the no-sync version.

In my DEV builds I fix the "auth issue" in the code; not so in the Stable build: I prefer that individuals set the approriate flag.

There will be no 67.0.3396.79 stable build - unless that's the final v67 version, after v67 WebRTC will be enabled. I've been more concerned with establishing a Mojave Chromium build system.
Aargl
10 Jun 2018, 15:04
@marmaduke
Ok. If I understood correctly what you wrote some time ago, v67.x will be the last stable for MacOS 10.9.5?
marmaduke
10 Jun 2018, 23:01
@Aargl

The Mac Chrome/Chromium releases currently use the 10.12 SDK, which is compatible with OSX 10.9.5. Given Apple's push towards the "Metal 2" architecture, it is almost certain that the Chromium build requirements will change and that OSX 10.9.5 will not be supported.

As long as 10.12 SDK is officially used to build Chromium then OSX 10.9.5 will be supported (and "stable" builds will be produced).

I've produced the Mojave (10.14) builds so that users can assess the preliminary compatibility of SDK 10.14 with the(ir) current OSX/macOS releases.

@RobRich

My knowledge of macOS is limited to 10.11+

The backward compatibility of Chromium with previous versions of OSX is a function of the Chromium authors' build requirements.

To be honest, my sole concern is that I am reluctant to buy any new computer hardware. The GPU market has been totally distorted by crypto-miners; and the latest crop of CPUs are fundametally flawed. I'm satisfied, as long as my current build system can produce future versions of Chromium.
Anon3544
Anon3544
11 Jun 2018, 00:12
@RobRich

"... As for why, I suppose there could have been a change in how your particular color profile is managed."

My color profile, however, shouldn't be "particular" at all, as I never used other themes than the Chromium default one and never changed any of its settings, through all the Chromium releases I've been using.
That's why this sudden... yellow issue with this new release surprises me.

Anyway, I'll follow your suggestion and I thank you again.
Aargl
11 Jun 2018, 03:40
@marmaduke: Thanks a lot for your explanations! :-)
Anon3546
Anon3546
11 Jun 2018, 17:42
Anyone know how to force the chromium to use the accent colour for its title bar?
It becomes grey after ver 68 I think?
Mumu
12 Jun 2018, 01:31
Hi Anon3546,

What do to mean by « accent colour » and by « title bar » ?

Can you make a screenshot of before and after ?

Isn’t it the same problem that @Anon3532 ? Or are you talking about nth’time that Chromium take a ugly decision about UI/ Design ?

Prior everything, have you tried RobRich solution :
<<
Try opening up « chrome://flags » and set « #enable-color-correct-rendering » to « disabled ».
And/Or disabling hardware acceleration in « chrome://settings/ » at the bottom ?
>>
Mumu
13 Jun 2018, 10:15
Hi Nik,

I need some help/precision about your helping tutorial about adding codecs to chromium compilation.

I used pastebin because the comment section here kill white spaces⁽¹⁾ :

https://pastebin.com/embed_iframe/JcRKteeQ

Here a pattern to cut’n’paste to save you some time for your reply (if you would)

———————————————————————————
Question 1:
[YES] or [NO Because… … …]

Question 2:
A/ [CHROME] or [CHROMIUM] or [BOTH]
B/ [WIN] or [WIN-MSVC] or [BOTH]

Question 3:
[x64 folder only for x64 && ia32 folder only for x86] or [BOTH]
———————————————————————————

Of course, it’s an open-ended question and if RobRich, marmaduke, WildByDesign or anyone who understand and/or know something, feel free to post!

⁽¹⁾ : Hey Jerry ! What about a secret tag "code" in this comment section without documentation about it that only oldfag will use ?
Anon3549
Anon3549
13 Jun 2018, 11:25
Thanks nik
Just updated to No sync • No WebRTC • No Widevine • 67.0.3396.87 (550428) • Wednesday, 13 Jun 2018 (64bit)
All good so far - been online for an hour or so
Thanks Jerry too
Much apreciated for your time and great sharing
nik
13 Jun 2018, 11:58
@Mumu:
1) yes
2) in my case it's ___\Chrome\win\___ because gn arg is ffmpeg_branding = "Chrome"
3) if you build x64 then x64, if x86 then ia32
admin
Jerry
13 Jun 2018, 14:50
@Mumu: I add a BBCode tag for rendering code snippets. You can see an example at ?all=1#comment-3488 (This link will show all comments. It can be slow to display). Note it is currently experimental.
Mumu
13 Jun 2018, 17:28
Thank you Nik!
For the moment I was able to find how to customize bookmarks bar height, radius, highlight, spacing, padding, etc. And as soon as I will get every codecs working fine I will post a full step by step pictured tutorial to compile chromium here and/or github .

Thank you Jerry too! Let be honest, we rarely need to write code in this comments section ; but exactly as you mention here ?all=1#comment-3488 when we will need it, it will be really helpful!

Not like in this line ;)
Anon3553
Anon3553
13 Jun 2018, 18:53
Guys, maybe a stupid question but... does Chrlauncher always have to download the full binaries (whole archive) to update Chromium to a new version? I ask because the updates are 70-75MB on average.
Mumu
14 Jun 2018, 02:56
@Anon3553

Yes, ChrLauncher always download the full binary, even if the update is only one word in a translation pack.
And I am pretty sure that ChrLauncher use Jerry API’ to make his update with here the details :

dev-official ➜ The Chromium Authors (dev) ➜ api/v3/?os=windows&bit=64&type=dev-official&out=json
dev-codecs-sync ➜ Nik (lkcr) ➜ api/v3/?os=windows&bit=64&type=dev-codecs-sync&out=json
dev-codecs-nosync ➜ Nik (lkcr) ➜ api/v3/?os=windows&bit=64&type=dev-codecs-nosync&out=json
dev-clang-nosync ➜ RobRich (lkcr) ➜ api/v3/?os=windows&bit=64&type=dev-clang-nosync&out=json

stable-codecs-sync ➜ Nik (stable) ➜ api/v3/?os=windows&bit=64&type=stable-codecs-sync&out=json
stable-codecs-nosync ➜ Nik (stable) ➜ api/v3/?os=windows&bit=64&type=stable-codecs-nosync&out=json

ungoogled-chromium ➜ Nik (lkcr) ➜ api/v3/?os=windows&bit=64&type=ungoogled-chromium&out=json

Note that it’s an incomplete response, I am pretty sure too that the API can retrieve Linux, Android and Mac update and probably order French fries…
More about API ➜ #api
Aargl
14 Jun 2018, 13:11
@marmaduke & everybody...
Hi all!
Got a very strange issue here: my PSU died and I transferred my complete MacOS from my desktop hackintosh to a laptop, all is working except for Chromium where all my extensions get cancelled and all my parameters reset... Tried a few times, no way.
I suppose Chromium detects that it's not the same computer and resets everything.
Is there anything I can do?
marmaduke
14 Jun 2018, 14:29
hat is standard behaviour.

Previous Chromium settings will be at:

~/Library/Application Support/Chromium

If the original values were not backed up (or over written) then you will have to manually reset them, and re-install your plug-ins, which ideally should be all in a specified folder.

You can approximate a Mac portable install (ie, changing the user directory) by following the instructions at:

https://chromium.googlesource.com/chromium/src/+/master/docs/user_data_dir.md
Anon3557
Anon3557
14 Jun 2018, 15:17
@Mumu

Thank you very much! :)
Aargl
14 Jun 2018, 16:13
@marmaduke
Yes that's the folder. The original is intact — only Chromium has not been closed properly because of the PSU failure.
I've tried the instructions of the link you gave, creating this script:
set chrome to "\"/Applications/Chromium.app/Contents/MacOS/Chromium\""
set userdatadir to "\"/Users/Myself/Chromium\""
do shell script chrome & " --user-data-dir=" & userdatadir & " > /dev/null 2>&1 &"
(and putting my backup profile folder at /Users/Myself/Chromium/Default)
It starts but wipes out the profile all the same...

I'm not sure I understand you well when you say "if the original values were not backed up (or over written)", sorry — (I'm French...): I have also tried using a clean backup from two weeks ago (with Chromium closed properly), same result.
Do you mean using Chrome Sync feature?

Isn't there a way to recover things in a situation like this? It seems amazing! :-o
On this aspect, Firefox is much easier to deal with, you copy profiles here and there with no fuss... :-(
Anon3559
Anon3559
14 Jun 2018, 18:25
@Aargl

I learned that the hard way as well. I did a backup of my Chromium profile (located at AppData) and formatted my computer. Once done, i went to the AppData folder again as put it there. Chromium did open but the profile was broken. I then searched Google and apparently Chrome stores/encrypt his stuff along with Windows (using CryptProtectData function). In other words, since it's not the same Windows user it doesn't work as it stores needed data on a user account level.
marmaduke
14 Jun 2018, 23:59
I always start Chromium from a command line (shortcut).

On a correctly functioning Chromium, configured to your particular requirements, go to chrome://version and make a note of the "Command Line". Store your unpacked extensions in a directory, and when/if required manually reload them. If the original data directory has not been corrupted then any extension used should be configured and work.

I know that my instructions are terse. But it is for the user to mitigate against any potential data loss.

I run Chromium for Windows as a "PortableApp", which can be moved from computer to computer with the profile intact; with the exception that any extensions used have to be reinstalled. Not ideal, but it works for me.
Aargl
15 Jun 2018, 04:56
Ok. Thanks for your explanations. I'll see what I can do when I repair my desktop's PSU... ;-)
By the way, I see that it is about the same for any chromium based browser: Opera and Vivaldi also lost their extensions...
I'm wondering: if I run Chromium through VMware Fusion, I suppose I could bring the VM on any Mac I want? (except for the loss in performance...)
admin
Jerry
15 Jun 2018, 05:48
@marmaduke, @Aargl: About extensions, you can move their folder to another folder. But for security reasons on Chromium and all Chromium-based browsers (Google Chrome, Opera, Vivaldi...), the extensions will not be loaded. Use the sync option... or reload each extension. I explained that at https://www.reddit.com/r/Chromium/comments/6sfxct/chromium_portable_deleting_extensions_folder/ few months ago. However, I see it is/was possible (https://www.adlice.com/google-chrome-secure-preferences/)
Aargl
16 Jun 2018, 13:58
@Jerry: Thanks! I'll read that with great interest! :-)
RobRich
16 Jun 2018, 16:49
Chromium 69.0.3463.0 (Official Build) unstable (Linux 64-bit) - No Sync | WebRTC Enabled | No Widevine
Revision 26e766991a4fed6c1f6b1b1a43ccfdc1ea1ab9e4-refs/heads/master@{#567896}
Compiler clang (+lld_linker +thinlto +pgo/afdo +linker_optimizations)

https://github.com/RobRich999/Chromium_Misc/releases/tag/v69.0.3463.0-r567896-linux64
Anon3565
Anon3565
18 Jun 2018, 20:54
Frequent/Excessive 'Aw Snap' Errors with 3460
Sebato
19 Jun 2018, 00:23
Hi,

I have the latest version of Chromium portable open and running (it's not the default browser in my system).
I've instructed a few programs to open links in Chromium via command line.

What happens is, the links from those programs get opened in a tab at the end of the current open window (intended behaviour) but there is also a second window with an empty tab opened (unintended behaviour).

Is there anything I can do so that the second, unnecessary window is not opened each time?
Mumu
19 Jun 2018, 02:06
My poor Sebato!

I have exactly the same problem since 4 or 5 years now... I have tried everything :(

I managed once to restore normal behaviour by half destroying my registry (deleting all registry keys chrom*, deleting all URL link default open, browser...) and applying a hacked BAT.

In short, I managed once to make it worked normaly, but only for a short time anyway because I broke it again as soon as I forgot to untick 'use as default to open' by opening a webm file.

This message will not offer you any help, but bring you compassion: you're not the only one with this problem it seem and I think it's almost impossible to solve it...

Sorry for us :(
But I will try to investigate again on a Virtual Machine to not detroy my system again...
Anon3568
Anon3568
19 Jun 2018, 20:44
@sebato, i have the same problem, except I used the .bat file included in chrlauncher.
tbh though, it doesn't bother me too much, i've gotten used to it
Sebato
19 Jun 2018, 23:17
Well, it's bothering me and I always try ti fix things that bother me on my computer.

So if anyone has an idea where to start looking or how to fix this, please comment!

Leave few words !

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

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