Skip to main content

Google Chrome 76 will stop websites from seeing users in Incognito Mode

Google Chrome 76, scheduled to roll out on July 30, will fix a loophole that allows websites to detect visitors who are Incognito Mode, a move that will affect how publishers implement paywalls for their content.

In a blog post, Google said that some websites have been taking advantage of an unintended loophole involving Chrome’s FileSystem API. When in Incognito Mode, the API is disabled so that people will not leave traces of activity. Websites have been checking for the availability of the API, and if they do not find it, they determine that Incognito Mode is activated.

Related Videos

In Chrome 76, the behavior of the FileSystem API will be changed to prevent the Incognito Mode detection. Google also expressed its commitment to the principles of private browsing by saying that it will fix any other means of Incognito Mode detection.

The fix, which was first flagged in February, will impact publishers, particularly those who assume that users on Incognito Mode are trying to bypass metered paywalls. The Boston Globe started blocking visitors in Incognito Mode in 2017, requiring users in private browsing to log in to paid subscriber accounts to gain access to the website. The New York Times, Los Angeles Times, and other newspapers followed suit.

Ars Technica confirmed with Chrome 76 beta that the Boston Globe, the New York Times, and the Los Angeles Times were unable to detect that the browser was in Incognito Mode, unlike with Chrome 75.

Google acknowledged that the move will complicate matters for publishers who are enforcing paywalls, with many news websites limiting readers without subscriptions to a limited number of free articles per month. Incognito Mode, however, may bypass these limitations.

Google said that metered paywalls are “inherently porous,” as it requires cookies to track the number of free articles that a user has viewed. The company suggested options to news websites that include reducing the number of free articles, requiring free registration to view content, and hardening paywalls. Google added that publishers should take a look at the effect of the FileSystem API fix before making any changes to their websites.

“Our News teams support sites with meter strategies and recognize the goal of reducing meter circumvention, however any approach based on private browsing detection undermines the principles of Incognito Mode,” said Google.

Editors' Recommendations

Chrome extensions with 1.4M users may have stolen your data
Google Chrome icon in mac dock.

McAfee researchers have discovered various Google Chrome extensions that steal browsing activity, with the add-ons racking up more than a million downloads.

As reported by Bleeping Computer, threat analysts at the digital security company have come across a total of five such malicious extensions.

Read more
The best Google Chrome games for 2022

When most people think about Google Chrome, the search engine itself or apps like Gmail and Google Docs are typically the first things to come to mind. Google Chrome’s extensive list of free in-browser games isn't well-known. 

Google Chrome, in fact, has a vast array of apps and games from different genres that users can play on their mobile devices or laptop. With standouts like 2048 or Spelunky, among many others, you’re sure to find something you’ll enjoy.

Read more
Google Chrome extensions are failing, and $8,000 is on the table for a fix
A mouse pointer hovering over the CrankWheel Chrome Eextension.

There seems to be some mysterious problem affecting certain Chrome extensions, but it's intermittent enough that it hasn't yet been solved. The problem is annoying enough that one developer has posted two $4,000 bug bounties and created an Upwork job listing that pays up to $150 per hour. These incentives might inspire others to help track down and fix the bug.

First spotted by TechRadar and described in detail in a blog post written by Jói Sigurdsson, founder and CEO of the CrankWheel screen-sharing extension for the Google Chrome browser, the bug is related to a failure to trigger an action when the extension's icon is clicked on the toolbar. Since this is frequently how an extension is used, it's a crippling error. Unfortunately, the problem is difficult to recreate and is estimated to impact only 3% to 5% of those that have affected extensions installed.

Read more