Running Disney Plus as a standalone app on macOS: keep playing while you look something up

Anyone hunting for a Disney Plus app for Mac will find the answer faster on Disney's own supported devices page than in an app store. That page lists web browsers, then mobile devices, and under mobile devices it names Apple iPhones and iPads, Android phones and tablets, Amazon Fire tablet, and Windows 10 and 11 tablets and computers. Windows computers appear. Mac computers do not.

The App Store listing tells the same story from the other side. Disney+ lists compatibility for iPhone requiring iOS 16.5 or later, iPad requiring iPadOS 16.5 or later, Apple Vision requiring visionOS 2.0 or later, and Apple TV requiring tvOS 16.5 or later. There is no macOS entry.

Disney is direct about what that leaves. Under the heading that asks whether the service can be watched on a Mac, the help centre answers: "Disney+ is supported on the latest versions of Chrome, Firefox, Edge, and Safari on macOS 11 and newer." On a Mac, the product is the site.

Why that matters more on a laptop than on a television

On an Apple TV the absence of a Mac app is irrelevant. On a laptop it produces a specific, repeated annoyance: the video lives in a tab, and a tab is the one container that cannot be left alone.

The pattern is familiar. An episode is playing, then a question arrives. Which season was that character introduced in. What else has that actor been in. Whether the next film in the sequence is on the service at all. Answering any of those means using the browser, and the browser is where the video is. The tab either gets covered or gets scrolled out of view, and finding it again means reading a row of favicons that are all roughly the same size and colour.

The thing missing on macOS is not a native binary. It is a window that the browser cannot swallow.

That window is buildable, it takes about ten minutes, and macOS ships two ways to do it.

The route Apple ships

Apple's support document, "Use Safari web apps on Mac," describes the feature in its first line: "Starting with macOS Sonoma 14, you can use Safari to save any webpage as a web app, so that you can use it independently of Safari."

The procedure is three steps. Open the page in Safari, choose File then Add to Dock from the menu bar, or click the Share button and choose Add to Dock, then type a name and click Add. Apple notes the result "is saved to the Applications folder of your home folder, and you can also open it from the Dock or Spotlight."

What makes this worth doing for a video service is the isolation. Apple's wording is unambiguous: a web app "shares no browsing history, cookies, website data, or settings with Safari. In this way, it keeps your browsing separate, similar to using a Safari profile." The window holds its own login. Signing out of Safari does not sign out of the window, and whatever account Safari is signed into is irrelevant to it.

The toolbar is deliberately sparse. Apple lists back, forward, Share, and buttons belonging to installed Safari extensions. There is no tab strip and no address bar, which for a full-screen video is exactly right and for anything requiring navigation is occasionally limiting. Apple's escape hatch: click the Share button, then choose Open in Safari.

The window also has settings, reachable by clicking the app's name in the menu bar and choosing Settings. Apple lists Application Name, Application URL with a Set to Current Page button, a custom Icon chosen from any image file, whether navigation controls appear in the toolbar at all, and whether the title bar takes on the site's colour. A privacy tab exposes website data such as cookies and cache, and an extensions tab toggles Safari extensions for that window alone.

The route Chrome ships

Google's help page, "Use web apps," gives the Chrome path: open the site, then More, then Cast, save, and share, then Install page as app. On some sites an Install icon appears at the right of the address bar instead. Removing one runs through More then Uninstall, with an option to also delete the site's data from Chrome, and the whole set is listed at chrome://apps.

The difference from Safari's version is the cookie jar. A Chrome-installed app runs inside the Chrome profile it was created in, so it is signed in the moment it opens and signed in as whoever Chrome is. That is convenient on a single-account machine and unhelpful on a shared one.

Engine choice is the other difference, and Disney's documentation makes it concrete. The help centre names Chrome, Firefox, Edge and Safari as the supported browsers on macOS 11 and newer. A Safari web app plays through Safari. A Chrome-installed app plays through Chrome. Both are on Disney's supported list, so either works, but whichever browser already plays the service smoothly on a given machine is the sensible one to build from rather than the one that happens to be open.

Comparing the three routes

	Safari Add to Dock	Chrome Install page as app	Site to app tool
Requirement	macOS Sonoma 14 or later	Chrome installed	macOS 12 or later
Playback engine	Safari	Chrome	Chrome, Canary, Chromium, Brave, Edge, Vivaldi or Opera
Login separate from the browser	Yes	No, shares the Chrome profile	Yes, own profile per app
Toolbar control	Navigation controls on or off	Fixed	Tab bar and address bar on or off per app
Icon	Any image file	Site favicon	Preset, uploaded image or fetched favicon
Cost	Free	Free	Free for up to three apps

For one window, the free routes are the answer and there is nothing to think about. The calculation changes at three or four, where naming, icon hunting and signing in stop being a novelty. That is the point at which a site to app tool starts to pay for the time it takes to learn, and the preset list, which already includes Disney+, is visible on Supported services.

Making the window actually stay out of the way

A standalone window solves the tab problem. Two further settings decide whether it solves the interruption problem, which is the one in the title.

Position is the first. A window can be parked on a second display, or sized to a corner and left half visible while a browser takes the rest of the screen. Neither is possible for a tab, which is bound to the frame of the browser holding it. Mission Control treats the window as its own item, so the four-finger swipe reaches it directly.

Power behaviour is the second, and it is the most common cause of playback that stops when attention moves elsewhere. Browsers put inactive tabs to sleep to save memory, and operating systems throttle background processes to save battery. Other streaming services document this plainly. radiko, a Japanese service in the identical position of having no Mac app, instructs people whose playback stops in the background to review the machine's power-saving settings and to exempt the site from the browser's own tab-sleeping feature. The same two places are worth checking on a Mac before concluding that the window itself is at fault.

Notifications are the third and are optional. Apple's documentation notes that a web app's Dock icon can display the number of unread notifications, and that the permission has to be granted inside the web app rather than in Safari for the window to appear in the Notifications list in System Settings. For a streaming service that is of limited use. For the mail or chat window built next to it, it is the entire reason to bother.

Profiles, households and the second account

Disney's supported devices page lists a wide set of screens, and households tend to use several of them with different profiles. On a Mac, the browser can only hold one signed-in session per profile, which is why a second account means a private window that forgets everything on close.

Isolation fixes that, and it is worth being precise about which route provides it. Apple states that a Safari web app shares no cookies or website data with Safari. A site to app tool goes further and gives each app its own browser profile, so cookies, sessions, history and cache are separate between apps rather than just separate from the browser. Chrome's installed apps do neither, since they live inside the Chrome profile.

The practical result of the isolated routes is two windows, two accounts, both permanently signed in. What that does not change is how many streams a plan allows, which is set by the subscription and not by the desktop. The plan page is the place to confirm that before assuming a second window means a second simultaneous viewer.

What the window does not add

A standalone window changes where the video sits. It does not change what the service allows, and three limits survive the move intact.

Offline viewing is the clearest. Disney's plan descriptions list downloading titles to a supported device for on-the-go streaming, and the supported devices doing the downloading are the phone and tablet apps. A window built from the site streams, because the site streams. An episode for a flight still means a tablet.

Device support is the second. The supported devices page is a long list, covering Fire TV, Apple TV from the fourth generation onward, Chromecast, PlayStation, Xbox, Android TV, several smart television brands, Audi and BMW vehicles, Apple Vision Pro and Meta Quest, plus HDMI and AirPlay as ways to reach a television. A Mac window joins that list as a browser destination, not as a new class of device, so anything conditioned on the native app stays conditioned on the native app.

Account limits are the third, and the most commonly misread. Streams are counted by the subscription. Building a second window on the same machine produces a second place to sign in, not a second entitlement. Reading the plan page before setting up a household arrangement saves an argument later.

Choosing which sites deserve the treatment

Building one window takes ten minutes. Building nine is a habit, and a habit needs a threshold.

The threshold that survives contact with a real week is frequency multiplied by session length. Something opened once a month belongs in a bookmark. Something opened five times a day, or opened once and left running for two hours, belongs in a window, because those are the two patterns where a tab strip costs measurable time. Streaming sits in the second pattern. Mail, calendars, chat and whatever internal dashboard a job involves sit in the first.

The second half of the threshold is whether the vendor already ships a desktop app. When one exists, it is the better object: it updates itself, it registers for notifications under its own name, and someone else maintains it. Building a window is for the other case, and Disney+ on macOS is squarely in it, with apps for phones, tablets, televisions, headsets and cars, and a browser for the desktop. The Guide covers the build, which is short enough that testing the idea on a single site costs almost nothing.

What to change first

Open Disney+ in whichever of Chrome, Firefox, Edge or Safari already plays it cleanly, then build the window: File then Add to Dock in Safari on macOS Sonoma 14 or later, or More then Cast, save, and share then Install page as app in Chrome. Check the power settings before deciding whether background playback is broken. If one window turns into several and the engine or the per-app login starts to matter, Kagemusha builds them from presets instead of by hand, and the common questions are answered on the FAQ.