Chromium

Still too much Google snooping in Chromium. You're better off getting Ungoogled Chromium instead. It requires a plugin to use the Google Chrome App Store, but well worth it if you value your privacy and sanity.

I like it mainly because it is an additional browser I can use on my Mac for specialized purposes.

For anyone still on a pre10.15 MacOS (10.7 to 10.14): after a few years using Brave, I've switched to Chromium-legacy by blueboxd, works perfectly. Use the builds numbered like 119.0.6045.105.1 (tagged "stable"), not the ones like 1211971 (Canary builds). I haven't met any issue in two months use.

v119.0.6008.0 is out. It includes a SECURITY PATCH for CVE-2023-4863, an in-the-wild exploit of Google's WebP image format. Update ASAP.

Is it unfair to ask that future versions be zipped in a format that doesn't require buying a commercial product or run an emulator to unpack? I'm not a developer, so I'm not up on the intricacies of file archiving, but if the tool currently being used isn't compatible with standard Mac tools...

v117.0.5884.0 is the current version. The links here still provide the latest version. Be sure to read below about how to unzip the archive without the app throwing errors.

* HOW TO UNZIP: The unzipping of the ARM version of Chromium is a SPECIAL CASE. We covered it below in the comments. You CANNOT use Apple's default Archive Utility. The result will read as broken, with the only option being to Trash it. WHY? The problem is not just that the Chromium project isn't a certified Apple developer. Somehow the archives are created with a zipping tool strange to macOS, likely one made for Windows. - - INSTEAD use a THIRD PARTY unzipping app. I use Unarchive, (not 'The Unarchiver', which fails) that's part of Parallels Toolbox with total success. - - WHAT WORKS: (1) Better Zip (2) WinZIP (3) Unarchive - - What fails: (a) StuffIt Expander (b) Archiver (c) A-Zippr (d) UnRAR Expander (e) The Unarchiver. (f) Apple's Archive Utility - - There are likely other unzip apps that work. DIY test.

The ARM version posted on June 22, 2023 unzips to another executable file. I find myself curious if whatever version they compile runs before they zip the file or if they zip program they have breaks it.

The ARM version released on June 19th, 2023 unzips to yet another damaged file.

Yet another broken download. Unzips to a nonexecutable file.

ARM version is being flagged as damaged on MacBook Pro M1 Max Ventura (13.2.1)

ARM version is being flagged as damaged or incomplete on 2020 Mac mini M1 16/512 running latest Monterrey 12.6.2.

The BAD zip archiving of Chromium.app continues. I've submitted a detailed bug report to the project as I am sick of this nonsense.

ARM (Apple Silicon) version--> https://download-chromium.appspot.com/?platform=Mac_Arm&type=snapshots

Q: Are YOU running into trouble unzipping Chromium Apple Silicon archives? A: If you are, try different unarchiving apps that *aren't* Apple's Archive Utility. I don't know what's going on, but the very recent chrome-mac.zip archives, certainly for Apple Silicon, are showing up as strictly broken, according to macOS 12.5.1. (I am about to update to 12.6). At the moment, what I found actually worked as an unarchiver was "Unarchive" from Parallels Toolkit for macOS. Last time this happened (a few days ago, different version of Chromium) it was The Unarchiver app that worked. And yet it failed today. This is frustrating! I never have this problem with other zip files. So I have to point at the Chromium developer project as the source of this oddball problem. So :-P

The current version is 107.0.5272.0

The downloaded file is "Version 99.0.4775.0 (Developer Build) (x86_64)" - despite the fact it zip file has an ID of "98.0.4775.0"

The last Marmuduke build with all video playback codecs and ungoogled that still runs on pre macOS 11 (Big Sur) is Chromium v95.0.4638.69-r920003- is located here. https://github.com/macchrome/macstable/releases/ As of this date, his builds after 95.xx simply crash on startup, on Catalina and Mojave and presumably any macOS earlier. Marmuduke didn't seem particularly concerned or motivated to address this when responding to some inquiries. The issue IMO is not in the browser code per se but in the way the build is compiled, so those of you with the verve can always compile your own and compare the differences in the build flags used. Code and build flags are all at the same site I just mentioned.

Note that the DL link here points to a Development or beta build, AFAICT, not the "ungoogled" version. As such, you won't have all codecs neither. As for Marmaduke's current build (96.0.4664.45), he dropped support for pre 11 MacOS — I don't know if this is it's a temporary choice or a final decision... A few months ago I started using Brave instead, it's probably not as "ungoogled" as Chromium but it looks a very good alternative, and sometimes more stable.

I've been using Marmaduke's builds for years now and they usually work perfectly (some issue might arise with some not yet updated extensions, that's all). Only downside for the "ungoogled" version: it may be delayed quite a lot (currently 2 months and there's no sign there'll be a new one sometime...) Marmaduke seems to have switched his preference to the "sync" version, lately, probably easier to build. Still the fastest browser around!