Thorium-Win: the Windows build repo for the Thorium Chromium fork

What Thorium-Win actually is, and who it is not for

The README opens with a line that resolves most confusion about this repository: it exists "to serve Windows builds of Thorium". That is the whole job. The source code, the patches and the Linux builds live in Alex313031/Thorium; Thorium-Win publishes the Windows artifacts and the notes that go with them. If you came here looking for the patch set that makes Thorium different from Chromium, the README sends you to the features section of the main repository instead.

The intended audience is narrow and specific. You want a Chromium-based browser on Windows that the README says is "Intended to behave like and have the featureset of Google Chrome", with the differences and patches listed in the main repo. You do not want to build Chromium from source, which on Windows is a multi-hour job with a large toolchain.

The audience it excludes is just as clearly stated. Windows 7, 8 and 8.1 users are told in bold to use the separate thorium-win7 repository. 32-bit and SSE3/SSE4 machines are routed to Thorium-Special. ARM64 Windows goes to Thorium-WOA. And AVX2 builds now live at Thorium-Win-AVX2, a change the README flags with a "NEW" marker. Picking the wrong repository is the most common way to end up with a binary that will not start.

How the repository is laid out and how a build reaches you

The top-level listing is small and readable: a .github directory, LICENSE, README.md, ThoriumLogo.png, a CROSS_BUILD_VS_ARCHIVE file, WIN_CROSS_BUILD_INSTRUCTIONS.txt, WIN_INSTRUCTIONS.txt, two Speedometer screenshots, a Google site-verification HTML file, and thor_compat_mode.bat. There is no Chromium source tree here, which is the point. The Batchfile language label on the repository comes from scripts like that one rather than from the browser itself.

The delivery mechanism is GitHub releases. The README states that Thorium ships as an .exe installer and a portable .zip, and that portable instructions are in the Readme inside the zip. Releases are tagged with the Chromium milestone they track: M154.0.8037.45, M152.0.7977.55 and M151.0.7922.72, each described in its own title as a beta release. The README's claim that Thorium is "Always built with the latest stable version of Chromium" sits alongside those beta labels, and that is worth noticing before you deploy it on a work machine. The last push to this repository was on 2026-09-24.

For anyone building rather than downloading, the README does not describe the build itself. It points to BUILDING_WIN.md for a native Windows build and BUILDING_WIN_CROSS.md for cross-building on Linux, both in the main Thorium repository. Two files in this repo's root, WIN_CROSS_BUILD_INSTRUCTIONS.txt and CROSS_BUILD_VS_ARCHIVE, are not explained in the README text, so treat them as raw notes rather than documented procedure.

Installing Thorium on Windows 10 or 11 and running it once

There is no package manager step. The README gives two artifacts, so the install is a download from the releases page followed by either an installer run or a ZIP extraction.

If you want the conventional route, take the .exe from the release whose tag matches the Chromium milestone you want, and run it. The README describes the artifact only as an .exe installer, so the filename will follow the release tag you picked.

What you should see is the standard Chromium-family install flow. The README does not document a silent-install flag, an install directory override, or a per-user versus per-machine choice, so do not assume one exists.

For the portable route, download the .zip for the same release and unpack it. The README is explicit that the portable instructions are in the Readme inside the zip file, not in this repository's README. Read that file before launching, because portable Chromium builds normally depend on where the profile directory is placed relative to the executable. The repository README does not state that layout, so the bundled Readme is the only source for it.

There is also thor_compat_mode.bat in the repository root. The README never mentions it, so its behaviour is not documented in the README or the repository listing; if you need it, read the script before running it.

The limitations you should weigh before switching

The most concrete limitation is the release labelling. Every recent release in this repository carries the words "Beta Release" in its title, including M154.0.8037.45. The README's promise of the latest stable Chromium and the release titles do not say the same thing. If you are rolling this out to people who cannot debug a broken browser, that gap matters more than any feature list.

The second limitation is platform coverage, and it is a hard boundary rather than a soft one. Windows 7, 8 and 8.1 are explicitly redirected elsewhere. 32-bit and older-SIMD machines are redirected to Thorium-Special. ARM64 Windows is redirected to Thorium-WOA. The AVX2 path is now a different repository entirely, which means a machine that needs AVX2 builds has to track a second project's release cadence, not this one's.

The third is documentation depth in this repo. The README covers what Thorium is and where to get it, and then defers. Building, features, differences from Chromium, and portable setup all live in other files or other repositories. Anyone expecting Thorium-Win to answer questions about the browser's internals will be following links for most of the session. If you need a browser with a documented enterprise policy story and a vendor support contract, this is not that project, and the README makes no claim that it is.

Thorium versus staying on Chrome or plain Chromium

The obvious alternative is Google Chrome, and the README frames the comparison itself: Thorium is "Intended to behave like and have the featureset of Google Chrome", with differences and patches enumerated in the main repository. That framing tells you what you are trading. Chrome gives you a vendor, an auto-update channel and an enterprise policy surface. Thorium gives you the same Chromium engine with a modified default configuration, distributed through GitHub releases as an installer and a portable ZIP.

The second alternative is upstream Chromium, and the distance is different again. Upstream Chromium is deliberately bare: no bundled proprietary media components, a default configuration many users find spartan, and builds that most people never install directly. Thorium's patches exist to close that gap toward Chrome behaviour while keeping the Chromium lineage. The README states the goal but does not enumerate the patches here; that list is in the main Thorium repository, and you should read it before assuming which side of the Chrome/Chromium line any given feature falls on.

A third option is one of the sibling Thorium repositories, which is less an alternative than a correction. If your hardware is older or your Windows is older, thorium-win7, Thorium-Special or Thorium-WOA is the right project, and Thorium-Win is simply the wrong download.

Maintenance, licensing and the cost of keeping up

This repository is not archived, and its last push was on 2026-09-24, days before this article. Release cadence over the visible window is roughly one release per month: M151 in early August, M152 in late August, M154 in late September. Tracking Thorium means tracking Chromium milestones, because the release tags are Chromium versions, and a browser that lags a Chromium milestone accumulates upstream security fixes it has not received. That is the real upgrade cost: not the install, but the discipline of moving to the next tagged release.

Licensing is straightforward to state and worth stating precisely. The repository carries BSD-3-Clause, which is the Chromium project's own licence family. Chromium bundles components under other licences, and third-party notices ship with the binary. Nothing here changes your obligations under those. This is a description of what the repository declares, not legal advice; if you redistribute a modified build, read the notices that come with it.

One maintenance detail is easy to miss: because AVX2 builds moved to Thorium-Win-AVX2 and legacy Windows builds moved to thorium-win7, this repository's own scope has narrowed over time. A bookmarked releases URL from a year ago may now point at a project that no longer publishes the build you need.

Editorial conclusion

Use Thorium-Win if you are on Windows 10 or 11 on an x86-64 machine and you want a Chromium build whose defaults are closer to Chrome than to upstream Chromium, without compiling it yourself. Do not use it on Windows 7, 8 or 8.1, on 32-bit Windows, or on ARM64 Windows: the README points those users at thorium-win7, Thorium-Special and Thorium-WOA instead. Before installing, check the release tag against the Chromium major version you need, read the portable instructions inside the ZIP if you want the no-installer route, and confirm whether your CPU needs the AVX2 build from Thorium-Win-AVX2 rather than the default one here.

Frequently asked questions

Official sources

1. Alex313031/Thorium-Win on GitHub
2. License: BSD-3-Clause
3. Project website
4. README
5. Releases