 Rachel Andrew Technical Writer [GitHub](https://github.com/rachelandrew) [LinkedIn](https://www.linkedin.com/in/rachelandrew) [Mastodon](https://front-end.social/@rachelandrew) [Bluesky](https://bsky.app/profile/rachelandrew.bsky.social) [Homepage](https://rachelandrew.co.uk)
Published: February 10, 2026
Chrome 145 is rolling out now, and this post shares some of the key features
from the release. Read the full [Chrome 145 release notes](https://developer.chrome.com/release-notes/145.md.txt).
Highlights from this release:
- [Column wrapping for multicol](https://developer.chrome.com/blog/new-in-chrome-145.md.txt#multicol) enables vertical column layout.
- [The Origin API](https://developer.chrome.com/blog/new-in-chrome-145.md.txt#origin-api) makes working with origins easier.
- [Device Bound Session Credentials](https://developer.chrome.com/blog/new-in-chrome-145.md.txt#dbsc) protects user sessions.
## Column wrapping for multicol
From Chrome 145, the `column-wrap` and `column-height` properties from the
[multi-column layout level two specification](https://drafts.csswg.org/css-multicol-2/)
are supported. These properties let you wrap columns onto a new row in the block
direction.
Prior to Chrome 145, if the height of the multicol container was restricted,
content that didn't fit into the available space would appear as overflow
columns in the inline direction. This would create a horizontal scrollbar on the
web.
With the `column-height` and `column-wrap` properties you can set a height for
the row of columns and set the overflow columns to appear as a new row.
Learn more in [Support for wrapped columns in CSS multicol](https://developer.chrome.com/blog/multicol-wrapping.md.txt).
## The Origin API
The [origin](https://datatracker.ietf.org/doc/rfc6454/) is a fundamental
component of the web's implementation, essential to both the security and
privacy boundaries that user agents maintain.
In Chrome 145, the Origin API introduces an `Origin` object that encapsulates the
origin concept and provides helpful methods for comparison, serialization, and
parsing.
Previously, origins were not directly exposed to developers. While there are
various origin getters, they return the ASCII serialization of an origin. This
could lead to vulnerabilities when attempting same-origin or same-site
comparisons. The Origin API addresses this gap.
## Device Bound Session Credentials
[Device Bound Session Credentials (DBSC)](https://developer.chrome.com/docs/web-platform/device-bound-session-credentials.md.txt)
lets websites bind a user's session to their specific device, making it
significantly harder for stolen session cookies to be used on other machines.
DBSC binds authentication sessions to the device by using short-lived cookies
and a hardware-backed key pair. The browser periodically proves possession of
the private key to refresh the session cookie.
## Further reading
This covers only some key highlights. Check the following links for additional
changes in Chrome 145.
- [Release notes for Chrome 145](https://developer.chrome.com/release-notes/145.md.txt).
- [What's new in Chrome DevTools (145)](https://developer.chrome.com/blog/new-in-devtools-145.md.txt).
- [ChromeStatus.com updates for Chrome
145](https://chromestatus.com/features#milestone%3D145).
- [Chrome release calendar](https://chromiumdash.appspot.com/schedule).
## Subscribe
To stay up to date, [subscribe](https://goo.gl/6FP1a5) to the [Chrome Developers
YouTube channel](https://www.youtube.com/user/ChromeDevelopers/), and you'll get
an email notification whenever we launch a new video. Or follow us on X or
LinkedIn for new articles and blog posts.
As soon as Chrome 146 is released, we'll be right here to tell you what's new in
Chrome!