A browser window with nothing in it but the thing you came for

The search for a distraction free browser almost always starts the same way. A page was opened for one reason, twenty minutes disappeared, and the obvious culprit is the software. So the next step is to look for a browser built to strip things away. Several exist, and installing one does change the feel of the first afternoon.

The change rarely survives a week, and the reason is structural. Most of what pulled attention away was not on the page. It was the other eighteen tabs sitting above it, and those move to the new browser on day one. Sorting out which of three separate problems is actually in play decides whether the fix is a new browser, a setting already on the Mac, or a different shape of window entirely.

Three different things are called a distraction

The word covers three layers, and each has a different fix. Applying the wrong one produces a week of effort and no change in behaviour.

The first layer is the page. Cookie banners, newsletter overlays, autoplaying video, a column of related articles running down the right side. This is the layer that content blockers and reader modes address, and they address it well. It is also the layer that matters least for anyone who spends the day inside a small number of work tools, because a task board and a shared inbox do not carry advertising.

The second layer is the browser itself. The tab strip across the top is a permanent list of every other thing that could be done instead. The address bar suggests destinations. The bookmarks bar is a row of buttons leading away from the current page. None of this is a defect. A browser is a tool for moving between places, and it is designed to make moving easy. That design is exactly wrong for the case where the goal is to stay in one place for three hours.

The third layer is everything outside the browser. Notification banners, a desktop covered in files, other applications visible behind the window, the Dock reacting to every background event. Changing browsers does nothing at all to this layer.

The layer that most people mean, and least often fix, is the second one. The rest of this article is mostly about that.

Why switching browsers usually does not hold

A browser marketed as focused or minimal starts from the same premise as every other browser: one window holds many destinations, and the interface exists to help move between them. A quieter version of that interface is still that interface.

The practical test is simple. Count the tabs open right now. Install any other browser, import the session, and count again a week later. If the number is similar, the browser was not the variable.

There is a second cost that gets underestimated. A browser is where sessions, saved passwords, extensions and the default handler for links all live. Moving to a second browser splits those across two places, which produces its own category of interruption: opening a link and landing in the browser where the account is not signed in. For some people the destination is worth the migration. For someone who simply wants one work tool to stop competing with nineteen others, it is a large change aimed at the wrong layer.

None of this is an argument against those products. It is an argument for identifying the layer first, because the cheapest fixes for layer two need no new browser at all.

A quick way to tell which layer is in play

Keep the browser open for one working day and note, each time attention moves, where it went. Three patterns show up, and each names its own layer. Landing on something else on the same page is layer one. Clicking a different tab, or typing into the address bar out of habit, is layer two. Leaving the browser entirely for a notification or another application is layer three. Whichever pattern accounts for most of the entries is the layer worth spending money and effort on, and it is frequently not the one that prompted the search.

One window, one site

The structural fix for layer two is to stop putting the site in a browser. Since macOS Sonoma 14, Safari can turn any page into a standalone web app through File then Add to Dock, and the result is not a browser window with the decorations turned off. It is a separate application.

Apple's documentation is explicit about how separate:

A web app functions independently of Safari. It shares no browsing history, cookies, website data, or settings with Safari. Source: support.apple.com

The same page describes the toolbar as streamlined, carrying a back button, a forward button, a Share button, and buttons belonging to any installed Safari extensions. There is no tab strip and no address bar. A new destination cannot be typed, because there is nowhere to type it. Moving to Safari proper requires the Share button and an explicit Open in Safari.

That last detail is the whole point. Layer two distraction is not a visual problem, it is an availability problem. A tab strip works because the alternative is one click away. Remove the mechanism and the click has to be replaced by a deliberate act, which is enough friction to change what happens by default.

The separate cookie store has a second effect worth naming. A work account signed into a service inside a web app does not collide with a personal account signed into the same service in Safari. Two accounts stop being a toggle and become two icons.

There is a third effect that only shows up after a few days. A standalone app gets its own entry in the Command Tab switcher and its own Dock icon, so the site becomes reachable by name rather than by position in a strip of favicons. Reaching it no longer requires passing the other nineteen destinations on the way. That is a small change per trip and a large one across a day, because the trip that never passes a distraction cannot be derailed by it.

What each fix actually removes

Approach	Removes page clutter	Removes the tab strip	Removes other apps	Cost
Reader mode or a content blocker	Yes	No	No	Free, built in
Full screen on a normal window	No	No	Yes, while it lasts	Free, built in
A different browser	Sometimes	No	No	A migration
Safari web app	No	Yes	No	Free, macOS Sonoma 14 or newer
Site to app tool	No	Yes	No	A tool, usually paid

The table makes the useful point on its own. No single row fixes all three layers, and the two rows that fix layer two are the two that most people searching for a distraction free browser never try. A realistic setup combines a row from the top of the table with a row from the bottom, not one row doing everything.

The layer three settings are already on the Mac

Everything outside the window is handled in System Settings under Desktop & Dock, and three of the options there matter more than their names suggest.

Stage Manager is described by Apple as a way to organise apps and windows so the desktop is clutter free. In practice it keeps one window in the centre and parks the rest at the edge, which suits a single app window far better than it suits a browser holding twenty tabs.

Show Items controls whether desktop files appear at all. Turning it off hides them until the desktop is clicked, which removes a surprisingly persistent source of drift for anyone whose download folder empties onto the desktop. Show Widgets does the same for widgets.

The Dock has its own contributions. Automatically hide and show the Dock returns the space and removes the row of icons from view. Animate opening applications and Show indicators for open applications both add movement at the bottom of the screen, and both can be turned off. Show suggested and recent apps in Dock adds icons nobody chose, and turning it off keeps the Dock to the list that was decided deliberately.

Automatically hide and show the Dock: Hide the Dock when you're not using it. To show the hidden Dock, move the pointer to the edge of the screen where the Dock is located. Source: support.apple.com

None of these need a download, and together they do more for layer three than any browser can.

Notifications belong to this layer too, and they are the one part that a window cannot fix from the inside. A site that is allowed to send alerts will interrupt whatever is on screen regardless of which window it lives in. Deciding that per site, when the permission prompt first appears, is more effective than deciding it later across a long list in System Settings. A focused window around a service that is permitted to shout every four minutes is still a focused window, and the day is still interrupted every four minutes.

Where the built in route stops

Safari's web app route is free and covers the common case, and its limits are worth knowing before building a whole day around it.

• It uses Safari's engine. A service that only supports a different engine will not work.
• Safari extensions carry into a web app. Extensions written for other browsers do not exist on this path.
• Web apps do not sync between Macs. A second machine means building them again.
• Each one is made by hand: open the page, type a name, accept whatever icon the site supplies.
• External links hand off to the default browser, which can pull a focused session straight back into the tab strip.

That last point is the one that undoes the work most often. A window built to hold one service is only as focused as its behaviour when a link inside it is clicked. A tool that turns a website into a standalone Mac app exists largely to give control over these five points: choosing the engine, deciding how external links open, and starting from a prepared name and icon rather than assembling each app manually.

The catalogue such tools ship with is itself a useful signal. More than 300 services are available as ready made presets, and the list on Supported services leans heavily toward tools that stay open all day, which is a fair description of the sites worth removing from a tab strip in the first place. What that adds over the built in route is set out on Features, and the build steps are on the Guide.

What to change first

Pick the one site that holds the most hours in a week and give it a window with no tab strip, using Safari's Add to Dock. Leave the browser exactly as it is for everything else, because the goal is not a quieter browser, it is fewer things that have to happen inside one. If that first window holds up for a week and the list of sites that deserve the same treatment grows, Kagemusha builds the rest from presets instead of one at a time.