Google Chrome

• 1. Introduction

  ›

  Google Chrome was built by a company whose own chief executive spent six years trying to stop it. Eric Schmidt opposed an independent Google web browser. He argued that "at the time, Google was a small company." He did not want to go through "bruising browser wars." Then co-founders Sergey Brin and Larry Page hired several Mozilla Firefox developers and built a working demonstration. Afterward, Schmidt said, "It was so good that it essentially forced me to change my mind."

  Chrome now has approximately 3.62 billion users as of March 2026. How did a project its own boss resisted turn into the browser most of the world opens first? What made it fast, and what kept it standing when a single website failed? And what has that reach cost, for privacy, for rivals, and for Google itself?

  18161521

• 2. Launch Week

  ›

  In September 2004, rumors first appeared that Google was building a web browser. Online journals and U.S. newspapers noted that the company was hiring former Microsoft web developers. The timing was pointed. Mozilla Firefox 1.0 had just been released and was taking market share from Internet Explorer, which had noted security problems. Development of Chrome itself began in 2006, spearheaded by Sundar Pichai.

  The public reveal was supposed to be orderly. The announcement was scheduled for the 3rd of September 2008. Journalists and bloggers were to receive a comic by Scott McCloud explaining the new browser's features. Copies meant for Europe shipped early, however. German blogger Philipp Lenssen of Google Blogoscoped received his on the 1st of September 2008 and posted a scan of all 38 pages. Google then put the comic on Google Books and explained the early release on its official blog.

  The browser went public on the 2nd of September 2008, officially as a beta. It ran on Windows XP and newer and supported 43 languages. The "stable" release followed on the 11th of December 2008. On that same day, a CNET news item flagged a passage in the beta's terms of service. It seemed to give Google a license to everything sent through the browser. The wording had been inherited from Google's general terms. Google answered the criticism immediately and removed the passage.

  Usage told an uneven story. Chrome quickly gained about 1% of usage share, then slid to a low of 0.69% in October 2008. By December 2008 it had climbed back past 1%. Versions for macOS and Linux lagged behind. Developer previews were announced on the 4th of June 2009, with a blog post warning that many features were missing. Chrome 5.0, announced on the 25th of May 2010, was the first stable release for all three platforms. That same year, Chrome was one of twelve browsers offered on BrowserChoice.eu to European Economic Area users of Microsoft Windows.

  192530941

• 3. Engine Room

  ›

  Chrome was assembled from 25 different code libraries, some from Google and some from third parties. They included Mozilla's Netscape Portable Runtime, Network Security Services, the Skia Graphics Engine, and SQLite. One part was judged too important to build inside the main effort. The V8 JavaScript virtual machine went to a separate team in Denmark, coordinated by Lars Bak. Google argued that existing engines were designed for small programs where speed hardly mattered. Web applications such as Gmail, by contrast, push the browser hard on DOM manipulation and JavaScript.

  The speed claims were tested within days. In 2008, several websites ran the SunSpider benchmark and Google's own tests, which included ray tracing and constraint solving. They unanimously reported that Chrome beat Safari for Windows, Firefox 3.0, Internet Explorer 7, Opera, and Internet Explorer 8. On the 3rd of September 2008, Mozilla replied that its TraceMonkey engine, then in beta, was faster in some tests. John Resig, Mozilla's JavaScript evangelist, described Chrome's "decimating" of the field. He questioned whether Google's suite resembled real programs. He said Firefox 3.0 struggled on recursion-heavy tests because Mozilla had not yet built recursion-tracing. Two weeks after launch, the WebKit team announced SquirrelFish Extreme and cited a 36% speed gain over V8. By the 11th of October 2010, independent tests put Chrome just behind Opera's Presto engine, which had been updated in version 10.5.

  Standards tests added a second scoreboard. The first release passed both Acid1 and Acid2, and from version 4.0 Chrome passed every part of Acid3. As of April 2017 it no longer does, because consensus on web standards changed. On the ECMAScript Test262 suite, scored by failures, Chrome 37 failed 10 tests and passed 11,578. Firefox 19 failed 193, and Internet Explorer 9 failed more than 600. On an HTML5 test, Chrome 41 scored 518 out of 555, and Chrome 44 reached 526.

  Underneath, Chrome began with the WebKit rendering engine. In 2013, Google forked WebKit's WebCore component to create its own engine, Blink. Blink swapped in other pieces, including its own multi-process architecture. That design gives each site instance and plugin a separate process. If one fails, the user sees a Sad Tab, a cousin of the Sad Mac, and only that tab crashes. The approach costs a fixed amount per process up front. It saves memory over time, because fragmentation stays confined to each process. Safari and Firefox later adopted the idea. Chrome also ships a Task Manager that shows which sites and plugins use the most memory, bandwidth, and processor time, and it can end them.

  For a while, Chrome spoke Google's own SPDY protocol to servers that supported it, including Google services, Facebook, and Twitter. SPDY support was removed in Chrome version 51, after HTTP/2 arrived as a standard built upon it.

  4411596067

• 4. Sandboxes and Exploits

  ›

  Chrome periodically fetches two blacklists, one for phishing and one for malware, and warns users before they visit a flagged site. Google also offers the service to others through a free public interface called the Google Safe Browsing API. The browser's deeper defense is the sandbox. Following the principle of least privilege, each tab process cannot touch critical memory, user files, or other tabs. The Sandbox Team is said to have "taken this existing process boundary and made it into a jail." On Linux, the sandbox relies on seccomp mode.

  For three years, from 2009 to 2011, no vulnerability in Chrome was exploited at Pwn2Own. At Pwn2Own 2012, a French team ended the streak. They used zero-day exploits in the version of Flash shipped with Chrome. With them they took complete control of a fully patched 64-bit Windows 7 PC through a booby-trapped website. Chrome also fell twice at the 2012 CanSecWest Pwnium. Google's official response came from Jason Kersey. He congratulated the researchers and said both submissions "are works of art and deserve wider sharing and recognition." Fixes were deployed within 10 hours.

  Flash kept appearing in the wreckage. The successful 2016 Pwn2Own attack on Chrome chained four vulnerabilities. Two were in Flash, one was in Chrome, and one was in the Windows kernel. In 2016, Google announced that it would phase Flash out, starting in version 53. The first step disabled Flash for ads and background analytics. The goal was to switch it off completely by the end of the year, except on sites Google judged broken without it.

  Older plugin technology met a slower end. Chrome supported plug-ins through the Netscape Plugin API, called NPAPI, which ran them as unrestricted processes outside the sandbox. On the 12th of August 2009, Google introduced a more portable and more secure replacement, the Pepper Plugin API. Its Flash player reduced Flash crashes by 20% when it reached Windows in version 21. Google announced the end of NPAPI on the 23rd of September 2013. On the 14th of April 2015, Chrome 42 disabled it by default, which stranded plugins such as Java, Silverlight, and Unity. Version 45, released on the 1st of September 2015, removed NPAPI entirely.

  Other safeguards arrived one release at a time. Download scanning came in Chrome 17. Since 2008, critics have faulted Chrome for lacking a master password for saved logins. Developers argued that a master password gives no real protection against determined attackers. Bug reports on the issue were marked "WontFix." As of February 2014, Chrome instead asks for the user's Windows account password before revealing saved passwords. In February 2018, Google introduced an ad blocking feature based on recommendations from the Interactive Advertising Bureau. Sites with invasive ads got a 30-day warning before their ads were blocked. Consumer Reports suggested dedicated ad blockers instead, for stronger protection against malware and tracking. Documents leaked from 2013 to 2016 under the codename Vault 7 detailed how the United States Central Intelligence Agency could compromise browsers, Chrome included.

  On the 2nd of September 2020, Chrome 85 extended Secure DNS to Chrome for Android. The browser now switches to DNS-over-HTTPS automatically whenever the user's DNS provider supports it.

  435299100

• 5. Clean Interface

  ›

  The name "Chrome" began as a code name, chosen because chrome is associated with fast cars and speed. Google kept it for the final product as a cheeky, ironic moniker. One of the main aims was to minimize the interface chrome, the frame of buttons and bars around a page.

  The most visible break with tradition was the tab bar. Chrome moved tabs to the top of the window, instead of below the controls. Users could drag a tab with its state from one window to another. Each tab carried its own set of controls, including the Omnibox. That box merged the address bar and the search bar, an idea other browsers later copied. Typing a site's address and pressing Tab let the user search that site directly. Suggestions drew on previously visited pages, popular websites, and popular searches. The Instant feature could be turned off, but suggestions from visited sites could not.

  The New Tab Page originally showed thumbnails of the nine most visited websites. In Chrome 2.0 users could hide unwanted thumbnails. Version 3.0 cut the grid to eight sites that could be rearranged, pinned, and removed. It also brought themes, with a gallery reached through a "Get themes" button. Chrome 4.1 added a translation bar powered by Google Translate, now available for 52 languages. A hidden menu for experimental features was first called about:labs. It was renamed about:flags to be less obvious to casual users.

  The logo went through its own simplification. In March 2011, Google replaced the 3D logo used since the project began. Designer Steve Rura said the refresh reflected a browser that is "all about making your web experience as easy and clutter-free as possible." Later changes followed. A native dark theme reached Chrome on Windows 10 on the 2nd of January 2019. In 2023, Google announced a full revamp using its Material You design language. It brought rounder corners, dynamic colors borrowed from Android 12, and a simpler three-dot menu.

  Chrome also let users turn any web page into a desktop shortcut. A page opened this way showed only a title bar. The aim was not to "interrupt anything the user is trying to do." That let web applications sit alongside local software.

  Then there is the dinosaur. When Chrome has no internet connection, an 8-bit Tyrannosaurus rex appears above the "No internet" message. Press the space bar, click it, or tap it, and the dinosaur jumps and starts running across a cactus-ridden desert. The game is an infinite runner with no time limit. It speeds up as it goes and periodically tints the screen black. A school or enterprise manager can disable it.

  5679717475

• 6. Extensions and Manifest V3

  ›

  On the 9th of September 2009, Google enabled extensions by default on Chrome's developer channel and supplied several samples for testing. The Extensions Gallery beta opened in December 2009 with approximately 300 extensions. It launched on the 25th of January 2010 alongside Chrome 4.0, holding approximately 1500. Extensions are written with HTML, JavaScript, and CSS, and they work only in the desktop edition. Google Tone, built by Google, uses a computer's speakers to swap URLs with nearby computers running the same extension.

  The Chrome Web Store was announced on the 19th of May 2010 and opened on the 7th of December 2010. Most of its early web applications were simply links to popular pages or games. A few, such as Springpad, added features like offline access. In September 2013, Google began offering Chrome apps "for your desktop," which launched in their own windows and looked more like native applications.

  Google also tightened control over where extensions come from. In 2014, it started blocking some Windows users from installing extensions not hosted on the Web Store. The following year, Google reported a "75% drop in customer support help requests for uninstalling unwanted extensions." It then extended the restriction to all Windows and Mac users.

  In October 2018, Google announced a major change to the extension interface, called Manifest V3. It uses declarative APIs, replaces background pages with feature-limited service workers, and bans remotely hosted code. Google said the change would improve security and performance. Critics said it would hobble ad blockers. Rule limits cap what a blocker can check, and the ban on remote code stops filter lists from updating independently of the extension. In June 2019, Google raised the cap from 30,000 to 150,000 entries. In 2021, the Electronic Frontier Foundation called Manifest V3 "outright harmful to privacy efforts."

  The rollout stalled and restarted. In December 2022, Google paused the transition to address developer feedback. In November 2023, it announced the transition would resume. Manifest V2 extensions were removed from non-stable builds beginning in June 2024, and from the Web Store in June 2025. Other Chromium browsers reacted differently. Microsoft said it would support Manifest V2 ad blockers. Brave created a separate section for downloads of Manifest V2 blockers, including uBlock Origin. Mozilla said Firefox would add Manifest V3 support for compatibility, without the limits that hurt privacy and blocking extensions. uBlock Origin itself was reborn as uBlock Origin Lite, with a static filter list and fewer filters.

  A study from Goethe University Frankfurt complicated the fear. Its researchers found that popular Manifest V3 extensions had bypassed most of Google's restrictions. The tested blockers stopped as many requests to trackers and ads as their older versions, or more. But their cosmetic filters, which hide elements on a page, were over 20% less effective.

  9394829599

• 7. Channels and Platforms

  ›

  On the 8th of January 2009, Google announced a release system with three channels: Stable, Beta, and Developer preview. Stable was updated roughly quarterly, Beta roughly monthly, and the Developer channel once or twice a week. On the 22nd of July 2010, Google sped everything up. Major stable updates moved from quarterly to every six weeks, and a fourth channel appeared, named Canary.

  Canary is rebuilt daily at 09:00 UTC from the most stable of the last 40 revisions. The name comes from canaries in coal mines. If a change "kills" Canary, it is blocked from moving down to the Developer channel until a later build fixes it. Canary runs side by side with other installations and keeps its own profiles, themes, and settings. It began on Windows only, and a macOS version arrived on the 3rd of May 2011. In March 2021, Google announced that from Chrome 94 in the third quarter of 2021, Stable releases would come every four weeks. A new channel for system administrators would get releases every eight weeks.

  Every release carries a four-part number. Version 42.0.2311.90, for example, was the Windows Stable release of the 14th of April 2015. The major number marks a product release, and Chrome issues seven or eight a year. Chromium's Branch Point for version 42 fell on the 20th of February 2015. Developer builds stopped at 42.0.2311.4 four days later. The first Stable release came 53 days after the Branch Point.

  Chrome reached phones in 2012. A beta for Android 4.0 devices launched on the 7th of February 2012. It left beta and became stable on the 27th of June 2012. On the 26th of September 2012, a release became the first Chrome for Android to support Intel x86 devices. The iPhone and iPad version appeared in the Apple App Store on the 26th of June 2012. Apple's rules require browsers there to use iOS WebKit, so that version cannot run Google's V8 engine. According to Chitika, Chrome held 1.5% of the iOS browser market in 2012, rising to 3% by October 2013.

  Support for older systems ended in stages. Chrome for Windows XP and Vista stopped after version 49.0.2623.112, released on the 7th of April 2016 and re-released on the 11th of April. Windows 7 support was due to end on the 15th of July 2021. The COVID-19 pandemic moved the date to the 15th of January 2022. Slow enterprise migration pushed it again to the 15th of January 2023. The last version to support Windows 7, 8, and 8.1 was Chrome 109. On Linux, 32-bit Intel support ended in March 2016.

  The browser also became an operating system. Google announced ChromeOS on the 7th of July 2009. On ChromeOS devices, the only applications are a browser with a media player and a file manager. For businesses, Google provided an MSI wrapper around the installer in 2010. It now offers more than 500 policies to control Chrome's behavior. In 2016 it launched Chrome Browser Enterprise Support, a paid service. In 2019 it added Chrome Browser Cloud Management, a dashboard for IT managers.

  374149105

• 8. Dominance and Privacy

  ›

  On Sunday, the 18th of March 2012, StatCounter reported that Chrome was the world's most used browser for a single day. It took 32.7% of global browsing, and Internet Explorer followed at 32.5%. From the 14th to the 21st of May 2012, Chrome led for a full week, with 31.88% against Internet Explorer's 31.47%. At the 2012 Google I/O conference, Google claimed 310 million active users, almost double the 160 million claimed for 2011. Chrome had passed Firefox in worldwide usage in November 2011. In June 2013, it passed Internet Explorer in the United States. As of December 2025, StatCounter put Chrome at 71.22% across all platforms.

  Early reviews were warm. Matthew Moore of The Daily Telegraph summarized the verdict as "attractive, fast and has some impressive new features." Microsoft reportedly played down the threat. Opera said Chrome would strengthen the web as an application platform. By the 25th of February 2010, BusinessWeek credited Google with shaking Microsoft out of its competitive torpor over Internet Explorer.

  With dominance came suspicion. Google has been accused of using Chrome and Blink to push standards it proposed itself, leaving competing browsers with compatibility problems. Some developers test only on Chrome. Tom Warren of The Verge compared Chrome to Internet Explorer 6. In 2021, computer scientist and lawyer Jonathan Mayer made a sharper charge. He called Chrome "the only major web browser that lacks meaningful privacy protections by default."

  The numbers behind the privacy debate are specific. A 2020 study found that Chrome collects 20 types of data, against 6 for the average competitor. In 2019, Geoffrey A. Fowler of the Washington Post found that Chrome allowed thousands more cookies than Firefox in a typical week. The Omnibox suggestion service sends typed text to the search provider before the user presses return, tied to an IP address. The RLZ identifier measures marketing campaigns, and unofficial builds such as SRWare Iron remove it. In June 2015, Debian developers found that Chrome 43 and Chromium 43 downloaded a hotword module. It could enable the "OK Google" voice extension, though it was off by default. It was removed in Chrome 45.

  Incognito mode became a courtroom subject. It stops the browser storing history, cookies, site data, and form inputs locally, but it hides nothing from websites or internet providers. A class-action lawsuit filed in 2020 sought $5 billion in damages, saying Google misled people about tracking in Incognito. A proposed settlement was filed in federal court on the 1st of April 2024. Google would delete billions of browsing records, revise its disclosures, and let users block third-party cookies in Incognito for five years. It included no money damages and awaited court approval.

  Advertising raised the stakes further. In January 2021, Google promised to phase out third-party cookies in Chrome and replace them with a technology called FLoC. The U.K.'s Competition and Markets Authority and the European Commission opened formal probes. DuckDuckGo, Brave, and the Electronic Frontier Foundation said FLoC underestimated how well it could track users. On the 25th of January 2022, Google ended FLoC and proposed the Topics API. Topics uses a week of browsing to pick five interests and refreshes them every three weeks. Chrome's popularity has also attracted imitators. In late 2015, an adware copy called eFast hijacked Chrome installations and injected advertisements into web pages.

  In August 2024, a federal judge in Washington, D.C. ruled that Google maintained an illegal monopoly over search. In November 2024, the U.S. Department of Justice demanded that Google sell Chrome. On the 12th of August 2025, Perplexity AI offered to buy it for $34.5 billion, saying a sale could remedy the antitrust case.

  1315162256