YouTube Music app on Mac: the four containers that exist

Google does not publish a YouTube Music app for macOS. As of October 18, 2026, the YouTube Music listing on the App Store states compatibility with iPhone, iPad, and Apple Watch, and nothing else. On a Mac, the product is the web player at music.youtube.com. So the useful question behind a search for a youtube music app mac is not where to download it, but which container to put that web player in. Four kinds of container exist: an install from the browser itself, a community desktop client built on Electron, a small native wrapper built on WebKit, and a site to app tool that builds on a browser already on the Mac. They play the same music. They differ in accounts, extensions, updates, and how much trust they ask for.

This site is published by the developer of a site to app tool, which is one of the four options covered below.

What Google actually ships for the Mac

The web player is built to be installed, and the evidence is in its web app manifest. The manifest file served by music.youtube.com, checked on October 18, 2026, declares the name YouTube Music, the short name YT Music, a black background, and a start URL ending in source=pwa, which lets Google tell installed launches apart from ordinary tabs. It lists icons from 48 to 512 pixels, including maskable versions at 192 and 512.

The display mode it requests is minimal-ui, not standalone. That one value explains a common complaint. When the page is installed from Chrome, a thin strip with navigation controls stays at the top of the window. That strip is the site asking for it, not a fault in the install.

The manifest also lists related applications for Android and sets prefer_related_applications to true. On a phone, that steers people to the store app. On a Mac there is no store app to steer to, so the web player is what remains.

Two practical consequences follow. First, every container in this article runs the same page, so the library, the queue, recommendations, and sound quality are identical across them. Whether ads play is decided by the Google account, not by the window around it. Second, anything that claims to be a better YouTube Music app for Mac is really offering a better window: separate sign in, real media keys, protection from an accidental Cmd+W, or extra features layered on top of the page.

Container one: install it from the browser

This is the zero cost route and the fastest one. Two browsers on the Mac offer it.

Chrome

Chrome Help describes the steps as: open the site, then at the top right choose More, then Cast, save, and share, then Install page as app. On some sites an Install button also appears at the right end of the address bar. Because the YouTube Music manifest is complete, the name and icon fill themselves in. Installed web apps can be managed at chrome://apps, and uninstalling is done from More inside the app window, where the option to also delete data from Chrome appears.

The limit is identity. The installed app belongs to the Chrome profile that created it. Signing out of Google in that profile signs the music app out too, and the extensions in that profile come along with it.

Safari

Apple's support article on Safari web apps gives the steps for macOS Sonoma 14 or later: open the page, choose File, then Add to Dock (or use the Share button), type a name, and click Add. The app is saved to the Applications folder inside the home folder and opens from the Dock or Spotlight.

The difference that matters for a music service is isolation. Apple states that a web app "shares no browsing history, cookies, website data, or settings with Safari." The music app keeps its own Google session, so the browser can switch accounts freely. The trade is extensions: a Safari web app can only use Safari extensions, enabled per app from the Extensions tab in its Settings, and Chrome Web Store extensions do not apply.

Container two: a community desktop client

Two open source desktop clients built on Electron are the best known. Both are independent projects, not Google products.

Pear Desktop

The project long known as th-ch/youtube-music now lives at pear-devs/pear-desktop on GitHub under the name Pear Desktop. Checked on October 18, 2026, it is MIT licensed, has about 33,800 stars, and its latest release is v3.12.0 from June 28, 2026. The README documents a Homebrew install with brew install pear-devs/pear/pear-desktop. It also documents a fix for the "is damaged and can't be opened" message after a manual download, which is to clear extended attributes with /usr/bin/xattr -cr on the app.

The README is direct about its status: the project "and its contributors, are not affiliated with, authorized by, endorsed by, or in any way officially connected with Google LLC, YouTube, or any of their subsidiaries or affiliates." What it offers in return is a plugin system with features the web player lacks.

YTMDesktop

The YTMDesktop repository is GPL 3.0 licensed, has about 6,600 stars, and published v2.0.12 on September 8, 2026. For the Mac, the README points to the GitHub release files and to a Homebrew cask, ytmdesktop-youtube-music, which it marks as community maintained.

What this container costs

Electron apps bundle their own copy of Chromium, so each one is a separate browser engine on disk and in memory, updated on the project's schedule rather than with the browser. The Google sign in lives inside an unofficial application. For many people that is a fair trade for the extra features. For a work Mac with managed accounts it may not be.

Container three: a native WebKit wrapper

A smaller category sits between the two. youtube-music-macos by 0xjemm is a Swift app that wraps the web player in WebKit rather than Electron. Checked on October 18, 2026, it has about 60 stars, an MIT license, and a latest release of v1.1.0 from May 27, 2026.

Its README lists media key support, Now Playing integration in Control Center with album artwork, Discord Rich Presence, and a frameless window. It requires macOS 14 Sonoma or later. Installation is by Homebrew tap or a manual download, and in both cases the README tells the user to run xattr -cr on the app, describing this as "required for unnotarized apps."

That last point is the real decision. Running xattr -cr removes the quarantine flag that lets Gatekeeper check the app, and the README says the build is not notarized by Apple. That is common for a small hobby project and not a sign of anything wrong, but it means the trust decision moves from Apple's check to the reader. The app is light and feels native. The project is also maintained by a single account with a small following, so the pace of fixes is worth checking on the releases page before relying on it.

Container four: a site to app tool on the browser already installed

The fourth option keeps a Chromium browser that is already on the Mac, such as Chrome, Brave, or Edge, and builds a separate app around one site. The approach differs from the Chrome install in one central way: each app gets its own browser profile. Cookies, sign in, history, and cache are separate from the main browser and from every other app.

For YouTube Music, a typical tool of this kind works like this, using the screen names from its guide:

1. Click Create New in the left sidebar.
2. Type "YouTube Music" in the search field and select it from the preset list. The URL, the official icon, and the app name are filled in.
3. Under Browser Engine, choose a browser that is already installed.
4. Click Create App. The app is saved to a folder inside Applications.
5. In App Manager, click Launch and sign in with the Google account meant for music.

Two settings are worth turning on for a music player. Quit Confirmation shows a dialog when Cmd+Q is pressed, which stops an accidental quit in the middle of a playlist. Show in Dock is on by default and keeps the app reachable with Cmd+Tab. Chrome Web Store extensions can be switched on per app, so an extension wanted for music does not have to run everywhere else. Because the app points to the installed browser rather than a bundled copy, a browser update reaches the music app too.

The list of supported services includes YouTube Music as a preset, alongside YouTube, Spotify, Apple Music, and Amazon Music.

The four side by side

Container	Separate Google sign in	Extensions	Engine and updates	Who builds the app
Chrome install	No, shares the profile	Chrome, from that profile	Chrome, updated with Chrome	Chrome, from the page
Safari Add to Dock	Yes	Safari only, per app	WebKit, updated with macOS	Safari, from the page
Pear Desktop or YTMDesktop	Yes	Own plugin system or none	Bundled Chromium, updated by the project	Volunteers
Native WebKit wrapper	Yes	None	WebKit, unnotarized build	One developer
Site to app tool	Yes, a profile per app	Chrome, per app	Installed browser, updated with it	Tool vendor, page from Google

The five rows cover four kinds, since Chrome and Safari installs are the same idea in two browsers.

The details that decide it on a real Mac

The account comes first. If the playlists live on a Google account that is not the browser's main one, the Chrome install is the wrong choice unless a second Chrome profile is created and switched by hand. Safari, the community clients, and a profile per app tool all solve this.

The media keys come second. When several tabs can play audio, the play and pause keys and the Now Playing control in Control Center go to whatever macOS treats as the active media session. Moving music into its own app makes that predictable. The native wrapper advertises this directly. The other containers get it by being a separate app with one page in it.

Accidental closing comes third. A pinned tab dies to Cmd+W like any other. An app in the Dock needs a deliberate Cmd+Q, and with a quit confirmation turned on, a second click.

Trust comes last but weighs the most for some readers. The browser installs and the site to app tool run Google's page inside a browser signed by its vendor. The community clients and the wrapper are code from outside Google that holds a Google sign in. That is a choice to make on purpose rather than by accident.

What to change first

If the music account is the same as the browser's account, install the page from Chrome or Safari today and stop there. If the accounts differ, or extensions are needed only for music, a profile per app container is the cleaner fix, and Kagemusha describes how that setup works.