YouTube in its own window on a Mac

There is no official YouTube application for macOS. Google ships one for Android and iOS, and for televisions, and for nothing in between. On a Mac, YouTube is a website, which is why searching for a youtube web app for mac returns a mix of unofficial wrappers, browser tricks, and forum threads that end without a conclusion.

The good news is that the browser tricks are not tricks anymore. Both Safari and Chrome can turn a page into a standalone application window with a Dock icon, and the result behaves like an app in every way that matters for daily use. The question is which of those routes to take, and whether the thing being solved is actually the missing app or something else. For a lot of people the real complaint is not that YouTube lacks a window. It is that YouTube shares a window with work.

What a standalone window actually gives YouTube

A YouTube tab is one of forty. It has no icon, no separate entry in Command Tab, and no way to be positioned on a second display and stay there. Closing the browser closes it. Restoring the session restores it in a random position among everything else.

A standalone window fixes all of that mechanically. It appears in the Dock with its own icon. It survives a browser restart. It can be moved to a second monitor, or a dedicated desktop in Mission Control, and macOS will put it back there. Media keys on the keyboard target the window that is playing rather than whichever tab last had focus, which alone removes a recurring source of confusion when three tabs are all capable of playing audio.

There is also the matter of the chrome around the page. A web app window has no tab bar, no address bar, and no bookmarks. That sounds cosmetic until the effect on behavior is measured against a normal window: without an address bar there is nowhere to type a different destination, so the window stays a video window rather than becoming another general purpose browser that happens to be open.

Video playback itself is unchanged. Picture in Picture works. Full screen works. Playback continues when the window is behind other windows, which is already true of any desktop browser and is the reason the mobile restriction on background playback does not apply here.

The four routes, compared

Route	Requirement	Session storage	Update behavior
Safari, Add to Dock	macOS Sonoma or later	Separate from Safari	Follows the live site
Chrome, install page as app	Recent Chrome	Shared with the Chrome profile	Follows the live site
Unofficial wrapper app	Download and trust a third party	Inside the wrapper	Depends on the developer
App aggregation browser	Install once, all apps	Per app container	Follows the live site

Safari's route is the most native. From the menu bar, File then Add to Dock creates a web app that is stored in the Applications folder inside the home directory and can be launched from the Dock or Spotlight. Apple documents that the resulting web app keeps its own data.

A web app works separately from Safari. It does not share browsing history, cookies, website data, or settings with Safari. Source: support.apple.com

That last part has a consequence people run into immediately: the new web app starts signed out, and the Google account has to be signed in again inside it. That is inconvenient once and useful afterwards, for reasons covered below.

Chrome's route is faster and shares the profile's existing login, so the window opens already signed in. The trade is that it is not really separate. It is the same profile in a different frame, so history, cookies, and extensions are shared with every other Chrome window.

Unofficial wrapper applications exist and some are well made, but they carry an ongoing dependency on a single developer for security updates to a browser engine. That is a heavier commitment than the built in routes require.

The account problem hiding behind the app problem

A large share of people looking for a YouTube app on a Mac are not chasing a window. They are chasing a clean account boundary. A company Google account and a personal one, or a channel managed for a client and a personal watch history, end up mixed because YouTube inherits whichever Google session the browser is already carrying.

The visible symptom is the recommendation feed. Research watched for work seeds the home page for weeks, and personal viewing shows up while screen sharing. Switching accounts inside YouTube does not fully solve it, because subscriptions, history, and Watch Later belong to the account that was active when each action happened, and it is easy to be signed into the wrong one without noticing.

Separation has to happen at the storage layer, not inside the site. Two containers, each with its own cookies, is the only arrangement that holds. A Safari web app is such a container. A second Chrome profile is another. A browser that keeps each web app in its own window treats every app as a container by default, which is the same mechanism that lets two Slack workspaces or two mail accounts coexist without switching. Which services are commonly arranged this way is listed under supported apps.

Where a window helps concentration and where it does not

Moving YouTube out of the tab strip has an effect on attention, and it is worth being precise about the size of that effect. Removing YouTube from the same window as documents means it is no longer one click away during a task, and the extra step of switching applications is enough to stop the reflexive check. That is a real gain.

What a window does not do is remove the recommendation engine. Opening the app still lands on a feed engineered to produce a second video. If the goal is fewer accidental hours, a window alone is insufficient. Two additional settings do more: turning off watch history, which empties the recommendation feed, and using a subscriptions view as the launch page instead of the home page.

For anyone whose YouTube use is genuinely work, such as tutorials or competitor research, the opposite adjustment is better. Keep history on, keep it in an account used only for that purpose, and let the feed become a research tool. That only works if the account is separate, which brings the question back to containers. Grouping the apps that belong to one kind of work, and keeping them out of the windows belonging to another, is the idea behind workspaces.

Media keys, Picture in Picture, and the second screen

Three behaviors change once YouTube stops being a tab, and each one removes a specific daily annoyance.

Media keys stop being ambiguous. With several tabs capable of playing audio, the play and pause keys on the keyboard target whichever one macOS last decided was the active media source, which is frequently not the one making noise. A standalone window is a distinct application, so the keys act on it predictably, and pausing does not require finding the tab first.

Picture in Picture becomes practical rather than fragile. The floating player can be detached from the window and kept on top while other work happens, and because the source window is a separate application it can be sent behind everything else without being closed. In a tab, the same maneuver risks the tab being closed later by a cleanup that had nothing to do with the video.

Position on a second display finally persists. macOS remembers where an application's windows belong. A video window parked on the right hand monitor returns to the right hand monitor after a restart. A tab has no position of its own, only the position of the browser holding it, so a multi monitor setup has to be rebuilt by hand every time.

There is a fourth, quieter change: full screen video no longer takes the browser with it. Sending a tab to full screen commandeers the whole browser window and everything in it, which is why exiting full screen often lands somewhere unexpected. A dedicated window goes full screen as itself, and the rest of the working set stays where it was.

Practical setup notes

A few details save time. Name the web app something short, because the name shows under the Dock icon and in Command Tab. Sign in inside the new window before assuming the setup failed, since a fresh container will look logged out even though the browser next to it is not.

If notifications from YouTube are not wanted, deny them at the first prompt inside the new app rather than later, because a standalone web app has its own entry in System Settings and its own permissions to manage.

Full screen behaves like any other application, so a dedicated desktop for a video window is possible and persists. And if the machine is short on memory, remember that a standalone window is still a full browser process. Four web apps open all day cost roughly what four heavy tabs cost, not less.

Two more details are worth knowing before committing. Extensions do not carry over the same way in every route: a Safari web app runs without the extensions that a normal Safari window has, while a Chrome installed app inherits the extensions of the profile it came from. Anyone relying on an ad blocker or a playback speed extension should check this before deleting the old tab, because the behavior inside the new window can differ noticeably from what the browser was doing a minute earlier.

The other detail concerns links. Clicking a YouTube link from mail or chat will open it in the default browser, not in the web app, unless the operating system has been told otherwise. In practice the video window becomes the place for deliberate viewing, and incoming links keep arriving in the browser. That split is usually acceptable, but it surprises people who expected the app to capture every YouTube URL on the system.

What to check after a week

A setup that looks correct on day one can still be wrong on day seven, and there are three specific things worth revisiting.

The first is whether the window is being used or being ignored. If the browser tab habit returned within a few days, the window is not solving a real problem and the honest answer is to delete it rather than maintain it. The second is whether the account inside it is the intended one, because signing in during setup while distracted is common and the watch history will show it. The third is whether the window is now competing with the browser for the same job, which happens when general browsing starts leaking into it.

If two or three more services are heading for the same treatment, that is the point where per site setup stops paying for itself and the arrangement is better handled once, at the level of the browser rather than the site. The trade-offs between doing that with a paid tool and an open source one are laid out in the comparison with Ferdium.

What to change first

Create the window with Safari's Add to Dock and sign in with the account that should own the watch history, since that single choice decides what the feed looks like for the next several weeks. If the same separation is needed for mail, chat, and a calendar as well, setting it up one site at a time stops being worth it, and drawing the boundary once at the browser level is the cheaper path, which is what SpaceDeck does by default.