Putting Netflix in the Dock, out of the browser

Searching for a Netflix Mac app produces a strange result. Netflix has an app on iPhone, on iPad, on Android, on Fire tablets, on every television sold in the last decade, and on Windows. On a Mac, the answer is a browser tab, and it has been a browser tab for years.

That leaves two separate questions tangled together. The first is whether a Netflix window can be made to behave like an application on a Mac, which it can. The second is what that window costs, and here the answer is more specific than most advice admits: on a Mac, the browser engine behind the window sets the maximum picture quality, and Netflix publishes the numbers.

What Netflix ships, and for which computers

Netflix's own requirements page is direct about the computer story. It opens by saying an account can be created and Netflix watched "using one of the below web browsers on your computer," and lists Chrome, Edge, Firefox, Opera and Safari. For a Mac it then sets a floor: macOS 10.15.5 or later.

The contrast with Windows is instructive rather than a complaint. Netflix's Windows help page describes a Netflix app for Windows 10 and later, installed from the Microsoft Store, and notes that the app requires the Microsoft Edge browser to be installed. Even the one desktop application Netflix does ship is a browser engine with a different name on the window.

That is the useful frame for a Mac. Nothing is being withheld that exists elsewhere in a fundamentally different form. The question is not how to get a missing application, it is which window to run the website in, and macOS has had a built in answer since Sonoma.

A Netflix window on a Mac is always a browser window. The only decision is which engine is inside it and whether the browser furniture is visible.

The window decides the picture quality

This is the part that changes the recommendation, and it comes straight out of Netflix's requirements table for Mac.

Browser	Minimum version	Maximum video resolution on a Mac
Safari	14 or later	Up to Ultra HD (2160p)
Chrome	117 or later	Up to Full HD (1080p)
Firefox	129 or later	Up to Full HD (1080p)
Opera	92 or later	Up to Full HD (1080p)
Edge	118 or later	Up to HD (720p)

Netflix adds conditions to the top row. Safari 14 requires macOS 11 or later, watching in Ultra HD requires macOS 11 or later plus hardware that meets Netflix's separate Ultra HD requirements, and Macs on macOS 10.15 play up to Full HD regardless. Live events on Netflix require Safari 15 or later.

The consequence for anyone building a standalone window is easy to miss. A window built with Chrome's install feature is a Chrome window, so it sits on the 1080p row. A window built with Safari's Add to Dock runs on WebKit, which is the engine on the 2160p row. Someone who pays for the 4K plan and builds the Netflix app out of Chrome has quietly capped the thing they are paying for, and nothing on screen announces it.

Worth stating the limit of that reasoning honestly. Netflix publishes these ceilings by browser, not by standalone web app, and the 4K path also depends on the hardware conditions above. Whether a given Mac actually reaches 2160p in a Safari web app is something to confirm on the title's details page, which Netflix says carries a video quality label showing the quality a title will play at on the device being used. Build the window, open a title known to be available in 4K, and read the label before deciding the experiment worked.

Two ways to build the window

Both are free and both take under a minute.

Apple's route arrived with macOS Sonoma 14. Open netflix.com in Safari, then choose File > Add to Dock from the menu bar, or use the Share button and choose Add to Dock. Name it, click Add, and the app lands in the Applications folder inside the home folder, reachable from the Dock and from Spotlight. Apple describes the result as functioning independently of Safari, with a streamlined toolbar holding back, forward and Share buttons.

Chrome's route is the same idea from the other engine. With netflix.com open, the menu at the top right leads to Cast, save, and share, then Install page as app. Google notes that some sites also offer an Install icon directly in the address bar. Installed web apps are managed at chrome://apps, and uninstalling offers to delete the site's data from Chrome at the same time.

For Netflix specifically the Safari route has a second advantage beyond the resolution table, and it is about what the window knows. Apple states that a Safari web app "shares no browsing history, cookies, website data, or settings with Safari." A Netflix app built this way signs in once, on its own, and stays signed in to whichever profile was chosen, independent of whatever the browser is doing. For a service where signing out of one place tends to sign out of others, a window with its own session is the quieter arrangement.

The cost of that isolation is the first launch. The Netflix session already open in Safari does not carry over, so the new app asks for the email address and password once, and the profile picker appears the way it does on a new device.

What the window still will not do

Two limits survive every route, and knowing them in advance saves an evening of trying to fix something that is not broken.

The first is downloads. Netflix's help page on watching offline lists the devices that support it: Android phones and tablets, iPhone and iPad, Amazon Fire tablets, and Google Chromebooks with the Play Store installed. A Mac is not on that list, in any browser, in any window. A standalone Netflix app on a Mac does not add offline playback, because offline playback is a feature of the Netflix mobile app rather than a feature of the window.

The second is the engine requirement. Netflix streams protected video, and playback depends on the window's engine supporting the content protection system Netflix uses. The two routes above both inherit a supported engine, which is why they work. A window built on some other engine is a different situation, and the correct test is not a trailer or the homepage but a full title that plays for several minutes. If a tool offers a choice of engine, this is the site where that choice has consequences rather than preferences.

Neither of these is an argument against building the window. They are the two things that a Dock icon does not change, stated up front so that the window gets judged on what it actually does.

What actually improves

With those limits named, the gains are real and they are mostly about attention.

The window has no tab strip and no address bar, so Netflix stops being one entry in a list of thirty things and becomes a place that is either open or closed. Cmd+Tab reaches it directly. The Dock icon can be given a name and an icon, and Apple documents changing both from the Settings panel inside the web app, along with the URL the app opens, whether navigation controls are shown, and whether the title bar takes its colour from the site.

Closing the browser no longer closes Netflix, and quitting Netflix no longer means hunting for the right tab among many. On a Mac used for work during the day, that separation has a second effect worth more than it sounds: the thing that was one keystroke away inside the browser now requires a deliberate launch.

Full screen behaves better too, because a window with no browser interface has nothing to collapse. What is on screen when the video expands is the video, rather than the video plus whatever the browser was showing a moment before.

Apple also documents adding a web app as a login item so that it opens automatically at sign in, and deleting one by dragging it from the Applications folder in the home folder to the Trash. Both are worth knowing before building several, because a window that is trivial to remove is a window that can be tried without commitment.

When playback fails in the window

Netflix playback problems usually trace back to one of three things, and a standalone window makes two of them easier to handle.

The first is stale site data. Apple's Settings panel for a Safari web app includes a Privacy tab that clears that app's website data, including cookies and caches, which is the standard Netflix troubleshooting step without signing out of anything else on the Mac. In a browser the same action tends to take other sites down with it.

The second is the version floor. Netflix requires specific minimum browser versions, and the window inherits its version from whatever is underneath: macOS for a Safari web app, Chrome for an installed Chrome app. A Mac held back on an older macOS release is held back in the window too, and the requirements table is where to check the number rather than guessing from the symptom.

The third is the account itself, such as a plan that does not include the resolution being expected or a device limit already in use elsewhere. That one is unrelated to the window and no amount of rebuilding will move it.

Household profiles

A Netflix account holds several profiles, and the window remembers the one last chosen. Because Apple states a Safari web app keeps its own cookies and website data, two such windows can sit in the Dock holding two different profiles, which removes the profile picker from the start of every session. That is a small thing on a personal Mac and a noticeable one on a shared machine where the last person to watch decided what the next person sees first.

Which one to build

For anyone on a plan that includes 4K, on macOS 11 or later, Safari's Add to Dock is the route that matches Netflix's own numbers, and it is the one that gives the window its own sign in. For anyone on a 1080p plan who already lives in Chrome and wants the profile and extensions that come with it, the Chrome route costs nothing in picture quality that the plan was going to deliver anyway.

For anyone building a second and third window after this one, for a mail service or a task board or a music service, the repetition is the argument. Each window built by hand means opening the page, naming it, choosing an icon, signing in, and deciding about notifications, and none of those steps is difficult on its own. Building them from a prepared list instead of one at a time is what a site to app tool is for, and the Guide covers the settings that matter once there is more than one.

What to change first

Build the Netflix window in Safari, sign in once, and open a title that is available in 4K to read its quality label before deciding anything else. Leave the browser exactly as it is for everything else. If the window holds up for a week and the next three sites deserve the same treatment, Kagemusha builds those from presets rather than by hand.