Google Chrome 64-bit Exits Beta: Stable Version Officially Available for Free Download

On August 26, 2014, Google announced the launching of Chrome 64-bit Stable on their official chromium developer blog. With the native x64 support now available on Chrome, the browser could offer many enhanced features which was not possible in its x86 build.

Normally, Google would only provide web-install for downloading and installing Chrome. Personally, I hate using web-installers. Wanna know why? Just take this scenario.

An admin is looking for to deploy/upgrade Google Chrome on about 100 computers in an enterprise network.

Normally, he would have to do web-install on each 100 computers of that enterprise. Seems easy? No, it’s not easy.

When doing web-install, we have to remember that; the Google Chrome is downloaded on each computer of that enterprise.

Let’s do the math.

Typically, the installer binary of Google Chrome ranges between 35-40 MiB in size. So, if the admin decides to try out the web-install method for each 100 computers of that enterprise network, he would probably have to download 3.4 GiB of data!

100 computers X 35 MiB = 3.4 GiB (3.41796875 MiB)!

(I took the MiB, GiB notation instead of MB, GB values. MiB, GiB stands for Mebibyte and Gibibyte respectively. The difference with the two types of notations is that, the Megabyte [MB], Gigabyte [GB] notations use 10 as their base. Whereas, the Mebibyte [MiB], Gibibyte [GiB] notations use 2 as their base.

The MiB, GiB values was established by the IEC [International_Electrotechnical_Commission] to end the confusion between the earlier SI decimal prefix of Megabyte [MB], Gigabyte [GB] values and the binary prefixes of base 2.)

Back to the topic! Yes, downloading 3.4 GiBs of data just for installing Google Chrome on 100 computers, is just an example of utter wastage of bandwidth. In other words, installing Google Chrome via web-install on each 100 computers is a bandwidth hog on the network.

Internet bandwidth is a finite resource. We should learn to conserve it and use it more intelligently.

That’s why I’m a big fan of standalone offline installers. Not only it conserves bandwidth, it’s also very simple to use and deploy. Standalone installer method is much more efficient than the web-installer one.

Official Download Links

Click here to download Google Chrome x64 (64-bit) [v 37.0.2062.94] from Google’s server

Click here to download Google Chrome x86 (32-bit) [v 37.0.2062.94] from Google’s server

If you’re having any trouble downloading from the above official links, try downloading from our public FTP servers.

Google Chrome x64 (64-bit) [v 37.0.2062.94]

1) FTP Server 1:

     FTP Server 2:

2) HTTP Server 1:

     HTTP Server 2:

Google Chrome x86 (32-bit) [v 37.0.2062.94]

1) FTP Server 1:

     FTP Server 2:

2) HTTP Server 1:

      HTTP Server 2:

Tip: Before installing the x64 build, you have to first uninstall the x86 build of Google Chrome, keeping the history and bookmarks intact. It’s because, even after you install the x64 build along with the x86 one, when trying to launch Google Chrome, the x86 build will open up, instead of the x64 one.

Checksums (SHA-512)

Google Chrome x64 (64-bit): BDCB9FABE23F759418E753758BDA04248195591930420551617217C64E59AF269A7DF53F187B91FCF26F55AAB1824A3EE2584C42AAA6A05369259E9DF8E328B8

Google Chrome x86 (32-bit): 824DF45B706494DCECCB934730C6E6B12EA0C2CF2C5C456C2B1D46DE32E16C07D08E05C93C019FB99A005DA3E495A2F37D472E5A29CC7A1FE683536E78C9AC90

Copyright: Text is licensed to Robin Mathew Rajan under the Creative Commons Attribution-ShareAlike 3.0 Unported License. To view a copy of this license, visit

For those who don’t know, the ‘Creative Commons’ license doesn’t forbid copying. It actually allows anyone to copy the licensed text. But with only one condition! Proper source must be specified with the copied text. That is, if someone copied some text which is licensed under the Creative Commons, he/she must attribute/acknowledge the original source and author of that text.