How to Use Apple Music Playlists with Your Local Music Library

Connect Apple Music in Emthree to read your playlists, compare every track against the files you already own, and export the result as a standard .m3u. The connection is read-only, nothing is written back to Apple Music, and your audio files never leave your machine.

What the connection actually does

Emthree authorises through Apple's own MusicKit window, then reads three things: the playlists in your Apple Music library, the tracks inside them, and optionally every song in your library. It compares that list against the tags in your scanned local folder and tells you which tracks you already have on disk.

It is read-only by design. Emthree never creates, renames, reorders or deletes anything in Apple Music, and it never downloads or streams audio. The only thing crossing over is metadata: title, artist, album, duration, and a small artwork thumbnail.

Two things need to be true before any of it is useful. You need an Apple ID with an active Apple Music subscription, because the library endpoints Emthree reads are subscriber-only. And you need to have scanned your music folder in Emthree first, because the local half of the comparison is your scanned library. Connect without a scan and every track comes back as not found.

Two ways in

From the library page, the Import panel on the right has two buttons. Apple Music opens the import dialog, which works one playlist at a time and ends in an exported or saved playlist. Apple Music catalog opens a separate page that pulls everything at once and gives you a searchable inventory instead.

Use the first when you want a specific playlist as an .m3u. Use the second when you want to know what your collection is missing.

Importing a single playlist

Click Apple Music, then Connect Apple Music. Apple's sign-in window handles the credentials, so Emthree never sees your Apple ID password. Once you are through, Emthree lists your library playlists with their track counts.

Pick one and it fetches the tracks, matches them against your scanned library, and drops you on a review screen. Every track is sorted into one of three states:

• Matched in library, with a green dot. Confident matches, included automatically.
• Possible match, with an amber dot and a checkbox. Something plausible was found but the metadata does not fully agree. Tick the ones you want to include.
• Not found, greyed out. Nothing in your scanned folder looks like this track.

The counts sit above the list, so you know straight away that you matched, say, 41 of 60 tracks confidently with 5 possible and 14 missing. The playlist name is pre-filled from Apple Music and you can rename it before doing anything else.

Three actions from there. Export M3U downloads a standard .m3u built from your local files, with an #EXTM3U header and #EXTINF lines, exactly like any other Emthree export. Save playlist drops the matched tracks into the normal save flow so the playlist lives alongside your others, which counts against the free limit of three saved playlists if you are not signed in. Export missing writes a plain text file of everything that did not make the cut, formatted as artist, title and album per line, which is a useful shopping list when you are filling gaps in a collection.

How matching works, and why some tracks miss

Matching is metadata comparison, not audio fingerprinting. Titles and artists are normalised first: lowercased, accents stripped, punctuation flattened to spaces, so "Sigur Rós, Ný Batterí" and "sigur ros ny batteri" line up.

Each candidate then earns a score. An exact title match is worth 2 points and a partial one is worth 1. An exact artist match adds 1, a partial adds half. A duration within three seconds adds 1, within six adds half. Anything scoring 2 or more is treated as confident, and anything below 1.5 is discarded as noise.

Two guards stop bad matches from sneaking through. Placeholder tags never count as agreement, so a file tagged Unknown Artist or Track 04 cannot confirm anything, no matter how well the rest lines up. And a partial title on its own is never enough, it has to be corroborated by a real artist match or an exact duration.

The practical consequence is that match quality is a function of your tags, not of Apple's data. If a chunk of your library is untagged or tagged inconsistently, that is where the misses will be. Fix the tags, rescan the folder, and rerun the match.

The Apple Music catalog

The catalog page does the same comparison across everything at once. It reads every playlist in your library, and with Include my whole library ticked, every song in your Apple Music library as well, including tracks that are not in any playlist. Large libraries are paged in behind a progress bar with a running estimate.

Duplicates are collapsed, so a track appearing in six playlists is one row that lists all six. Tracks pulled in from the library sweep rather than a playlist show as Library only.

You get four counters across the top (tracks, in your library, possible match, not found), a search box, sorting by artist, title, album or playlist count, and an Only tracks I don't own filter. Export CSV writes out whatever is currently visible, filters included, with columns for title, artist, album, duration, playlists, whether it is in your library, and the local file path when there is one.

The catalog is saved. Signed in, it goes to your account and comes back on any device. Anonymous, it stays in that browser. Either way it is re-compared against your current local library every time you open the page, so as your collection grows the missing count drops without reconnecting to Apple. Clear saved removes it. If a rebuild detects that the Apple side has changed, Emthree also offers to rescan your local folder so the two stay in step.

What happens to your data

Your audio files are never uploaded, and the matching itself runs in your browser. Apple's API cannot be called directly from a browser, so requests are proxied through Emthree's server using a short-lived user token, which means the track metadata Apple returns passes through the server on its way to you. If you are signed in, the catalog snapshot (titles, artists, albums, durations, artwork URLs, playlist names) is stored against your account so it can be restored later. Nothing about your local file paths goes to Apple.

What it cannot do

It is a one-way read. You cannot push a local playlist up into Apple Music, create Apple playlists, or edit the ones you have. It only sees playlists in your library, not editorial playlists you have never added. It is a snapshot rather than a live sync, so rebuild when you want fresh data. And it will not help you obtain music you do not own, the missing list is a list, nothing more.

In short

The Apple Music connection turns playlists you already curate on your phone into .m3u files pointing at your own files, and the catalog turns your whole Apple Music library into an inventory of what you own and what you do not. Both run off the same matcher, so both are only as good as your tags. Scan first, tag properly, and the rest falls into place.