Fluid on a modern Mac: what still works

Fluid still downloads, still installs, and still turns a URL into an app with its own Dock icon. On a Mac bought in the last few years, though, it runs only through Rosetta 2, and Apple has now published the release after which that stops. So the honest answer to "does the Fluid app work on a Mac" is: yes, for now, with a known end date. The rest of this page covers what the current build does, how long it can keep doing it, how to check the copies already installed, and which routes replace it on macOS 26 and later. All official pages cited below were checked on October 18, 2026.

This site is published by the developer of a site to app tool for macOS, which is one of the routes compared further down.

What the current Fluid build actually is

The Fluid home page still describes the same three-step idea it has used for years: enter a website's URL, give it a name, optionally choose an icon, and click Create. The result is a separate application that appears in the Dock and in Command Tab, opening only that site.

The same page lists the current download as version 2.1, a 6.3 MB download that requires Mac OS 10.12 or later, with a copyright line dated 2019. The page still uses the phrases "Mac OS X Status Bar" and "OS X desktop apps", which tells you how long it has been since the copy was touched.

The Fluid changelog gives more detail than the home page. The top entry is 2.1.2, a single fix for bookmark clicks. Version 2.1 added support for Mojave Dark Mode, which places that release in the macOS 10.14 era. Version 2.0 was described as a significant rewrite on Apple's WebKit2 API with process separation. There is nothing newer than 2.1.2 on that page.

Free versus the $5 license

The pricing has never been the problem. The home page states that Fluid is free and that you can create as many Fluid Apps as you like. A $5 license unlocks three extras, and only three:

• Pinning a Fluid App to the status bar
• Userscripts and userstyles inside an app
• Full screen mode

That list matters for migration. If any of your old apps depend on a userscript, that is the one piece of setup that will not carry over automatically, so note it before you delete anything.

Why the engine is less of a worry than the shell

Because 2.0 was built on WebKit2, the pages inside a Fluid App are drawn by the WebKit that ships with macOS. Apple patches that engine with every system update, so the rendering is not frozen in 2018. What is frozen is the container around it: the menus, the preferences, the way it handles downloads, pop-ups, and links. When a site changes its login flow or a macOS release changes an API, nobody is shipping a fix for that layer.

The Apple silicon problem and the Rosetta deadline

The compatibility index Does It ARM lists Fluid 2.1.2 with x86 as its only supported architecture and marks it as not reported native to Apple silicon. Every Mac Apple currently sells uses Apple silicon, so on any recent machine Fluid runs through Rosetta 2, the translation layer.

For a web wrapper, Rosetta's speed cost is barely noticeable. The issue is time. On September 1, 2026, Apple posted Rosetta support for Intel-based macOS apps with two dates that settle the question:

• macOS 26.4 or later: users may receive a system notification when launching an app that relies on Rosetta, telling them to update to an Apple silicon version.
• macOS 27: the final release to support Rosetta. Intel-only apps will no longer run on Apple silicon Macs after that update.

The only stated exception is older, unmaintained games that rely on Intel-based frameworks. A site wrapper is not in that group.

What that means in practice

If you are on macOS 26.4 or later and launch a Fluid App, the notification described above is expected behavior, not a bug. The app will keep opening through the macOS 27 cycle. After that, unless a native build appears, it will not launch on Apple silicon at all.

Given that the newest changelog entry is a minor fix from the Mojave era, planning a daily workflow around a native release arriving in time is a bet with nothing behind it. Using Fluid for a quick test this week is fine. Moving a set of work tools onto it is a decision you would have to undo within a year.

Intel Macs are a separate case

On an Intel Mac, Fluid runs natively and Rosetta is not involved. The Apple notice is about Apple silicon. The limit on an Intel Mac is different: it is the last macOS version that machine can install, and how long sites keep supporting the WebKit that comes with it.

How to check the apps already in your Applications folder

If you built Fluid Apps years ago, they are probably still there. There is no need to guess which of them, or which other old utilities, will stop working. macOS shows the architecture of every application.

Finder

1. Select the app in the Applications folder.
2. Choose File, then Get Info.
3. Read the Kind line near the top. "Application (Intel)" means it needs Rosetta. "Application (Universal)" or "Application (Apple silicon)" means it runs natively.

Activity Monitor

With the app running, open Activity Monitor from Applications, then Utilities. If there is no Kind column, right-click any column header and turn it on. Each process is labeled Apple or Intel. This is the quickest way to see everything that is currently going through translation, not only the Fluid Apps.

Terminal

For a batch check, run lipo -archs against the executable inside a bundle, for example the file in Contents/MacOS of an app. An output of x86_64 alone means there is no Apple silicon code in it.

Do this once for the whole folder. Old wrappers tend to sit next to old menu bar utilities and old installers from the same period, and the macOS 27 cutoff applies to all of them at the same time.

Moving off Fluid without losing anything

Fluid Apps hold very little. There is no document format and no local database to export. What each one contains is a URL, a name, an icon, a login session, and, for licensed users, possibly a userscript or userstyle.

A five-minute migration per app

1. Open the Fluid App and note the home URL from its preferences.
2. If you set a custom icon, find the original image file, or plan to use the site's own icon.
3. If the app uses a userscript or userstyle, copy its contents into a text file.
4. Build the replacement with one of the routes in the next section.
5. Sign in again inside the new app. Sessions do not move between containers.
6. Quit the old Fluid App and drag it to the Trash.

What does not carry over

Two things need attention. The first is userscripts, which only some replacements support. The second is any app you pinned to the status bar, because the free routes built into macOS and Chrome do not offer a menu bar mode. If either matters, check that the replacement supports it before you delete the original.

The replacement routes, compared

There are three realistic directions on a current Mac: Safari's built-in web apps, Chrome's installed web apps, and a dedicated site to app tool. The table uses official pages where they exist.

	Fluid 2.1.2	Safari, Add to Dock	Chrome, Install page as app	Dedicated site to app tool
Price	Free, $5 for three extras	Free	Free	Free tier, then paid (varies)
Runs natively on Apple silicon	No, Rosetta only	Yes	Yes	Yes, for current tools
Minimum macOS	10.12	Sonoma 14	Any supported Chrome	Varies by tool
Separate cookies from your browser	Yes, its own container	Yes	No, uses the Chrome profile	Usually one profile per app
Notifications	Not documented	Yes, with Dock badge	Yes	Usually yes
Status bar or menu bar mode	Yes, with license	No	No	Some tools
Browser extensions	No	Safari extensions only	Chrome extensions	Some tools
Still updated	No release since 2.1.2	With macOS	With Chrome	Depends on the developer

Safari web apps

Apple's guide Use Safari web apps on Mac says the feature is available from macOS Sonoma 14, and that a web app shares no browsing history, cookies, website data, or settings with Safari. It can have any name or icon, and for sites that send notifications the Dock icon can show an unread count. To create one, open the site in Safari, choose File, then Add to Dock (or use the Share button in the toolbar), type a name, and click Add. The new app is saved to the Applications folder inside your home folder, as described in Turn a website into an app in Safari on Mac.

For most people leaving Fluid, this covers the core job at no cost, and it will not be affected by the Rosetta cutoff.

Chrome installed apps

Google's help page Use web apps describes the path: open the site in Chrome, open the More menu, choose Cast, save, and share, then Install page as app. The installed app lives inside the Chrome profile that created it, so it shares that profile's sign-ins and extensions. That is useful if the site needs a Chrome extension. It is a limitation if you need a work account and a personal account of the same service open at once.

A dedicated tool

The paid routes exist for the rows the free ones leave empty: a separate profile per app, extensions turned on per app, a menu bar or sidebar mode, and grouping several services into one window. Whether any of that matters depends on the sites. The feature list and the supported services directory are a quick way to see whether a specific site is already set up with its icon and URL.

Which sites deserve their own app

The tool comparison gets much shorter once the list of sites is decided. A site earns a separate app when most of these are true:

• It is opened every working day.
• It does one job, so there is no reason to navigate away from it.
• It sends something time-sensitive, like messages or alerts.
• Finding it in a row of tabs costs real time several times a day.

Mail, a team chat, a calendar, and sometimes one admin dashboard usually pass. A site opened twice a month is a bookmark. A site used for research, where following links outward is the point, is worse in a window with no address bar.

Account separation decides the route

The other filter is accounts. If the same service is used with a work login and a personal login, each app needs its own cookie store. Safari web apps keep cookies apart from Safari itself. Chrome installed apps follow their profile, so two accounts need two profiles. Tools that give each app its own profile handle it without extra setup. The setup guide walks through creating that kind of app step by step.

What to change first

Run the Finder check on your Applications folder today, then rebuild the one Fluid App you open most with Safari's Add to Dock. Live with it for a week before deciding whether a menu bar mode, per-app extensions, or separate profiles are worth paying for, and if they are, Kagemusha lists its plans and limits openly.