Skip to main content

Guide · All Extensions

Chrome 147 Release Notes: EVERY Change for Tab Users (2026)

Chrome 147 stable April 7, 2026. HTTPS-First auto-enables for 1B users, vertical tabs roll out gradually, tab scrolling slips its promise. Full breakdown.

9 min read Verified Chrome 150

Chrome 147 hits stable on April 7, 2026. Desktop users on the early stable channel started receiving it March 25. The headline change most users will notice: HTTPS-First mode activates automatically for roughly one billion people. For tab power users, native vertical tabs begin a gradual no-flag desktop rollout in Chrome 147.

Key takeaways

  • HTTPS-First mode auto-enables April 7 for Enhanced Safe Browsing users. Full rollout to all Chrome users is October 2026 (Chrome 154).
  • Vertical tabs: gradual desktop rollout. Chrome 147 starts the no-flag rollout. ChromeOS follows in 148. Users included in the rollout need no flag.
  • Tab scrolling missed its H1 2026 promise — still not shipped as of Chrome 150, and no new date.
  • Projects Panel (Gemini + tab groups): Canary only. No ETA for stable.
  • Extension security tightened: 8.8M+ users affected by ongoing malware campaigns. Chrome 147 extends Safety Check risk scoring.

HTTPS-First Mode: The Change That Affects a Billion Users

Chrome 147 is the version where HTTPS-First mode stops being opt-in and becomes the default for anyone using Enhanced Safe Browsing. That covers roughly one billion Chrome users.

What actually changes: Chrome now attempts HTTPS before loading any public site. If the site supports HTTPS (which 95% of page loads already do), nothing looks different. If the site is HTTP-only, Chrome shows a warning page before allowing you through.

The warning is not a virus alert. It is not indicating the site is actively malicious. It means the connection is unencrypted — a meaningful risk on login forms or payment pages, a theoretical risk on a static read-only page you’ve visited a hundred times. Chrome does not distinguish between those cases. It warns on any HTTP URL.

ScenarioChrome 147 behavior
HTTPS siteNo change — loads normally
HTTP site, Enhanced Safe Browsing onWarning page before loading
HTTP site, Enhanced Safe Browsing offNo warning until Chrome 154
Private IP (192.168.x.x, 10.x.x.x, localhost)Exempt — loads without warning
Corporate intranet on public domainMay trigger warning (IT can apply policy exemptions)
Chrome 154 (October 2026)HTTPS-First for all users regardless of Safe Browsing setting

The Chrome 147 rollout is the first large-scale automatic activation. Chrome 154 in October 2026 is the full rollout to every Chrome user on every profile. If you’re seeing warnings on a specific site and want them gone, the dedicated fix guide covers five specific scenarios including router admin panels, corporate intranets, and globally disabling the feature.

Vertical Tabs: Gradual Desktop Rollout in Chrome 147

Chrome 146 exposed experimental vertical tabs behind a flag. Chrome 147 begins the gradual no-flag rollout on Windows, macOS and Linux; ChromeOS follows in 148.

For users included in the Chrome 147 desktop rollout, the flag is no longer required:

  1. Right-click a tab and choose Show Tabs Vertically.
  2. Or open Settings > Appearance > Tab position and select Vertical.

The no-flag option rolled out gradually from desktop Chrome 147 and ChromeOS 148.

If you already have vertical tabs enabled from Chrome 146, nothing changes. Your settings carry over.

What Chrome’s built-in vertical tabs do: move the tab strip to a collapsible left sidebar, show full tab titles, and respect existing tab groups. What they still don’t do: named workspaces, session persistence across restart, keyboard search across open tabs, tab previews, or session time-travel. None of those gaps closed between 146 and 147.

For the deep comparison of Chrome native vertical tabs against extension-based tab management, that analysis lives at Chrome 146 Vertical Tabs vs Extensions — the feature set hasn’t changed in 147, so the conclusions remain current.

Tab Scrolling: Promised for H1 2026, Still Not Here

Google removed tab scrolling in 2025 and heard about it. When the tab strip fills past the point where every tab is visible, you used to be able to scroll horizontally through them. That went away, users complained, and Google said it would return in the first half of 2026.

That window has closed. H1 2026 ended on June 30 and tab scrolling has not shipped — not in 147, and not in any release through Chrome 150. The chrome://flags/#scrollable-tabstrip flag that used to bring it back was itself removed in Chrome 144. No milestone currently carries a commitment for it, so treat the return as intended but unscheduled rather than imminent.

The practical effect of its absence: on a crowded tab bar, tabs keep shrinking to favicon-only slivers instead of staying readable in a scrollable strip. If you routinely hold 20+ tabs and do not want to wait on Google, vertical tabs (native since Chrome 147) or a tab manager are the answers available today.

Projects Panel: Gemini + Tab Groups (Canary Only)

Google’s most ambitious tab-organization experiment remains behind a Canary wall. The Projects Panel connects Gemini AI chat threads directly to tab groups — the idea being that a research session with an AI assistant and a set of open tabs are one coherent “project” rather than separate things.

Two layout variants are in testing. Neither has an ETA for the stable channel.

AspectCurrent status (April 2026)
AvailabilityChrome Canary only
AI componentGemini chat embedded in panel
Tab integrationLinks to existing tab groups
Layouts testedTwo variants
Stable ETANot announced
Account requiredYes (Google account for Gemini)

The feature does not conflict with third-party tab management extensions. Extensions that use Chrome’s side panel API (including SuperchargeNavigation) operate on a separate surface from the Projects Panel experiment. If you’re using Canary and the Projects Panel, both can coexist.

Enterprise: DLP Expanded and Extension Risk Scoring

Two Chrome 147 changes that matter mainly to IT teams but have downstream effects on users:

DLP extended to encrypted files up to 2GB. Chrome’s Data Loss Prevention policies — which flag or block sensitive data from being uploaded, copied, or shared — now apply to encrypted files up to 2GB. Previously, large encrypted files could slip through DLP scans because scanning them was resource-intensive. This matters in corporate environments where compliance teams rely on Chrome’s DLP to enforce data handling rules.

Extension risk score management. Chrome’s Safety Check, the periodic browser health review accessible at chrome://settings/safetyCheck, now surfaces extension risk scores more prominently. High-risk extensions can be auto-disabled based on the score, and IT administrators can configure policies around automatic handling. For individual users, the practical effect is that a suspicious extension might get flagged or disabled during a routine Safety Check without you explicitly initiating a review.

This is part of a broader pattern — see the extension security section below.

Extension Security: Ongoing Enforcement

Google’s extension security enforcement continued through early 2026 with a campaign that affected 8.8 million users across multiple malware-laced extensions. “Save image as Type” was among the extensions removed recently.

The pattern: extensions that appear legitimate accumulate large user bases, get acquired or compromised, and begin injecting scripts or harvesting data. Chrome 147’s enhanced Safety Check risk scoring is one response to this. The structural issue — that any installed extension has significant access to your browsing — remains unchanged.

A few practical points:

  • Review your installed extensions. Go to chrome://extensions and audit anything you installed over a year ago that you don’t actively use.
  • Check permissions. Extensions with “Read and change all your data on all websites” deserve scrutiny. Most productivity extensions don’t need access that broad.
  • Local processing and sync boundaries matter. SuperchargePerformance processes its core features locally. SuperchargeNavigation stores workspace data locally, with default-enabled browser-account sync through your Google or Microsoft account. Browser-account workspace sync is enabled by default. Readable remote data can resolve setup automatically, and choosing Skip also permits syncing; otherwise writes wait for setup resolution. You can disable sync on this device, preserving local workspaces and the existing remote copy. Workspace sync uses your browser account, not a SuperchargeBrowser workspace server. Core features process locally. Network requests can include browser-account sync, site resources, previews, and user-selected sharing. Chrome and Edge lifecycle pages open the website, which records install events and uses website analytics.

Chrome ARM64 Linux: Q2 2026

Chrome is adding native ARM64 Linux builds in Q2 2026. Chrome 147 (April 7) sits at the beginning of that window.

ARM64 Linux users currently run Chrome through emulation or use Chromium builds. Native ARM64 binaries mean lower CPU overhead, better battery behavior on ARM laptops running Linux, and no emulation layer. Arch Linux ARM, Raspberry Pi OS (64-bit), and similar distributions are the primary beneficiaries.

This is a build artifact change, not a feature change. Extensions and web APIs behave identically across architectures.

What Didn’t Make Chrome 147

Context for the features Chrome users are tracking but that haven’t shipped yet:

FeatureStatus as of April 2026
Vertical tabs: available without a flagGradual desktop rollout begins in 147; ChromeOS follows in 148. Rollout is gradual.
Projects Panel (Gemini + tab groups)Canary only. No stable ETA.
AI Mode in Google SearchGradual rollout. Not universal.
Tab scrollingPromised for H1 2026; still absent as of Chrome 150. No new date.
HTTPS-First for all usersChrome 154, October 2026.

What Chrome 147 Means for Tab Management

The net effect for people who use Chrome heavily for tab-intensive work: this is a security and enterprise release. Native vertical tabs begin a gradual no-flag desktop rollout in Chrome 147. The Projects Panel remains experimental. Tab scrolling may or may not arrive in exactly this version.

If you’re managing 30+ tabs across multiple work contexts, the native tools in Chrome 147 give you the same toolkit as Chrome 146. Named workspaces, session recovery, keyboard navigation across open tabs and history, and tab previews without context-switching are still extension territory.

SuperchargeNavigation handles these via Chrome’s side panel API: named workspaces with persistence across restarts, up to 50 global snapshots across all workspaces and windows in one local ring buffer, checked every five minutes when state changes for session time-travel, Alt+K to search open tabs from any page, and Alt+Click to peek at a tab without switching to it. Free core, no SuperchargeBrowser account required. Browser-account workspace sync is enabled by default. Readable remote data can resolve setup automatically, and choosing Skip also permits syncing; otherwise writes wait for setup resolution. You can disable sync on this device, preserving local workspaces and the existing remote copy. Workspace sync uses your browser account, not a SuperchargeBrowser workspace server.

If your main Chrome 147 concern is the HTTPS warning appearing on specific sites, the fix guide covers it in under five minutes. If you want the full vertical tabs analysis comparing Chrome native to extension options, that’s at Chrome 146 Vertical Tabs vs Extensions.

For most users: update when Chrome prompts you. The HTTPS-First change is the one to understand, especially if you use old bookmarks, local network tools, or internal apps that haven’t moved to HTTPS.

Frequently Asked Questions

What is new in Chrome 147?
As of April 2026, Chrome 147 (stable April 7, 2026) enables HTTPS-First mode automatically for Enhanced Safe Browsing users, continues rolling out DLP protections for enterprise encrypted files up to 2GB, and extends extension risk scoring in the Chrome Safety Check. Vertical tabs begin a gradual no-flag desktop rollout in Chrome 147; horizontal tabs remain the default layout. Tab scrolling was promised for H1 2026 but has not shipped as of Chrome 150; the window closed on June 30 with no replacement date. Projects Panel with Gemini AI is Canary-only with no ETA for stable.
Does Chrome 147 have vertical tabs by default?
No. From April 7, 2026, native vertical tabs began a gradual no-flag desktop rollout in Chrome 147. In current stable Chrome, right-click a tab and choose Show Tabs Vertically, or go to Settings > Appearance > Tab position > Vertical. Unlike the experimental flag in Chrome 146, Chrome 147 begins the gradual no-flag desktop rollout.
When does HTTPS-First mode turn on in Chrome 147?
As of April 2026, Chrome 147 enables HTTPS-First mode automatically for users with Enhanced Safe Browsing enabled. The full rollout to all Chrome users (regardless of Safe Browsing setting) is planned for Chrome 154 in October 2026.
What is the Chrome Projects Panel?
As of April 2026, the Projects Panel is an experimental feature in Chrome Canary that links Gemini AI chat threads to tab groups. Google is testing two layout variants. There is no confirmed timeline for the feature to reach Chrome stable.
Is Chrome 147 ARM64 Linux available?
Google announced native ARM64 Linux builds in March 2026 and targeted Q2 2026. That quarter closed on June 30, and we have not been able to confirm from a primary source that general ARM64 Linux builds actually shipped — treat it as announced but unconfirmed rather than available, and check Chrome's Linux download page for your architecture before planning around it.
Did Chrome remove the 'Save image as Type' extension?
As of April 2026, 'Save image as Type' was removed from the Chrome Web Store as part of Google's ongoing extension security enforcement. It was among several extensions removed during a campaign that affected over 8.8 million users.