starred/audiobookshelf
1
0
Fork 0
mirror of https://github.com/advplyr/audiobookshelf.git synced 2026-05-30 23:40:40 +02:00
Code Issues 1.0k Packages Projects Releases 10 Wiki Activity

[Feature]: Excessive Storage Usage Due to Large Embedded Cover Images from Audible #2669

New Issue
Open
opened 2026-04-25 00:09:28 +02:00 by adam · 0 comments
adam commented 2026-04-25 00:09:28 +02:00
Owner
Copy Link
Copy Source

Originally created by @Demian98 on GitHub (Mar 18, 2025).

What happened?

When retrieving cover images from Audible, the average cover size is around 800 KB. Audiobookshelf embeds this cover image into every audio file. With a large audiobook library, this results in significant storage consumption.

For example, consider a library of 70,000 audio files with a total size of 430 GB. If each file embeds an 800 KB image, the total storage used by cover images alone is:
70,000 files × 0.8 MB = 56,000 MB = 56 GB.
This means approximately 13% of the total storage is just cover images.

What did you expect to happen?

I expected Audiobookshelf to:

  • Have an option to exclude the cover images from embedding into the audio files, they are already stored as a separate file in the audiobook folder.
  • Provide an option to use smaller, optimized cover images when embedding to reduce storage consumption. It would be great to have a setting for the specific resolution used (preferred).

Steps to reproduce the issue

Just check your cover sizes and do some calculation from on the library statistics.

Audiobookshelf version

2.20.0

How are you running audiobookshelf?

Docker

What OS is your Audiobookshelf server hosted from?

Linux

If the issue is being seen in the UI, what browsers are you seeing the problem on?

None

Logs

Additional Notes

No response

Originally created by @Demian98 on GitHub (Mar 18, 2025). ### What happened? When retrieving cover images from Audible, the average cover size is around 800 KB. Audiobookshelf embeds this cover image into every audio file. With a large audiobook library, this results in significant storage consumption. For example, consider a library of 70,000 audio files with a total size of 430 GB. If each file embeds an 800 KB image, the total storage used by cover images alone is: **70,000 files × 0.8 MB = 56,000 MB = 56 GB.** This means approximately **13% of the total storage** is just cover images. ### What did you expect to happen? I expected Audiobookshelf to: - Have an option to exclude the cover images from embedding into the audio files, they are already stored as a separate file in the audiobook folder. - Provide an option to use smaller, optimized cover images when embedding to reduce storage consumption. It would be great to have a setting for the specific resolution used (preferred). ### Steps to reproduce the issue Just check your cover sizes and do some calculation from on the library statistics. ### Audiobookshelf version 2.20.0 ### How are you running audiobookshelf? Docker ### What OS is your Audiobookshelf server hosted from? Linux ### If the issue is being seen in the UI, what browsers are you seeing the problem on? None ### Logs ```shell ``` ### Additional Notes _No response_
adam added the bug label 2026-04-25 00:09:28 +02:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
authentication
backlog
bug
chapter editor
config-issue
ebooks
encoding/embedding
enhancement
help wanted
listening sessions & progress
planned
possible plugin
progress sync
pull-request
Mirrored from GitHub Pull Request
 sorting/filtering/searching
unable to reproduce
upload
users & permissions
waiting
No Label bug
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
adam (Adam Melkus)
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/audiobookshelf#2669
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?