[Issue]: Save artwork into media folders not working as expected for movies #3976

Closed
opened 2026-02-07 00:13:21 +03:00 by OVERLORD · 2 comments
Owner

Originally created by @mbhayden14 on GitHub (Jun 28, 2022).

Please describe your bug

I have the 'Save artwork into media folders' option selected for each of my libraries, and before upgrading to 10.8.0/10.8.1, a 'folder.jpg' & 'backdrop.jpg' would be saved to the same location of the movie files each time you add & identify a new movie (along with automatically updating themselves when changing existing art work). After updating it seems to not be working; this is what happens:

  • When adding a new movie (& identifying it), no new 'folder.jpg' & 'backdrop.jpg' are created in its media folder.
  • When updating a existing movie's art work in the browser, the previous 'folder.jpg' & 'backdrop.jpg' in its media folder do not get updated. This makes it so the next time you run 'Scan Media Library' the artwork reverts back to its previous version that is still saved in the media folder.

I attempted to restart the Jellyfin application and also turn on and off the 'Save artwork into media folders' option, but it still isn't working.

Jellyfin Version

Other

if other:

10.8.1

Environment

- OS: Linux (Ubuntu)
- Virtualization: Docker
- Clients: Browser
- Browser: Brave/Chrome
- FFmpeg Version: N/A
- Playback Method: N/A
- Hardware Acceleration: N/A
- Plugins: none
- Reverse Proxy: none
- Base URL: none
- Networking: N/A
- Storage: local

Jellyfin logs

No response

FFmpeg logs

No response

Please attach any browser or client logs here

No response

Please attach any screenshots here

No response

Code of Conduct

  • I agree to follow this project's Code of Conduct
Originally created by @mbhayden14 on GitHub (Jun 28, 2022). ### Please describe your bug I have the 'Save artwork into media folders' option selected for each of my libraries, and before upgrading to 10.8.0/10.8.1, a 'folder.jpg' & 'backdrop.jpg' would be saved to the same location of the movie files each time you add & identify a new movie (along with automatically updating themselves when changing existing art work). After updating it seems to not be working; this is what happens: - When adding a new movie (& identifying it), no new 'folder.jpg' & 'backdrop.jpg' are created in its media folder. - When updating a existing movie's art work in the browser, the previous 'folder.jpg' & 'backdrop.jpg' in its media folder do not get updated. This makes it so the next time you run 'Scan Media Library' the artwork reverts back to its previous version that is still saved in the media folder. I attempted to restart the Jellyfin application and also turn on and off the 'Save artwork into media folders' option, but it still isn't working. ### Jellyfin Version Other ### if other: 10.8.1 ### Environment ```markdown - OS: Linux (Ubuntu) - Virtualization: Docker - Clients: Browser - Browser: Brave/Chrome - FFmpeg Version: N/A - Playback Method: N/A - Hardware Acceleration: N/A - Plugins: none - Reverse Proxy: none - Base URL: none - Networking: N/A - Storage: local ``` ### Jellyfin logs _No response_ ### FFmpeg logs _No response_ ### Please attach any browser or client logs here _No response_ ### Please attach any screenshots here _No response_ ### Code of Conduct - [X] I agree to follow this project's Code of Conduct
OVERLORD added the bugstale labels 2026-02-07 00:13:21 +03:00
Author
Owner

@mbhayden14 commented on GitHub (Aug 4, 2022):

Still an issue as of 10.8.3

@mbhayden14 commented on GitHub (Aug 4, 2022): Still an issue as of 10.8.3
Author
Owner

@jellyfin-bot commented on GitHub (Jan 29, 2023):

This issue has gone 120 days without comment. To avoid abandoned issues, it will be closed in 21 days if there are no new comments.

If you're the original submitter of this issue, please comment confirming if this issue still affects you in the latest release or master branch, or close the issue if it has been fixed. If you're another user also affected by this bug, please comment confirming so. Either action will remove the stale label.

This bot exists to prevent issues from becoming stale and forgotten. Jellyfin is always moving forward, and bugs are often fixed as side effects of other changes. We therefore ask that bug report authors remain vigilant about their issues to ensure they are closed if fixed, or re-confirmed - perhaps with fresh logs or reproduction examples - regularly. If you have any questions you can reach us on Matrix or Social Media.

@jellyfin-bot commented on GitHub (Jan 29, 2023): This issue has gone 120 days without comment. To avoid abandoned issues, it will be closed in 21 days if there are no new comments. If you're the original submitter of this issue, please comment confirming if this issue still affects you in the latest release or master branch, or close the issue if it has been fixed. If you're another user also affected by this bug, please comment confirming so. Either action will remove the stale label. This bot exists to prevent issues from becoming stale and forgotten. Jellyfin is always moving forward, and bugs are often fixed as side effects of other changes. We therefore ask that bug report authors remain vigilant about their issues to ensure they are closed if fixed, or re-confirmed - perhaps with fresh logs or reproduction examples - regularly. If you have any questions you can reach us on [Matrix or Social Media](https://docs.jellyfin.org/general/getting-help.html).
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/jellyfin#3976