What chrome://flags/#enable-chrome-home does
This page explains the flag chrome://flags/#enable-chrome-home in practical, evergreen terms. This flag relates to Chrome’s Home area, which can replace the new tab page or appear as a dedicated section with shortcuts, feeds, and content suggestions. Enabling this flag does not automatically change your homepage in the traditional sense; instead, it activates Chrome’s modern Home experience when the related Home setting is configured to use it. Outcomes depend on your Chrome version, platform, policies, and whether enterprise or profile settings manage Home behavior.
Flags are experimental by design, so results can vary across Chrome versions and channels. Some users may see a redesigned Home with faster access to tabs, sessions, and suggested content, while others see minimal changes. This explainer covers behavior, prerequisites, risks, defaults, how to check or revert the flag, and related settings that affect the Home experience.
Background and context
Chrome periodically experiments with ways to make the browser start and task entry points more useful without changing the core browsing experience for everyone at once. Flags like enable-chrome-home allow users and IT admins to opt into these experiments ahead of stable rollouts. The Home area can show links to frequently used sites, recently closed tabs, sessions, shortcuts, and content from apps like Google Lens or Discover, depending on configuration. Because Home can be set via policies, device settings, or user preferences, the flag’s impact depends on which setting takes precedence.
Key terms defined
- Chrome Home: The designated area in Chrome that can appear on startup or as a replacement for the new tab page, depending on settings.
- chrome://flags: A developer-facing page that lets you change experimental browser behavior before it ships broadly.
- Flag: An experimental on/off switch that may change visuals, performance, or functionality, and is not yet guaranteed in the stable channel.
- Home setting: The user- or policy-controlled choice of what content appears in the Home area (default tab page, custom URL, or Chrome Home).
How the flag behaves in practice
Turning on enable-chrome-home typically does one of two things, depending on your Home setting:
- If Home is set to
Chrome, you may see a redesigned Home with organized shortcuts, a feed of content, and faster access to sessions and apps. - If Home is set to
New tab pageor a custom URL, enabling the flag often has no visible effect on the UI unless you later switch Home to use Chrome.
On desktop, mobile, and ChromeOS, the flag name is the same, but the exact UI and available options can differ. Enterprise policies and managed configurations can override user choices, so IT admins should check policy documentation for HomeLocation and related settings before relying on the flag.
Default status and rollout notes
Flags tied to upcoming Home experiences are usually disabled by default in stable channels until the rollout is verified. During field trials or broader testing in beta and dev channels, the flag may be automatically enabled for some users. Because availability varies by platform and version, it is common for the flag to appear present but inactive on many installs. Chrome updates can also change or remove flags without notice, which is why evergreen documentation should describe current behavior rather than a fixed rollout timeline.
Typical defaults by channel (indicative)
| Chrome channel | Flag default | Notes |
|---|---|---|
| Stable | Disabled | Flag usually off; Home defaults controlled by user or policies |
| Beta, Dev | May be enabled for some users | Part of limited experiments or A/B tests |
| Canary | Often enabled | Early testing environment; behavior can change without warning |
How to check or change the flag
Because flags can change between versions, the safest method is to verify in your current Chrome build. To view or toggle the flag:
- Open a new tab and enter
chrome://flagsin the address bar. - Search for Enable Chrome Home or for
#enable-chrome-homein the URL after navigating tochrome://flags. - Use the dropdown to set it to Enabled, Disabled, or Default.
- Relaunch Chrome if prompted, then check your Home setting under Settings > Home.
To see whether Home is using Chrome or another source, go to Settings > Home and review the selected option. The flag only matters if Home is set to use Chrome; otherwise, changing the flag does not alter which page appears on startup.
Risks, caveats, and troubleshooting
Because this is an experimental flag, you may encounter visual glitches, unexpected layout changes, or minor performance differences. If the Home area behaves oddly after enabling the flag, try one of these steps:
- Set the flag to Disabled and relaunch Chrome.
- Check that your Home setting matches your intended experience (Chrome vs New tab page vs Custom URL).
- Reset any overridden startup pages in Settings > Startup.
- Update Chrome to the latest stable build to ensure compatibility.
Flags do not typically affect core browsing history, bookmarks, or passwords, but unstable flag implementations can cause temporary UI issues. Disabling the flag and relaunching usually restores the prior behavior.
When to use this flag and when to avoid it
You might consider enabling the flag if you want early access to a redesigned Home area and are comfortable with occasional UI inconsistencies. It is generally safe in Beta or Dev channels for testing, but most stable users should leave the flag at default and manage Home through stable Settings instead. If your organization uses policies to control Home, coordinate with IT before changing flags, as policies can override user flag settings.
Related settings and concepts
- Homepage in Settings: Controls which page appears when you open Chrome or open a new tab, independent of flags once configured.
- Startup pages: Set one or more pages to load when Chrome starts, which can coexist with or override Home content.
- Content suggestions and feed: May appear in the Home area when enabled and when signed in; managed separately in privacy and personalization settings.
Status and change management
Flags like enable-chrome-home are subject to change or removal without prior notice as Chrome evolves. If you depend on a consistent experience for work or shared devices, prefer stable Settings over flags and pin your Chrome version for a short period after major updates. Document any flag changes in runbooks so reversions are fast and predictable.
Bottom line
The chrome://flags/#enable-chrome-home flag activates Chrome’s modern Home experience when the Home setting is configured to use Chrome. It does not by itself change your homepage or new tab page, and it is intended for experimentation and early feedback rather than production stability. For most users, configuring Home through stable Settings provides a predictable, policy-friendly setup without needing to change flags.