Google Chrome

This article is about the web browser. For the operating system, see Chrome OS.
Google Chrome

Google Chrome 54.0.2824.0 running on Windows 10
Developer(s) Google Inc.
Initial release September 2, 2008 (2008-09-02)
Stable release(s) [±]
Windows, macOS, Linux 55.0.2883.75 / December 1, 2016 (2016-12-01)[1]
Android 54.0.2840.98 / November 8, 2016 (2016-11-08)[2]
iOS 54.0.2840.91 / November 4, 2016 (2016-11-04)[3]
Preview release(s) [±]
Beta (Windows, macOS, Linux) 55.0.2883.75 / December 1, 2016 (2016-12-01)[4]
Beta (Android) 55.0.2883.75 / December 1, 2016 (2016-12-01)[5]
Dev (Windows, macOS, Linux) 56.0.2924.14 / December 2, 2016 (2016-12-02)[6]
Dev (Android) 56.0.2924.13 / December 1, 2016 (2016-12-01)[7]
Development status Active
Written in C++[8]
Operating system
Engines Blink (WebKit on iOS), V8
Platform IA-32, x64, ARMv7
Available in 47 languages[10]
Type Web browser, mobile browser
License Freeware under Google Chrome Terms of Service[11][note 1]

Google Chrome is a freeware web browser developed by Google.[11] It was first released in 2008, for Microsoft Windows, and was later ported to Linux, macOS, iOS and Android. Google Chrome is also the main component of Chrome OS, where it serves a platform for running web apps.

Google releases the majority of Chrome's source code as the Chromium open-source project.[12][13] A notable component that is not open-source is the built-in Adobe Flash Player (that Chrome will start blocking later in 2016[14]). Chrome used the WebKit layout engine until version 27. As of version 28, all Chrome ports except the iOS port use Blink, a fork of the WebKit engine.[15][16][17]

As of October 2016, StatCounter estimates that Google Chrome has a 63% worldwide usage share of web browsers as a desktop browser.[18] It also has 50% market share across all platforms combined,[19] because it's also the most popular browser for smartphones. Its success has led to Google expanding the "Chrome" brand name on various other products such as Chromecast, Chromebook, Chromebit, Chromebox and Chromebase.


Google CEO Eric Schmidt opposed the development of an independent web browser for six years. He stated that "at the time, Google was a small company," and he did not want to go through "bruising browser wars." After co-founders Sergey Brin and Larry Page hired several Mozilla Firefox developers and built a demonstration of Chrome, Schmidt admitted that "It was so good that it essentially forced me to change my mind."[20]

Rumors of Google building a web browser first appeared in September 2004. Online journals and U.S. newspapers stated at the time that Google was hiring former Microsoft web developers among others. It also came shortly after the final 1.0 release of Mozilla Firefox, which was surging in popularity and taking market share from Internet Explorer which was suffering from major security problems.[21]


The release announcement was originally scheduled for September 3, 2008, and a comic by Scott McCloud was to be sent to journalists and bloggers explaining the features within the new browser.[22] Copies intended for Europe were shipped early and German blogger Philipp Lenssen of Google Blogoscoped[23] made a scanned copy of the 38-page comic available on his website after receiving it on September 1, 2008.[24] Google subsequently made the comic available on Google Books[25] and mentioned it on their official blog along with an explanation for the early release.[26] The product was allegedly named "Chrome" because Google wanted to minimize the chrome of the browser,[27] though this meaning was added somewhat post-hoc, the 'codename' before release apparently chosen from a connotation of speed (and most simply as a derivative of 'Chromium').[28]

Public release

An early version of Chromium for Linux, explaining the difference between Chrome and Chromium

The browser was first publicly released on September 2, 2008 for Windows XP and later, with 43 supported languages, officially a beta version,[29] and as a stable public release on December 11, 2008.

On the same day, a CNET news item[30] drew attention to a passage in the Terms of Service statement for the initial beta release, which seemed to grant to Google a license to all content transferred via the Chrome browser. This passage was inherited from the general Google terms of service.[31] Google responded to this criticism immediately by stating that the language used was borrowed from other products, and removed this passage from the Terms of Service.[11]

Chrome quickly gained about 1% usage share.[26][32][33][34] After the initial surge, usage share dropped until it hit a low of 0.69% in October 2008. It then started rising again and by December 2008, Chrome again passed the 1% threshold.[35]

In early January 2009, CNET reported that Google planned to release versions of Chrome for OS X and Linux in the first half of the year.[36] The first official Chrome OS X and Linux developer previews[37] were announced on June 4, 2009, with a blog post[38] saying they were missing many features and were intended for early feedback rather than general use.

In December 2009, Google released beta versions of Chrome for OS X and Linux.[39][40] Google Chrome 5.0, announced on May 25, 2010, was the first stable release to support all three platforms.[41]

Chrome was one of the twelve browsers offered to European Economic Area users of Microsoft Windows in 2010.[42]


Chrome was assembled from 25 different code libraries from Google and third parties such as Mozilla's Netscape Portable Runtime, Network Security Services, NPAPI (dropped as of version 45),[43] Skia Graphics Engine, SQLite, and a number of other open-source projects.[44] The V8 JavaScript virtual machine was considered a sufficiently important project to be split off (as was Adobe/Mozilla's Tamarin) and handled by a separate team in Denmark coordinated by Lars Bak at Aarhus. According to Google, existing implementations were designed "for small programs, where the performance and interactivity of the system weren't that important", but web applications such as Gmail "are using the web browser to the fullest when it comes to DOM manipulations and JavaScript", and therefore would significantly benefit from a JavaScript engine that could work faster.

Chrome initially used the WebKit rendering engine to display web pages. In 2013, they forked the WebCore component to create their own layout engine Blink. Based on WebKit, Blink only uses WebKit's "WebCore" components, while substituting other components, such as its own multi-process architecture, in place of WebKit's native implementation.[45]

Chrome is internally tested with unit testing, "automated user interface testing of scripted user actions", fuzz testing, as well as WebKit's layout tests (99% of which Chrome is claimed to have passed), and against commonly accessed websites inside the Google index within 20–30 minutes.[25]

Google created Gears for Chrome, which added features for web developers typically relating to the building of web applications, including offline support.[25] Google phased out Gears as the same functionality became available in the HTML5 standards.[46]

On January 11, 2011, the Chrome product manager, Mike Jazayeri, announced that Chrome would remove H.264 video codec support for its HTML5 player, citing the desire to bring Google Chrome more in line with the currently available open codecs available in the Chromium project, which Chrome is based on.[47] Despite this, on November 6, 2012, Google released a version of Chrome on Windows which added hardware-accelerated H.264 video decoding.[48] In October 2013, Cisco announced that it was open-sourcing its H.264 codecs and will cover all fees required.[49]

On February 7, 2012, Google launched Google Chrome Beta for Android 4.0 devices.[50] On many new devices with Android 4.1 and later preinstalled, Chrome is the default browser.[51]

Version history


Google Chrome features a minimalistic user interface, with its user-interface principles later being implemented into other browsers. For example, the merging of the address bar and search bar into the omnibox.[52] Chrome also has a reputation for strong browser performance.[53][54]

Bookmarks and settings synchronization

Chrome allows users to synchronize their bookmarks, history, and settings across all devices with the browser installed by sending and receiving data through a chosen Google Account, which in turn updates all signed-in instances of Chrome. This can be authenticated either through Google credentials, or a sync passphrase.

Web standards support

The results of the Acid3 test on Google Chrome 4.0

The first release of Google Chrome passed both the Acid1 and Acid2 tests. Beginning with version 4.0, Chrome has passed all aspects of the Acid3 test.[55]

As of May 2011, Chrome has very good support for JavaScript/ECMAScript according to Ecma International's ECMAScript standards conformance Test 262[56] (version ES5.1 of 2012-05-18). This test reports as the final score the number of tests a browser failed; hence lower scores are better. In this test, Chrome version 37 scored 10 failed/11578 passed. For comparison, Firefox 19 scored 193 failed/11752 passed and Internet Explorer 9 has a score of 600+ failed, while Internet Explorer 10 has a score of 7 failed.

In 2011, on the official CSS 2.1 test suite by standardization organization W3C, WebKit, the Chrome rendering engine, passes 89.75% (89.38% out of 99.59% covered) CSS 2.1 tests.[57]

On the HTML5 web standards test, Chrome 41 scores 518 out of 555 points, placing it ahead of the five most popular desktop browsers.[58][59] Chrome 41 on Android scores 510 out of 555 points.[60][61][62] Chrome 44 scores 526, only 29 points less than the maximum score.[63]


Chrome periodically retrieves updates of two blacklists (one for phishing and one for malware), and warns users when they attempt to visit a site flagged as potentially harmful. This service is also made available for use by others via a free public API called "Google Safe Browsing API".[25]

Chrome uses a process-allocation model to sandbox tabs.[64] Using the principle of least privilege, each tab process cannot interact with critical memory functions (e.g. OS memory, user files) or other tab processes  similar to Microsoft's "Protected Mode" used by Internet Explorer 9 or greater. The Sandbox Team is said to have "taken this existing process boundary and made it into a jail." This enforces a computer security model whereby there are two levels of multilevel security (user and sandbox) and the sandbox can only respond to communication requests initiated by the user.[65] On Linux sandboxing uses the seccomp mode.[66][67]

Since 2008, Chrome has been faulted for not including a master password to prevent casual access to a user's passwords. Chrome developers have indicated that a master password does not provide real security against determined hackers and have refused to implement one. Bugs filed on this issue have been marked "WontFix".[68][69] As of February 2014, the Windows version asks the user to enter the Windows account password before showing saved passwords.[70]

In January 2015, TorrentFreak reported that using Chrome when connected to the internet using a VPN can be a serious security issue due to the browser's support for WebRTC.[71]

On September 12, 2016, it was reported that starting with Chrome 56, users will be warned when they visit non-secure HTTP websites to encourage more sites to make the transition to HTTPS.[72]

Security vulnerabilities

No security vulnerabilities in Chrome were exploited in the three years of Pwn2Own from 2009–2011.[73]

At Pwn2Own 2012, Chrome was defeated by a French team who used zero day exploits in the version of Flash shipped with Chrome to take complete control of a fully patched 64-bit Windows 7 PC using a booby-trapped website that overcame Chrome's sandboxing.[74]

Chrome was compromised twice at the 2012 CanSecWest Pwnium.[74][75][76] Google's official response to the exploits was delivered by Jason Kersey, who congratulated the researchers, noting "We also believe that both submissions are works of art and deserve wider sharing and recognition."[77] Fixes for these vulnerabilities were deployed within 10 hours of the submission.[78][79]

A significant number of security vulnerabilities in Chrome occur in the Adobe Flash player. For example, in the 2016 Pwn2Own successful attack on Chrome relied on four security vulnerabilities. Two of the vulnerabilities were in Flash, one was in Chrome, and one was in the Windows kernel.[80] In 2016, Google announced that it was planning to phase out Flash Player in Chrome, starting in version 53. The first phase of the plan is to disable Flash for ads and "background analytics", with the ultimate goal of disabling it completely by the end of the year, except on specific sites that Google has deemed to be broken without it. Flash would then be re-enabled with the exclusion of ads and background analytics on a site-by-site basis.[81]

Malware blocking

Google introduced download scanning protection in Chrome 17.[82]



Incognito mode

Google Chrome in Incognito mode

The private browsing feature called Incognito mode prevents the browser from permanently storing any history information or cookies from the websites visited. Incognito mode is similar to the private browsing feature in other web browsers. It doesn't prevent saving in all windows: "You can switch between an incognito window and any regular windows you have open. You'll only be in incognito mode when you're using the incognito window".[94]

User tracking

Chrome sends details about its users to Google through both optional and non-optional user tracking mechanisms.[95]

Some of the tracking mechanisms can be optionally enabled and disabled through the installation interface[96] and through the browser's options dialog.[97] Unofficial builds, such as SRWare Iron, seek to remove these features from the browser altogether.[98] The RLZ feature is not included in the Chromium browser either.[99]

In March 2010, Google devised a new method to collect installation statistics: the unique ID token included with Chrome is now only used for the first connection that Google Update makes to its server.[100]

The optional suggestion service included in Google Chrome has been criticized because it provides the information typed into the Omnibox to the search provider before the user even hits return. This allows the search engine to provide URL suggestions, but also provides them with web usage information tied to an IP address.[101]

The optional feature to use a web service to help resolve spelling errors has privacy implications.[102]

Tracking methods
Method[98] Information sent When Optional?
Installation Randomly generated token included in installer. Used to measure success rate of Google Chrome once at installation.[103]

On installation

RLZ identifier[104] Encoded string, according to Google, contains non-identifying information about where Chrome was downloaded from and its installation week, and is used to measure promotional campaigns.[103] Google provides the source code to decode this string.[99]
  • On Google search query
  • On first launch and first use of address bar[103]
[note 2][103]
clientID[97] Unique identifier along with user preferences, logs of usage metrics and crashes. Unknown Yes[105]
default disabled
Omnibox predictions[97] Text typed into the address bar. While typing Yes
default enabled
Page not found Text typed into the address bar. Upon receiving "Server not found" response Yes
default enabled
Google Update (Windows) Information about how often Chrome is used, details about the OS and Chrome version. Periodically Partial
[note 3][106]
Google Software Update (OS X)

Do Not Track

In February 2012, Google announced that Chrome would support Do Not Track (DNT) by the end of 2012; the protocol was implemented in version 23. In line with the W3's draft standard for DNT,[107] it is turned off by default in Chrome.[108]


The JavaScript virtual machine used by Chrome, the V8 JavaScript engine, has features such as dynamic code generation, hidden class transitions, and precise garbage collection.[25]

In 2008, several websites performed benchmark tests using the SunSpider JavaScript Benchmark tool as well as Google's own set of computationally intense benchmarks, which include ray tracing and constraint solving.[109] They unanimously reported that Chrome performed much faster than all competitors against which it had been tested, including Safari (for Windows), Firefox 3.0, Internet Explorer 7, Opera, and Internet Explorer 8.[110][111][112][113][114][115] However, on October 11, 2010, independent tests of JavaScript performance, Chrome has been scoring just behind Opera's Presto engine since it was updated in version 10.5.[116]

On September 3, 2008, Mozilla responded by stating that their own TraceMonkey JavaScript engine (then in beta), was faster than Chrome's V8 engine in some tests.[117][118][119] John Resig, Mozilla's JavaScript evangelist, further commented on the performance of different browsers on Google's own suite, commenting on Chrome's "decimating" of the other browsers, but he questioned whether Google's suite was representative of real programs. He stated that Firefox 3.0 performed poorly on recursion-intensive benchmarks, such as those of Google, because the Mozilla team had not implemented recursion-tracing yet.[120]

Two weeks after Chrome's launch in 2008, the WebKit team announced a new JavaScript engine, SquirrelFish Extreme,[121] citing a 36% speed improvement over Chrome's V8 engine.[122][123][124]

Like most major web browsers, Chrome uses DNS prefetching to speed up website lookups,[125] as do other browsers like Firefox,[126] Safari,[127] Internet Explorer (called DNS Pre-resolution),[128] and in Opera as a UserScript (not built-in).[129]

Chrome formerly used their now deprecated SPDY protocol instead of only HTTP[130][131] when communicating with servers that support it, such as Google services, Facebook, Twitter. SPDY support was removed in Chrome version 51.


Screenshot of Chrome browser crash

A multi-process architecture is implemented in Chrome[132] where, by default, a separate process is allocated to each site instance and plugin. This procedure is termed process isolation,[133] and it prevents tasks from interfering with each other, raising security and stability. An attacker successfully gaining access to one application gains access to no others,[134] and failure in one instance results in a Sad Tab screen of death, similar to the well-known Sad Mac, but only one tab crashes instead of the whole application. This strategy exacts a fixed per-process cost up front, but results in less memory bloat over time as fragmentation is confined to each instance and no longer needs further memory allocations.[25] This architecture was adopted in Safari[135] and Firefox.[136]

Chrome includes a process management utility called Task Manager which lets users see what sites and plugins are using the most memory, downloading the most bytes and overusing the CPU and provides the ability to terminate them.[25] Chrome Version 23 ensures its users an improved battery life for the systems supporting Chrome's GPU accelerated video decoding.[137][138]

User interface

Google Chrome logos
3D motif from project start until March 2011
2D motif from March 2011 to October 2015
Material Design motif used from September 2014 onward for mobile version and October 2015 onward for the desktop version

By default, the main user interface includes back, forward, refresh/cancel and menu buttons. A home button is not shown by default, but can be added through the Settings page to take the user to the new tab page or a custom home page.[139]

Tabs are the main component of Chrome's user interface and as such, have been moved to the top of the window rather than below the controls. This subtle change contrasts with many existing tabbed browsers which are based on windows and contain tabs. Tabs, with their state, can be transferred seamlessly between window containers by dragging. Each tab has its own set of controls, including the Omnibox.[25]

The Omnibox is a URL box that combines the functions of both the address bar and search box. If a user enters the URL of a site previously searched from, Chrome allows pressing Tab to search the site again directly from the Omnibox. When a user starts typing in the Omnibox, Chrome provides suggestions for previously visited sites (based on the URL or in-page text), popular websites (not necessarily visited before  powered by Google Instant), and popular searches. Although Instant can be turned off, suggestions based on previously visited sites cannot be turned off. Chrome will also autocomplete the URLs of sites visited often.[25] If a user types keywords into the Omnibox that don't match any previously visited websites and presses enter, Chrome will conduct the search using the default search engine.

One of Chrome's differentiating features is the New Tab Page, which can replace the browser home page and is displayed when a new tab is created. Originally, this showed thumbnails of the nine most visited web sites, along with frequent searches, recent bookmarks, and recently closed tabs; similar to Internet Explorer and Firefox with Google Toolbar, or Opera's Speed Dial.[25] In Google Chrome 2.0, the New Tab Page was updated to allow users to hide thumbnails they did not want to appear.[140]

Starting in version 3.0, the New Tab Page was revamped to display thumbnails of the eight most visited web sites. The thumbnails could be rearranged, pinned, and removed. Alternatively, a list of text links could be displayed instead of thumbnails. It also features a "Recently closed" bar that shows recently closed tabs and a "tips" section that displays hints and tricks for using the browser.[141]

Chrome includes a bookmarks submenu that lists the user's bookmarks, provides easy access to Chrome's Bookmark Manager, and allows the user to toggle a bookmarks bar on or off.

For web developers, Chrome features an element inspector (Inspect Element), similar to the browser extension in Firebug, which allows users to look into the DOM and see what makes up the webpage.[125]

Chrome has special URLs that load application-specific pages instead of websites or files on disk. Chrome also has a built-in ability to enable experimental features. Originally called about:labs, the address was changed to about:flags to make it less obvious to casual users.[142][143]

In March 2011, Google introduced a new simplified logo to replace the previous 3D logo that had been used since the project's inception. Google designer Steve Rura explained the company reasoning for the change: "Since Chrome is all about making your web experience as easy and clutter-free as possible, we refreshed the Chrome icon to better represent these sentiments. A simpler icon embodies the Chrome spirit  to make the web quicker, lighter, and easier for all."[144]

In September 2013, Google started making Chrome apps "For your desktop." This meant offline access, desktop shortcuts, and less dependence on Chrome- They launch in a window separate from Chrome, and look more like native applications.[145]

Desktop shortcuts and apps

Chrome allows users to make local desktop shortcuts that open web applications in the browser. The browser, when opened in this way, contains none of the regular interface except for the title bar, so as not to "interrupt anything the user is trying to do". This allows web applications to run alongside local software (similar to Mozilla Prism and Fluid).[25]

This feature, according to Google, will be enhanced with the Chrome Web Store, a one-stop web-based web applications directory which opened in December 2010.[146][147]

Chrome Web Store

Main article: Chrome Web Store

Announced on December 7, 2010, the Chrome Web Store allows users to install web applications as extensions to the browser, although most of these extensions function simply as links to popular web pages and/or games, but some of the apps like Springpad do provide extra features like offline access. The themes and extensions have also been tightly integrated into the new store, allowing users to search the entire catalog of Chrome extras.[148]

The Chrome Web Store was opened on February 11, 2011, with the release of Google Chrome 9.0.[149]


On September 9, 2009, Google enabled extensions by default on Chrome's developer channel, and provided several sample extensions for testing.[150] In December, the Google Chrome extension gallery beta began with over 300 extensions.[40][151]

Along with Google Chrome 4.0, the extension gallery was officially launched on January 25, 2010, containing over 1500 extensions.[152]

As of February 4, 2011, the extension gallery featured more than 11,500 extensions,[153] including official extensions from the Independent,[154] CEOP,[155] Transport for London,[156] Cricinfo,[157] Web of Trust (WOT),[158] and FIFA.[159]

Many Chrome extensions, once installed, have access to the user's data. There are three levels of permissions that an app or extension may request.[160]

On May 27, 2014, Google issued an update to Chrome preventing Windows users from installing extensions obtained outside the Chrome Web Store.[161]


Starting with Google Chrome 3.0, users can install themes to alter the appearance of the browser.[162] Many free third-party themes are provided in an online gallery,[163] accessible through a "Get themes" button in Chrome's options.[164]

Automatic web page translation

Starting with Google Chrome 4.1 the application added a built-in translation bar using Google Translate. Translation is currently available for 52 languages.[165] When Chrome detects a foreign language other than the user's preferred language as set during the installation time, it asks the user whether or not to translate.

Release channels, cycles and updates

The first production release on December 11, 2008, marked the end of the initial Beta test period and the beginning of Production. Shortly thereafter, on January 8, 2009, Google announced an updated release system with three channels: Stable (corresponding to the traditional Production), Beta, and Developer preview (also called the "Dev" channel). Where there were before only two channels: Beta and Developer, now there were three. Concurrently, all Developer channel users were moved to the Beta channel along with the promoted Developer release. Google explained that now the Developer channel builds would be less stable and polished than those from the initial Google Chrome's Beta period. Beta users could opt back to the Developer channel as desired.

Each channel has its own release cycle and stability level. The Stable channel updated roughly quarterly, with features and fixes that passed "thorough" testing in the Beta channel. Beta updated roughly monthly, with "stable and complete" features migrated from the Developer channel. The Developer channel updated once or twice per week and was where ideas and features were first publicly exposed "(and sometimes fail) and can be very unstable at times". [Quoted remarks from Google's policy announcements.][166][167][168]

Google Chrome Canary Application Icon

On July 22, 2010, Google announced it would ramp up the speed at which it releases new stable versions; the release cycles were shortened from quarterly to six weeks for major Stable updates.[169] Beta channel releases now come roughly at the same rate as Stable releases, though approximately one month in advance, while Dev channel releases appear roughly once or twice weekly, allowing time for basic release-critical testing.[170] This faster release cycle also brought a fourth channel: the "Canary" channel, updated daily from a build produced at 09:00 UTC from the most stable of the last 40 revisions.[171] The name refers to the practice of using canaries in coal mines, so if a change "kills" Chrome Canary, it will be blocked from migrating down to the Developer channel, at least until fixed in a subsequent Canary build.[172] Canary is "the most bleeding-edge official version of Chrome and somewhat of a mix between Chrome dev and the Chromium snapshot builds". Canary releases run side-by-side with any other channel; it is not linked to the other Google Chrome installation and can therefore run different synchronization profiles, themes, and browser preferences. This ensures that fallback functionality remains even when some Canary update may contain release-breaking bugs.[173] It does not natively include the option to be the default browser, although on OS X it can be set through System Preferences. Canary was Windows-only at first; an OS X version was released on May 3, 2011.[174]

The Chrome beta channel for Android was launched on January 10, 2013; like Canary, it runs side-by-side with the stable channel for Android.[175][176] Chrome Dev for Android was launched on April 29, 2015.[177]

All Chrome channels are automatically distributed according to their respective release cycles. The mechanism differs by platform. On Windows, it uses Google Update, and auto-update can be controlled via Group Policy.[178] Alternatively, users may download one of two standalone installers of a version of Chrome that does not auto-update.[179][180] On OS X, it uses Google Update Service, and auto-update can be controlled via the OS X "defaults" system.[181] On Linux, it lets the system's normal package management system supply the updates. This auto-updating behavior is a key difference from Chromium, the non-branded open source browser which forms the core of Google Chrome. Because Chromium also serves as the pre-release development trunk for Chrome, its revisions are provided as source code and buildable snapshots are produced continuously with each new commit, requiring users to manage their own browser updates.[182]

Release version numbers

Releases are identified by a four-part version number, e.g. 42.0.2311.90 (Windows Stable release April 14, 2015[183]). The components are[184][185]

Major.minor reflects scheduling policy
Build.patch identifies content progression

Chromium and Chrome release schedules are linked through Chromium (Major) version Branch Point dates, published annually.[184] The Branch Points precede the final Chrome Developer build (initial) release by 4 days (nearly always) and the Chrome Stable initial release by roughly 53 days.[186]

Example: The version 42 Branch Point was February 20, 2015.[184] Developer builds stopped advancing at build 2311 with release 42.0.2311.4 on February 24,[187] 4 days later. The first Stable release, 42.0.2311.90, was April 14, 2015,[183] 53 days after the Branch Point.

Color management

Main article: Color management

Chrome supports color management by using the system-provided ICC v2 and v4 support on OS X, and from version 22 supports ICC v2 profiles by default on other platforms.[188]


In Chrome, when not connected to the Internet and an error message displaying "There is no Internet" is shown, on the top, an "8-bit" Tyrannosaurus rex is shown, but when pressing the space bar on a keyboard, mouse-clicking on it or tapping it on touch devices, the T-Rex instantly jumps once and dashes across a cactus-ridden desert, revealing it to be an easter egg in the form of a platform game.[189][190][191][192] The game itself is an infinite runner, and there is no time limit in the game as it progresses faster and periodically tints to a black background. A school Chromebook administrator can disable the game.[193]


Chrome is available for:

As of April 2016, stable 32-bit and 64-bit builds are available for Windows, with only 64-bit stable builds available for Linux and OS X.[198][202][203] 64-bit Windows builds became available in the developer channel and as canary builds on June 3, 2014,[204] in beta channel on July 30, 2014,[205] and in stable channel on August 26, 2014.[206] 64-bit OS X builds became available as canary builds on November 7, 2013,[207][208] in beta channel on October 9, 2014,[209] and in stable channel on November 18, 2014.[198]

Android version

A beta version for Android 4.0 devices was launched on February 7, 2012, available for a limited number of countries from Google Play.[210]

Notable features: synchronization with desktop Chrome to provide the same bookmarks and view the same browser tabs,[211] page pre-rendering,[212] hardware acceleration.[213]

Many of the latest HTML5 features: almost all of the Web Platform’s features: GPU-accelerated canvas, including CSS 3D Transforms, CSS animations, SVG, WebSocket (including binary messages), Dedicated Workers; it has overflow scroll support, strong HTML5 video support, and new capabilities such as IndexedDB, WebWorkers, Application Cache and the File APIs, date and time pickers, parts of the Media Capture API.[212][214] Also supports mobile oriented features such as Device Orientation and Geolocation.[214]

Mobile customizations: swipe gesture tab switching,[211] link preview allows zooming in on (multiple) links to ensure the desired one is clicked,[211] font size boosting to ensure readability regardless of the zoom level.[214]

Missing in the mobile version are sandboxed tabs,[212][215] Safe Browsing,[212] apps or extensions,[213] Adobe Flash (now and in future),[213] Native Client.[213]

Development changes: remote debugging,[212][216] part of the browser layer has been implemented in Java, communicating with the rest of the Chromium and WebKit code through Java Native Bindings.[214] The code of Chrome for Android is a fork of the Chromium project. It is a priority to upstream most new and modified code to Chromium and WebKit to resolve the fork.[214]

The April 17, 2012 update, included the availability to access in 31 additional languages and in all countries where Google Play is available. A desktop version of a website can also be requested as opposed to a mobile version. In addition, Android users can now add bookmarks to their Android home screens if they choose and decide which apps should handle links opened in Chrome.[217]

On June 27, 2012, Google Chrome for Android exited beta and became stable.[218]

Chrome 18.0.1026311, released on September 26, 2012, was the first version of Chrome for Android to support Intel x86 based mobile devices.[219]

Starting from version 25, the Chrome version for Android is aligned with the desktop version, and usually new stable releases are available at the same time between the Android and the desktop version. Google released a separate Chrome for Android beta channel on January 10, 2013, with version 25.[175] Currently, a separate beta version of Chrome is available in the Google Play store and it can run side-by-side with the stable release.[220]

Chrome OS

Main article: Chrome OS

Google Chrome is the basis of Google's Chrome OS operating system that ships on specific hardware from Google's manufacturing partners.[221] The user interface has a minimalist design resembling the Google Chrome browser. Chrome OS is aimed at users who spend most of their computer time on the Web; the only applications on the devices are a browser incorporating a media player and a file manager.[222][223][224][225][226]

Google announced Chrome OS on July 7, 2009.[227]

iOS version

Chrome is available on Apple's mobile iOS operating system as Google Chrome for iOS. Released in the Apple App Store on June 26, 2012, it supports the iPad, iPhone, and iPod touch, and requires that the device has iOS 9.0 or greater installed.[228] In accordance with Apple's requirements for browsers released through their App Store, this version of Chrome uses the iOS WebKit  which is Apple's own mobile rendering engine and components, developed for their Safari browser  therefore it is restricted from using Google's own V8 JavaScript engine.[229][230] Chrome is the default web browser for the iOS Gmail application, but it cannot be used as the device-wide default application for opening webpages because Apple has not provided iOS users with the option to change the default from Safari.[231]

In a review by Chitika, Chrome was noted as having 1.5% of the iOS web browser market as of July 18, 2012.[232] In October 2013, Chrome had 3% of the iOS browser market.[233]


Windows XP and Vista

Support for Google Chrome on Windows XP and Windows Vista has ended as of April 2016.[234] The last release of Google Chrome that can be run under Windows XP and Windows Vista was version 49.0.2623.112 m, released on Apr 7, 2016,[235] then re-released on April 11, 2016.[236]

Windows 8 version

In June 2012, the now discontinued "Windows 8 mode" was introduced to developer channel, which enables Windows 8/8.1 users to run Chrome in a full-screen, tablet-optimized interface within the Metro shell, with access to snapping, sharing, and search functionalities.[237] In October 2013, Windows 8 mode on developer channel changed to use a desktop environment mimicking the interface of Chrome OS with a dedicated windowing system and taskbar for web apps.[238] This was discontinued as of version 49 and users that have upgraded to Windows 10 will lose this feature.[239]



Google dropped support for 32-bit versions of Chrome on OS X in November 2014, with Chrome 38 being the last supported 32-bit version.

10.6, 10.7, 10.8

Support for Google Chrome on 64-bit versions of OS X 10.6, 10.7 and 10.8 has ended as of April 2016.[234]


Google Chrome was met with acclaim upon release. In 2008, Matthew Moore in the The Daily Telegraph summarized the verdict of early reviewers: "Google Chrome is attractive, fast and has some impressive new features..."[240]

Initially, Microsoft reportedly played down the threat from Chrome and predicted that most people would embrace Internet Explorer 8. Opera Software said that "Chrome will strengthen the Web as the biggest application platform in the world".[241] But by February 25, 2010, BusinessWeek had reported that "For the first time in years, energy and resources are being poured into browsers, the ubiquitous programs for accessing content on the Web. Credit for this trend  a boon to consumers  goes to two parties. The first is Google, whose big plans for the Chrome browser have shaken Microsoft out of its competitive torpor and forced the software giant to pay fresh attention to its own browser, Internet Explorer. Microsoft all but ceased efforts to enhance IE after it triumphed in the last browser war, sending Netscape to its doom. Now it's back in gear."[242] Mozilla said that Chrome's introduction into the web browser market comes as "no real surprise", that "Chrome is not aimed at competing with Firefox", and furthermore that it would not affect Google's revenue relationship with Mozilla.[243][244]

Chrome's design bridges the gap between desktop and so-called "cloud computing." At the touch of a button, Chrome lets you make a desktop, Start menu, or QuickLaunch shortcut to any Web page or Web application, blurring the line between what's online and what's inside your PC. For example, I created a desktop shortcut for Google Maps. When you create a shortcut for a Web application, Chrome strips away all of the toolbars and tabs from the window, leaving you with something that feels much more like a desktop application than like a Web application or page.


Market share

Further information: Usage share of web browsers and Browser wars
Most used web browser by country as of June 2015, before the launch of Microsoft Edge.[247]
  No info

Chrome overtook Firefox in November 2011, in worldwide usage. As of June 2016, according to StatCounter, Google Chrome had 62% worldwide desktop usage share, making it the most widely used web browser, while and Firefox had 16% and Internet Explorer had 12%.[248][249]

Along with Safari and Mozilla Firefox, Chrome receives a weekend "bump", which boosts its market share by as much as three percentage points on week-ends, at the expense of Internet Explorer.[250]

It was reported by StatCounter, a web analytics company, that for the single day of Sunday, March 18, 2012, Chrome was the most used web browser in the world for the first time. Chrome secured 32.7% of the global web browsing on that day, while Internet Explorer followed closely behind with 32.5%.[251]

From May 14–21, 2012, Google Chrome was for the first time responsible for more Internet traffic than Microsoft's Internet Explorer, which long had held its spot as the most used web browser in the world.[252] According to StatCounter, 31.88% of web traffic was generated by Chrome for a sustained period of one week and 31.47% by Internet Explorer. Though Chrome had topped Internet Explorer for single day's usage in the past, this was the first time it had led for one full week.[253]

At the 2012 Google I/O developers' conference, Google claimed that there were 310 million active users of Chrome, almost double the number in 2011, which was stated as 160 million active users.[254]

In June 2013, according to StatCounter, Chrome overtook Internet Explorer for the first time in the US.[255]

In August 2013, Chrome was used by 43% of internet users worldwide. This study was done by Statista, which also noted that in North America, 36% of people use Chrome, the lowest in the world.[256]

Desktop/laptop browser statistics
Google Chrome
Mozilla Firefox
Internet Explorer
Microsoft Edge
Desktop web browser market share according to StatCounter for October 2016.[257]

Enterprise deployment

In December 2010, Google announced that to make it easier for businesses to use Chrome they would provide an official Chrome MSI package. For business use it is helpful to have full-fledged MSI packages that can be customized via transform files (.mst)  but the MSI provided with Chrome is only a very limited MSI wrapper fitted around the normal installer, and many businesses find that this arrangement does not meet their needs.[258] The normal downloaded Chrome installer puts the browser in the user's local app data directory and provides invisible background updates, but the MSI package will allow installation at the system level, providing system administrators control over the update process[259]  it was formerly possible only when Chrome was installed using Google Pack. Google also created group policy objects to fine tune the behavior of Chrome in the business environment, for example by setting automatic updates interval, disabling auto-updates, and configuring a home page.[260] Until version 24 the software is known not to be ready for enterprise deployments with roaming profiles or Terminal Server/Citrix environments.[261]


In September 2008, Google released a large portion of Chrome's source code as an open-source project called Chromium. This move enabled third-party developers to study the underlying source code and to help port the browser to the macOS and Linux operating systems. The Google-authored portion of Chromium is released under the permissive BSD license.[262] Other portions of the source code are subject to a variety of open-source licenses.[263] Chromium is similar to Chrome, but lacks built-in automatic updates and built-in Flash player, as well as Google branding and has a blue-colored logo instead of the multicolored Google logo.[264][265] Chromium does not implement user RLZ tracking.[99][266][267] Initially, the Google Chrome PDF viewer, PDFium, was excluded from Chromium, but was later made open-source in May 2014.[268][269] PDFium can be used to fill PDF forms.[270]

Developing for Chrome

It is possible to develop applications, extensions, and themes for Chrome. They are zipped in a .crx file and contain a manifest file that specifies basic information (such as version, name, description, privileges, etc.), and other files for the user interface (icons, popups, etc.). Google has an official developer's guide.[271] Chrome has its own web store where people can upload and download these applications and extensions.[272]

See also


  1. Chrome's WebKit & Blink layout engines and its V8 JavaScript engine are each free and open-source software, while its other components are each either open-source or proprietary. However, section 9 of Google Chrome's Terms of Service designates the whole package as proprietary freeware.
  2. Browser must be downloaded directly from the Google Chrome website to opt-out of the RLZ identifier.
  3. Requires advanced user intervention.
  4. As of Chrome version 26, Linux installations of the browser may be updated only on systems that support GCC v4.6 and GTK v2.24 or later. Thus systems such as Debian 6's 2.20, and RHEL 6's 2.18 are now among those marked as deprecated.[200]


  1. "Stable Channel Update for Desktop". Chrome Releases. Blogger. December 1, 2016. Retrieved December 2, 2016.
  2. "Chrome". Google Play. Google. November 8, 2016. Retrieved December 2, 2016.
  3. "Chrome - web browser by Google". iTunes Preview. November 4, 2016. Retrieved November 4, 2016.
  4. "Beta Channel Update for Desktop". Google Blogspot. 2016-12-01. Retrieved 2016-12-02.
  5. "Chrome Beta". Google Play. Google. 2016-12-01. Retrieved 2016-12-02.
  6. "Dev Channel Update for Desktop". Google Blogspot. 2016-12-02. Retrieved 2016-12-02.
  7. "Chrome Dev". Google Play. Google. 2016-12-01. Retrieved 2016-12-02.
  8. Lextrait, Vincent (January 2010). "The Programming Languages Beacon, v10.0". Retrieved March 14, 2010.
  9. "Chrome for iOS".
  10. Supported Languages - Developer Console Help Retrieved 18 December 2015.
  11. 1 2 3 "Google Chrome Terms of Service".
  12. Paul, Ryan (September 2, 2008). "Google unveils Chrome source code and Linux port". Ars Technica. Retrieved July 11, 2012.
  13. "Welcome to Chromium".
  14. "Flash and Chrome". Retrieved August 10, 2016.
  15. "Google going its own way, forking WebKit rendering engine". Ars Technica. Retrieved April 3, 2013.
  16. Protalinski Google replaces WebKit version ID with Blink in latest Chrome build, Emil. "Google replaces WebKit version ID with Blink in latest Chrome build".
  17. "Top 5 Desktop Browsers on Nov 2016". StatCounter.
  18. "Top 9 Browsers from on Sept 2016". StatCounter.
  19. Julia Angwin (July 9, 2009). "Sun Valley: Schmidt Didn't Want to Build Chrome Initially, He Says". WSJ Digits Blog. Retrieved May 25, 2010.
  20. "Rumours surround Google browser".
  21. Scott McCloud (September 1, 2008). "Surprise!". Google Blogoscoped. Retrieved September 1, 2008.
  22. Philipp Lenssen (September 1, 2008). "Google Chrome, Google's Browser Project". Retrieved September 1, 2008.
  23. Philipp Lenssen (September 1, 2008). "Google on Google Chrome – comic book". Google Blogoscoped. Retrieved September 1, 2008.
  24. 1 2 3 4 5 6 7 8 9 10 11 "Google Chrome comic". Google Book Search. September 1, 2008. Retrieved September 2, 2008.
  25. 1 2 Pichai, Sundar; Upson, Linus (September 1, 2008). "A fresh take on the browser". Google Blog. Retrieved July 11, 2012.
  26. Dougerty, Conor (July 12, 2015). "Sundar Pichai of Google Talks About Phone Intrusion". New York Times. Retrieved July 13, 2015.
  27. "Google Chrome - The reason behind its name revealed!". The Windows Club. Retrieved September 3, 2015.
  28. "It was when not if... Google Chrome". September 2008. Retrieved September 2, 2008.
  29. "Be sure to read Chrome's fine print". CNET. Retrieved September 3, 2008.
  30. "Google Terms of Service – Policies & Principles – Google". March 1, 2012. Retrieved March 30, 2013.
  31. "Google Chrome update: First screenshot, and live-blog alert". CNet. September 1, 2008. Retrieved July 11, 2012.
  32. "Google launches Chrome web browser". The Canadian Press. Associated Press. September 2, 2008. Retrieved September 2, 2008.
  33. "Come on Google... Chrome for Mac?". November 2008. Retrieved November 22, 2008.
  34. Gruener, Wolfgang (January 3, 2009). "Google Chrome crosses 1% market share again". Chicago (IL), United States: TG Daily. Retrieved July 11, 2012.
  35. Shankland, Stephen (January 9, 2009). "Chrome gets Mac deadline, extensions foundation". CNET. Retrieved January 13, 2009.
  36. "Early Access Release Channels". Retrieved April 8, 2012.
  37. "Danger: Mac and Linux builds available". Retrieved June 9, 2009.
  38. Mark Larson (December 8, 2009). "Beta Update: Linux, Mac, and Windows". Google. Retrieved July 11, 2012.
  39. 1 2 "Google Chrome for the holidays: Mac, Linux and extensions in beta". Retrieved July 11, 2012.
  40. Brian Rakowski (May 25, 2010). "A new Chrome stable release: Welcome, Mac and Linux!". Google. Retrieved July 11, 2012.
  41. "Microsoft offers browser choices to Europeans". BBC News. March 1, 2010. Retrieved July 11, 2012.
  42. "NPAPI deprecation: developer guide - The Chromium Projects". Retrieved September 3, 2015.
  43. Peteris Krumins (September 5, 2008). "Code reuse in Google Chrome Browser". Retrieved May 13, 2010.
  44. Ian Fette (February 19, 2010). "Hello HTML5". Google. Retrieved July 11, 2012.
  45. "HTML Video Codec Support in Chrome". January 11, 2011. Retrieved April 8, 2012.
  46. "Longer battery life and easier website permissions". November 6, 2012. Retrieved December 3, 2012.
  47. Trollope, Rowan (December 22, 2013). "Open-Sourced H.264 Removes Barriers to WebRTC". Retrieved December 22, 2013.
  48. "Google Chrome Beta arrives on Android". Engadget. Aol. Retrieved July 11, 2012.
  49. "Chrome Out Of Beta, Default Browser Of Android 4.1".
  50. Rafe Needleman (May 14, 2008). "The future of the Firefox address bar". CNET News. Retrieved May 13, 2010.
  51. Stephen Shankland (September 2, 2008). "Speed test: Google Chrome beats Firefox, IE, Safari – Business Tech". CNET News. Retrieved May 13, 2010.
  52. Kevin Purdy (June 11, 2009). "Lifehacker Speed Tests: Safari 4, Chrome 2, and More – Browsers". Lifehacker. Retrieved May 13, 2010.
  53. Anthony Laforge. "Stable Channel Update". Google. Retrieved May 25, 2010.
  54. "ECMAScript test262". ECMAScript. Retrieved May 6, 2011.
  55. "CSS 2.1 Test Suite RC6 Results". W3C. Retrieved May 6, 2011.
  56. "HTML5 test desktop". Visred. Retrieved March 19, 2015.
  57. "HTML5 test desktop browser comparison". Visred. Retrieved March 19, 2015.
  58. "HTML5 test Android Chrome 41 Galaxy S5". Visred. Retrieved March 19, 2015.
  59. "HTML5 test tablet". Sights. Retrieved March 19, 2015.
  60. "HTML5 test mobile". Sights. Retrieved March 19, 2015.
  61. "HTML5test - How well does your browser support HTML5?". Retrieved October 29, 2015.
  62. Chung, Marc (September 5, 2008). "chromes-process model explained". Retrieved September 10, 2008.
  63. Barth, Adam; Jackson, Collin; Reis, Charles; The Google Chrome Team. "The Security Architecture of the Chromium Browser" (PDF). Stanford Security Laboratory. Retrieved September 11, 2008.
  64. Markus Gutschke (May 6, 2009). "Re: (PATCH 2/2) x86-64: seccomp: fix 32/64 syscall hole". Retrieved February 17, 2011.
  65. Jake Edge (August 19, 2009). "Google's Chromium sandbox". Retrieved February 17, 2011.
  66. "Issue 53 - chromium - No Master Password Option". Google. September 2, 2008. Retrieved August 13, 2013.
  67. Kember, Elliott (August 7, 2013). "Chrome's Password Security Strategy Is Insane". Retrieved August 13, 2013.
  68. "Issue 53 - chromium - No Master Password Option (post #151)". Retrieved May 3, 2014.
  69. Huge Security Flaw Leaks VPN Users’ Real IP-addresses (January 30, 2015). Retrieved on 2015-02-21.
  70. Adam. "Chrome will start flagging insecure HTTP sites". Retrieved 2016-09-13.
  71. Gregg Keizer (March 10, 2011). "Google's Chrome untouched at Pwn2Own hack match". Computerworld.
  72. 1 2 "Pwn2Own 2012: Google Chrome browser sandbox first to fall". ZDNet. CBS Interactive. March 7, 2012. Retrieved April 8, 2012.
  73. "CanSecWest Pwnium: Google Chrome hacked with sandbox bypass". ZDNet. CBS Interactive. March 7, 2012. Retrieved April 8, 2012.
  74. "Teenager hacks Google Chrome with three 0day vulnerabilities". ZDNet. CBS Interactive. March 9, 2012. Retrieved April 8, 2012.
  75. Kersey, Jason (March 10, 2012). "Chrome Stable Update". Retrieved March 10, 2012.
  76. "Google Chrome exploit fetches "Pinkie Pie" $60,000 hacking prize". Ars Technica. October 10, 2012.
  77. "Pwnium 2: results and wrap-up". Chromium Blog. October 10, 2012.
  78. "Pwn2own Day 1 Exploits: Google Chrome, Adobe Flash, Apple Safari". Retrieved 2016-09-20.
  79. "Google targets HTML5 default for Chrome instead of Flash in Q4 2016". VentureBeat. Retrieved 2016-09-20.
  80. "Chrome Browser". Retrieved April 21, 2014.
  81. 1 2 "Google Chrome FAQ for web developers". Google. Archived from the original on September 4, 2008. Retrieved April 8, 2012.
  82. Paul, Ryan (March 2010). "Google bakes Flash into Chrome, hopes to improve plug-in API". Retrieved March 14, 2010.
  83. "Java and Google Chrome". Retrieved December 11, 2009.
  84. "Issue 10812 – chromium – No java plugin support yet". Google. Retrieved May 18, 2010.
  85. "". February 24, 2012. Retrieved March 23, 2013.
  86. "Pepper Plugin API (PPAPI)". Retrieved March 23, 2013.
  87. "Chromium Blog: The road to safer, more stable, and flashier Flash". August 8, 2012. Retrieved August 29, 2012.
  88. "Securing Flash Player for our Mac users". Google. Retrieved November 14, 2012.
  89. "Chromium Blog: Saying Goodbye to Our Old Friend NPAPI". Chromium Blog. Retrieved July 13, 2015.
  90. "PSA: Chrome for Linux planning to drop NPAPI support as soon as April". Retrieved April 22, 2015. Another thing I found last night is a Debian package called PepperFlashPlayer. Apparently it works the same way as the existing FlashPlayer package (which downloads Adobe Flash from Adobe and installs it) -- it downloads Chrome from Google, extracts the PPAPI Flash plugin, and installs it for Chromium. That might be a good work-around for Chromium users in the interim. (Note: I am not endorsing this method, just making people aware of it.) But obviously it would be better if PPAPI Flash were available in a more "official" context.
  91. NPAPI deprecation
  92. "Explore Google Chrome Features: Incognito Mode". September 2, 2008. Retrieved September 4, 2008.
  93. "Chromium Blog: Google Chrome, Chromium, and Google". October 1, 2008. Retrieved April 8, 2012.
  94. "Google Chrome Privacy Notice". Google. December 13, 2011. Retrieved February 4, 2012
  95. 1 2 3 "Google Reacts to Some Chrome Privacy Concerns". Retrieved September 24, 2008.
  96. 1 2 "SRWare Iron webpage". Retrieved October 12, 2008.
  97. 1 2 3 "In The Open, For RLZ". The Chromium Blog. June 2, 2010. Retrieved June 20, 2010.
  98. "Google Chrome Unique Identifier Change". March 16, 2010. Retrieved March 24, 2010.
  99. Fried, Ina (September 3, 2008). "Google's Omnibox could be Pandora's box". Retrieved May 13, 2010.
  100. "Chrome's privacy settings". Retrieved April 25, 2013.
  101. 1 2 3 4 "Google Chrome Privacy Whitepaper" (PDF). Retrieved April 8, 2012.
  102. "&rlz= in Google referrer: Organic traffic or AdWords?". Retrieved February 27, 2009.
  103. Controlled by the setting "Send usage statistics and error reports". Default off.
  104. "Turning Off Auto Updates in Google Chrome". Retrieved December 12, 2014.
  105. "Tracking DNT". W3C. Retrieved 17 December 2015.
  106. "Google and Chrome To Support Do Not Track". Retrieved March 3, 2012.
  107. "V8 Benchmark suite". Google code. Archived from the original on September 4, 2008. Retrieved September 3, 2008.
  108. Rupert Goodwins (September 2, 2008). "Google Chrome – first benchmarks. Summary: wow". Archived from the original on September 3, 2008.
  109. "Google Chrome Javascript Benchmarks". September 1, 2008. Archived from the original on January 7, 2012. Retrieved April 8, 2012.
  110. Kingsley-Hughes, Adrian (September 2, 2008). "Google Chrome is insanely fast ... faster than Firefox 3.0". ZDNet. CBS Interactive.
  111. Shankland, Stephen (September 2, 2008). "Speed test: Google Chrome". CNET Business Tech.
  112. Alexander Limi (September 2, 2008). "Chrome: Benchmarks and more". Archived from the original on April 24, 2010. Retrieved May 13, 2010.
  113. Vygantas Lipskas (March 1, 2009). "Safari 4 vs. Firefox 3 vs. Google Chrome vs. Opera 10, 9.6 vs. Internet Explorer 8, 7". Favbrowser. Retrieved May 13, 2010.
  114. Scott M. Fulton, III (October 11, 2010). "Firefox in the dust: Opera poised to reclaim browser performance lead". Archived from the original on July 14, 2011. Retrieved November 6, 2010.
  115. Stephen Shankland (September 3, 2008). "Firefox counters Google's browser speed test – Business Tech". CNET News. Retrieved May 13, 2010.
  116. Eich, Brendan (September 3, 2008). "TraceMonkey Update".
  117. Stephen Shankland (November 3, 2008). "Third Chrome beta another notch faster – News". Builder AU. Retrieved May 13, 2010.
  118. Resig, John (September 3, 2008). "JavaScript Performance Rundown".
  119. Maciej Stachowiak (September 18, 2008). "WebKit blog: Introducing SquirrelFish Extreme". Retrieved May 13, 2010.
  120. Cameron Zwarich (September 18, 2008). "SquirrelFish Extreme has landed!". Archived from the original on April 27, 2009. Retrieved May 13, 2010.
  121. Stephen Shankland (September 22, 2008). "Step aside, Chrome, for Squirrelfish Extreme – News". Builder AU. Retrieved May 13, 2010.
  122. Charles Ying (September 19, 2008). "SquirrelFish Extreme: Fastest JavaScript Engine Yet". Retrieved May 13, 2010.
  123. 1 2 Preston Gralla (September 3, 2008). "Three hidden Chrome features you'll love". Retrieved September 16, 2008.
  124. "DNS prefetching for Firefox". November 8, 2008.
  125. Apple Inc. (June 7, 2010). "What's new in Safari 5". Retrieved July 6, 2010.
  126. "Internet Explorer 9 Network Performance Improvements". March 17, 2011. Retrieved April 8, 2012.
  127. João Eiras. "Page prefetcher". Retrieved April 8, 2012.
  128. "chrome] Index of /trunk/src/net/spdy – Chromium SPDY client implementation". Retrieved April 8, 2012.
  129. "SPDY Proxy Examples – The Chromium Projects". Retrieved April 8, 2012.
  130. Reisn, Charlie (September 11, 2008). "Multi-process Architecture". Retrieved September 12, 2008.
  131. "Process Models". The Chromium Projects. Google. September 3, 2008. Retrieved September 12, 2008.
  132. Prince, Brian (December 11, 2008). "Google Chrome Puts Security in a Sandbox". Ziff Davis Enterprise Holdings Inc. Retrieved June 4, 2010.
  133. "[webkit-dev] Announcing WebKit2". Retrieved April 8, 2012.
  134. "Firefox Lorentz beta available for download and testing". Mozilla. April 8, 2010.
  135. "Chrome 23 Closes 15 Security Vulnerabilities, Promises Longer Battery Life & Added Do Not Track (DNT)". Retrieved November 9, 2012.
  136. "Longer battery life and easier website permissions". Retrieved November 6, 2012.
  137. Google (2012). "Set your home page". Retrieved May 22, 2012.
  138. "A Speedier Google Chrome for all users". Google Chrome Blog.
  139. Anthony Laforge (September 15, 2009). "Google Chrome after a year: Sporting a new stable release". Google. Retrieved May 13, 2010.
  140. "Chromium". Retrieved September 1, 2010.
  141. Pash, Adam (October 2010). "Chrome's About:Labs Renamed to About:Flags, Adds a Warning". LifeHacker. Retrieved October 19, 2010.
  142. Rura, Steve (March 2011). "A fresh take on an icon". Retrieved March 22, 2011.
  143. "A New Breed of Chrome Aps". Google Chrome Blog. September 2013. Retrieved February 2, 2014.
  144. "Chrome Web Store". Google. May 19, 2010. Retrieved May 24, 2010.
  145. Erik Lay (May 19, 2010). "The Chrome Web Store". Google. Retrieved May 24, 2010.
  146. Paul, Ryan (December 2010). "Chrome Web Store: a solution in search of a problem?". Ars Technica. Retrieved December 10, 2010.
  147. Google (February 2011). "A dash of speed, 3D and apps". Retrieved February 7, 2011.
  148. Aaron Boodman (September 9, 2009). "Extensions Status: On the Runway, Getting Ready for Take-Off". Google. Retrieved May 13, 2010.
  149. Erik Kay (December 8, 2009). "Extensions beta launched, with over 300 extensions!". Google. Retrieved May 13, 2010.
  150. Nick Baum (January 25, 2010). "Over 1,500 new features for Google Chrome". Google Chrome Blog. Retrieved May 13, 2010.
  151. "Security improvements and registration updates for the Google Chrome Extensions Gallery". August 19, 2010.
  152. "Official Independent Chrome Extension".
  153. "CEOP Official Chrome Extension".
  154. "Official TfL Chrome Extension".
  155. from "Chrome Web Store – ESPN Cricinfo". Google. Retrieved April 8, 2012.
  156. "WOT – Google Chrome extension gallery".
  157. "Official World Cup FIFA Chrome Extension".
  158. "Chrome Web Store Help". Google. Retrieved April 8, 2012.
  159. Lardinois, Frederic (May 27, 2014). "Chrome For Windows Will Now Only Install Extensions From Google's Web Store". TechCrunch. Retrieved July 10, 2014.
  160. Glen Murphy (October 5, 2009). "A splash of color to your browser: Artist Themes for Google Chrome". Google Chrome Blog. Retrieved May 13, 2010.
  161. "Chrome Web Store". Google. Retrieved April 8, 2012.
  162. "Basic settings: Change browser theme". Google Chrome Help.
  163. "Change Chrome languages & translate webpages".
  164. Mark Larson (January 8, 2009). "Google Chrome Release Channels". Retrieved January 9, 2009.
  165. Mark Larson (January 8, 2009). "Dev update: New WebKit version, new features, and a new Dev channel". Retrieved January 9, 2009.
  166. Ian Fette (December 11, 2008). "Thanks For All Your Help". Retrieved May 1, 2015.
  167. Anthony Laforge (July 22, 2010). "Release Early, Release Often". Retrieved July 25, 2010.
  168. The Chromium Authors. "Chrome Release Channels". Retrieved October 29, 2014.
  169. Paul Irish (November 2, 2012). "Chrome Canary for Developers". Retrieved October 29, 2014.
  170. Bridge, Henry (August 2, 2010). "Google Chrome in a Coal Mine". Chromium Blog. Retrieved March 19, 2015.
  171. Mathews, Lee (July 23, 2010). "Google drops Chrome Canary build down the Chrome mineshaft". Archived from the original on July 25, 2010. Retrieved July 25, 2010.
  172. "Adding more yellow to the Mac color scheme". May 2, 2011. Retrieved February 4, 2012.
  173. 1 2 McCarty, Brad (January 10, 2013). "Google launches Chrome Beta channel for Android 4.0+ phones and tablets, releases version 25". TheNextWeb. Retrieved March 23, 2013.
  174. "Chrome beta for Android on Google Play". Retrieved March 23, 2013.
  175. "Google Launches Dev Channel for Chrome on Android". Chrome Story. Retrieved July 13, 2015.
  176. David Dorwin (May 14, 2009). "Google Update Releases Update Controls". Retrieved May 13, 2010.
  177. "Alternate (offline) Google Chrome installers for Windows - Chrome Help".
  178. Alex Chitu (March 1, 2009). "Standalone Offline Installer for Google Chrome". Google Operating System. Retrieved May 13, 2010.
  179. "Google Help page "Managing updates in Google Software Update"".
  180. "Tour of the Chromium Buildbot Waterfall - The Chromium Projects". Retrieved December 2, 2014.
  181. 1 2 "Version 42 Stable Release". Chrome Releases. Blogger. 14 April 2015. Retrieved 28 December 2015.
  182. 1 2 3 "Chromium Development Calendar and Release Info". The Chromium Projects. Retrieved May 1, 2015.
  183. Mike Frysinger (March 14, 2014). "Version Numbers". The Chromium Projects. Retrieved May 1, 2015.
  184. Anthony LaForge (December 16, 2010). "Chrome Release Cycle -12/16/2010". Google Slides. Retrieved May 1, 2015.
  185. "Version 42 Developer Update". Chrome Releases. Blogger. 26 February 2015. Retrieved 28 December 2015.
  186. "Issue 143: Handle color profiles in tagged images". September 2, 2008. Retrieved March 23, 2013.
  187. "Google Chrome Easter Egg T-Rex Mini Game". Business Insider.
  188. "Play Google Chrome's Secret Offline Game".
  189. "How do I find the secret dinosaur game on Google Chrome when my internet connection is down?". RadioTimes.
  190. "Google Chrome's 'Unable to connect to the Internet' page has a hidden endless runner game". The Independent.
  191. "Issue 462221 - chromium - Disable offline game (T-Rex) if device is enrolled - Monorail". Chromium. 26 February 2015. Retrieved 27 July 2016.
  192. 1 2 3 "Download and install Google Chrome". Google Help. See system requirements. Retrieved 2016-04-20.
  193. 1 2 Pawliger, Marc (10 November 2015). "Updates to Chrome platform support". Google Chrome Blog (blog). Google. Retrieved 2016-04-20. Starting April 2016, Chrome will continue to function on these platforms but will no longer receive updates and security fixes.
  194. "Chrome updates on Mac 32-bit". Chrome help. Google.
  195. "Google to Discontinue 32-bit Chrome for Mac Next Month". OMG! Chrome!.
  196. 1 2 3 Google (November 18, 2014). "Stable Channel Update". Retrieved November 18, 2014.
  197. "Chrome no longer supports Mac OS X 10.5". Google. Archived from the original on 2015-03-29.
  198. "Chrome stops declaring Linux systems obsolete - The H Open: News and Features". February 14, 2013. Retrieved March 30, 2013.
  199. "Google ends 32-bit Linux support for Chrome". OSNews.
  200. Google. "64-bit Support – The Chromium Projects". Retrieved March 5, 2012.
  201. "Download Chrome for Linux". Google.
  202. Google. "Try out the new 64-bit Windows Canary and Dev channels". Retrieved July 1, 2014.
  203. Google. "Announcing the Chrome 64-bit Beta Channel for Windows!". Retrieved August 11, 2014.
  204. "64 bits of awesome: 64-bit Windows Support, now in Stable!". August 26, 2014. Retrieved August 27, 2014.
  205. Google. "[chromium-dev] Yesterday's Mac canary was 64-bit". Retrieved July 1, 2014.
  206. Google. "Re: [chromium-dev] Re: Chromium 64-bit on Mac OS". Retrieved July 1, 2014.
  207. Google (October 9, 2014). "Beta Channel Update". Retrieved October 10, 2014.
  208. "Install Chrome for Android Beta – Google Chrome Help". Google. Retrieved April 6, 2012.
  209. 1 2 3 "Beta version of Chrome for Android 4.0 released". Retrieved February 9, 2012.
  210. 1 2 3 4 5 "Google Operating System: Chrome for Android". February 27, 2004. Retrieved February 9, 2012.
  211. 1 2 3 4 "Google Chrome for Android – 23 Questions and Answers". Chrome Story. Retrieved February 9, 2012
  212. 1 2 3 4 5 "Bringing Google Chrome to Android". Peter Beverloo. January 30, 2012. Retrieved February 9, 2012.
  213. "Security overview". Google. Retrieved February 9, 2012.
  214. "Google Chrome for Android: Remote Debugging". Google. Retrieved February 9, 2012.
  215. Lardinois, Frederic (April 17, 2012). "Chrome For Android Gets Desktop View, Home Screen Bookmarks, File Downloads".
  216. "Google Chrome for Android comes out of beta, Hits Play today". Engadget. June 27, 2012. Retrieved June 27, 2012.
  217. "Chrome for Android Update". September 26, 2012. Retrieved March 23, 2013.
  218. "Chrome Beta for Android". May 26, 2013. Retrieved July 4, 2013.
  219. Dylan F. Tweney (November 19, 2009). "Gadget Lab Hardware News and Reviews Google Chrome OS: Ditch Your Hard Drives, the Future Is the Web". Wired. Retrieved November 22, 2009.
  220. Sengupta, Caesar (November 19, 2009). "Releasing the Chromium OS open-source project". Official Google Blog. Google, Inc. Retrieved November 19, 2009.
  221. Stokes, Jon (January 19, 2010). "Google talks Chrome OS, HTML5, and the future of software". Ars Technica. Retrieved January 23, 2010.
  222. Womack, Brian (July 8, 2009). "Google to Challenge Microsoft With Operating System". Bloomberg. Retrieved July 8, 2009.
  223. Hansell, Saul (July 8, 2009). "Would you miss Windows with a Google operating system?". New York Times. Retrieved July 8, 2009.
  224. Pichai, Sundar (July 7, 2009). "Introducing the Google Chrome OS". Official Google Blog. Google, Inc. Retrieved July 16, 2009.
  225. Mediati, Nick (July 7, 2009). "Google Announces Chrome OS". PC World. Retrieved July 8, 2009.
  226. "Chrome entry - Apple's App Store".
  227. "Google Chrome on iOS Hits #1 Free App". Forbes.
  228. "iOS 8 WebKit changes finally allow all apps to have the same performance as Safari".
  229. Steve Kovach (May 8, 2013). "Here's Even More Evidence That Google Is Trying To Take Over The iPhone". Business Insider. Retrieved June 10, 2013.
  230. Reisinger, Don (July 18, 2012). "Chrome already nabs 1.5 percent of iOS browser market". CNET. Retrieved June 10, 2013.
  231. "Chrome's Share of iOS Usage Doubles Year-Over-Year to 3%". Mac Rumors. October 11, 2013. Retrieved April 21, 2014.
  232. 1 2 "Updates to Chrome platform support". Google Chrome Blog.
  233. "Stable Channel Update". Retrieved August 10, 2016.
  234. "Google Chrome 49.0.2623.112". Retrieved August 10, 2016.
  235. Newman, Jared. "Google Chrome Gets Early Metro-Style App for Windows 8". PCWorld. Retrieved June 13, 2012.
  236. "Google is building Chrome OS straight into Windows 8". The Verge. Retrieved October 5, 2013.
  237. "Unable to open Google Chrome in windows 8 mode - Google Product Forums". Retrieved September 29, 2016.
  238. Moore, Matthew (September 2, 2008). "Google Chrome browser: Review of reviews". Daily Telegraph. Retrieved September 24, 2011.
  239. Liedtke, Michael (September 3, 2008). "Google polishes product line with Chrome browser". Associated Press.
  240. Jaroslovsky, Rich (February 25, 2010). "Browser Wars: The Sequel". BusinessWeek.
  241. "Thoughts on Chrome & More". John's Blog. September 1, 2008. Retrieved May 13, 2010.
  242. Collins, Barry (September 2, 2008). "Mozilla: Google's not trying to kill us". PC Pro. Retrieved July 11, 2012.
  243. Mediati, Nick (September 3, 2008). "Google Chrome Web Browser". PC World. Retrieved September 7, 2008.
  244. "Top 5 Browsers from December 2010 to December 2011". StatCounter. Retrieved January 8, 2012.
  246. "Top 9 Desktop Browsers from W01 2015 to W27 2016". StatCounter.
  247. For additional sources see Usage share of web browsers#Summary table
  248. "Global Web Browser Marketshares". Clicky Analytics. Retrieved April 8, 2012.
  249. "Chrome is world's number one browser for a day". Global Stats press release. StatCounter. March 21, 2012.
  250. "Chrome overtakes Internet Explorer as No. 1 browser -- maybe". CNN. May 21, 2012. Retrieved May 21, 2012.
  251. Pachal, Peter (May 21, 2012). "Google Chrome Now the No. 1 Browser in the World".
  252. "Chrome tops 310 million users, almost 100% growth over last year". June 28, 2012.
  253. "Stats Counter US Monthly bar graph". June 2013. Retrieved July 25, 2013.
  254. Fox, Zoe (August 14, 2013). "43% of Global Web Surfers Choose Google Chrome".
  255. "Top 5 Desktop browser on Oct 2016". StatCounter. Retrieved 2 November 2016.
  256. "Change MSI from a wrapper to "full" MSI". Google. January 4, 2011. Retrieved April 8, 2012.
  257. Paul, Ryan (December 2010). "Google offering MSI to simplify Chrome enterprise deployment". Ars Technica. Retrieved July 11, 2012.
  258. "Google Update for Enterprise – Google Help". Google. Retrieved July 11, 2012.
  259. "Issue 2423 – chromium – Windows Roaming Profile support – An open-source browser project to help move the web forward. – Google Project Hosting". Google. September 17, 2008. Retrieved April 8, 2012.
  260. "Home (Chromium Developer Documentation)". Chromium Developer Documentation. 2009. Retrieved May 5, 2009.
  261. "Chromium Terms and Conditions". Google Code. September 2, 2008. Archived from the original on September 4, 2008. Retrieved September 3, 2008.
  262. Chromium Project (March 2011). "ChromiumBrowserVsGoogleChrome". Retrieved July 10, 2011.
  263. McAllister, Neil (September 11, 2008). "Building Google Chrome: A first look". Fatal Exception. InfoWorld. Retrieved September 16, 2008. As the name suggests, Chromium is a rawer, less polished version of Chrome. The UI is mostly identical, with only a few very minor visual differences. [...] The most readily evident difference is the logo, which sheds the Google colors in favor of a subdued blue design.
  264. "Google Chrome, Chromium, and Google". The Chromium Blog. 2008. Retrieved February 17, 2010.
  265. "Differences between Google Chrome and Linux distro Chromium". Google. 2010. Retrieved September 1, 2010.
  266. "Chromium revision log: Changes in revision 271531". May 20, 2014. Retrieved May 24, 2014.
  267. "Change log for Chromium wiki showing removal of a part that said PDF support were different between Chromium and Google Chrome". May 20, 2014. Retrieved May 24, 2014.
  268. Garthwaite, Emily. "Google throws PDFium into the open source community". IT Pro Portal. Retrieved 2016-09-11.
  269. "Developer's Guide - Google Chrome". Retrieved February 17, 2014.
  270.|title=Chrome web store

External links

Wikimedia Commons has media related to Google Chrome.
This article is issued from Wikipedia - version of the 11/30/2016. The text is available under the Creative Commons Attribution/Share Alike but additional terms may apply for the media files.