Announcements

Help Wizard

Step 1

NEXT STEP

FAQs

Please see below the most popular frequently asked questions.

Loading article...

Loading faqs...

VIEW ALL

Ongoing Issues

Please see below the current ongoing issues which are under investigation.

Loading issue...

Loading ongoing issues...

VIEW ALL

(Desktop) Playback issues with local files

We're receiving reports of users experiencing playback issues with local files. This seems to happen specifically on the desktop app, where playback stops at 0 seconds after every song.

Hey folks!

We're marking this as Not Right Now for the time being but it's on our radar.
Make sure to check the floated reply to find a workaround to this issue 🙂

In case you need any further assistance, don't hesitate to open a new thread in the Help boards. 
Cheers!

Top Answer
Bloodtraitor

Hey guys, 

I've tried out a temporary fix mentioned before and thought I would share it here:

This was mentioned before but I thought I would elaborate with a step by step guide - the 'corrupted' audio files will have a sample rate of 48000, when you want it to be 44100. You can check what the sample rate is by right clicking your file and looking at properties, under 'Details' it will say "Audio Sample Rate" with a number. If it's 48000, write it down because you'll need to change it.

Open up the Audacity software and dump in your corrupted audio files, then immediately hit export (you don't have to do anything yet!) Before you export it will show a couple options on how to export (mp3, mp4, etc) - ignore everything except for the "Sample Rate" section, and select 44100 in the dropdown. 

The file should now work. 
It sucks that we have to resort to these methods but I hope this helps at least a couple people.

Good luck, 
Bloodtraitor

Comments
Deuseph

Hi. Just as an update, a member from the Spotify's Escalations team wrote me an email in which it said:

"The details have been submitted to the relevant team for further investigation. We're unable to provide any timeline for when this will be resolved. We suggest keeping auto-update enabled to ensure you get the latest fixes and features as soon as they are available."

I hope it actually gets investigated and fixed, but for now I still suggest you to use the 1.2.60.564.gcc6305cb version. I will be auto-updating Spotify until it gets fixed and will be commenting here when it is confirmed that it is.

gya

This happens because the songs have different sample rates — 44100 Hz or 48000 Hz.

gya

premium

 

I'm experiencing an issue with local MP3 files on the Spotify desktop app (Windows). When I create a playlist consisting of multiple local tracks, some songs do not automatically transition to the next track when the previous one ends. Instead, playback stops, and I have to manually start the next track.

Interestingly, the issue seems to occur when the sample rates of the tracks differ (e.g., one is 44100 Hz and the next is 48000 Hz). Tracks with matching sample rates transition correctly. All tracks play fine manually, and the same playlist works without issue on the mobile app.

I’ve tried reinstalling Spotify, clearing the local files cache, and ensuring the network and VPN settings are identical across devices — but the problem persists only on desktop.

image_2025-06-13_10-15-10.png
WasentTaken

Been having the same issue lately. Premium user on Windows 10 as well.

I have a large playlist with nearly 1000 songs, about 60 of which are local files. Whenever a song on Spotify ends, and the next song is a local file, the song just sits at 0:00. I have to manually move the progress bar to get the song to play. This also happens whenever a local file finishes playing, causing the song from Spotify to get stuck at 0:00 with the same fix.

This happens regardless of whether the playlist has shuffle on or off. I usually have crossfade on, but turning off seems to resolve the issue for now. 

WasentTaken

A temp fix for me was to turn off crossfade in settings. Hope this works for you as well.

image.png
RichyG93

Hello @Eni,

 

I'm replying to you to add additional information to this thread:

 

  • It does indeed seem to be related to local files queued / playlists with local files mixed in.
  • This issue appeared suddenly, as all these files were playing without issue until recently.
    • These files have been played multiple times in the past, as I listened to my playlist nearly every day with regular shuffle enabled. Past tense, as I now can't run the playlist alone without it stopping.
  • These local files were:
    • Ripped from YouTube videos.
    • Audio only - taken by using the cobalt.tools website.
    • Modified with MP3Tag to fix the artist name, song name, album name, and cover arts.
  • These local files are saved on a storage drive different to the installation drive of Spotify.

With the exception of converting the files or removing them from my playlist, no other solution works for me.

 

My system information:

  • Windows 11 Pro, 64 bit, 24H2, build 26100
  • Intel Core i5 12600K
  • 32GB Memory
  • EVGA Nvidia GeForce RTX 3070
  • Spotify install directory: 256GB SSD with 35GB remaining
  • Local songs directory: 2TB SSD with 495GB remaining
  • Spotify Desktop version: 1.2.65.255.g85e641b4

 

I have attached a short clip of the issue occurring, and an mp3 that causes this issue to occur. (inside the zip, since uploading an mp3 alone is prohibited)

 

EDIT 1: I noticed the problematic files I have are at a frequency of 48000.

 

EDIT 2: Although not preferred, converting the files with a frequency of 48000 down to 44100 seems to fix the issue.

Kerint

@eni, @dessi, @aleyar, @yordan, @vasil

I have the same issue with playing the local files and nothing helps with it. It all started after june 11 update to the app. It affects all new and old mp3 files. 

nebsterww

how do i get the  1.2.60.564.gcc6305cb version?

nebsterww

actually i got the 1.2.60.564.gcc6305cb version? but it still happens

Iazer

I've been having the same issue for a couple of weeks and it's taken me until today to find that in my case at least, turning off shuffle stops the issue