SpotifyLauncher.exe
Also called spotifylauncher, spotify launcher
Spotify bootstrap launcher. It starts or updates the client, then hands off. Spotify.exe is the player.
What you need to know
Launcher is not the player.
SpotifyLauncher.exe bootstraps Spotify. It can apply an update, then start Spotify.exe. The player and tray are Spotify.exe. Ending the player does not always kill a leftover launcher. Ending the launcher mid-update can leave a half-patched client.
- Safe?
- Yes, from Spotify
- Is it the player?
- No. Spotify.exe is the player
- Should I end it?
- A launch or update can fail
What is SpotifyLauncher.exe?
SpotifyLauncher.exe is the launcher, not the player. Spotify.exe streams and draws the UI. audiodg.exe is still the Windows audio graph.
What does it do?
It starts or updates the Win32 client, then hands off to Spotify.exe. It does not mix the device. It does not stay as the Now Playing process.
Why is it running?
You clicked Spotify, a shortcut pointed at the launcher, or an update ran first. A launcher with no Spotify.exe after a minute is a stuck bootstrap.
Is it safe?
Usually safe when Spotify signed
A Spotify-signed launcher under AppData\Roaming\Spotify is the bootstrap. SpotifyLauncher.exe in a "premium" zip is not. This is still not the player.
A legitimate copy normally runs from:
C:\Users\<you>\AppData\Roaming\Spotify\SpotifyLauncher.exe
- Player is Spotify.exe in the same folder family
- Store installs may skip this Win32 launcher
- Not audiodg.exe
Can I end it?
A launch or self-update can fail
Ending SpotifyLauncher.exe during an update can leave Spotify unable to start. If music is already playing, the player is Spotify.exe. Do not end audiodg to stop a song.
Can I remove it?
Uninstall Spotify
Use Settings > Apps. Deleting only Spotify.exe leaves the launcher. Deleting only the launcher leaves a player that may not update.
Should it start with Windows?
A Startup Apps row can point at the launcher, which then starts Spotify.exe. Turn that off in Spotify settings.
Normal resource behavior
These are contextual labels, not universal averages.
- CPU
- Short spike while it updates or starts the player
- Memory
- Small. The player holds the cache
- Disk
- Patch write during an update
- Network
- Update fetch, then the player streams
File information
| Executable name | SpotifyLauncher.exe |
|---|---|
| Common legitimate path | C:\Users\<you>\AppData\Roaming\Spotify\SpotifyLauncher.exe |
| Publisher | Spotify AB |
| Signature expectation | Signed by Spotify AB |
Common problems
People end the launcher and the music keeps going
Playback is Spotify.exe. The launcher already handed off.
Stuck on the splash after an update
Quit both the launcher and Spotify.exe, then start Spotify again. Do not repair audiodg for that.
Troubleshooting
Diagnose before you change anything destructive.
Quit Spotify from the tray, then start it once
Let the launcher finish, then confirm Spotify.exe is the remaining row. Hardware acceleration lives on the player, not here.
Open file location on both names
SpotifyLauncher.exe is this article. Spotify.exe is the player. A launcher in Temp is a different file.
Technical details
Technical details
| Image name | SpotifyLauncher.exe |
|---|---|
| Role | Spotify bootstrap / launcher |
| Player | Spotify.exe |
Sources and verification
Reviewed by Feex editorial. Last verified August 2026 Status: Feex Reviewed. How we research.
- Spotify Support: desktop app · Official client
- Spotify Support: CPU and memory · Player settings, not the launcher
- Foxhole process map · First-party samples on Windows PCs. Not a lab benchmark.
Was this article useful?
A yes or no is enough. Pick a reason if you want, or add a short note.
Thanks. That helps us improve this page.