Google Chrome Frame is no longer supported and retired as of February 25, 2014. For guidance on what you need to know as a developer or IT administrator, please read our developer FAQs for Chrome Frame.
Google Chrome Frame supports enterprise features such as an offline (MSI) installer, control of automatic updates, and centralized management via Group Policy.
An offline installer for the current stable release of Google Chrome Frame can be downloaded from:
The version number for the current stable release is always available at:
In keeping with Google’s dedication to a secure browsing experience, installations of Google Chrome Frame are automatically kept up to date with the current stable release via Google Update. Automatic updates can be disable when desired, although the decision to do so must not be taken lightly. While new major versions of Google Chrome Frame are expected roughly every six weeks, minor updates that address serious security vulnerabilities are released on an as-needed basis. As such, turning off automatic updates leaves users running vulnerable software. If, after careful consideration, you decide to disable automatic updates, it is essential that you plan to deploy updates via MSI in a timely manner. Automatic updates for Google Chrome Frame can be disabled via the “Update policy override” Group Policy setting for these Group Policy categories:
Either of the “Manual updates only” or “Updates disabled” options will disable automatic updates. See Google Update for Enterprise for more information about these Group Policy settings and Turning Off Auto Updates in Google Chrome for frequently asked questions.
If you have chosen to disable automatic updates to allow for some time to qualify new releases prior to deployment, you can generally find the next major version on the beta channel. The current beta can be installed from:
See the Chromium Common Problems and Solutions documentation for more information regarding deploying updates via MSI.
Many behaviors of Google Chrome Frame can be managed via Group Policy. The authoritative list of all Google Chrome and Google Chrome Frame Group Policy settings can be found in the Google Chrome Policy List. Settings that pertain directly to Google Chrome Frame are detailed below.
The settings in the “Default HTML renderer for Google Chrome Frame” Group Policy category can be used to set the default renderer as well as to specify a set of URLs for which the default is to be overridden. Use the “ChromeFrameRendererSettings” Group Policy setting to set either the host browser (Internet Explorer) or Google Chrome Frame as the default renderer. When the host browser is configured as the default, any URLs matching patterns present in the “RenderInChromeFrameList” Group Policy setting are rendered in Google Chrome Frame regardless of whether or not content obtained from those URLs opts-in. Conversely, when Google Chrome Frame is configured as the default, URLs matching patterns present in the “RenderInHostList” Group Policy setting are rendered in the host browser unless content obtained from those URLs opts-in.
URL patterns in the “RenderInChromeFrameList” and “RenderInHostList” Group Policy settings may contain ‘?’ (matching zero or one character) or ‘*’ (matching zero or any number of characters) wildcards.
The settings in the “Allow Google Chrome Frame to handle the following content types” Group Policy category can be used to specify additional content types to be rendered in Google Chrome Frame. By default, the following media types are rendered in Google Chrome Frame if the X-UA-Compatible HTTP response header is present as described in Making Your Pages Work With Google Chrome Frame:
The ChromeFrameContentTypes Group policy setting can be configured with a list of additional content types.
Google Chrome Frame respects Google Chrome’s “ApplicationLocaleValue” Group Policy setting.
The “GCFUserDataDir” Group Policy setting controls the directory under which Google Chrome Frame stores user data.
To pass additional command line args to Chrome when run by Chrome Frame, you can use the AdditionalLaunchParameters policy setting.