Chromium browser main logo


The free and open-source project behind Google Chrome


Here, you see your Chromium version.
Works only if your web browser is based on Chromium like Google Chrome, Chromium browser, Opera, Vivaldi...

Windows 10, 8, 7

Chromium is not available on XP and Vista since version 50. For help, version 49 works fine (installer, archive, portable). In addition, if you have an old CPU without SSE2 support, version 34 is the last one (portable, build before 253860).

1. Chromium for 64-bit Windows only

Reference: Current stable version (Google Chrome): 67.0.3396.99 (n/a) • 24 days ago


Sync • WebRTC • Widevine • 67.0.3396.99 (550428) • 23 days ago

No syncNo WebRTCNo Widevine • 67.0.3396.99 (550428) • 23 days ago


Sync • WebRTC • No Widevine • 69.0.3496.0 (576176) • 1 day ago


No sync • WebRTC • No Widevine • 69.0.3492.0 (575161) • 5 days ago

The Chromium Authorsdev64-bitwindows

No sync • WebRTC • No Widevine • 70.0.3498.0 (576911) • 33 minutes ago


No sync • WebRTC • No Widevine • 69.0.3456.0 • 1 month ago


No sync • WebRTC • No Widevine • 64.0.3282.168 • 5 months ago

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

Reference: Current stable version (Google Chrome): 67.0.3396.99 (n/a) • 24 days ago


Sync • WebRTC • Widevine • 67.0.3396.99 (550428) • 23 days ago

No syncNo WebRTCNo Widevine • 67.0.3396.99 (550428) • 23 days ago


Sync • WebRTC • Widevine • 69.0.3496.0 (576176) • 1 day ago


No sync • WebRTC • No Widevine • 69.0.3492.0 (575161) • 5 days ago

The Chromium Authorsdev32-bitwindows

No sync • WebRTC • No Widevine • 70.0.3498.0 (576920) • 22 minutes ago


No sync • WebRTC • No Widevine • 69.0.3456.0 • 1 month ago


No sync • WebRTC • No Widevine • 64.0.3282.168 • 5 months ago


1. Chromium for 64-bit macOS only

Reference: Current stable version (Google Chrome): 67.0.3396.99 (n/a) • 24 days ago


No sync • WebRTC • No Widevine • 67.0.3396.99 (n/a) • 24 days ago


Sync • WebRTC • Widevine • 67.0.3396.87 (550428) • 1 month ago

No syncNo WebRTCNo Widevine • 67.0.3396.87 (550428) • 1 month ago


Sync • WebRTC • No Widevine • 69.0.3481.0 (572140) • 17 days ago

No sync • WebRTC • No Widevine • 69.0.3481.0 (572140) • 17 days ago

The Chromium Authorsdev64-bitmac

No sync • WebRTC • No Widevine • 70.0.3498.0 (576900) • 51 minutes ago

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

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


Reference: Current stable version (Google Chrome): 67.0.3396.99 (n/a) • 24 days ago


Chromium OS






Linux Mint












Arch Linux


Gentoo Linux


Puppy Linux




Reference: Current stable version (Google Chrome): 67.0.3396.99 (n/a) • 24 days ago






Reference: Current stable version (Google Chrome): 67.0.3396.87 (550428) • 1 month ago

There is no stable Chromium version for Android:

The Chromium Authorsdev32-bitandroid

No sync • WebRTC • No Widevine • 70.0.3498.0 • (576910) • 37 minutes ago


Reference: Current stable version (Google Chrome): 67.0.3396.87 • 1 month ago

Chromium on iOS is a big fake!


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), stable and portable builds.

All downloads are from reliable sources only:

1. Project

Chromium exists since 2008. It is the free and open-source project (#features) behind the famous Google Chrome browser. Intrinsically, Chromium is a Google project maintained by many authors (developers, engineers, graphic designers, security researchers...) from Google, Opera, Yandex, Samsung, Intel, Facebook, Hewlett-Packard... and external contributors. 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 this project.

Chromium is the project then Google Chrome is the product.

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.99. In this version, there are 99 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.99) 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 stable version of Chromium is compiled by:

3. Development

Basically, Chromium has few versions every day, but you can stick with a version for about a month before you need to upgrade.

A DEV build (also known as "Snapshot", "Nightly" or "Raw" build) is compile of the Chromium code whenever there are submitted code changes. Check the buildbot console. A snapshot build will be created as long as the code compiles successfully. Its binary files are stored in the Snapshots repository of Google Storage. This build is really just development tool for checking whether issues are fixed in the latest Chromium code. It can be buggy and unstable.

A LKCR build does at least provide some level of guarantee that the particular revision actually should build, which is good for third-party builds for not wasting time on potentially uncompilable builds. As a result, LKCR usually trails the dev trunk by a few revisions (commits).

If building straight off dev, it can be a guess whether a build will compile or not, so a third-party builder could be wasting processor cycles that could otherwise go to a known compilable build (LKCR).

Each snapshot build is then run through the automated tests. If that snapshot build successfully passes the automated tests, it is considered as a good build: LKGR (Last Known Good Revision)... and can become potentially a stable build.

Note LKGR builds were stored in the Continuous repository until Friday, 18 Mar 2016. The Chromium team has removed few LKGR builders (407399, 576253 and chromium-dev) but other ones still work (latest commit, latest builds). Finally, there is no LKGR binary shared by the Chromium team... but any developer can re-compile it! ^^

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

In resume:

4. Finally

Except for stable versions, the developers use the official Snapshots repository to re-compile their builds.

So I give you the opportunity to download only nice Chromium releases ;)
If you want, check the simplest multilingual page: → download/

This entire website (#news and #api included) is auto-updated each hour by the server itself.

Thanks for your attention.
Have a good time! ;)


Chromium vs Google Chrome.

Chromium browser has:
  • only open-source licenses (BSD license, MIT license, LGPL, MS-PL and MPL/GPL/LGPL tri-licensed code) plus unlicensed files. It is a FOSS project. A full list of software developed by third-parties is available within the browser at chrome://credits (similar to this online page)
  • a blue-colored logo
  • the similar sandbox as Google Chrome (For info, Firefox also uses it)
  • the similar user interface and settings as Google Chrome
  • the similar support for Extensions, Themes and Web Apps as Google Chrome
  • the similar user agent as Google Chrome
  • the built-in Chrome PDF Viewer (known as PDFium), on Windows
  • the built-in Chromoting Viewer (To use it, you need to first install the Chrome Remote Desktop app)
  • the built-in Google Native Client
  • the built-in Print preview and print system
  • no stable version offered by the official team (aka The Chromium Authors)
  • no digital signature
  • no auto-update system (Solution: Use an #updater • On #linux, use the integrated software/package manager, indeed a PPA)
  • no Google API keys (Solution: Check #google-api-keys)
  • no built-in Flash player (Solution: Check #flash)
  • no unwanted software protection (known as Chrome Cleanup and "software_reporter_tool.exe"), on Windows
  • no support of proprietary codecs (AAC, MP3, H.264) (Solution: Check #html5-audio-video)
  • no user RLZ identifier
  • no user metrics (usage statistics) (opt-in option)
  • no crash report (opt-in option)
  • More details on the official site, focused on Linux.

Some developers maintain forks of Chromium that offer more features and enhancements. Thanks a lot for developers! ;)

And if you want to follow new Chromium features, check the Google+ posts of the Chromium Evangelist at Google

Google API keys

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

1. Without your own Google API keys

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

Now launch Chromium. Enjoy! ;)

2. With your own Google API keys

(Based on an original tutorial wrote by Chris Van Wiemeersch)

  1. Clicking on that yellow disclaimer message takes you to the confusing API keys docs page.
  2. If you aren't already, subscribe to the chromium-dev[at] mailing list. (You can just subscribe to the list and choose to not receive any mail. FYI: the Chromium project restricts the APIs to those subscribed to that group - that is, Chromium devs.)
  3. Make sure you are logged in with the Google account associated with the email address that you used to subscribe to chromium-dev.
  4. Log in to the Google Cloud Platform, and select an existing project or press the "Create Project" button.
  5. From the project's API Manager, select the Credentials tab in the sidebar.
  6. Create a Browser API Key.
  7. You'll see a modal with an API key. Copy and paste that somewhere.
  8. Now create an OAuth Client ID.
  9. After you complete all the steps and the "content screen", you'll be presented with a modal with your Google Client ID and Client Secret.
  10. You'll need to set three environment variables:

On #windows: Launch Command Prompt (cmd.exe) and enter the following commands:
setx GOOGLE_API_KEY yourkey
setx GOOGLE_DEFAULT_CLIENT_ID yourclientid
setx GOOGLE_DEFAULT_CLIENT_SECRET yourclientsecret

On #mac and #linux: Plop these in your ~/.profile file:
export GOOGLE_API_KEY="yourkey"
export GOOGLE_DEFAULT_CLIENT_ID="yourclientid"
export GOOGLE_DEFAULT_CLIENT_SECRET="yourclientsecret"

Now launch Chromium. Enjoy! ;)


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

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

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

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

Now, the full manual installation tutorial...
(If Google Chrome is already installed, go directly to the step 3: #add-command-line-flags)

1. Get PepperFlash (PPAPI)

This plugin is a non-free (proprietary) software developed by Adobe, and distributed bundled with Google Chrome. So get it from the official sources: Adobe or Google.

1.1 From Adobe

Different official ways:
After install, the plugin path will be:
- On a 64-bit #windows:
  • C:\Windows\system32\Macromed\Flash\pepflashplayer64_[version].dll (64-bit version)
  • C:\Windows\SysWOW64\Macromed\Flash\pepflashplayer32_[version].dll (32-bit version)
- On a 32-bit #windows:
  • C:\Windows\system32\Macromed\Flash\pepflashplayer32_[version].dll (32-bit version)

1.2 From Google Chrome

Canary channel:

1.3 From an unofficial source

(Use an online service to prevent #malware)
  1. Search "PepperFlash" or "PPAPI" at [RU] or
  2. Download and open the .7z archive
  3. Get "pepflashplayer.dll" (rename it, if needed) and "manifest.json" files.

Optionally, get the Flash version number:
(If you want to see the correct version number on Chromium internal pages)
  • On all platforms, open the manifest.json text file in the PepperFlash folder.
  • On Windows, you can do a right-click → Properties → Details, on the .dll file

2. Change the plugin directory

If you want, prefer a short path for the plugin. It will be easier for the next step. ^^
Example on Windows: Put this .dll file in a path like C:\PepperFlash\ (Create the directory if needed)

3. Add command-line flags

Use these #command-line-flags:
  • --ppapi-flash-path=[plugin path]
  • --ppapi-flash-version=[plugin version]
  • And optionally --allow-outdated-plugins to disable browser notifications about outdated plugins

On #windows, create a Chromium shortcut. Then go to its properties and edit the target field: --ppapi-flash-path="C:\PepperFlash\pepflashplayer.dll" --ppapi-flash-version="" --allow-outdated-plugins
On #mac, you will need to launch it from the command-line (in the Terminal): /Applications/ --ppapi-flash-path=/Library/Internet\ Plug-Ins/PepperFlashPlayer/PepperFlashPlayer.plugin --ppapi-flash-version= The "&" at the end is not a typo. It is there to make sure Chromium is launched in a separate thread. Without the "&", Chromium would exit as soon as you quit the Terminal. Moreover, to simplify the Chromium launch, check How to create simple Mac apps from shell scripts (Archive: 1). Also see the #comment-566 and #comment-344.

4. Restart the browser

Relaunch it to apply changes.

5. Check the installation

6. Enjoy!

Now, even after browser updates, Chromium uses PepperFlash. ^^

NPAPI plugin support

Chromium build 45.0.2416.0 (331982) is the last version which still has NPAPI plugin support enabled via chrome://flags or group policy registry. (sourceNPAPI deprecation)

Solutions to still use NPAPI plugins:
More info on site archives:

HTML5 audio/video

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

  • Use Nik builds on #windows or Marmaduke builds on #mac. All codecs are enabled ^^
  • or compile Chromium from #source-code
  • or install an older version having ffmpegsumo file (Ex: 333350, 333334, 333283, 333258...)
  • or choose other #browsers
  • On #linux, you can use Chromium with proprietary codecs

Before 4 June 2015, we used an alternative with the Google Chrome ffmpegsumo file and our Patch HTML5 Media extension. More info on site archives:

1. Check HTML5 audio/video support

If there is a video issue, disable hardware acceleration (see #browser-crash).


1. Internal pages

To access to all internal pages, use chrome://about. Copy and paste this special URL directly into the address bar (omnibox).
Obviously, this special URL works only in Chromium and Google Chrome.

About plugins
Since version 57, the chrome://plugins page no longer exists. (official source)


Few internal pages:
Note: About configuration settings, there is nothing similar to Firefox's about:config in Chromium.

Example: How to clear DNS cache?
Open chrome://net-internals/#dns and click on the Clear host cache button.

2. Keyboard shortcuts

To use keyboard shortcuts (on Windows, Mac and Linux), check this full list of official shortcuts... and this one if you are developer. Most of the shortcuts are similar to IE, Firefox or any other browser.

3. User data directory

About your bookmarks, profile... it is important to know where is stored your user data.

4. Command-line flags

There are command-line flags (or "switches") that Chromium accept in order to enable particular features or modify otherwise default functionality. Note flags often contain experimental or obsolete code, so they tend not to stick around for long.
Example: How to start Chromium directly in incognito (or private) mode on Windows?
Add flag at the end of the Chromium shortcut and restart the browser. (screenshot)
"C:\{...}\Chromium\Application\chrome.exe" --incognito

5. External extension installation

How to install an external brower add-on?
  1. Get source .crx file of any extension directly from the Chrome Web Store via CRX Viewer, Chrome extension source viewer, Get CRX or via a site like Chrome Extension Downloader, Crx4Chrome
  2. Go to chrome://extensions
  3. Drag and drop the .crx file on the page

If it does not work...
  1. Unzip the .crx file
  2. Go to chrome://extensions
  3. Drag and drop the unzipped folder on the page... or click on Developer mode then Load unpacked extension...

About updates:
  • You have to update manually
  • You can update when you want! ^^
  • If ever a new version sucks, just re-install the previous one

6. Source code

Before all, check the official guide for developers.

Official links to easily get or see the full Chromium source code:
Interesting info:

7. Older version

Never update your browser with a very old version. It even does not start.

To downgrade Chromium installed with the Installer (.exe):
  1. Open Chromium and check its actual version at chrome://version
  2. Close Chromium.
  3. Uninstall Chromium WITHOUT to delete your #user-data-directory. It is an option of its uninstaller. (screenshot)
  4. Get the Installer (.exe) of an older version (from the → download/ page or Snapshots repository about "official" builds)
  5. Execute it to install Chromium.
  6. Open Chromium and check the new installed version at chrome://version

8. Browser crash

You have encountered a browser crash or issue :/

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

Also you can use #command-line-flags: --disable-extensions, --disable-gpu, --disable-accelerated-video-decode...
Note that incognito mode disables all extensions by default.


This is a free and simple API for developers to update Chromium to the latest good build via a bash (shell) script, a browser extension... Read my #notes.

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

GET request parameters:
  • os(required) windows or mac or android
  • bit(optional • 64 by default) 64 or 32
  • out(optional • json by default) json or string or xml or revision

chromiumwindows or mac or android
  • architecture(string) 64-bit or 32-bit
  • timestamp(integer) Unix time of this release built on the Chromium Buildbot server
  • editor(string) The Chromium Authors
  • channel(string) dev
  • repository(string) snapshots
  • version(string) (like xx.x.xxxx.x)
  • revision(integer) Git revision's commit position
  • commit(string) Git revision's commit hash

Basic examples:
Example to get the latest build with the outrevision parameter:


1. Open-source browsers

2. Chromium forks

In simple words, a fork of Chromium means Chromium engine is used to create another web browser.

Proprietary browsers:
(developed by official contributors of the Chromium #project)
I do not recommend:
Why not recommended?
Because all of these browsers are closed-source, outdated, based on Chromium (like Google Chrome and Opera)... and most of the features they remove don't even exist in Chromium, in the first place. Control your personal info and #privacy yourself ^^

Moreover, InsanityBit explains this very well on his blog: SRWare Iron Browser – A private alternative to Chrome? (2012 • Archives: 1, 2)

Note if a new browser with "better privacy" than Google Chrome is based on Chromium and is fully open-source, it should be ok for me. But... Google is famous. Its private policy and marketing strategy are well known. So you have to ask you some questions. Do you trust in an unknown team more than Google? Is an outdated Chromium fork?
Few free and open-source Chromium forks:


For a better privacy protection, use open-source #browsers like Chromium or Firefox. Do not forget: It is open-source does not mean it is secure and respects user privacy (and security ≠ privacy). But, if your browser is fully "open-source", it means that somebody with the capability can review the #source-code. With versioning tools like SVN or Git, it is 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.


4. DNS services

By default you are using the DNS servers of your ISP but you do not have to stick with them. Free alternative Internet DNS services for personal use:
Info: CompareDNS Performance

5. Web search engines

Note: Few #extensions exist to protect your privacy on search engines.

Search engines

Metasearch engine

If you are a web developer, use your own metasearch engine yourself ^^

6. Extensions

Note: Extensions hosted on Chrome Web Store are updated via the Chrome update mechanism (cf. Chromium source code) which developers and users do not control. For a manual installation, read the #external-extension-installation part.

Priority to open-source (no code obfuscation) extensions for Chromium and Firefox:

Block ads, trackers, scripts and popups

uBlock Origin + uBO-Extra

Stop everyone from tracking you


Force to use secure connection of websites (https://)

HTTPS Everywhere

Stop link redirection in Google, DuckDuckGo and Yandex search pages

Google search link fix

Control the HTTP Referer on a per-site basis

Referer Control

Prevent canvas fingerprint

Canvas Defender

Emule locally CDN


Prevent WebRTC IP leak

WebRTC Leak Prevent

Unblock websites with a browser VPN/proxy

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


Your antivirus has detected 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 surely 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. You will get a similar result if you compile Chromium yourself.

Note a thing relative to Chromium browser:
  1. Chromium has no digital signature (unlike Google Chrome)
  2. VirusTotal is a Google service which use its Trusted Source project to limit false positives... in Google Chrome (because it is digitally signed), not in Chromium.
  3. So, unsigned Chromium + VirusTotal service = More chance to get an antivirus alert.

False positive reports known for few years ago:

Authentic malware?

Yes. Obviously, it is also 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 Browser, Fusion Browser, Mustang Browser, MyBrowser, Olcinium Browser, Palikan, Qword Browser, Torch, Tortuga Browser...).
  • The other way is about a compromised Chromium repository on a reliable source (#notes).

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


Quick access: #Read the latest comment

Now, you can post anonymously remarks and suggestions about this site. Do not hesitate! ;)

Please, DO NOT report bugs by a review. Use the official issue tracker or chromium-discuss/dev topics:!forum/chromium-discuss!forum/chromium-dev

Also, I prefer direct links. You are not on Twitter ;)

Thank you for your attention!
Reload this page to display older comments

30 latest comments

Thanks for the clarification Rob. Hopefully that doesn't last too long.
maybe useful for somebody - not sure if its good enought for listing here on your site
Chrome Bookmarks Recovery Tool
@marmaduke I love your builds! The July 3 one is good, but I can't seem to resize the browser window by dragging the corners or sides, it just lets me move it around. I was able to use Window > Zoom to make it the size of the screen, but that's it.

I've noticed that! I'll investigate. Hopefully, the resizing problem will be solved by by dev build 70 - my next intended (DEV) build.

Stable build 67.0.3396.XXX will be the last build with no WebRTC: I will build the last revision.
Chromium 69.0.3492.0 (Official Build) unstable (Linux 64-bit) - No Sync | WebRTC Enabled | No Widevine
Revision 74ff2c231069c5746724df6f4f1e1c93fcac991e-refs/heads/master@{#575161}
Compiler clang (+lld_linker +thinlto +pgo/afdo +linker_optimizations)
Good news on 69.0.3492.0 (575161) the tabs don't require to be on foreground anymore to load. They now load when in the background. Normal behavior restored. Thank you Rob for the update.
Buck Ofama
Address bar is back in focus in 69.0.3492.0. No more Ctrl+L. Great.
Is nik's stable latest no sync build working ok ? I cant log in to gmail, i get error "something went wrong". i tried clearing all caches, tried reinstalling, nothing helped.
Jan van Westland

As I understand it Chromium does not auto update from one stable version to the other automatically.
For me this is the only reason why I will not install it yet.
However, as soon as this is implemented I, and I believe many many others, will !!!!
@user: sometimes it's happens, i don't know why, maybe because it's nosync
@Jan van Westland: i doubt it, but you can use chrlauncher
Buck Ofama
@user I get that happening for some time now, but loads fine in incognito mode.
@marmaduke when can we expect a new stable macos build? Thanks!
@user @nik

I had that issue after upgrading to 67 and had no idea how to fix it. tried everything, even new profile. just used gmail in incognito for a while but that was annoying.

for some reason the google sign-on "challenge" (captcha maybe?) returns a 401 response and fails to sign in.

can confirm that switching to sync build makes it work again
@nik @user @twig
I think it has something to do with chrome://flags/#account-consistency
Disabling it fixes the login issue.
nik: how can I see which is the latest lkcr (or dev) 64-bit version with sync, WebRTC, Widevine, and codecs?

On the github releases pages, widevine isn't mentioned but I see that v69.0.3470.0-r569821-win64 has it and I can play Widevine protected content.

In addendum to #comment-3619, you will now need to disable chrome://flags/#ntp-backgrounds too
@earthsound: widevine is enabled in all my builds
@nik, then why your 64-bit stable nosync, 64-bit dev sync, 32-bit stable nosync builds are labeled "No Widevine" here?
@Anon3649: sorry my bad, only the "sync" have widevine (anyway soon the "nosync" will be gone)
@nik, 64-bit dev sync builds are still labeled "No Widevine"!
@RobRich, uMatrix extension randomly crashed on 69.0.3492.0, and once the browser went nuts with the screen blacked out for a sec, looks like a buggy build. Downgrading to 69.0.3487.0.
Thanks for that @Anon3644, I was wondering why switching to sync on Windows build worked but not Mac build.

Back to nosync for me!
@Anon3642 - upthread @marmaduke said his next build would be version 70, so hopefully his will drop soon after The Chromium Team releases 70
Sorry, I was away for 2 weeks.

However, I come back with a Beta version!
Warning : x64 only for Beta-test…

Nothing better than Rob, Nik or Marmaduke it's just a version adapted to my preferences that I share:

It get in particular:
 1/ A compact bookmarks bar between Rob appearance and Firefox style.
 2/ Normally no error to connect to Google, Youtube or Alphabet-like accounts.
 3/ Full codecs:
 a/ Widevine in theory works: be careful to check/update it before in « chrome://components » (Widevine Content Decryption Module - Version: - Search for updates)
 b/ The recent AV1 codec will only work after « Enabled » it in « chrome://flags/#enable-av1-decoder »
 4/ The default classic appearance. But it is possible to force Material Refresh (Yuck! Sic!) into « chrome://flags/#top-chrome-md »
 5/ The old classic New Tab page.

So I'm looking for Beta-testers to check :
 α/ That Netflix, Youtube, Twitter, Spotify, Google, Deezer, Facebook and so on that I don’t use works without errors…
 β/ That all videos found on the Net are playable…
 γ/ That the default appearance of the browser and the « new tab » page are in classic style by default under Windows 7, 8.1 and 10.

If everything works flawlessly for everyone I will put an online tutorial with all sources/changes I made so that anyone can compile the same browser as this one or copy only part that interest them (bookmarks, codecs, Classic UI, etc.).

If there is a problem, thank you to tell me here what wrong that I add it to my need-to-repair list.

So here we are :
Chromium 69.0.3496.0 (Official build) (64 bits)
Révision 7e9fce12dabda70dab7b51b1f7d4c5143e3a1736-refs/heads/master@{#576093}

« » compatible version with Nik / Henry++ format ➜ (78,5 Mo)
« mini_installer.exe » version ➜ (45,7 Mo)

Note: I did not invent anything it is a compilation of all the advice I received in the comments section here and everyone will be thanked by (pseudo)name in the future tutorial with my alpha / official version.

Note²: Do not hotlink, this is a temporary-link-hosting for this Beta version while waiting to open a more serious Github or give everything to Rob, Jerry, Henry++ and/or Nik.
Thank you very much Mumu. I test your build.
@Sebas: I am happy you wrote this about the google account issue. Since a while I cannot log in either to google services such as gmail or drive. I get error message with no further detail. I checked my chromium (nosync, stable from nik) settings again and again, also my extensions, but I cant login to google. But I never tried out to open a.e. gmail in incognito window. And youre right, there it works.
I hope, issue get fixed with new version from chromium.
Blaise Matuidi

In the words of Burning Spear: "It is good when a man can think for himself"

I've tested your build (apart from Netflix - Blaise prefers NetTorrents! Luke Cage in 4K is a delight.) and everything appears to be OK. Looking forward to the tutorial so that I can incorporate some of your features into my build.

I've always found Nik, RobRich and that rather cantankerous Novichok addict Marmaduke to be quite generous with their advice: IF individuals are willilng to make an effort.


Youtube, Twitter and Google works fine from scratch. Netflix and Spotify works after go to "chrome://components" and update "Widevine Content Decryption Module" like you mentioned.
I don't use Deezer so can't test. Same goes for Facebook.
The default appearance of the browser is the classic style, no new modern stuff.
Bookmarks also have the compact view, even more compact than Rob's builds.

Will test further.

Appreciate your efforts :)
Thanks guys !

It seem there is not too much errors except with automatic translation that seems to be dependent on « sync » or « no-sync » version.
I must investigate this point.

The purpose of my future tutorial is not to give the changes that I made without explanations but to provide some advice for anyone that want to build their own Chromium to choose and understand what they want to do or not. (to choose for example bookmarks bar’s height, margin & padding, color ; widevine or not, sync or not, etc.)

That permit also to everyone to participate as Nik, Rob, Marmaduke and Juan Guillermo Cuadrado Bello for example which had help me to build this.

Soon, we will succeed in making our own Open-source Chromium only between us without being forced to apply disgusting and ugly changes imposed by Google ;)

I'm a bit slow at the moment because I have lots of stuff to settle IRL in addition to holidays, but we'll get there !
Has @marmaduke disappeared?

Side note - what do others think of the UI refresh coming? I think it is an awful direction to move towards - hopefully there will be a way to stick to the old interface.

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

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