Chrome 156 Uses SQLite for New IndexedDB Stores: Windows Update and Testing Guide

What actually changes for stored data?​

Google’s Chrome Platform Status describes three stages: Incognito’s in-memory stores came first; new persistent stores follow in Chrome 156; migration of existing stores comes later. A first site visit, or a visit after clearing site data, can create SQLite-backed storage. There is no IndexedDB web API change.

The practical implication for testing is important: an established browser profile and a fresh test environment may exercise different backends. Testing only an existing installation would therefore miss the new-store path described by Google. That is a testing recommendation derived from the rollout design, not evidence of a known compatibility defect.

Chrome 156 release versions and rollout​

Google’s Chrome Releases team announced Stable promotion on October 20, 2026, with desktop distribution continuing over the following days and weeks. Its announcement identifies these initial builds:

The desktop versions come from Google’s desktop announcement; the Android version comes from its separate mobile announcement, which promises Google Play availability over the next few days. Release day is not an installation deadline for every device.

There is also a more immediate reason to update than database architecture: Google’s desktop announcement reports 353 security fixes. That is separate from the SQLite project and should not be mistaken for a measure of its reliability improvement.

CSS, call diagnostics and fenced frames​

Chrome Platform Status also lists four CSS changes:

• random() generates numeric values within a range.
• A navigation-source pseudo-class selects the initiating element during navigation.
• overflow: scroll clip supports single-axis scrolling.
• scroll-snap-type: pair keeps both axes targeting the same element, unlike independently selected targets with both.

For enterprise calling apps, the desktop WebRTC Diagnostic Logging API permits authorized diagnostic collection and user-authorized sharing with the browser vendor. Administrators control access through WebRtcDiagnosticLogCollectionAllowedForOrigins; this is not an Android WebView launch.

Fenced-frame elements and window.fence APIs become stubs in milestone 156. Full element removal in milestone 157 remains conditional on staged testing and further approval—not a guaranteed removal date.

What Windows users should do​

Google’s documented desktop update procedure is straightforward:

1. Open Chrome’s three-dot menu.
2. Select Help → About Google Chrome.
3. Allow the page to check for updates.
4. Select Relaunch if offered.
5. Return to the About page to confirm the installed version.

One useful precaution: Google says regular tabs and windows reopen after relaunch, but Incognito windows do not. Finish anything important there before restarting. If updates are explicitly disabled by an administrator, Google’s troubleshooting guidance directs users without the necessary permissions to their administrator.

For developers, the priority is targeted new-store testing—not an application rewrite. For everyone else, this is chiefly an update-and-relaunch story: the database machinery changes beneath the same IndexedDB API.