Chrome Enterprise release notes

Last updated on: May 25, 2021

For administrators who manage Chrome browser or Chrome OS devices for a business or school.

In the following notes, the stable release or milestone number (M##) refers to the version of the scheduled feature launch. For example, M75 indicates a feature scheduled to launch with the stable version of Chrome 75. See below for a changelog and version history of Chrome.
 
 

Current Chrome version release notes

Open all   |   Close all Chrome 91

Chrome browser updates

 
  • Chrome pauses collapsed tab groups 

    Chrome allows users to organize tabs into collapsible groups, helping them stay productive. For some users, Chrome 91 pauses those tabs when the user collapses them, to reduce CPU and power consumption. Chrome does not pause tabs if they are playing audio, holding a web lock, holding an IndexedDB lock, connected to a USB device, capturing video or audio, being mirrored, or capturing a window or display.
     
  • Chrome blocks port 10080 and adds a policy for allowing specific ports 

    Chrome 91 adds port 10080 to the restricted ports list and blocks traffic through it. This does not affect customers using standard ports, but custom configurations using non-standard ports may be affected.
    If you're affected by this change, or if you were affected by the previous change that blocked port 554, Chrome introduces the ExplicitlyAllowedNetworkPorts enterprise policy, where you can allow these specific ports in your environment.
     
  • Chrome enables quantum computer resistant security 

    Chrome 91 supports a post-quantum key-agreement mechanism in TLS when communicating with some domains. This increases the size of TLS handshake messages which, in rare cases, may cause issues with network middleboxes that incorrectly assume that TLS messages fit in a single network frame.
    You can set the CECPQ2Enabled policy to disable this mechanism. You can also disable it by setting the ChromeVariations policy to a non-default value. For more details, see https://www.chromium.org/cecpq2.
     
  • Chrome no longer allows TLS 1.0 or TLS 1.1

    The SSLVersionMin policy no longer allows setting a minimum version of TLS 1.0 or 1.1. This means the policy can no longer be used to suppress Chrome's interstitial warnings for TLS 1.0 and 1.1. Administrators must upgrade any remaining TLS 1.0 and 1.1 servers to TLS 1.2.
    We previously communicated that this would happen as early as January 2021, but we extended the deadline until Chrome 91.
     
  • PWAs can launch when the user logs into the OS

    Users expect some apps, like chat apps, to launch as soon as they log into a Windows or Mac device. Chrome 91 allows users to set Progressive Web Apps (PWAs) to launch as soon as the user logs into the OS.
    As an admin, you can configure a PWA at install time with the option to launch automatically when a user logs in to its OS session.  
    You control this behavior using the WebAppSettings enterprise policy.
     
  • Chrome on iOS warns users if they reuse their saved passwords on known phishing sites

    To better protect users from phishing schemes, Chrome warns users if it appears that they've entered a saved password on a known phishing site. This feature is now being expanded to Chrome on iOS.  
    You control your organization's use of this feature using the PasswordManagerEnabled enterprise policy.

     
  • Chrome introduces initial_preferences

    As part of Chrome's move to using more inclusive naming, admins can control the browser's initial preferences using a file named initial_preferences. This file behaves the same way as, and will eventually replace, the master_preferences file that exists today. To minimize any disruption, Chrome continues to support the master_preferences file and more notice will be given before we remove support for master_preferences.
     
  • Chrome uses DNS-over-HTTPS on Linux
     
    DNS-over HTTPS protects user privacy by encrypting DNS queries, and was already enabled for Windows, Mac, ChromeOS, and Android in prior releases. Chrome 91 supports this feature on Linux. The DNS requests of all users will be auto-upgraded to their DNS provider’s DNS-over-HTTPS (DoH) service if available (based on a list of known DoH-capable servers).  
     
    You can disable DNS-over-HTTPS for your users with the DnsOverHttpsMode policy with Group Policy or in the Google Admin Console. Setting it to off ensures that your users are not affected by Secure DNS.
     
  • Chrome adds Referrer Chain to Client Side Detection pings
     
    To better protect users, Chrome conducts client-side checks of suspicious websites. In Chrome 91, if Enhanced Protection is enabled, the referrers of the website are also sent to Chrome.
     
    You control this behavior using the SafeBrowsingProtectionLevel enterprise policy.
     
  • Download deep scanning available for Enhanced Safe Browsing users
     
    Users who consented to Enhanced Safe Browsing can send downloads to Google for deep scanning when the existing safety checks are inconclusive.  
     
    You can disable this by controlling the user's Safe Browsing setting via the SafeBrowsingProtectionLevelpolicy. 
     
  • Chrome adds Google Account-tied tokens to Enhanced Safe Browsing pings
     
    For users who consented to Enhanced Safe Browsing, who have signed in to their Google accounts, Google Account-tied tokens are added to various phishing detection pings. This provides better protection and reduces false positives.  

    You control this feature on your environment using the SafeBrowsingProtectionLevel enterprise policy.
     
  • Chrome rollout status is available with the Chrome VersionHistory API
     
    The Chrome VersionHistory API is a web service API for retrieving information about Chrome versions and releases. It may be useful for administrators who want to see which versions of Chrome are currently rolled out, including to which fraction of users, to also see the history of Chrome rollouts.
     
    For more details, see https://developer.chrome.com/docs/versionhistory/.
     
  • Chrome can survey users about their experience managing Privacy Sandbox settings
     
    Users who visit the Privacy Sandbox settings page may be asked for their opinion about their experience. 
     
    You control if such surveys appear for your users with the MetricsReportingEnabled policy.
     
  • Chrome on Android tablets requests the desktop site
     
    Chrome 90 on Android tablets requested the desktop version of websites for some users. This is rolling out to all users in Chrome 91.
     
  • BrowserSignIn enterprise policy is available on iOS
     
    Admins can use the BrowserSignIn policy to allow, disable, or force users to sign into Chrome. Chrome 91 extends this policy to iOS. On iOS, you can use this policy to allow or disable user sign-in, but not force users to sign in.
     
  • Chrome uses updated table rendering
     
    Chrome 91 updates the way it renders tables on web pages. This change fixes known issues and brings Chrome closer to the behavior of other browsers, so we expect the impact to be minimal. However, you should test important workflows in your environment for unexpected issues. A full explainer is available here.

     
  • Chrome no longer accepts server certificates issued by the Camerfirma
     
    Websites that use server certificates issued by the Camerfirma Certification Authority are distrusted in Chrome 91. Affected sites should have already been contacted by Camerfirma and have migration plans in place. Note that this does not affect client certificates, only those used for authentication of TLS servers.
     
  • Network state partitioned in Chrome 91
     
    Today, some network objects are shared globally for performance reasons, but this makes it possible to fingerprint users and track them across sites. To protect user privacy, Chrome 91 partitions many network objects by topmost frame domain and iframe domain. A comprehensive description is available here.

    No impact is expected other than minor performance changes, but you can test the change in advance by using the command line flag: 
    --enable-features=PartitionConnectionsByNetworkIsolationKey,PartitionExpectCTStateByNetworkIsolationKey,PartitionHttpServerPropertiesByNetworkIsolationKey,PartitionNelAndReportingByNetworkIsolationKey,PartitionSSLSessionsByNetworkIsolationKey,SplitHostCacheByNetworkIsolationKey
     
  • Legacy Browser Support (LBS) parsing fix reverted in Chrome 91
     
    A fix in LBS was made in M90 that resulted in our rules parsing engine to be more strict and similar to the IE-sitelist rules parsing engine.  We have learned, however, that many customers relied on less-strict parsing behavior.  Due to the unintended impact, we are reverting the fix for Chromium bug 1176742.

    Please verify that your LBS rules work in M91 before deployment.  In a future release, we will offer a new policy to enable stricter rules parsing.
     

Chrome OS updates

 
  • Nearby Share on Chrome OS
     
    Nearby Share is a platform that provides easy, reliable, and secure file, text, and URL sharing across Chrome OS and Android devices.
     
  • VPN before login 
     
    Admins can configure built-in VPNs on Chrome OS so that users can connect to a VPN from the login screen. This allows users to authenticate securely via a VPN connection, which is especially helpful for enterprise-hosted single sign-on situations. Built-in VPN support includes L2TP/IPsec and OpenVPN.
     

Admin Console updates

 
  • Pin extensions to the browser toolbar
     
    Admins can now pin Chrome extensions to the browser toolbar from the Apps & Extension Page.  We recommend admins test out the feature on a small set of devices and browsers before deploying to their fleet. For more details, see here.
     
  • Chrome Insights Report: AUE Report
     
    The Auto Update Expiration (AUE) Chrome Insights Report allows admins to easily see how many Chrome OS devices in their fleet have reached their AUE dates or are expiring soon. Admins can navigate directly to the Device List from the report to view all devices expiring in the time frame selected. 
     
  • Sending Remote Commands for Chrome Desktop
     
    As an admin, you can use your Google Admin console to remotely send actions to managed Chrome Desktop Browsers (Win/Mac). For example, you can delete browser cache or cookies remotely.  For more details on sending commands, see here.
     
  • Additional policies in the Admin console 
     
Policy Name Pages Supported on Category/Field
KerberosRememberPasswordEnabled User & Browser Settings Chrome OS Kerberos / Remember Kerberos passwords
KerberosAddAccountsAllowed User & Browser Settings Chrome OS Kerberos / Kerberos accounts
SecurityTokenSessionBehavior User & Browser Settings; Managed Guest Session Settings Chrome OS Security / Security token removal / Action on security token removal (for example, smart card)
SecurityTokenSessionNotificationSeconds User & Browser Settings; Managed Guest Session Settings Chrome OS Security / Security token removal / Removal notification duration (seconds)
WebXRImmersiveArEnabled User & Browser Settings Android Other settings / WebXR "immersive-ar" sessions
SSLErrorOverrideAllowedForOrigins User & Browser Settings; Managed Guest Session Settings Chrome
Chrome OS
Android
Network / SSL error override allowed domains / Domains that allow clicking through SSL warnings
SystemProxySettings Device Settings Chrome OS Other settings / Authenticated Proxy Traffic
DeviceAllowMGSToStoreDisplayProperties Managed Guest Session Settings Chrome OS User experience / Persist display settings
DeviceAllowedBluetoothServices Device Settings Chrome OS Other settings / Bluetooth services allowed / Only allow connection to Bluetooth services in the list
DevicePciPeripheralDataAccessEnabled Device Settings Chrome OS Other settings / Data access protection for peripherals 

AccessibilityShortcutsEnabled

AutoclickEnabled

CaretHighlightEnabled

CursorHighlightEnabled

DictationEnabled

FloatingAccessibilityMenuEnabled

HighContrastEnabled

KeyboardFocusHighlightEnabled

LargeCursorEnabled

MonoAudioEnabled

PrimaryMouseButtonSwitch

ScreenMagnifierType

SelectToSpeakEnabled

SpokenFeedbackEnabled

StickyKeysEnabled

VirtualKeyboardEnabled

Device Settings

Chrome OS

Kiosk accessibility

  • New and updated policies (Chrome and Chrome OS)
Policy Description
BrowserThemeColor
Browser Only
Configure the color of the browser's theme
CECPQ2Enabled CECPQ2 post-quantum key-agreement enabled for TLS
DefaultFileHandlingGuardSetting Lets web apps ask for access to file types via the File Handling API.
DeviceAllowedBluetoothServices
Chrome OS Only
Only allow connection to the Bluetooth services in the list
ExplicitlyAllowedNetworkPorts Permits bypassing the list of restricted ports
FileHandlingAllowedForUrls Specifies web apps allowed to access file types via the File Handling API.
FileHandlingBlockedForUrls Specifies web apps blocked from accessing file types via the File Handling API.
ForcedLanguages
Browser Only
Configure the content and order of preferred languages
HeadlessMode Control use of the Headless Mode
SharedArrayBufferUnrestrictedAccessAllowed Specifies whether SharedArrayBuffers can be used in a non cross-origin-isolated context.
SuppressDifferentOriginSubframeDialogs Specifies if JavaScript dialogs triggered from a different origin subframe will be blocked
URLBlocklist
New on iOS
Specifies disallowed URLs
URLAllowlist
New on iOS
Specificies allowed URLs
WebAppSettings
Browser only
Specifies settings for web apps installed through WebAppInstallForceList Note: This is an experimental policy that may be replaced in a future version of Chrome.
WebRtcIPHandling WebRTC will use TCP on the public-facing interface, and will only use UDP if supported by a configured proxy

Coming soon


Note: The items listed below are experimental or planned updates. They might change, be delayed, or canceled before launching to the Stable channel.
 
  • Chrome is moving to a 4-week stable channel and introducing an 8-week extended stable channel as early as Chrome 94
     
    Chrome on mobile, Windows, Mac, and Linux will move from its current 6-week release cycle to a 4-week release cycle, allowing security features, new functionality and bug fixes to reach users more quickly.
     
    No action is required for most enterprises, but if you manually update or test new releases of Chrome and prefer a slower release cadence, you'll be able to use the TargetChannel policy to switch Chrome on Mac and Windows to an extended stable channel, with a new release every 8 weeks instead. More details can be found on our blog post at blog.chromium.org
     
    Chrome OS is working on the changes to the release cadence and will send a separate announcement.  As always, Chrome OS will prioritize the latest security updates, and maintain a high quality and stable experience for users, customers, partners, and developers.
     

Upcoming Chrome browser changes

 
  • Managed profile sign-in popup will be more clear in Chrome 92
     
    Chrome will update the notice when users sign into a managed profile. The new notice will use clear language and the available actions will be simplified. Some users will see a link to open Chrome in guest mode when they sign in to a new profile that's different from the profile signed in to Chrome.  
     
  • SharedArrayBuffers will need Cross-Origin-Opener-Policy and Cross-Origin-Embedder-Policy in Chrome 92
     
    If your organization uses apps that leverage SharedArrayBuffers, those apps will need to set Cross-Origin-Opener-Policy and Cross-Origin-Embedder-Policy in the HTTP header. Web apps not setting the appropriate policies will no longer be able to access SharedArrayBuffers.  
    If your organization needs additional time to make the transition, the SharedArrayBufferUnrestrictedAccessAllowed policy will be available in Chrome 91. This is a temporary policy that will eventually be removed. The removal timeline will be communicated in future release notes.
     
  • Insecure public pages no longer allowed to make requests to private or local URLs in Chrome 92
     
    Insecure pages will no longer be able to make subresource requests to IPs belonging to a more private address space (as defined in Private Network Access). For example, http://public.page.example.com will not be able to make requests targeting IP 192.168.0.1 or IP 127.0.0.1. You will be able to control this behavior using the InsecurePrivateNetworkRequestsAllowed and InsecurePrivateNetworkRequestsAllowedForUrls enterprise policies.
     
  • Different-origin iframes will not be able to trigger javascript dialogs in Chrome 92
     
    Chrome will prevent iframes from triggering prompts (window.alert, window.confirm, window.prompt) if the iframe is a different origin from the top-level page. This change is intended to prevent embedded content from spoofing the user into believing a message is coming from the website they're visiting, or from Chrome itself.
    If you have any web apps affected by this change, you'll be able to use the temporary enterprise policy SuppressDifferentOriginSubframeDialogs to revert to the previous behavior. This policy will be removed in Chrome 95.
     
  • Chrome will launch a sharing hub in Chrome 92
     
    Users will be able to more easily share their current page in Chrome 92, including the ability to send the current page to their devices, get a QR code for the current URL,  screenshot and markup the current page, and share to third party apps.
    You'll be able to control this feature using an enterprise policy.
     
  • Chrome 92 on iOS will prefer https to http when not specified in the address bar
     
    When a user types an address into the address bar without specifying the protocol, Chrome will attempt to navigate using https first, then fallback to http if https is not available. For example, if the user navigates to example.com, Chrome will first attempt to navigate to https://example.com, then fallback to http://example.com if required. For more information, see Chrome’s blog post, A safer default for navigation: HTTPS.
    Desktop and Android users already had this change, and iOS will be rolled out in Chrome 92.
     
  • Chrome 92 on Android will introduce the Magic Toolbar 

    The Chrome toolbar on Android will add a new adaptable button, which will show different shortcuts depending on what the user is most likely to need and will also be customizable. 
     
  • Chrome 92 will expand DNS HTTPS records queries for users using classic DNS 
     
    Chrome is currently querying and parsing DNS HTTPS records alongside the traditional A and AAAA records for users using Secure DNS. From Chrome 92,  we will expand this behavior to users using classic DNS. The information from these records will be used to improve privacy and performance of HTTPS web connections. You can temporarily disable these extra queries for users using classic DNS, via the AdditionalDnsQueryTypesEnabled policy with Group Policy or in the Google Admin Console. Please share details about issues that led you to use the policy as a workaround. Note that this policy has no effect for users using Secure DNS.
     
  • Lock in address bar will be replaced in Chrome 93
     
    The lock in the address bar will be replaced with a new icon. Chrome is moving to security messaging that highlights known security issues, and shows neutral messaging otherwise. Showing an icon that implies safety based solely on the connection's encryption may lead to a false sense of security.
     
  • Network Service on Windows will be sandboxed as early as Chrome 93
     
    The network service, already running in its own process, will be sandboxed on Windows to improve the security and reliability of the service. As part of this, third party code that is currently able to tamper with the Network Service will be prevented from doing so. This might cause interoperability issues with software that injects code into Chrome's process space, such as Data loss Prevention software.You'll be able to disable the change with an enterprise policy when it becomes available.
     
  • Chrome may leverage MiraclePtr to improve security, as early as Chrome 93
     
    Chrome will leverage MiraclePtr to reduce the risk of security vulnerabilities relating to memory safety. The Chrome team is gathering data on the performance cost of MiraclePtr in Chrome 91, but domain-joined enterprises on the stable channel are excluded from MiraclePtr builds during this phase. A full release of MiraclePtr in Chrome may be as early as Chrome 93.
     
  • UserAgentClientHintsEnabled will be removed in Chrome 93
     
    When Chrome introduced User-Agent Client Hints, some servers were not able to accept all characters in the User-Agent Client Hints headers as part of the broader Structured Headers  emerging standard.
    To give enterprises extra time updating these servers, the UserAgentClientHintsEnabled policy was introduced. This transition period will end with Chrome 93, and the policy will be removed.
     
  • SyncXHR policy will no longer be supported on Chrome 93
     
    The AllowSyncXHRInPageDismissal enterprise policy will be removed in Chrome 93. For any apps that rely on the legacy web platform behavior, be sure to update them before Chrome 93. This change was previously planned for Chrome 88, but delayed to provide more time for enterprises to update legacy applications.
     
  • LegacySameSiteCookieBehaviorEnabled will be removed in Chrome 93
     
    When same-site cookie behavior was introduced, Chrome included policies to give admins extra time to adjust the implementation of any enterprise apps that relied on the legacy cookie behavior.
    The first phase of the transition plan will end in Chrome 93, and LegacySameSiteCookieBehaviorEnabled will no longer take effect. You will still be able to opt specific sites into the legacy cookie behavior using LegacySameSiteCookieBehaviorEnabledForDomainList until Chrome 109.
     
  • Chrome 93 will not support Ubuntu 16.04 

    Ubuntu 16.04 is past the end of standard support, and will not be supported as of Chrome 93. The updated system requirements for Chrome are available here.
     
  • Chrome 93 will remove 3DES TLS cipher suites 

    Chrome will remove support for 3DES TLS cipher suites. The TripleDESEnabled enterprise policy will be made available in Chrome 92 to test this change, and will be available temporarily until Chrome 95, to give enterprises additional time to adjust.
     
  • Chrome apps will be deprecated in Chrome 94 on Mac, Windows, and Linux 

    Chrome apps will no longer function on Mac, Windows, and Linux in Chrome 94, as part of the previously-communicated plan to replace Chrome apps with the open web. For enterprises that need extra time to adjust to the removal of Chrome apps, a policy will be available to extend support for them until June 2022.
     
  • Chrome will maintain its own default root store as early as Chrome 95 

    To improve user security, and provide a consistent experience across different platforms, Chrome intends to maintain its own default root store. If you are an enterprise admin managing your own certificate authority, you should not have to manage multiple root stores. We do not anticipate any changes to be required for how enterprises currently manage their fleet and trusted enterprise CAs, such as through group policy, macOS Keychain Access, or system management tools like Puppet.
     
  • Legacy policies with non-inclusive names will be removed in Chrome 95 

    Chrome 86 through Chrome 90 introduced new policies to replace policies with less inclusive names (for example, whitelist blacklist). To minimize disruption for existing managed users, both the old and the new policies currently work. This transition time is to ensure it's easy for you to move to and test the new policies in Chrome.
    Note: If both the legacy policy and the new policy are set for any row in the table below, the new policy will override the legacy policy.
    This transition period will end in Chrome 95, and the following policies in the left column will no longer function. Please ensure you're using the corresponding policy from the right column instead:

     

    Legacy Policy Name New Policy Name
    NativeMessagingBlacklist NativeMessagingBlocklist
    NativeMessagingWhitelist NativeMessagingAllowlist
    AuthNegotiateDelegateWhitelist AuthNegotiateDelegateAllowlist
    AuthServerWhitelist AuthServerAllowlist
    SpellcheckLanguageBlacklist SpellcheckLanguageBlocklist
    AutoplayWhitelist AutoplayAllowlist
    SafeBrowsingWhitelistDomains SafeBrowsingAllowlistDomains
    ExternalPrintServersWhitelist ExternalPrintServersAllowlist
    NoteTakingAppsLockScreenWhitelist NoteTakingAppsLockScreenAllowlist
    PerAppTimeLimitsWhitelist PerAppTimeLimitsAllowlist
    URLWhitelist URLAllowlist
    URLBlacklist URLBlocklist
    ExtensionInstallWhitelist ExtensionInstallAllowlist
    ExtensionInstallBlacklist ExtensionInstallBlocklist
    UserNativePrintersAllowed UserPrintersAllowed
    DeviceNativePrintersBlacklist DevicePrintersBlocklist
    DeviceNativePrintersWhitelist DevicePrintersAllowlist
    DeviceNativePrintersAccessMode DevicePrintersAccessMode
    DeviceNativePrinters DevicePrinters
    NativePrinters Printers
    NativePrintersBulkConfiguration PrintersBulkConfiguration
    NativePrintersBulkAccessMode PrintersBulkAccessMode
    NativePrintersBulkBlacklist PrintersBulkBlocklist
    NativePrintersBulkWhitelist PrintersBulkAllowlist
    UsbDetachableWhitelist UsbDetachableAllowlist
    QuickUnlockModeWhitelist QuickUnlockModeAllowlist
    AttestationExtensionWhitelist AttestationExtensionAllowlist
    PrintingAPIExtensionsWhitelist PrintingAPIExtensionsAllowlist
    AllowNativeNotifications AllowSystemNotifications
    DeviceUserWhitelist DeviceUserAllowlist
    NativeWindowOcclusionEnabled WindowOcclusionEnabled

If you're managing Chrome via the Google Admin Console (for example, Chrome Browser Cloud Management), no action is required; the Google Admin Console will manage the transition automatically.
 

Upcoming Admin Console changes

 
  • Sending Extension Requests for Chrome Browser Desktop and Chrome OS 
     
    As an admin, you can block users from installing extensions and the Chrome Web Store will now have a “Request” button so that you can see their requests from within the Admin Console and take an action to allow or to block the extensions.  You can sign up to get early access to this feature by filling out our Trusted Tester form. 

     
 

Previous release notes 

Chrome 90

Chrome Browser updates

 
  • Single words are not treated as intranet locations by default

    By default, Chrome improves user privacy and reduces load on DNS servers by avoiding DNS lookups for single keywords entered into the address bar. This change may interfere with enterprises that use single-word domains in their intranet. That is, a user typing "helpdesk" is no longer directed to "https://helpdesk/".
    You can control the behavior of Chrome using the IntranetRedirectBehavior enterprise policy, including preserving the existing behavior (value 3: Allow DNS interception checks and did-you-mean "http://intranetsite/" infobars.).
    Some users saw this change in Chrome 88 and 89; a full rollout is happening in Chrome 90.
     
  • Chrome prefers https to http when not specified in the address bar

    When a user types an address into the address bar without specifying the protocol, Chrome attempts to navigate using https first, then falls back to http if https is not available. For example, if the user navigates to example.com, Chrome first attempts to navigate to https://example.com, then falls back to http://example.com if required. See Chrome’s blog post, A safer default for navigation: HTTPS, for more information.
    Desktop and Android users see this in Chrome 90, with a release on iOS following soon after.
     
     
  • Chrome blocks port 554 in Chrome 90

    Port 554 is added to the restricted ports list,  so Chrome blocks traffic through port 554. This should have no effect on customers using standard ports, but custom configurations (for example, delivering PAC scripts) using non-standard ports may be affected. You should instead use standard ports for your use case (for example, delivering PAC scripts via HTTPS through port 443).

     
  • The TargetChannel policy allows you to set Chrome's channel

    Chrome 90 allows you to choose between stable, beta, and dev channels via the enterprise policy TargetChannel. You can read more about setting the policies for Mac and Windows.

     
  • Chrome compresses public HTTPS images

    When Chrome Lite mode is enabled, Chrome compresses public HTTPS images to reduce users’ data costs, by routing the requests through a Google service. You can control this using the DataCompressionProxyEnabled enterprise policy.

     
  • Chrome saves data with Lite videos

    To reduce the data-cost and improve the experience of videos on metered and limited data connections, Chrome on Android reduces the effective bitrate of videos for Lite mode users on cellular connection. You can control this feature using the DataCompressionProxyEnabled policy.

     
  • AllowNativeNotifications updated to AllowSystemNotifications

    As part of Chrome's move to using more inclusive policy names, AllowNativeNotifications is renamed to AllowSystemNotifications. The existing AllowNativeNotifications policy will be available until Chrome 95.

     
  • Chrome supports Intel CET

    Chrome supports Intel’s Control Flow Enforcement Technology (CET), known as Hardware-enforced Shadow Stacks on Windows. This only affects Chrome running on hardware that supports CET (Intel 11th Gen or AMD Zen 3). While no issues are expected, you can manage CET by manipulating Image File Execution Options (IFEO) through group policy.

     
  • Some permission requests are less intrusive

    Permission requests that the user is unlikely to allow are automatically blocked, when Safe Browsing is set to Enhanced. A less intrusive UI allows the user to manage permissions for each site.


    You can control this feature on your environment using the SafeBrowsingProtectionLevel enterprise policy. Set it to 1 (standard), 2 (enhanced), or leave the policy unset to enable the quieter requests. Set it to 0 (disabled) to always use the standard requests instead of the quieter requests.

    You can also explicitly allow or disable notifications for certain sites using the NotificationsAllowedForUrls and NotificationsBlockedForUrls. This may be better suited for your use case and doesn't require the user to be prompted at all.

     
  • Extension settings load from the same place for all channels on Mac

    All Chrome channels read the extension policies from the same .plist file. For example, the extension Password Alert always loads its policies from com.google.Chrome.extensions.noondiphcddnnabmjcihcjfbhfklnnep.plist instead of com.google.Chrome.canary.extensions.noondiphcddnnabmjcihcjfbhfklnnep.plist in Chrome Canary.

     
  • Security key enterprise attestation

    Chrome supports device-unique attestation of security keys without needing a policy configured. This is useful in situations where security keys are distributed by an enterprise to personnel who may use them on non-policy-managed computers. This requires specially-manufactured security keys—talk to your security key vendor if this sounds useful.

     
  • WebXR depth sensing API will be supported

    The WebXR Depth Sensing API allows Chrome to measure distance from the user’s device to real world geometry in the user’s environment. With this, Chrome will be able to power immersive experiences in WebXR-powered apps (for example, for physics, and lifelike occlusion for augmented reality).

    You will be able to control access to WebXR and other augmented reality APIs using the WebXRImmersiveArEnabled enterprise policy.

     
  • Admin controls on shutdown delay for fetch keepalive

    When Chrome is closed, any outstanding fetch keepalive requests are cancelled by default. In Chrome 90, you can use the FetchKeepaliveDurationSecondsOnShutdown enterprise policy to block browser shutdown for a specified period of time to serve any outstanding fetch keepalive requests.

    This may be suitable for enterprise web applications that require the fetch keepalive requests to signal the end of a user session.

     
  • Legacy browser support works between Chrome and Microsoft Edge

    You can configure Legacy Browser Support to automatically switch between multiple browsers, assigning certain sites to always open in Chrome, while other sites always open in another browser, for example, Internet Explorer. With Chrome 90, we now support configuring your environment to switch between Chrome and Microsoft Edge in IE mode. See this help center article for more details.

     
  • Chrome on Android tablets requests the desktop site

    Chrome 90 on Android tablets requests the desktop version of websites for some users. This is expected to be rolled out to all users in Chrome 91.

     

Chrome OS updates

 
  • Deprecation of AMR and GSM audio codecs

    AMR-NB, AMR-WB, and GSM audio codecs are deprecated as part of this release. Affected users should file bugs here and may temporarily rollback this change via the use of chrome://flags/#deprecate-low-usage-codecs. Users with long-term need for these codecs may use stand-alone applications found in the Google Play Store.

 

  • New Diagnostics app

    The new Diagnostics app helps users understand how their Chrome OS device [battery, CPU, and memory] is performing. Within the app, users can also run troubleshooting tests – results are saved in a session log file for easy sharing with customer support.

     
  • Device Dock Update

    Device updates provide users the ability to have reliable and safe peripherals, by providing an avenue to update their software if needed. In Chrome OS 90, we are releasing a path for updates to docks with minimal user experience disruption, making it simple and safe for all our users that use Works With Chromebook certified accessories.

     
  • Updated UI for recent screenshots and downloads

    Quickly access your recent screenshots and downloads. Pin your important Files to launch, copy, or drag with one click. Visit here for more information.

     
  • Better account manager and add account flow

    Chrome OS’s account manager is getting a brand new design to help users better understand the Chrome OS identity model, such as the difference between device account and secondary Google Accounts, and the implications of adding multiple Google Accounts to a user session. Instead of being nested under the "People'' section, the redesigned account manager is part of a new "Accounts" section for clarity and ease of access. Finally, the add account flow is also redesigned to help nudge users away from adding their Google Accounts to user sessions that are not their own.

     
  • Add Live captions settings to Chrome OS settings

    Chrome Live Caption now supports Chrome OS. Live Captions enables you to caption any audio or video in your browser.

     
  • YouTube and Maps open in standalone windows for new users

    New users can now experience YouTube and Maps in standalone app windows by default, rather than opening as browser tabs. Existing users can right-click on the YouTube or Maps app icon, then select Open link in new tab or Open link in new window.

     
  • Files app: Enable offline for Docs, Sheets, and Slides files on Drive

    Users now have the ability to make Google Docs, Sheets, and Slides available for offline access directly from their Drive folder in the Chrome OS file manager.

     

Admin console updates

 
  • Chrome Policy API

    The Chrome Policy API is a brand new API for configuring Admin console Chrome policies. Admins can use the API to script changes across multiple OUs, compare policies or copy policies across multiple OUs, and more. The Chrome Policy API is now available with support for user & browser settings, as well as printer settings. Future versions of the API will also support managing apps & extensions, device settings, kiosk, and managed guest session settings.

     
  • Update Controls for macOS

    Admin Console now supports configuring update controls for macOS. Please see the Help Center article on how to configure these settings.

     
  • Version History API

    The Chrome Update team released a web service API for retrieving information about Chrome versions and releases.

     
  • Additional policies in the Admin console

    Many new policies are available in the Admin console, including:
     
Policy Name Pages Supported on Category/Field
BasicAuthOverHttpEnabled User & Browser Settings Chrome OS, Windows, Mac, Linux Network / Allow Basic authentication for HTTP
BrowserLabsEnabled User & Browser Settings Windows, Mac, Linux User experience / Browser experiments icon in toolbar
DefaultSensorsSetting User & Browser Settings; Managed Guest Session Settings Chrome OS, Windows, Mac, Linux, Android Hardware / Sensors / Default access
EnableDeprecatedPrivetPrinting User & Browser Settings; Managed Guest Session Settings Chrome OS, Windows, Mac, Linux Printing / Deprecated privet printing
FullscreenAlertEnabled User & Browser Settings Chrome OS User experience / Fullscreen alert
IntegratedWebAuthenticationAllowed User & Browser Settings Chrome OS Network / Login credentials for network authentication
NTPCardsVisible User & Browser Settings Chrome OS, Windows, Mac, Linux User experience / Show cards on the New Tab Page
PhoneHubAllowed User & Browser Settings Chrome OS Connected devices / Phone Hub
PhoneHubNotificationsAllowed User & Browser Settings Chrome OS Connected devices / Phone Hub
PhoneHubTaskContinuationAllowed User & Browser Settings Chrome OS Connected devices / Phone Hub
ProfilePickerOnStartupAvailability User & Browser Settings Windows, Mac, Linux Startup / Profile picker availability on browser startup
RemoteAccessHostDomainList User & Browser Settings; Managed Guest Session Settings Chrome OS, Windows, Mac, Linux Remote access / Remote access hosts / Remote access host domain
SensorsAllowedForUrls User & Browser Settings; Managed Guest Session Settings Chrome OS, Windows, Mac, Linux, Android Hardware / Sensors / Allow access to sensors on these sites
SensorsBlockedForUrls User & Browser Settings; Managed Guest Session Settings Chrome OS, Windows, Mac, Linux, Android Hardware / Sensors / Block access to sensors on these sites
SigninInterceptionEnabled User & Browser Settings Windows, Mac, Linux Sign-in settings / Signin interception
TargetBlankImpliesNoOpener User & Browser Settings; Managed Guest Session Settings Chrome OS, Windows, Mac, Linux, Android Security / Popup interactions
WifiSyncAndroidAllowed User & Browser Settings Chrome OS Other settings / Wi-Fi network configurations sync

 

  • New and updated policies (Chrome Browser and Chrome OS)
     
Policy Description
AllowSystemNotifications
Linux Only
Allow system notifications
AudioProcessHighPriorityEnabled
Windows Only
Allow the audio process to run with priority above normal on Windows
FetchKeepaliveDurationSecondsOnShutdown Fetch keepalive duration on Shutdown
SSLErrorOverrideAllowedForOrigins Allow proceeding from the SSL warning page on specific origins
WebXRImmersiveArEnabled Allow creating WebXR's "immersive-ar" sessions
WindowOcclusionEnabled
Browser only
Enable Window Occlusion

 

Coming soon

 

Note: The items listed below are experimental or planned updates. They might change, be delayed, or canceled before launching to the Stable channel.

  • Chrome is moving to a 4-week stable channel and introducing an 8-week extended stable channel as early as Chrome 94

    Chrome on mobile, Windows, Mac, and Linux will move from its current 6-week release cycle to a 4-week release cycle, allowing security features, new functionality and bug fixes to reach users more quickly.

    No action is required for most enterprises, but if you manually update or test new releases of Chrome and prefer a slower release cadence, you'll be able to switch Chrome to an extended stable channel, with a new release every 8 weeks instead. More details can be found on our blog post at blog.chromium.org.

    Chrome OS is also planning changes to the release cycle during the same release. As always, Chrome OS will prioritize the latest security updates, and maintain a high quality and stable experience for users, customers, partners, and developers.

     

Upcoming Chrome Browser changes

 
  • Chrome 91 will block port 10080 and add a policy for allowing specific ports

    Port 10080 will be added to the restricted ports list and traffic will be blocked through it. This should have no effect on customers using standard ports, but custom configurations using non-standard ports may be affected.

    If you're affected by this change, or other changes blocking ports for security reasons, Chrome will introduce an enterprise policy where you can allow specific ports in your environment.
     
  • Collapsed tab groups will be frozen in Chrome 91

    Chrome allows users to group tabs into collapsible groups, helping them stay organized and productive. In Chrome 91, those tabs will be frozen when the user collapses them, freeing up resources on the system. Chrome will not freeze tabs if they are playing audio, holding a web lock, holding an IndexedDB lock, connected to a USB device, capturing video or audio, being mirrored, or capturing a window or display.

     
  • Web apps will be able to run when the user logs into the OS in Chrome 91

    Users will be able to configure Progressive Web Apps to start automatically when they log into the OS. This allows some apps that the user expects to be always-on to behave as expected.

    You will be able to control which apps can start on OS login using the WebAppSettings enterprise policy.

     
  • Chrome will introduce initial_preferences in Chrome 91

    As part of Chrome's move to using more inclusive naming, Chrome will support an admin using a file to control the browser's initial preferences, named initial_preferences. This file behaves the same way as, and will eventually replace the master_preferences file that exists today. To minimize any disruption, master_preferences will continue to be supported in Chrome 90 and more notice will be given before support for master_preferences is removed.
     
  • Different-origin iframes will not be able to trigger javascript dialogs in Chrome 91

    Chrome will prevent iframes from triggering prompts (window.alert, window.confirm, window.prompt) if the iframe is a different origin from the top-level page. This change is intended to prevent embedded content from spoofing the user into believing a message is coming from the website they're visiting, or from Chrome itself.

    If you have any web apps affected by this change, you'll be able to use the temporary enterprise policy SuppressDifferentOriginSubframeDialogs to revert to the previous behavior. This policy will be removed in Chrome 94.

    You can test apps in your environment for compatibility using Chrome 91 Canary, and Chrome 91 Beta on April 22.
     
  • Network state will be partitioned in Chrome 91

    At present, some network objects are shared globally for performance reasons, but this makes it possible to fingerprint users and track them across sites. To protect user privacy, Chrome will partition many network objects by topmost frame domain and iframe domain. A comprehensive description is available here.

    No impact is expected other than minor performance changes, but you can test the change in advance by using the command line flag:

    --enable-features=PartitionConnectionsByNetworkIsolationKey,PartitionExpectCTStateByNetworkIsolationKey,PartitionHttpServerPropertiesByNetworkIsolationKey,PartitionNelAndReportingByNetworkIsolationKey,PartitionSSLSessionsByNetworkIsolationKey,SplitHostCacheByNetworkIsolationKey

     
  • The BrowserSignIn enterprise policy will be available for Chrome 91 on iOS

    The BrowserSignIn policy allows you to either disable or force users to sign into Chrome browser. The IncognitoModeAvailability policy allows you to disable Incognito mode. Both of these policies will be available for Chrome 90 on iOS.
     
  • Quantum computer resistant security will be enabled in Chrome 91

    Chrome will start supporting a post-quantum key-agreement mechanism in TLS when communicating with some domains. This increases the size of TLS handshake messages which, in rare cases, may cause issues with network middleboxes that incorrectly assume that TLS messages will fit in a single network frame.

    The CECPQ2Enabled policy can be set to disable this. It will also be disabled if the ChromeVariations policy is set to a non-default value. For more details on this rollout, see https://www.chromium.org/cecpq2

     
  • The SSLVersionMin policy will not allow TLS 1.0 or TLS 1.1 in Chrome 91

    The SSLVersionMin enterprise policy allows you to bypass Chrome's interstitial warnings for legacy versions of TLS. This will be possible until Chrome 91 (May 2021), then the policy will no longer allow TLS 1.0 or TLS 1.1 to be set as the minimum.

    We previously communicated that this would happen as early as January 2021, but the deadline has since been extended.

     
  • Server certificates issued by the Camerfirma will no longer be accepted, no later than Chrome 91

    Websites that use server certificates issued by the Camerfirma Certification Authority will be distrusted in a future release of Chrome. Affected sites should have already been contacted by Camerfirma and have migration underway. Note that this does not affect client certificates, only those used for authentication of TLS servers.

     
  • Chrome 91 on iOS will warn users if they reuse their saved passwords on known phishing sites

    To better protect users from phishing schemes, Chrome warns users if it appears that they've entered a saved password on a known phishing site. In Chrome 91, this feature will be expanded to Chrome on iOS.

    You can control your organization's use of this feature using the PasswordManagerEnabled enterprise policy.

     
  • Chrome 91 will use updated table rendering

    Chrome is updating the way it renders tables on web pages. This change fixes known issues and brings Chrome closer to the behavior of other browsers, so impact is expected to be minimal. However, you should test important workflows in your environment for unexpected issues. A full explainer is available here.

    You can enable the new rendering behavior using chrome://flags/#enable-table-ng in Chrome 90 and above. If you experience any unexpected issues when testing with the flag enabled, please file a chromium bug.

     
  • Managed profile sign-in popup will be more clear, with changes as early as Chrome 91

    Chrome will update the notice when users sign into a managed profile. The new notice has more clear language and the available actions have been simplified. Some users will see a link to open Chrome in guest mode when they sign into a new profile that's different from the profile signed into Chrome.

     
  • Insecure public pages no longer allowed to make requests to private or local URLs in Chrome 92

    Insecure pages will no longer be able to make requests to IPs belonging to a more private address space (as defined in CORS-RFC1918). For example, http://public.page.example.com will not be able to make requests targeting IP 192.168.0.1 or IP 127.0.0.1. You will be able to control this behavior using the InsecurePrivateNetworkRequestsAllowed and InsecurePrivateNetworkRequestsAllowedForUrls enterprise policies.

     
  • Lock in address bar will be replaced in Chrome 92

    The lock in the address bar will be replaced with a new icon. Chrome is moving to security messaging that highlights known security issues, and shows neutral messaging otherwise. Showing an icon that implies safety based solely on the connection's encryption may lead to a false sense of security.

     
  • The Network Service on Windows will be sandboxed as early as Chrome 92

    The network service, already running in its own process, will be sandboxed on Windows to improve the security and reliability of the service. As part of this, third party code that is currently able to tamper with the Network Service will be prevented from doing so. This might cause interoperability issues with software that injects code into Chrome's process space, such as Data loss Prevention software.You'll be able to disable the change with an enterprise policy when it becomes available.

     
  • Chrome will leverage MiraclePtr to improve security, as early as Chrome 93

    Chrome will leverage MiraclePtr to reduce the risk of security vulnerabilities related to memory safety. The Chrome team is gathering data on the performance cost of MiraclePtr in Chrome 91, but enterprises on the stable channel are excluded from MiraclePtr builds during this phase. A full release of MiraclePtr in Chrome may be as early as Chrome 93.
     
  • Chrome will maintain its own default root store as early as Chrome 92

    In order to improve user security, and provide a consistent experience across different platforms, Chrome intends to maintain its own default root store. If you are an enterprise admin managing your own certificate authority, you should not have to manage multiple root stores.We do not anticipate any changes to be required for how enterprises currently manage their fleet and trusted enterprise CAs, such as through group policy, macOS Keychain Access, or system management tools like Puppet.  
     
  • Chrome will launch a sharing hub in Chrome 92

    Users will be able to more easily share their current page in Chrome 92, including the ability to send the current page to their devices, get a QR code for the current URL,  screenshot and markup the current page, and share to third party apps.

    You'll be able to control this feature using an enterprise policy. 
     
  • UserAgentClientHintsEnabled will be removed in Chrome 93

    When Chrome introduced User-Agent Client Hints, some servers were not able to accept all characters in the User-Agent Client Hints headers as part of the broader Structured Headers  emerging standard.

    To give enterprises extra time updating these servers, the UserAgentClientHintsEnabled policy was introduced. This transition period will be ending with Chrome 93, and the policy will be removed. 
     
  • SyncXHR policy will no longer be supported on Chrome 93

    The AllowSyncXHRInPageDismissal enterprise policy will be removed in Chrome 93. For any apps that rely on the legacy web platform behavior, be sure to update them before Chrome 93. This change was previously planned for Chrome 88, but delayed to provide more time for enterprises to update legacy applications. 
     
  • LegacySameSiteCookieBehaviorEnabled will be removed in Chrome 93

    When same-site cookie behavior was introduced, Chrome included policies to give admins extra time to adjust the implementation of any enterprise apps that relied on the legacy cookie behavior. The first phase of the transition plan will end in Chrome 93, and LegacySameSiteCookieBehaviorEnabled will no longer take effect. You will still be able to opt specific sites into the legacy cookie behavior using LegacySameSiteCookieBehaviorEnabledForDomainList until Chrome 97. 
     
  • Legacy policies with non-inclusive names will be removed in Chrome 95

    Chrome 86 through Chrome 90 introduced new policies to replace policies with less inclusive names (for example, whitelist, blacklist). In order to minimize disruption for existing managed users, both the old and the new policies currently work. This transition time is to ensure it's easy for you to move to and test the new policies in Chrome. 

    Note: If both the legacy policy and the new policy are set for any row in the table below, the new policy will override the legacy policy. 

    This transition period will end in Chrome 95, and the following policies in the left column will no longer function. Please ensure you're using the corresponding policy from the right column instead: 
     
Legacy Policy Name New Policy Name
NativeMessagingBlacklist NativeMessagingBlocklist
NativeMessagingWhitelist NativeMessagingAllowlist
AuthNegotiateDelegateWhitelist AuthNegotiateDelegateAllowlist
AuthServerWhitelist AuthServerAllowlist
SpellcheckLanguageBlacklist SpellcheckLanguageBlocklist
AutoplayWhitelist AutoplayAllowlist
SafeBrowsingWhitelistDomains SafeBrowsingAllowlistDomains
ExternalPrintServersWhitelist ExternalPrintServersAllowlist
NoteTakingAppsLockScreenWhitelist NoteTakingAppsLockScreenAllowlist<
PerAppTimeLimitsWhitelist PerAppTimeLimitsAllowlist
URLWhitelist URLAllowlist
URLBlacklist URLBlocklist
ExtensionInstallWhitelist ExtensionInstallAllowlist
ExtensionInstallBlacklist ExtensionInstallBlocklist
UserNativePrintersAllowed UserPrintersAllowed
DeviceNativePrintersBlacklist DevicePrintersBlocklist
DeviceNativePrintersWhitelist DevicePrintersAllowlist
DeviceNativePrintersAccessMode DevicePrintersAccessMode
DeviceNativePrinters DevicePrinters
NativePrinters Printers
NativePrintersBulkConfiguration PrintersBulkConfiguration
NativePrintersBulkAccessMode PrintersBulkAccessMode
NativePrintersBulkBlacklist PrintersBulkBlocklist
NativePrintersBulkWhitelist PrintersBulkAllowlist
UsbDetachableWhitelist UsbDetachableAllowlist
QuickUnlockModeWhitelist QuickUnlockModeAllowlist
AttestationExtensionWhitelist AttestationExtensionAllowlist
PrintingAPIExtensionsWhitelist PrintingAPIExtensionsAllowlist
AllowNativeNotifications AllowSystemNotifications
DeviceUserWhitelist DeviceUserAllowlist
NativeWindowOcclusionEnabled WindowOcclusionEnabled
 

If you're managing Chrome via the Google Admin Console (for example, Chrome Browser Cloud Management), no action is required; the Google Admin Console will manage the transition automatically.
 

Upcoming Admin Console changes

 
  • Sending Extension Requests for Chrome Browser and Chrome OS

    As an admin, you can block users from installing extensions and the Chrome Web Store will now have a “Request” button so that you can see their requests from within the Admin Console and take an action to allow or to block the extensions.

     
  • Sending Remote Commands for Chrome Desktop

    As an admin, you can use your Google Admin console to remotely send actions to managed Chrome Desktop Browsers (Win/Mac/Linux). For example, you will be able to delete browser cache or cookies remotely.

     
 
Chrome 89

Chrome Browser updates

 
  • Single words will not be treated as intranet locations by default

    By default, Chrome will improve user privacy and will reduce load on DNS servers by avoiding DNS lookups for single keywords entered into the address bar. This change may interfere with enterprises that use single-word domains in their intranet. That is, a user typing helpdesk will no longer be directed to https://helpdesk/.

    You will be able to control the behavior of Chrome using the IntranetRedirectBehavior enterprise policy, including preserving the existing behavior (value 3: Allow DNS interception checks and did-you-mean http://intranetsite/ infobars.).

    Some users saw this change in Chrome 88; a full rollout is planned in Chrome 89.

  • Chrome will prefer https to http when not specified in the address bar

    When a user types an address into the address bar without specifying the protocol, Chrome will attempt to navigate using https first, then fallback to http if https is not available. For example, if the user navigates to example.com, Chrome will first attempt to navigate to https://example.com, then will fallback to http://example.com if required.

    Some users on Windows, Mac, Linux, and Android will see this change in Chrome 89, and all users should see this change in Chrome 90.

  • Users can search open tabs

    Users can search for open tabs across windows, as shown in this screenshot:

  • Enterprise realtime URL checking enabled by BeyondCorp Enterprise

    Chrome 89 will introduce new security capabilities enabled by BeyondCorp Enterprise allowing checking URLs for phishing attacks in realtime for BeyondCorp Enterprise customers.

  • Chrome profiles for separating users or accounts

    Chrome will add new features to help different users keep their browsing data like bookmarks, history, and settings separate.

    Users will be given the option to create a new Chrome profile and move their account over, when they sign in to a profile where another account is already signed in.

    If a user signs in with an account that is already signed in to another profile, they will be offered the option to switch. Users who have multiple profiles set up will see a profile picker on startup. 

    You can control whether Chrome offers to create or switch profiles with the SigninInterceptionEnabled enterprise policy and ProfilePickerOnStartupAvailability enterprise policies.
  • Certain features will be available to users who have signed in without having to enable Chrome Sync 

    Some users who have signed into Chrome may be able to access and save payment methods and passwords stored in their Google Account without Chrome Sync being enabled.

    You can control users' access to payment methods on Chrome on Android using the AutofillCreditCardEnabled enterprise policy. You can control access to passwords on Chrome on desktop by either setting the SyncDisabled enterprise policy to disabled, or by including passwords in SyncTypesListDisabled.
     
  • Chrome on Android will require the device to be certified

    Chrome on Android will only be able to run on devices that are Play Protect certified. This will affect all instances of Chrome including PWAs, but does not include WebView.

    Chrome on VMs and emulators will continue to work if an emulator is emulating an approved device or the emulator is Google-developed.

    See the Android Help Center article for details on how to verify a device’s certification status.  
     
  • Version pinning for self-hosted extensions & apps

    To increase the stability in high-reliability environments, Chrome 89 will facilitate the pinning of extensions and apps to a specific version. Administrators can self-host the extension or app of their choice, and instruct Chrome to use the update URL from the extension forcelist instead of the extension manifest. This will be via a new boolean parameter in ExtensionSettings policy. As a result, extensions & apps will not be updated via the updateURL that was originally configured in their manifest, and will stay on one specific version.  
     
  • Chrome introduces privacy-preserving APIs to replace some of the functionality of third-party cookies

    Several changes are coming in Chrome 89 to build a more private web. We originally announced these changes in the Chromium Blog.

    FLoC, an interest-based targeting API will be introduced as an origin trial. This API will allow working with cohorts—groups of users with similar interests. Users cannot be individually identified.

    An event-level conversion API will continue in the origin-trial stage for Chrome 89. This API will enable the correlation of an ad click on a website with a subsequent conversion on an advertiser site (a sale, a sign-up, etc). Users cannot be individually identified.

    Platform-provided trust tokens will be introduced to the ongoing Trust Token API Origin Trial. This experiment will be used to ascertain the value of tokens incorporating on-device state as a mechanism for anti-spam and anti-abuse systems, and to evaluate the feature’s performance relative to standard web-issued trust tokens. 

    First party sets will be introduced as an origin trial. This will allow a collection of related, commonly-owned domains to declare themselves as a first party set, so that browsers can consider this relationship when applying cross-site communication policies. 

    Schemeful Same-Site, which evolves the definition of same-site to include the URL scheme, will be fully rolled out and available to all audiences.

    User Agent Client Hints will also be fully rolled out and available to all audiences.

    See the chromium privacy sandbox page for details on these APIs and the privacy sandbox.
     
  • Chrome will require SSE3 for Chrome on x86

    Chrome 89 and above will require x86 processors with SSE3 support. This change does not impact devices with non-x86 (ARM) processors. Chrome will not install and run on x86 processors that do not support SSE3. SSE3 was introduced on Intel CPUs in 2003, and on AMD CPUs in 2005.

  • Chrome introduces BrowsingDataLifetime and ClearBrowsingDataOnExitList policies

    Chrome will give you more control over data in your environment by introducing two policies that clear browsing data after a specified amount of time, or once Chrome has been closed: BrowsingDataLifetime and ClearBrowsingDataOnExitList. These policies will be useful for customers that have strict regulatory requirements around data being stored on client devices.

  • Metrics reporting can be disabled by the user even if admin has it turned on

    To improve user privacy, end users will be able to turn off metrics reporting for themselves, even if you have set MetricsReportingEnabled to true. If you set MetricsReportingEnabled to false, users will not be able to enable metrics.

  • Chrome introduces the Serial API

    The Serial API will provide a way for websites to read and write from a serial device through script. You can read an explainer on the Serial API here.

    You will be able to control access to the Serial API using the DefaultSerialGuardSetting policy. You can also use the SerialAskForUrls and SerialBlockedForUrls policies to control serial device access on a site-by-site basis.

  • Chrome on iOS introduces biometric authentication for Incognito tabs

    Users will have a setting to enable access control for their Incognito tabs. When this setting is turned on, users will be prompted to re-authenticate themselves with biometric authentication when they return to Incognito tabs after closing Chrome on iOS.

Chrome OS updates

 
  • Extended auto-update blockout windows 

    Already as of today, the Chrome OS auto update blockout window device policy allows admins to block updates for their kiosk devices during certain business hours. This helps to save bandwidth in cases where Chromebooks are located at sites with limited network connectivity. From Chrome 89 on (official launch March 9th, 2021), the auto update blockout window policy will be extended. (1) Instead of only applying to kiosk sessions, it will also apply to user sessions & managed guest sessions (MGS). (2) Instead of only influencing the start of an update download, it will also pause previously started updates during blockout windows.

    Due to the extended impact of the auto-update blockout window policy, an adjustment of your policy settings might be required to guarantee continuous updates of your devices.

  • Scaled Print Server Support 

    Admins will be able to assign any number of IPP based print servers to be remotely configured from the admin console. Users will select a specific print server to connect to if the user has more than 16 print servers assigned. If there are less than 16 configured, Chrome OS will automatically query all assigned print servers simultaneously.

  • Scanning support

    Chrome OS will support the scanning functionality of compatible multifunction printers. Access to the Scan app on Chrome OS can be controlled by Admins.
     
  • QR code scanning support

    You can now scan QR codes with the Chrome OS Camera app. Just point your camera at a QR code and the results will automatically be scanned.

  • Switch Access settings Improvements

    Switch Access settings will allow you to use any key or external switch and will make setting up your switches easier by replacing the drop down menu with just pressing the switch you want to use. 
  • Enhanced Screen Capture

    Chrome OS screen capture just got better. Screen capture functionality is now always accessible via quick settings. A new capture mode provides users with an intuitive UI to switch between functionality. After taking a partial screenshot, you can adjust the selection to perfect your capture. New screen recording functionality lets you capture and share motion.


     
  • Desk improvements

    Improvements for frictionless smart creation and management of multiple workspaces (restore desks for browser, send to desk, and virtual desk improvements).
     
  • Wi-Fi Sync improvements

    Wi-Fi Sync is now even more powerful, with added support for Wi-Fi network sharing between Chrome OS and Android.
     
  • Clipboard: visual clipboard history

    Chrome OS introduces an extended clipboard to quickly transfer multiple pieces of content. Transfer everything you need with speed and ease.
     
  • Tote: quick access to recent and important Files

    Quickly access your recent screenshots and downloads. Pin your important Files to launch, copy, or drag with one click.
     
  • Improved Media Controls

    Brings unified media controls to quick settings. Access all your media sources in one place quickly.
     
  • App icon refresh

    The icons for the built-in apps on your Chromebook have a fresh new look, making it easier for you to distinguish between the core essential apps (for example, Canvas, Explore) that are made for Chrome OS and third-party apps that you’ve downloaded.
     
  • Enhanced Select-to-speak to better support users with Dyslexia

    Improve the Select-to-speak accessibility service with navigation controls (play/pause, navigate sentences and paragraphs, adjust speed in context).


     

Admin console updates

 
  • Apps & Extension Usage Report

    The Apps & Extension Usage Report report will allow admins to get a comprehensive view of the apps and extensions installed across their fleet of ChromeOS and Chrome Desktop devices.  Refer to the View app and extension usage details article on how to enable it. 
     
  • Reports API

    The Reports API will allow you to generate reports that give you aggregate information on your managed Chrome OS device / Chrome Browser deployment.  Please see the documentation here on how to use it. 
     
  • Additional policies in the Admin console

    Many new policies will be available in the Admin console, including:
Policy Name Pages Supported on Category/Field
NTPContentSuggestionsEnabled User & Browser Settings Android Startup / New Tab page content suggestions
RestrictAccountsToPatterns User & Browser Settings Android User experience / Visible Accounts / Restrict accounts that are visible in Chrome to those matching one of the patterns specified
MediaRecommendationsEnabled User & Browser Settings Chrome OS, Windows, Mac, Linux User experience / Media Recommendations
AllowFileSelectionDialogs User & Browser Settings Windows, Mac, Linux User experience / File selection dialogs
AllowWakeLocks User & Browser Settings; Managed Guest Session Settings Chrome OS Power and shutdown / Wake locks
IntranetRedirectBehavior User & Browser Settings; Managed Guest Session Settings Chrome OS, Windows, Mac, Linux Network / Intranet Redirection Behavior

 

  • New and updated policies (Chrome Browser and Chrome OS)

 

Policy Description

BrowsingDataLifetime

Browsing Data Lifetime Settings

ClearBrowsingDataOnExitList

Clear Browsing Data on Exit

EnableDeprecatedPrivetPrinting

Enable deprecated privet printing

ManagedConfigurationPerOrigin

Sets managed configuration values to websites to specific origins

PhoneHubTaskContinuationAllowed

Chrome OS only

Allow Phone Hub task continuation to be enabled

PhoneHubAllowed

Chrome OS only

Allow Phone Hub to be enabled

PhoneHubNotificationsAllowed

Chrome OS only

Allow Phone Hub notifications to be enabled

ProfilePickerOnStartupAvailability

Browser only

Profile picker availability on startup

RemoteAccessHostAllowRemoteAccessConnections

Browser only

Allow remote access connections to this machine

RemoteAccessHostMaximumSessionDurationMinutes

Browser only

Maximum session duration allowed for remote access connections

SigninInterceptionEnabled

Browser only

Enable signin interception

Coming soon

 

Note: The items listed below are experimental or planned updates. They might change, be delayed, or canceled before launching to the Stable channel.

  • Chrome will move to a 4-week stable channel and will introduce an 8-week extended stable channel as early as Chrome 94

    Chrome on mobile, Windows, Mac, and Linux will move from its current 6-week release cycle to a 4-week release cycle, allowing security features, new functionality and bug fixes to reach users more quickly.

    No action will be required for most enterprises, but if you manually update or test new releases of Chrome and prefer a slower release cadence, you'll be able to switch Chrome to an extended stable channel, with a new release every 8 weeks instead. More details can be found on our blog post at blog.chromium.org

    Chrome OS is also planning changes to the release cycle during the same release. As always, Chrome OS will prioritize the latest security updates, and maintain a high quality and stable experience for users, customers, partners, and developers.

Upcoming Chrome Browser changes

 
  • Chrome 90 will block port 554

    Port 554 will be added to the restricted ports list and traffic through it will be blocked. This should have no effect on customers using standard ports, but custom configurations (for example, delivering PAC scripts) using non-standard ports may be affected. You should instead use standard ports for your use case (for example, delivering PAC scripts via HTTPS through port 443).
     
  • Launch of PDF XFA forms in Chrome 90

    PDF XFA forms will be partially supported in Chrome 90, expanding the range of PDF documents that can open directly in Chrome.
     
  • Managed profile sign-in popup will be more clear in Chrome 90

    Chrome 90 will update the notice when users sign into a managed profile. The new notice will have more clear language and the available actions will be simplified.
     
  • Some permission requests will be less intrusive in Chrome 90

    Permission requests that the user is unlikely to allow will be automatically blocked. A less intrusive UI will allow the user to manage permissions for each site.

     
  • Chrome 90 will support Intel CET

    Chrome 90 will support Intel’s Control Flow Enforcement Technology (CET), known as Hardware-enforced Shadow Stacks on Windows. This will only affect Chrome running on hardware that supports CET. While no issues are expected, you can manage CET by manipulating Image File Execution Options (IFEO) through group policy.
     
  • Chrome 90 will introduce initial_preferences

    As part of Chrome's move to using more inclusive naming, Chrome will support an admin using a file to control the browser's initial preferences, named initial_preferences. This file will behave the same way as, and will eventually replace the master_preferences file that exists today. To minimize any disruption, master_preferences will continue to be supported in Chrome 90 and more notice will be given before support for master_preferences is removed.
     
  • AllowNativeNotifications updated to AllowSystemNotifications in Chrome 90

    As part of Chrome's move to using more inclusive policy names, AllowNativeNotifications will be renamed to AllowSystemNotifications. The existing AllowNativeNotifications policy will be available until Chrome 95.
     
  • Extension settings will load from the same place for all channels on Mac in Chrome 90

    All Chrome channels will read the extension policies from the same .plist file. For example, the extension Password Alert will always load its policies from com.google.Chrome.extensions.noondiphcddnnabmjcihcjfbhfklnnep.plist instead of com.google.Chrome.canary.extensions.noondiphcddnnabmjcihcjfbhfklnnep.plist in Chrome Canary.
     
  • Chrome will save data with Lite videos in Chrome 90

    To reduce the data-cost and improve the experience of videos on metered and limited data connections, Chrome on Android will reduce the effective bitrate of videos for Lite mode users on cellular connection. You will be able to control this feature using the DataCompressionProxyEnabled policy.
     
  • Data Saver: Chrome will compress public HTTPS images in Chrome 90

    Public HTTPS images will be compressed when Chrome lite mode is enabled, to further provide a rich web experience to users with unreliable internet connections.
     
  • Security key enterprise attestation in Chrome 90

    Chrome will support device-unique attestation of security keys without needing policy configured. This will be useful in situations where security keys are distributed by an enterprise to personnel who may use them on non-policy-managed computers. This will require specially-manufactured security keys—talk to your security key vendor if this sounds useful.
     
  • Launch WebXR capability - Depth Sensing API in Chrome 90

    The WebXR Depth Sensing API will allow Chrome to measure distance from the user’s device to real world geometry in the user’s environment. With this, Chrome will be able to power immersive experiences in WebXR-powered apps (e.g. for physics, and lifelike occlusion for augmented reality). You will be able to control access to WebXR and other augmented reality APIs using the WebXRImmersiveArEnabled enterprise policy.
     
  • Partition Network State in Chrome 90

    Today, some network objects are shared globally for performance reasons, but this makes it possible to fingerprint users and track them across sites. To protect user privacy, Chrome will partition many network objects by topmost frame domain and iframe domain. A comprehensive description is available here.

    No impact is expected other than minor performance changes, but you can test the change in advance by using the command line flag: 
    --enable-features=PartitionConnectionsByNetworkIsolationKey,PartitionExpectCTStateByNetworkIsolationKey,PartitionHttpServerPropertiesByNetworkIsolationKey,PartitionNelAndReportingByNetworkIsolationKey,PartitionSSLSessionsByNetworkIsolationKey,SplitHostCacheByNetworkIsolationKey
     
  • Legacy Browser Support for Edge in IE Mode will be available in Chrome 90

    For organizations accessing legacy web content in Microsoft Edge's IE mode, Chrome 90 will allow admins to configure Legacy Browser Support (LBS) to switch between Microsoft Edge in IE mode and Chrome. You can already use LBS to switch directly between Microsoft Internet Explorer and Chrome.
     
  • The Network Service on Windows will be sandboxed in Chrome 91

    The network service, already running in its own process, will be sandboxed on Windows in Chrome 90 to improve the security and reliability of the service. As part of this, third party code that is currently able to tamper with the Network Service will be prevented from doing so. This may cause problems when connecting to software such as:
    • Custom Authentication Packages.
    • Custom SSO (Single Sign-on) providers.
    • Custom Winsock Namespace/transport providers.
    • Data Loss Prevention software.
    • NTLM with Windows integrated authentication.

    Enterprises are encouraged to try the sandboxed network stack on Dev and Canary channel and report any issues via crbug.com. You'll be able to disable the change with an enterprise policy when it becomes available.
     
  • Lock in address bar will be replaced in Chrome 91

    The lock in the address bar will be replaced with a new icon. Chrome is moving to security messaging that highlights known security issues, and shows neutral messaging otherwise. Showing an icon that implies safety based solely on the connection's encryption may lead to a false sense of security.
     
  • Quantum computer resistant security will be enabled in Chrome 91

    Chrome will start supporting a post-quantum key-agreement mechanism in TLS when communicating with some domains. This increases the size of TLS handshake messages which, in rare cases, may cause issues with network middleboxes that incorrectly assume that TLS messages will fit in a single network frame.
    The CECPQ2Enabled policy can be set to disable this. It will also be disabled if the ChromeVariations policy is set to a non-default value.

    For more details on this rollout, see CECPQ2
     
  • Insecure public pages will no longer be allowed to make requests to private or local URLs in Chrome 91

    Insecure pages will no longer be able to make requests to IPs belonging to a more private address space (as defined in CORS-RFC1918). For example, http://public.page.example.com will not be able to make requests targeting IP 192.168.0.1 or IP 127.0.0.1. You will be able to control this behavior using the InsecurePrivateNetworkRequestsAllowed and InsecurePrivateNetworkRequestsAllowedForUrls enterprise policies.
     
  • The address bar may show the domain rather than the full URL as early as Chrome 90

    To protect your users from some common phishing strategies, Chrome will test showing only the domain in the address bar for some users. This change will make it more difficult for malicious actors to trick users with misleading URLs. For example, https://example.com/secure-google-sign-in/ will appear only as example.com to the user.

    Although this change is designed to keep your users’ credentials safe, you can revert to the old behavior through the ShowFullUrlsInAddressBar policy.

    This change has been enabled for some users, with a potential full rollout in a later release.
     
  • The SSLVersionMin policy will not allow TLS 1.0 or TLS 1.1 in Chrome 91

    The SSLVersionMin enterprise policy will allow you to bypass Chrome's interstitial warnings for legacy versions of TLS. This will be possible until Chrome 91 (May 2021), then the policy will no longer allow TLS 1.0 or TLS 1.1 to be set as the minimum.

    We previously communicated that this would happen as early as January 2021, but the deadline has since been extended.
     
  • Chrome will maintain its own default root store as early as Chrome 92

    In order to improve user security, and provide a consistent experience across different platforms, Chrome intends to maintain its own default root store. If you are an enterprise admin managing your own certificate authority, you should not have to manage multiple root stores.We do not anticipate any changes to be required for how enterprises currently manage their fleet and trusted enterprise CAs, such as through group policy, macOS Keychain Access, or system management tools like Puppet.
     
  • SyncXHR policy will no longer be supported on Chrome 93

    The AllowSyncXHRInPageDismissal enterprise policy will be removed in Chrome 93. For any apps that rely on the legacy web platform behavior, be sure to update them before Chrome 93. This change was previously planned for Chrome 88, but delayed to provide more time for enterprises to update legacy applications.
     
  • Old policies with non-inclusive names will be removed in Chrome 95

    Chrome 86 through Chrome 90 introduced new policies to replace policies with less inclusive names (e.g. whitelist, blacklist). In order to minimize disruption for existing managed users, both the old and the new policies currently work. This transition time is to ensure it's easy for you to move to and test the new policies in Chrome.

    This transition period will end in Chrome 95. A full list of the policies to be removed will be provided closer to the removal date. If you're managing Chrome via the Google Admin Console (for example, Chrome Browser Cloud Management), no action is required; the Google Admin Console will manage the transition automatically.
     

Upcoming Chrome OS changes

 
  • Deprecation of AMR and GSM audio codecs in Chrome OS 90

    AMR-NB, AMR-WB, and GSM audio codecs will be deprecated as part of this release. Affected users should file bugs here and may temporarily rollback this change via the use of chrome://flags/#deprecate-low-usage-codecs. Users with long-term need for these codecs may use stand-alone applications found in the Google Play Store.

Upcoming Admin Console changes

 
  • Sending Extension Requests for Chrome Browser and Chrome OS

    As an admin, you can block users from installing extensions and the Chrome Web Store will now have a Request button so that you can see their requests from within the Admin Console and take an action to allow or to block the extensions.
     
  • Sending Remote Commands for Chrome Desktop

    As an admin, you can use your Google Admin console to remotely send actions to managed Chrome Desktop Browsers (Win/Mac/Linux). For example, you will be able to delete browser cache or cookies remotely.
 
Chrome 88

Chrome Browser updates

  • Chrome will warn about mixed content forms
    Web forms that load using HTTPS but submit their content using HTTP (unsecured) pose potential risk to user privacy. Chrome 85 and above shows a warning on such forms, letting the user know that the form is insecure. Chrome 88 will show an interstitial warning when the form is submitted, which stops any data transmission, so the user will be able to choose whether to proceed or cancel the submission. This was previously rolled out in Chrome 87 but was rolled back due to the way it interacted with redirects. It is being rolled out again in Chrome 88, but will only show warnings for forms that either submit directly to an http:// URL, or when a redirect to an http:// happens and the form data is exposed across the redirect. For example, 307 or 308 code redirects for POST method forms.





    You will be able to control this behavior using the InsecureFormsWarningsEnabled enterprise policy. To test this behavior before the rollout, use the Mixed Forms Interstitial Chrome flag.
     
  • Improved resource consumption for background tabs
    To save on CPU load and prolong battery life, Chrome will limit the power consumption of background tabs. Specifically, Chrome will allow the timers in the background tabs to only run once per minute. Network event handlers are not affected, which allows sites like Gmail or Slack® to continue delivering timely notifications in the background. Some users saw this feature in Chrome 87. It's now available to all users in Chrome 88.

    You will be able to control this behavior using the IntensiveWakeUpThrottlingEnabled policy.
     
  • Insecure downloads are blocked from secure pages, with changes through Chrome 88
    In Chrome 88 on Windows®, Mac®, and Linux®, downloads from insecure sources will no longer be allowed when started from secure pages. This change has been rolled out gradually, with different file types affected in different releases:

     

  • Executables—Users were warned in Chrome 84, and files were blocked in Chrome 85.
  • Archives—Users were warned in the Chrome developer console in Chrome 85, and files were blocked in Chrome 86.
  • Other non-safe types, for example, PDFs—Users were warned in the Chrome developer console in Chrome 86, and files were blocked in Chrome 87.
  • Other files—Users were warned in the Chrome developer console in Chrome 87, and files will be blocked in Chrome 88.

    Warnings on Android will lag behind desktop warnings by one release. For example, executables showed a warning starting in Chrome 85.

    The existing InsecureContentAllowedForUrls policy can be used to allow specific URLs to download insecure files. You can read more details in our blog post.
  • The new tab page allows users to complete previously started workflows
    The Chrome new tab page will show cards to help users return to searches and workflows that were already in progress, like searching for recipes or price comparisons. Users are able to control and remove these cards.

    These cards appeared for some users in Chrome 87, and are now included in Chrome 88. You can control these cards using the NTPCardsVisible policy. 
     
  • Chrome introduces profiles for separating users or accounts
    Some users will be given the option to create a new Chrome profile and move their account over when they sign in to a profile where another account is already signed in. This allows different users to keep bookmarks, history, and settings separate. If a user signs in with an account that is already signed in to another profile, they’re offered to switch. Some users who have multiple profiles set up will see a profile picker on startup.

    You can control whether Chrome offers to create or switch profiles with the SigninInterceptionEnabled enterprise policy. In Chrome 89, you'll also be able to control the startup behavior for the profile picker with the ProfilePickerOnStartupAvailability enterprise policy.


    A wider release to more users is planned for a later release

  • Certain features are available to users who have signed in without having to enable Chrome Sync 
    Some users who have signed into Chrome might be able to access and save payment methods and passwords stored in their Google Account without Chrome Sync being enabled.

    On Chrome on Android, you can control a user's access to payment methods using the AutofillCreditCardEnabled enterprise policy. You can control access to passwords on Chrome on desktop by either setting the SyncDisabled enterprise policy to disabled, or by including "passwords" in SyncTypesListDisabled.
     
  • DTLS 1.0 has been removed
    DTLS 1.0, a protocol used in WebRTC for interactive audio and video, has been removed by default. Any applications that depend on DTLS 1.0 (most likely gateways to other teleconferencing systems) should update to a more recent protocol. You can test if any of your applications will be impacted by using the following command line flag when launching Chrome:

    --force-fieldtrials=WebRTC-LegacyTlsProtocols/Disabled/ 

    If your enterprise needs additional time to adjust, the WebRtcAllowLegacyTLSProtocols enterprise policy will be made available to temporarily extend the removal.
     
  • Chrome supports manifest v3
    Chrome 88 supports extensions written in the new Manifest V3 format. Manifest V3 is a new platform that makes extensions more secure, performant, and privacy-respecting by default. There is no breaking change at this time; extensions using Manifest v2 will continue to function normally in Chrome 88.
     
  • Chrome is launching an origin trial for detecting idle state
    An early origin trial allows websites to request the ability to query if users are idle, allowing messaging apps to direct notifications to the best device.
     
  • Single words are no longer being treated as intranet locations by default

    By default, Chrome improves user privacy and reduces load on DNS servers by avoiding DNS lookups for single keywords entered into the address bar. This change may interfere with enterprises that use single-word domains in their intranet. For example, a user typing "helpdesk" will no longer be directed to "https://helpdesk/".

    You can control the behavior of Chrome using the IntranetRedirectBehavior enterprise policy, including preserving the existing behavior (value 3: Allow DNS interception checks and did-you-mean "http://intranetsite/" infobars.).
  • Chrome introduces a new permission chip UI
    Permission requests can feel disruptive and intrusive when they lack context – which often happens when prompts appear as soon as a page loads or without prior priming. This leads to a common reaction where end users dismiss the prompt in order to avoid making a decision.

    Chrome now shows a less intrusive permissions chip in the address bar. Since the prompt doesn't intrude in the content area, users who don't want to grant the permission no longer need to actively dismiss the prompt. Users who wish to grant permission can click on the chip to bring up the permission prompt.




    This change will be rolled out gradually throughout Chrome 88.
     
  • The Legacy Browser Support extension has been removed from the Chrome Web Store
    Legacy Browser Support (LBS) is built into Chrome, and the old extension is no longer needed. The Chrome team unpublished LBS from the Chrome Web Store in Chrome 85, and it is disabled in Chrome 88. Legacy Browser Support will still be supported, please migrate away from the extension and towards using Chrome's built-in policies, documented here. The old policies set through the extension will no longer function, and you won't be able to force install the extension once it's been disabled.
     
  • Factor in scheme when determining if a request is cross-site (Schemeful Same-Site)
    Chrome 88 modifies the definition of same-site for cookies such that requests on the same registrable domain but across schemes will be considered cross-site instead of same-site. For example, http://site.example and https://site.example will be considered cross-site to each other which will restrict cookies using SameSite. For additional information please see the Schemeful Same-Site explainer. We recommend testing critical sites using the testing instructions.

    You may revert to the previous, legacy behavior, by using the LegacySameSiteCookieBehaviorEnabledForDomainList and LegacySameSiteCookieBehaviorEnabled policies. These policies will be available at least until Chrome 93, with the domain list planned to be available longer. For more details, including availability, please see Cookie Legacy SameSite Policies.
     
  • Chrome 88 on Mac does not support OS X 10.10 (Yosemite)
    Chrome 88 does not support OS X 10.10 (OS X Yosemite). Chrome on Mac requires OS X 10.11 or later.
     
  • Popup on page unload policy is no longer supported on Chrome 88
    The AllowPopupsDuringPageUnload enterprise policies have been removed in Chrome 88, as previously communicated. For any apps that rely on the legacy web platform behavior, be sure to update them immediately.
     
  • Chrome treats an empty string as an unset policy on Android for some policies in Chrome 88
    To integrate better with mobile management UEMs, Chrome on Android will not set list or dictionary policies from empty strings.
     
  • The BasicAuthOverHttpEnabled policy allows you to disable authentication over HTTP
    You can set the new BasicAuthOverHttpEnabled policy to disabled to disallow non-secure HTTP requests from using the Basic authentication scheme. If you do, only secure HTTPS will be allowed.

  • The Chrome Cleanup Tool can reset Chrome shortcuts
    When users run the Chrome Cleanup Tool, it will modify command line flags within Chrome shortcuts. This helps users restore Chrome to a safe state if malware has inserted malicious command line flags into the shortcut.

    You can control the Chrome Cleanup Tool using the ChromeCleanupEnabled policy, which will prevent this behavior.
     
  • Notifications will be suspended while presenting
    While Chrome is sharing a screen, web-notifications from Chrome will not show their content by default. They will be presented to the user after the screen sharing session ends or by manually revealing them via a notification action. Note that sharing a single window or tab does not affect the delivery of notifications from Chrome.
     
  • The microphone is visible beside the address bar for some users on Android
    The microphone button is visible in the top UI bar of Chrome for some users on Android. Users can to ask the Google Assistant to read the current page, or translate it to another language.

    When users interact with the microphone button, the URL of the current page is shared with Google. You can control this feature using the AudioCaptureAllowed policy.
     
  • Cloud Print is no longer supported
    The Google Cloud Print service is no longer supported on any Operating Systems.

    Chrome OS admins can select a print solution provider or migrate to the Chrome OS local and network printer solution. Admins of Windows®, Mac®, and Linux® operating systems can use the respective OS print workflow or engage with a print solution provider. Learn more about Cloud Print migration
     
  • Save to Drive is no longer supported
    Saving to Google Drive is no longer available from the Chrome print dialog on Mac®, Windows®, Linux® devices. Users can instead install the Save to Drive Chrome extension which has been updated to include this feature or print locally to PDF then upload the file to Google Drive through drive.google.com and select New > File upload. You can also set up automatic syncing between local files and Google Drive with Backup and Sync or Drive File Stream. More details on printing from Chrome are available here
     
  • FTP support has been removed
    Chrome 88 has removed support for FTP URLs. The legacy FTP implementation in Chrome no longer supports encrypted connections (FTPS), or proxies. Usage of FTP is very low, and more capable FTP clients are available on all affected platforms.

    More information is available here.

Chrome OS updates

  • WebAuthn using Fingerprint & PIN
    Tired of typing long passwords? Chrome OS now lets you sign in to supported websites without having to type your passwords for that website, if you have set up a PIN or fingerprint on your Chromebook. This feature, called Web Authentication, makes use of established protocols to make authentication into website simpler and more secure. Your Chromebook PIN/fingerprint are never shared with the websites requesting verification from your Chromebook and you don't have to worry about malicious attackers phishing for your passwords to websites.  If your organization has U2F enabled, the Webauthn feature will not work; U2F will be supported in a future release.
     
  • Autocorrect UI improvements
    For users with autocorrect enabled, we have improved the user interface with visual indications that autocorrects have happened, as well as new ways to undo them.
     
  • Magnifier Focus Following and Keyboard Support
    Chrome OS Magnifier can now be panned using the keyboard. Use Ctrl + Alt and the arrow key to pan the viewport.



     
  • Text app Screen Reader mode
    Text app now has a screen reader mode to support Chromevox users.
     
  • Improved switching between virtual desks
    Switching between virtual desks with the keyboard and touchpad is now faster and more responsive. You can double or triple tap the <Search> + [ or <Search> + ] shortcut to move between multiple desks.
     
  • Reverse Scrolling + Touchpad gesture consistency
    Touchpad gestures are now more consistent with your preference for Reverse Scrolling.
     
  • Chrome OS Camera now saves to a new location
    Photos and videos captured with the Chrome OS Camera app will now get saved to a new Camera folder under My files. Any previously captured photos/videos will remain in your Downloads folder.

Admin console updates

  • API for remote commands
    The Admin SDK Directory API now supports issuing remote commands to devices, including wipe users, remote powerwash, remote reboot (kiosk only), screenshot (kiosk only), and set volume (kiosk only). See the developer documentation for details.
     
  • Filter Chrome devices by version
    The Chrome device list now supports filtering by Chrome version.  Now you can quickly check which devices are up to date or out of date.
     
  • Bookmark Management improvements
    Admin Console has a new and improved bookmarks manager.  Enterprise admins can more easily create, delete, and move around hundreds or even thousands of bookmarks.  Details on the feature are described in the help center article.
     
  • New summary report for Chrome versions
    Admin Console has a new version report that shows the number of managed browsers and devices on each Chrome version.  Details on the feature are described in the help center article.
     
  • Group-based policy for printer management
    Group-based management is now available for printers. From the printers page, select a group, and then configure which printers are available to users in that group.
     
  • Kerberos credential manager
    As an admin, you can now enable Kerberos tickets on Chrome devices to enable single sign-on (SSO) for internal resources that support Kerberos authentication. Internal resources might include websites, file shares, certificates, and so on. Details on the feature are described in the help center article.

Additional policies in the Admin console

Many new policies are available in the Admin console, including:

Policy name Pages Category/Field
AbusiveExperienceInterventionEnforce

User & Browser Settingsand then
Managed Guest Session Settings

Chrome Safe Browsing / Abusive Experience Intervention
AccessibilityImageLabelsEnabled User & Browser Settingsand then
Managed Guest Session Settings
Accessibility / Image descriptions
AdsSettingForIntrusiveAdsSites User & Browser Settingsand then
Managed Guest Session Settings
Chrome Safe Browsing / Sites with intrusive ads
AdvancedProtectionAllowed User & Browser Settings Security / Advanced Protection program
AuthAndroidNegotiateAccountType User & Browser Settings Network / Account type for HTTP Negotiate authentication / Account type
AutoOpenAllowedForURLs User & Browser Settingsand then
Managed Guest Session Settings
Content / Auto open downloaded files / Auto open URLs
AutoOpenFileTypes User & Browser Settingsand then
Managed Guest Session Settings
Content / Auto open downloaded files / Auto open files types
BackForwardCacheEnabled User & Browser Settings Content / Back-forward cache
BrowserNetworkTimeQueriesEnabled User & Browser Settings Other settings / Google time service
CACertificateManagementAllowed User & Browser Settings Security / User management of installed CA certificates
ClientCertificateManagementAllowed User & Browser Settings Security / User management of installed client certificates.
CommandLineFlagSecurity
WarningsEnabled
User & Browser Settings Security / Command-line flags
ContextualSearchEnabled User & Browser Settings User experience / Touch to search
DefaultFileSystemReadGuardSetting User & Browser Settingsand then
Managed Guest Session Settings
Hardware / File system read access
DefaultFileSystemWriteGuardSetting User & Browser Settingsand then
Managed Guest Session Settings
Hardware / File system write access
DefaultSerialGuardSetting User & Browser Settingsand then
Managed Guest Session Settings
Hardware / Serial Port API / Control use of the Serial Port API
DefaultWebUsbGuardSetting User & Browser Settingsand then
Managed Guest Session Settings
Hardware / WebUSB API / Can web sites ask for access to connected USB devices
DeviceAllowRedeemChromeOs
RegistrationOffers
Device Settings Other settings / Redeem offers through Chrome OS registration
DeviceQuirksDownloadEnabled Device Settings Other settings / Hardware profiles
DeviceShowLowDiskSpaceNotification Device Settings Other settings / Low disk space notification
DeviceWebBasedAttestation
AllowedUrls
Device Settings Sign-in settings / Single sign-on verified access / Allowed IdP redirect URLs
DNSInterceptionChecksEnabled User & Browser Settingsand then
Managed Guest Session Settings
Network / DNS interception checks enabled
ExtensionCacheSize Device Settings Other settings / Apps and extensions cache size / Cache size in bytes
ExternalProtocolDialogShow
AlwaysOpenCheckbox
User & Browser Settings Content / Show "Always open" checkbox in external protocol dialog
FileSystemReadAskForUrls User & Browser Settingsand then
Managed Guest Session Settings
Hardware / File system read access / Allow file system read access on these sites
FileSystemReadBlockedForUrls User & Browser Settingsand then
Managed Guest Session Settings
Hardware / File system read access / Block read access on these sites
FileSystemWriteAskForUrls User & Browser Settingsand then
Managed Guest Session Settings
Hardware / File system write access / Allow write access to files and directories on these sites
FileSystemWriteBlockedForUrls User & Browser Settingsand then
Managed Guest Session Settings
Hardware / File system write access / Block write access to files and directories on these sites
GloballyScopeHTTPAuthCacheEnabled User & Browser Settingsand then
Managed Guest Session Settings
Network / Globally scoped HTTP authentication cache
GSSAPILibraryName User & Browser Settings Network / GSSAPI library name / Library name or full path
HSTSPolicyBypassList User & Browser Settingsand then
Managed Guest Session Settings
Network / HSTS policy bypass list / List of hostnames that will bypass the HSTS policy check
InsecureFormsWarningsEnabled User & Browser Settingsand then
Managed Guest Session Settings
Content / Insecure forms
KerberosAccounts User & Browser Settings Kerberos / Kerberos tickets
KerberosEnabled User & Browser Settings Kerberos / Kerberos tickets
LookalikeWarningAllowlistDomains User & Browser Settingsand then
Managed Guest Session Settings
Chrome Safe Browsing / Suppress lookalike domain warnings on domains / Allowlisted Domains
MaxConnectionsPerProxy User & Browser Settings Network / Max connections per proxy / Maximum number of concurrent connections to the proxy server
MaxInvalidationFetchDelay User & Browser Settingsand then
Managed Guest Session Settings
Other settings / Policy fetch delay / Maximum fetch delay after a policy invalidation
NativeMessagingAllowlist User & Browser Settings User experience / Native Messaging allowed hosts / Native Messaging hosts not subject to the blocklist
NativeMessagingBlocklist User & Browser Settings User experience / Native Messaging blocked hosts / Prohibited Native Messaging hosts
NativeMessagingUserLevelHosts User & Browser Settings User experience / Native Messaging user-level hosts
NtlmV2Enabled User & Browser Settings Network / NTLMv2 authentication
OverrideSecurityRestrictions
OnInsecureOrigin
User & Browser Settingsand then
Managed Guest Session Settings
Security / Override insecure origin restrictions / Origin or hostname patterns to ignore insecure origins security restrictions
PaymentMethodQueryEnabled User & Browser Settingsand then
Managed Guest Session Settings
User experience / Payment methods
PrinterTypeDenyList User & Browser Settingsand then
Managed Guest Session Settings
Printing / Blocked printer types
PrintRasterizationMode User & Browser Settings Printing / Print rasterization mode
RequireOnlineRevocationChecks
ForLocalAnchors
User & Browser Settingsand then
Managed Guest Session Settings
Network / Require online OCSP/CRL checks for local trust anchors

SafeBrowsingForTrusted
SourcesEnabled

User & Browser Settings Chrome Safe Browsing / Safe Browsing for trusted sources
ShowAppsShortcutInBookmarkBar User & Browser Settings User experience / Apps shortcut in the bookmark bar
SignedHTTPExchangeEnabled User & Browser Settingsand then
Managed Guest Session Settings
Network / Signed HTTP Exchange (SXG) support
SpellcheckEnabled User & Browser Settingsand then
Managed Guest Session Settings
User experience / Spell check
SuppressUnsupportedOSWarning User & Browser Settingsand then
Managed Guest Session Settings
Security / Unsupported system warning
UserFeedbackAllowed User & Browser Settingsand then
Managed Guest Session Settings
User experience / Allow user feedback
WebRtcLocalIpsAllowedUrls User & Browser Settings Network / WebRTC ICE candidate URLs for local IPs / URLs for which local IPs are exposed in WebRTC ICE candidates.
WebUsbAskForUrls User & Browser Settingsand then
Managed Guest Session Settings
Hardware / WebUSB API / Allow these sites to ask for USB access
WebUsbBlockedForUrls User & Browser Settingsand then
Managed Guest Session Settings
Hardware / WebUSB API / Block these sites from asking for USB access
WPADQuickCheckEnabled User & Browser Settingsand then
Managed Guest Session Settings
Network / WPAD optimization


New and updated policies (Chrome Browser and Chrome OS)

Policy Description
BasicAuthOverHttpEnabled Non-secure HTTP connections are not permitted to use Basic authentication; HTTPS is required
NTPCardsVisible Show cards on the New Tab Page

ProfilePickerOnStartupAvailability
Browser only

Specifies whether the profile picker is enabled, disabled or forced at the browser startup

SigninInterceptionEnabled
Browser only

This settings enables or disables sign in interception
TargetBlankImpliesNoOpener Do not set window.opener for links targeting _blank


Coming soon

Note: The items listed below are experimental or planned updates. They might change, be delayed, or canceled before launching to the Stable channel.


Upcoming Chrome Browser changes

  • Facilitated version pinning for self-hosted extensions & apps in Chrome 89

    To increase the stability in high-reliability environments, Chrome 89 facilitates the pinning of extensions and apps to a specific version. Administrators will be able to self-host the extension or app of their choice, and instruct Chrome to use the update URL from the extension forcelist instead of the extension manifest. This will be via a new boolean parameter in ExtensionSettings policy. As a result, extensions & apps will not be updated via the updateURL that was originally configured in their manifest, and will stay on one specific version.

  • Users will be able to search open tabs in Chrome 89
    Users will be able to search for open tabs across windows, as shown in this screenshot:

 

  • Chrome 89 will introduce privacy-preserving APIs to replace some of the functionality of third-party cookies
    An interest-based targeting API will be introduced as an origin trial. This API allows working with cohorts—groups of users with similar interests. Users cannot be individually identified.

    An event-level conversion API will continue in origin-trial stage for Chrome 89 This API enables the correlation of an ad click on a website with a subsequent conversion on an advertiser site, such as a sale, a sign-up, and so on. Users cannot be individually identified.

    See the chromium privacy sandbox page for details on these APIs and the privacy sandbox.
     
  • Some permission requests will be less intrusive in Chrome 89
    Permission requests that the user is unlikely to allow will be automatically blocked. A less intrusive UI will allow the user to manage permissions for each site.

 

  • Chrome 89 will require SSE3 for Chrome on x86
    Chrome 89 and above will require x86 processors with SSE3 support. This change does not impact devices with non-x86 (ARM) processors. Chrome will not install and run on x86 processors that do not support SSE3. SSE3 was introduced on Intel CPUs in 2003, and on AMD CPUs in 2005.
     
  • Chrome 89 will prefer https to http when not specified in the address bar
    When a user types an address into the address bar without specifying the protocol, Chrome will attempt to navigate using https first, then fallback to http if https is not available. For example, if the user navigates to google.com, Chrome will first attempt to navigate to https://google.com, then fallback to http://google.com if required.

    This change is planned for Windows, Mac, Linux, and Android in Chrome 89, and in Chrome 90 for iOS.
     
  • Chrome 89 will introduce the Serial API
    The Serial API provides a way for websites to read and write from a serial device through script. You can read an explainer on the Serial API here.

    You will be able to control access to the Serial API using the DefaultSerialGuardSetting policy. You can also use the SerialAskForUrls and SerialBlockedForUrls policies to control serial device access on a site-by-site basis.
  • Insecure public pages will no longer allowed to make requests to private or local URLs in Chrome 91
    Insecure pages will no longer be able to make requests to IPs belonging to a more private address space (as defined in CORS-RFC1918). For example, http://public.page.example.com will not be able to make requests targeting IP 192.168.0.1 or IP 127.0.0.1. You will be able to control this behavior using the InsecurePrivateNetworkRequestsAllowed and InsecurePrivateNetworkRequestsAllowedForUrls enterprise policies.
     
  • Chrome will maintain its own default root store as early as Chrome 92
    In order to improve user security, and provide a consistent experience across different platforms, Chrome intends to maintain its own default root store. If you are an enterprise admin managing your own certificate authority, you should not have to manage multiple root stores. We do not anticipate any changes to be required for how enterprises currently manage their fleet and trusted enterprise CAs, such as through group policy, macOS Keychain Access, or system management tools like Puppet.
     
  • The address bar might show the domain rather than the full URL as early as Chrome 90
    To protect your users from some common phishing strategies, Chrome will test showing only the domain in the address bar for some users. This change makes it more difficult for malicious actors to trick users with misleading URLs. For example, https://example.com/secure-google-sign-in/ will appear only as example.com to the user.

    Although this change is designed to keep your users’ credentials safe, you can revert to the old behavior through the ShowFullUrlsInAddressBar policy.

    This change has been enabled for some users, with a potential full rollout in a later release.
     
  • The SSLVersionMin policy will not allow TLS 1.0 or TLS 1.1 in Chrome 91
    The SSLVersionMin enterprise policy allows you to bypass Chrome's interstitial warnings for legacy versions of TLS. This will be possible until Chrome 91 (May 2021), then the policy will no longer allow TLS 1.0 or TLS 1.1 to be set as the minimum.

    We previously communicated that this would happen as early as January 2021, but the deadline has since been extended.
     
  • SyncXHR policy will no longer be supported on Chrome 93
    The AllowSyncXHRInPageDismissal enterprise policy will be removed in Chrome 93. For any apps that rely on the legacy web platform behavior, be sure to update them before Chrome 93. This change was previously planned for Chrome 88, but delayed to provide more time for enterprises to update legacy applications.
 
Chrome 87

Important: Adobe will no longer update and distribute Flash Player after December 31, 2020. Therefore, after this date, all versions of Chrome will stop supporting Flash content. Pinning to or keeping an earlier version of Chrome through any other mechanism, will not prevent this change.

You can read more about Adobe's plans to discontinue Flash player and your options in Adobe's blog post. Adobe is working with HARMAN, their exclusive licensing/distribution partner, to provide support for Flash Player in legacy browsers.

Chrome is designed to meet the needs of Chrome Enterprise customers, including integration with legacy web content. Companies that need to use a legacy browser to run Flash content after December 31, 2020 should use a HARMAN solution with Legacy Browser Support.

With Flash removed, Chrome 88 will no longer support these policies: DefaultPluginsSetting, PluginsAllowedForUrls, PluginsBlockedForUrls, AllowOutdatedPlugins, DisabledPlugins, DisabledPluginsExceptions, EnabledPlugins.
 

Chrome Browser updates

  • Google Cloud Print will no longer be supported after December 31, 2020
    As of January 1, 2021 Google Cloud Print will no longer be supported on Chrome. You can continue to use the Windows®, Mac®, and Linux® operating system print solutions or engage with a print solution provider. Chrome OS admins can select a print solution provider or migrate to the Chrome OS local and network printer solution. Learn more about Cloud Print migration.

  • Saving to Google Drive will no longer be available from the print dialog after December 31, 2020

    Mac®, Windows®, Linux® devices and Chrome Browser will no longer be able to save directly to Google Drive from the print dialog, starting on January 1, 2021. Users can instead print locally to PDF then upload the file to Google Drive through drive.google.com and select Newand thenFile upload. You can also set up automatic syncing between local files and Google Drive with Backup and Sync or Drive File Stream. More details on printing from Chrome are available here.

    Chrome OS has a new way of saving to Google Drive. See the Chrome OS section below for more information.

  • Legacy Browser Support might be affected by IE + Edge redirection

    Starting in November, Microsoft Edge® might enable automatic redirection from Internet Explorer to Microsoft Edge® for specific URLs. If you're using Legacy Browser Support, this might interfere with your existing setup. You can disable the redirection by setting the Microsoft Edge® policy RedirectSitesFromInternetExplorerRedirectMode to 0.

  • Improved resource consumption for background tabs

    To save on CPU load and prolong battery life, Chrome limits the power consumption of background tabs. Specifically, Chrome allows the timers in the background tabs to only run once per minute. Network event handlers are not affected, which allows sites like Gmail or Slack® to continue delivering timely notifications in the background. Some users will see this feature in Chrome 87, with a wider release planned for Chrome 88.

    You will be able to control this behavior using the IntensiveWakeUpThrottlingEnabled policy.

  • Updated PDF viewer

    Chrome has updated PDF viewer to include toolbar updates, table of contents, thumbnails, two-up view, and the ability to view annotations.    

     

 

     

 

        

  • Users can sign into the browser when they sign into Google web services

    When users sign into a Google web service while using an Android device, Chrome offers for them to sign in with the Google account already signed in on the device. Signing into Chrome doesn’t turn on sync; that’s a separate, optional step.

    This simplifies Android sign-in, makes the feature more consistent with Chrome on desktop, and provides signed-in users access to features without sync enabled. For example, click-to-call.

    You can control this feature with the BrowserSignin enterprise policy.

  • Certain features are available to users who have signed in without having to enable Chrome Sync

    Users who have signed into Chrome might be able to access and save payment methods and passwords stored in their Google Account without Chrome Sync being enabled.

    You can control users' access to payment methods on Chrome on Android using the AutofillCreditCardEnabled enterprise policy. You can control access to passwords on Chrome on desktop by either setting the SyncDisabled enterprise policy to disabled, or by including "passwords" in SyncTypesListDisabled.

  • Enhanced Safe Browsing

    Users will be prompted to consider enabling Enhanced Safe Browsing in Chrome, which provides better protection against phishing attacks. These prompts will show up on security warning interstitials and the new tab page, but only if you are not setting either of the SafeBrowsingProtectionLevel or SafeBrowsingEnabled policies. If one of these policies is set, your users can't change the setting and will not see any prompts to do so.

  • The new tab page allows users to complete previously started workflows

    The Chrome new tab page will show cards to help users return to searches and workflows that were already in progress, like searching for recipes or price comparisons. Users are able to control and remove these cards.

    They appear for some users in Chrome 87, but a wider rollout, by way of policy, is planned for a later release.

  • Chrome warns about mixed content forms

    Web forms that load using HTTPS but submit their content using HTTP (unsecured) pose potential risk to user privacy. Chrome 85 shows a warning on such forms, letting the user know that the form is insecure. Chrome 87 shows an interstitial warning when the form is submitted, which stops any data transmission, so the user will be able to choose whether to proceed or cancel the submission. This was previously planned for Chrome 86 but the rollout was delayed and is now available in Chrome 87.


    You will be able to control this behavior using the InsecureFormsWarningsEnabled enterprise policy.

 

  • Insecure downloads are blocked from secure pages, with changes through Chrome 88

    By Chrome 88, downloads from insecure sources will no longer be allowed when started from secure pages. This change will be rolled out gradually, with different file types affected in different releases:

  • Executables—Users were warned in Chrome 84, and files will be blocked in Chrome 85.
  • Archives —Users will be warned in the Chrome developer console in Chrome 85, and files will be blocked in Chrome 86.
  • Other non-safe types (For example, PDFs)—Users will be warned in the Chrome developer console in Chrome 86, and files will be blocked in Chrome 87.
  • Other files—Users will be warned in the Chrome developer console in Chrome 87, and files will be blocked in Chrome 88.

    Warnings on Android will lag behind computer warnings by one release. For example, executables showed a warning starting in Chrome 85.

    The existing InsecureContentAllowedForUrls policy can be used to allow specific URLs to download insecure files. You can read more details in our blog post.
  • Introducing more inclusive policy names

    Chrome is moving to more inclusive policy names. The terms "whitelist" and "blacklist" have been replaced with "allowlist" and "blocklist". If you're already using the existing policies, they will continue to work, though you will see warnings in chrome://policy stating that they're deprecated.

    The following policies have been deprecated, and equivalent policies are now available in Chrome 87 and 88. The deprecated policies will continue to work, and there is not yet any removal date planned. Future plans to remove the policies will be published in the enterprise release notes once confirmed.

    Deprecated Policy Name New Policy Name Version
    DeviceNativePrintersBlacklist DevicePrintersBlocklist 87
    DeviceNativePrintersWhitelist DevicePrintersAllowlist 87
    DeviceNativePrintersAccessMode DevicePrintersAccessMode 87
    DeviceNativePrinters DevicePrinters 87
    UsbDetachableWhitelist UsbDetachableAllowlist 87
    QuickUnlockModeWhitelist QuickUnlockModeAllowlist 87
    AttestationExtensionWhitelist AttestationExtensionAllowlist 87
    DeviceUserWhitelist DeviceUserAllowlist 87
    PrintingAPIExtensionsWhitelist PrintingAPIExtensionsAllowlist 87
    AllowNativeNotifications AllowSystemNotifications 88

     

  • Chrome Actions allow the user to accomplish tasks directly from the address bar

    Some Chrome users will be able take actions directly from the address bar, like clearing browsing data, using a button that appears among auto-complete suggestions. A wider rollout is planned for a later release.

  • Chrome will support remote commands from Chrome Browser Cloud Management in the future

    Admins using Chrome Browser Cloud Management will soon be able to issue remote commands to enrolled Chrome Browsers, for example remotely clearing cache and cookies. Although the functionality will come to the Admin console in the future, support for this set of features will be added in Chrome 87.

  • The CORB/CORS allowlist has been removed

    Chrome has removed the CORB/CORS allowlist in Chrome 87. Please test Chrome extensions that your business depends on to make sure they work with the new behavior.

    Please test Chrome 87.0.4266.0 or later versions of Chrome and run through critical workflows using your extension. Watch for fetches or XHRs that are initiated by content scripts and blocked by CORB or CORS. Some typical error messages are shown below:

    • Cross-Origin Read Blocking (CORB) blocked cross-origin response <URL> with MIME type <type>. See https://www.chromestatus.com/feature/5629709824032768 for more details.

    • Access to fetch at 'https://another-site.com/' from origin 'https://example.com' has been blocked by CORS policy: No 'Access-Control-Allow-Origin' header is present on the requested resource. If an opaque response serves your needs, set the request's mode to 'no-cors' to fetch the resource with CORS disabled.

      If the extension's content scripts create requests that don’t work when Chrome is launched with the chrome://flags listed above, then make sure you keep the extension updated so that it continues to work in Chrome 87 and above. In particular, the extensions must be updated to initiate cross-origin fetches from the extension background page (instead of from a content script).

      For more details see: https://www.chromium.org/Home/chromium-security/extension-content-script-fetches

  • The Chrome Web Store displays more privacy-focused information for extension

    The Chrome Web Store provides more information to users about how an extension uses their data, including authentication information, personally identifiable information, and user activity.

    Developers are required to provide privacy disclosures regarding their data collection and usage. This is mandatory for every update and publishing of extensions.

Chrome OS updates

  • Devices have a new way of saving to Google Drive

    The Save to Drive feature has been expanded upon, users can now rename the file or save the file to a specified Google Drive folder location.

  • Switch Access

    For users with motor impairments who are unable to use a traditional mouse or keyboard, Switch Access lets you interact with your Chrome OS Device using one or more switches. Switch Access works by scanning the items on your screen until you make a selection. Ablenet, one of the top producers of switch devices, is now in our Works with Chromebooks program, as well.

  • Tab Search

    Tab Search lets users search through their open tabs across all windows. This feature is currently available in Chrome OS 87 and will be available for Mac® and Windows® in Chrome OS 88.

  • Bluetooth battery levels

    Users can now view their connected Bluetooth peripheral battery levels in Settings and Quick Settings.
     

     

 

  • Coexistence of Multiple sign-in access and policy-provided custom trust anchors for TLS

    Starting in Chrome OS 87, the coexistence of Multiple sign-in access and policy-provided custom trust anchors for TLS is no longer blocked. If trust anchors are configured, they will be applied to the primary user account. As a result, users can switch faster between accounts in managed environments that require trust roots.

  • Language settings improvement for multilingual users

    Language settings can get extremely confusing if you are bilingual or multilingual. In Chrome OS 87, we have updated the user experience to address the needs of multilingual users.   

  • More interactive Alt+Tab

    When using Alt+Tab to switch between windows, you can now select a window with your mouse, touch screen, or stylus.

  • Renaming Virtual Desks & Launcher folders

    In Chrome OS 87, you will see visual improvements for the Virtual Desk renaming component. The visual improvements will also apply to folders in the Launcher as they use the same component.

  • Zero-touch enrollment

    Admins can configure devices to automatically enroll during the device setup process without requiring a user to invoke enterprise enrollment. More details can be found here.

Admin console updates

  • Website icons and titles now display in the Admin console and Kiosk devices

    In the Admin console, web apps that have been added under Apps & extensions now display the website's icon and title. In Kiosk devices, the website icons and titles are also displayed in the list of Kiosk web apps.

 

  • Restrict access to VPN (openVPN and L2TP)

    Admins can now add VPN to the list of Restricted Network Interfaces in the Admin console. This prevents users from connecting to OS-supported VPN options (openVPN and L2TP). Any third-party VPNs will need to be blocked through application management policies.

  • Additional policies in the Admin console

    Many new policies are available in the Admin console, including:

    Policy control Admin console location Description
    Emoji suggestions User & browser settingsand thenUser experienceand thenEmoji suggestions This policy enables Google Chrome to suggest emojis when users type text with their virtual or physical keyboards.
    URLs in the address bar User & browser settingsand thenUser experienceand thenURLs in the address bar This feature enables display of the full URL in the address bar.
    Audio sandbox User & browser settingsand thenSecurityand thenAudio sandbox This policy controls the audio process sandbox.
    Browser guest mode User & browser settingsand thenUser experienceand thenBrowser guest mode This policy controls guest logins.
    PIN auto-submit User & browser settingsand thenSecurityand thenPIN auto-submit

    The PIN auto-submit feature changes how PINs are entered in Chrome OS.

    Instead of showing the same textfield that is used for password input, this feature shows a special UI that clearly shows to the user how many digits are necessary for their PIN. As a consequence, the user's PIN length will be stored outside the user encrypted data. Only supports PINs that are between 6 and 12 digits long.

    Variations Device Settingsand thenDevice update settingsand thenVariations Configuring this policy allows to specify which variations are allowed to be applied on an enterprise-managed Google Chrome OS device.
    Single sign-on verified access Device Settingsand thenSign-in settingsand thenSingle sign-on verified access This policy configures which URLs will be granted access to use remote attestation of device identity during the SAML flow on the sign-in screen.

 

Coming soon

Note: The items listed below are experimental or planned updates. They might change, be delayed, or canceled before launching to the Stable channel.

Upcoming Chrome Browser changes

  • Single words will not be treated as intranet locations by default in Chrome 88

    By default, Chrome will improve user privacy and reduce load on DNS servers by avoiding DNS lookups for single keywords entered into the address bar. This change might interfere with enterprises that use single-word domains in their intranet. That is, a user typing "helpdesk" will no longer be directed to "https://helpdesk/".

    You will be able to control the behavior of Chrome using the IntranetRedirectBehavior enterprise policy, including preserving the existing behavior (which will perform a search immediately and then ask the user if they're trying to reach the intranet site).

  • Chrome will introduce a new permission chip UI in Chrome 88

    Permission requests can feel disruptive and intrusive when they lack context – which often happens when prompts appear as soon as a page loads or without prior priming. This leads to a common reaction where end users dismiss the prompt in order to avoid making a decision.

    Chrome will begin showing a less intrusive permissions chip in the address bar. Since the prompt doesn't intrude in the content area, users who don't want to grant the permission no longer need to actively dismiss the prompt. Users who wish to grant permission can click on the chip to bring up the permission prompt.

    This change will be rolled out gradually throughout Chrome 88.

  • Factor in scheme when determining if a request is cross-site (Schemeful Same-Site) in Chrome 88

    Chrome 88 will modify the definition of same-site for cookies such that requests on the same registrable domain but across schemes will be considered cross-site instead of same-site. For example, http://site.example and https://site.example will be considered cross-site to each other which will restrict cookies using Same-Site. For additional information please see the Schemeful Same-Site explainer. We recommend testing critical sites using the testing instructions.

    You may revert to the previous legacy behavior by using the LegacySameSiteCookieBehaviorEnabledForDomainList and LegacySameSiteCookieBehaviorEnabled policies. These policies will be available at least until Chrome 93. For more details, including availability, please see Cookie Legacy SameSite Policies.

  • Chrome 88 on Mac® will not support OS X 10.10 (Yosemite)

    Chrome 88 will not support OS X 10.10 (OS X Yosemite). Chrome on Mac® will require OS X 10.11 or later.

  • Popup on page unload policy will no longer be supported on Chrome 88

    The AllowPopupsDuringPageUnload enterprise policies will be removed in Chrome 88, as previously communicated. For any apps that rely on the legacy web platform behavior, be sure to update them before Chrome 88.

  • The Legacy Browser Support extension will be removed from the Chrome Web Store in Chrome 88

    Legacy Browser Support (LBS) is built into Chrome, and the old extension is no longer needed. The Chrome team unpublished LBS from the Chrome Web Store in Chrome 85, and it will be disabled in Chrome 88. Legacy Browser Support will still be supported, please migrate away from the extension and towards using Chrome's built-in policies, documented here.  The old policies set through the extension will no longer function, and you won't be able to force install the extension once it's been disabled.

  • Chrome will treat an empty string as an unset policy on Android for some policies in Chrome 88

    To integrate better with mobile management UEMs, Chrome on Android will not set list or dictionary policies from empty strings.

  • Users will be able to search open tabs in Chrome 88

    Users will be able to search for open tabs across windows, as shown in this screenshot:

 

  • The address bar will show the domain rather than the full URL in Chrome 88

    To protect your users from some common phishing strategies, Chrome will show only the domain in the address bar. This change makes it more difficult for malicious actors to trick users with misleading URLs. For example, https://example.com/secure-google-sign-in/ will appear only as example.com to the user.

    Although this change is designed to keep your users’ credentials safe, you can revert to the old behavior through the ShowFullUrlsInAddressBar policy.

    This change has been enabled for some users, with a full rollout planned for an upcoming release.

  • DTLS 1.0 will be removed in Chrome 88

    DTLS 1.0, a protocol used in WebRTC for interactive audio and video, will be removed by default. Any applications that depend on DTLS 1.0 (most likely gateways to other teleconferencing systems) should update to a more recent protocol. You can test if any of your applications will be impacted using the following command line flag when launching Chrome:

    --force-fieldtrials=WebRTC-LegacyTlsProtocols/Disabled/ 

    If your enterprise needs additional time to adjust, the WebRtcAllowLegacyTLSProtocols enterprise policy will be made available to temporarily extend the removal.

  • Chrome 88 will launch an origin trial for detecting idle state

    An early origin trial will allow websites to request the ability to query if users are idle, allowing messaging apps to direct notifications to the best device.

  • Chrome 89 will require SSE3 for Chrome on x86

    Chrome 89 and above will require x86 processors with SSE3 support. This change does not impact devices with non-x86 (ARM) processors. Chrome will not install and run on x86 processors that do not support SSE3. SSE3 was introduced on Intel CPUs in 2003, and on AMD CPUs in 2005.

  • Insecure public pages no longer allowed to make requests to private or local URLs in Chrome 89

    Insecure pages will no longer be able to make requests to IPs belonging to a more private address space (as defined in CORS-RFC1918). For example, http://public.page.example.com will not be able to make requests targeting IP 192.168.0.1 or IP 127.0.0.1. You will be able to control this behavior using the InsecurePrivateNetworkRequestsAllowed and InsecurePrivateNetworkRequestsAllowedForUrls enterprise policies.

  • The SSLVersionMin policy will not allow TLS 1.0 or TLS 1.1 in Chrome 91

    The SSLVersionMin enterprise policy allows you to bypass Chrome's interstitial warnings for legacy versions of TLS. This will be possible until Chrome 91 (May 2021), then the policy will no longer allow TLS 1.0 or TLS 1.1 to be set as the minimum.

    We previously communicated that this would happen as early as January 2021, but the deadline has since been extended.

  • Chrome will maintain its own default root store as early as Chrome 90

    In order to improve user security, and provide a consistent experience across different platforms, Chrome intends to maintain its own default root store. If you are an enterprise admin managing your own certificate authority, you should not have to manage multiple root stores. We do not anticipate any changes to be required for how enterprises currently manage their fleet and trusted enterprise CAs, such as through group policy, macOS Keychain Access, or system management tools like Puppet.

  • SyncXHR policy will no longer be supported on Chrome 93

    The AllowSyncXHRInPageDismissal enterprise policy will be removed in Chrome 93. For any apps that rely on the legacy web platform behavior, be sure to update them before Chrome 93. This change was previously planned for Chrome 88, but delayed to provide more time for enterprises to update legacy applications.

Upcoming Admin console changes

  • New Version Report and Update Controls

    There will be a new Version Report and Update Controls available in the Admin console. These features give increased visibility into the Chrome versions deployed in your enterprise and allows you to more granularly control how managed Chrome browsers update. If you would like to sign up to be a Trusted Tester for these features, enter your test domain and a contact email into this form.

 

Additional resources

Still need help?

Was this helpful?
How can we improve it?