Overview
The desktop client is the version most people end up using at a computer, because it does things the web player cannot: a proper local file library that sits alongside the streaming catalogue, gapless and crossfaded playback, an equaliser, output device selection including exclusive mode on supported hardware, and offline caching so a playlist keeps playing when the connection drops.
This build has the premium behaviour enabled, which means the catalogue plays on demand rather than shuffled, the interruptions between tracks are gone, higher quality streaming is selectable in settings, and downloads for offline listening are available on playlists and albums. Everything else is the standard desktop application with its normal interface.
The library side is worth mentioning on its own. Playlists, folders and collaborative lists sync across devices, the local files section indexes folders you point it at and mixes those tracks into playlists with streamed ones, and the connect feature hands playback off to another device on the same network without losing the queue. The client also exposes a full keyboard shortcut set and media key handling, which is why it stays open on a second monitor for most of a working day.
What it does well
On demand playback
Any track, album or playlist plays in order rather than shuffled, with no interruptions between items.
Offline caching
Playlists and albums cache to disk so playback continues without a connection, with a configurable cache location and size.
Local file library
Point it at folders of your own audio and those tracks appear in the library and can be mixed into playlists with streamed material.
Audio output control
Equaliser, crossfade, gapless playback, normalisation profiles and output device selection with exclusive mode on capable hardware.
Connect and shortcuts
Hand playback to another device on the network without losing the queue, and drive the whole client from the keyboard or media keys.
Changes in this build
- Higher quality streaming tier selectable in the audio settings panel.
- Local file indexing rewritten so large personal libraries scan in a fraction of the time.
- Lower idle memory use when the client is minimised for long periods.
- Queue editing reworked with drag reordering and multi select.
- Fixed an output device stall after waking from sleep on some audio interfaces.
What is in the package
- Spotify desktop client installer, 64-bit
- Premium behaviour configuration
- Local file indexing components
- Equaliser and output profile presets
- Multilingual interface files, 26 languages
System requirements
| Processor | Any x64 processor, dual core or better |
| Memory | 4 GB minimum |
| Graphics | Any GPU with a current driver |
| Storage | 1 GB free plus space for the offline cache |
| Display | 1280 x 720 minimum |
| System | Windows 10 or Windows 11, 64-bit |
Installation
- Remove any existing client, including the store based version, before starting.
- Extract the archive and run the installer to the default location.
- Do not launch it yet, apply the included configuration step first.
- Start the client and confirm the quality options are available in settings.
- Disable the built in updater so the configuration is not replaced.
Before you start
Letting the client update itself reverts the configuration, block the updater after install.
The offline cache defaults to the system drive, move it if you keep large playlists locally.
The store based version and this one fight over file associations, keep only one installed.
Questions about this title
Does it play tracks on demand?
Yes, on demand playback is enabled in this configuration.
Can it play my own files?
Yes, the local files section indexes folders you add and mixes those tracks into playlists.
Does offline listening work?
Yes, playlists and albums cache to disk and keep playing without a connection.
Will it update itself?
It tries on launch. Turn the updater off in settings once the client is running.
About this listing
This entry was checked on a clean install of Windows 10 / 11 (64-bit) before it was published, and it is rechecked whenever the package is rebuilt. The figures on this page come from the site index rather than from the publisher, so the download count is what people here have actually pulled.
If a mirror stops answering, use the contact form and it gets replaced. Reports about a specific title are handled faster than general messages because they name the file, the mirror and the point at which the transfer stopped.
Requests for a different version, a different language build or an older release go on the requests page. Older versions of a title are usually still held even when only the current one is listed.