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

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, the headline is what didn’t change: vertical tabs remain flag-only for the second consecutive release.

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: still flag-only. No graduation from Chrome 146. Same setup steps as before.
• Tab scrolling returns in H1 2026 after user backlash following its removal.
• 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.

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: Still a Flag in Chrome 147

Two releases in and vertical tabs have not graduated to a default Chrome feature. Chrome 146 shipped them for all platforms. Chrome 147 leaves the situation unchanged.

The steps to enable vertical tabs in Chrome 147 are identical to Chrome 146:

1. Go to chrome://flags/#vertical-tabs
2. Set the flag to Enabled
3. Relaunch Chrome
4. Go to Settings > Appearance > Tab strip position > Left

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 Returns in H1 2026

Google removed tab scrolling sometime in 2025 and heard about it. When the tab strip fills up with enough tabs that not all are visible, users previously could scroll horizontally through them. That behavior was removed, users complained, and the feature is returning in the first half of 2026.

Chrome 147 is in scope for that timeline. Whether it lands in exactly this release or a subsequent one before the H1 cutoff is not pinned down, but the direction is confirmed.

The practical effect: on a crowded tab bar, instead of tabs shrinking to favicon-only slivers, you get a scrollable strip. Tabs stay readable. This is meaningful for anyone who doesn’t use vertical tabs or a tab management extension but still maintains 20+ open tabs.

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.

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.
• Zero telemetry is a meaningful differentiator. Extensions that process everything locally (no remote servers, no data collection) can’t be turned into surveillance tools after acquisition. This is the architecture both SuperchargePerformance and SuperchargeNavigation are built on — local processing, zero telemetry, no account required. SuperchargePerformance keeps everything on-device with no sync at all; SuperchargeNavigation is local by default with optional browser-native sync (your Google or Microsoft account, never our servers).

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:

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. The tab management story did not move. Vertical tabs are where they were in 146. 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, 50 auto-snapshots at 5-minute intervals 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 account, local by default (optional browser-native sync via your Google or Microsoft account; zero telemetry either way).

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.