Since last night, I’ve been unable to save album art on any mp3 WHEN IN DROPBOX. Now, you’d think this is a Dropbox issue (and I’m also asking over there), but I was able to add cover art to an mp3 using VLC, and it showed up. I was then able to REMOVE the cover art in mp3tag, and could CTRL-Z it back on, but could not add a new cover.
Computer restart, several times as I went through the processes below.
Editing other metadata fields. Worked fine. Can even rename file.
Pause Dropbox, in case it was mid-sync. Nope. And sync is up to date.
Make a "new" version of the mp3 by converting the file (open in Audacity, copy waveform into a new window, export as mp3; also tried convert with Freemake). Nope, can’t edit new file.
Moved files out of Dropbox and tried adding art. This was successful! I put the files back in Dropbox and tried to edit again, and could not.
Upgrading Dropbox to latest version.
Downgraded Dropbox a few versions.
Upgraded again.
Made sure mp3tag was up to date. Latest version release was from November 11, 2025, so it seems unlikely to have broken due to that long-ago update.
Uninstalled Dropbox. Success! I was able to edit all mp3 files, no issue. Obviously, not ideal, because I need to back things up!
Reinstalled Dropbox. Failure. Can no longer add album art.
Checked if other kinds of files can be edited. Can edit images and .txt documents, stopped there. Issue really seems to just by album art for mp3s.
Checked if files were read-only, they are not. (Folders are marked as indeterminate, but this seems to be a Windows behavior. No hidden files found.)
Checked security/permissions. Authenticated users, SYSTEM, and Administrators have full permissions (except "Special permissions," which I wasn't able to enable for anyone.) Plain "Users" did not have write permission, but when I enabled write permission, this did not resolve the issue.
Uninstalled mp3tag, installed again fresh, didn’t touch any settings. Failure.
Made sure files were not loaded in any music player. Cannot see one, and I’m inclined to think it’s not, since ALL mp3 files within Dropbox are affected, and I’m able to edit other metadata and the file names.
I’m at a loss. The Dropbox forum people are trying to figure this out, in case it’s a them problem, but the fact that I can edit other file types might mean it’s not Dropbox? And yet, the fact that I CAN add cover art outside of Dropbox would make it seem like it’s DB! Agh!
I also tried with OneDrive and GMX-Cloud - no problem.
With Foobar2000 has the same problem as with Mp3Tag
Lately, inexplicable problems seem to be occurring with saving album art, even though the issues don't initially appear to be related.
Perhaps the recent Windows updates have actually changed something relevant in this regard.
It definitely USED to work. As of maybe 3 days ago, I could add cover art just fine in Dropbox, unless the file was actively being uploaded. That was reasonable. This is untenable.
I am getting the exact same error in OneDrive since yesterday. I tried changing the artwork in Foobar, also got an error. Moved the file out of Onedrive, no issues. The fact that it had an error in mp3tag and foobar leads me to believe it’s a OneDrive problem, and I used co-pilot to go through every solution, nothing worked. But then I see you’re having the issue in DropBox, and someone else said their OneDrive was working, so now I’m very confused. Are you using a Windows computer? Maybe a Windows update is to blame?
I need to revise my statement regarding OneDrive. My OneDrive folder was apparently not synchronized at the time of the test. I therefore suspect that the MP3 file was only stored locally in the OneDrive folder during the test, and I overlooked that. I'm now experiencing the same problem with OneDrive.
It looks like the latest Windows Updates (Win 10 KB5073724 and Win 11 KB5074109) broke increasing file size via SetEndOfFile() on file systems backed by cloud storage (e.g., OneDrive or Dropbox).
I've implemented a workaround for this and kindly ask you to test this version in case you're affected by this bug in Windows: