[Bug]: No audio on iPhone when listening to mp3 encoded m4b files. #2818

Closed
opened 2026-04-25 00:10:52 +02:00 by adam · 5 comments
Owner

Originally created by @nicktheone on GitHub (Jun 3, 2025).

What happened?

I've recently noticed my girlfriend can't listen to m4b files that are encoded as mp3 audio. Aac encoded files are ok, just mp3 encoded m4b files. We tried using Plappa as a client and also both Safari and Chrome straight from ABS. I don't know if it's of any help but all the mp3 books we have started as loose mp3 files audiobooks that I then converted to an m4b file through ABS.

What did you expect to happen?

The result is always the same: the files looks to be playing but there's no audio coming out.

Steps to reproduce the issue

  1. Add a multiple files audiobook encoded as mp3.
  2. Convert it to an m4b audiobook through the ABS tool.
  3. Try to play it on an iPhone (either through Plappa or the browser).

Audiobookshelf version

ABS v2.23.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

Her phone is a 13 Mini, her iOS version is iOS 18.4.1 and the ABS version is ABS v2.23.0 through Docker. Aside from converting to AAC (which I'd like to avoid, for fear of dramatically losing quality) is there anything that can be done on our side?

Originally created by @nicktheone on GitHub (Jun 3, 2025). ### What happened? I've recently noticed my girlfriend can't listen to m4b files that are encoded as mp3 audio. Aac encoded files are ok, just mp3 encoded m4b files. We tried using Plappa as a client and also both Safari and Chrome straight from ABS. I don't know if it's of any help but all the mp3 books we have started as loose mp3 files audiobooks that I then converted to an m4b file through ABS. ### What did you expect to happen? The result is always the same: the files looks to be playing but there's no audio coming out. ### Steps to reproduce the issue 1. Add a multiple files audiobook encoded as mp3. 2. Convert it to an m4b audiobook through the ABS tool. 3. Try to play it on an iPhone (either through Plappa or the browser). ### Audiobookshelf version ABS v2.23.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 Her phone is a 13 Mini, her iOS version is iOS 18.4.1 and the ABS version is ABS v2.23.0 through Docker. Aside from converting to AAC (which I'd like to avoid, for fear of dramatically losing quality) is there anything that can be done on our side?
adam added the bug label 2026-04-25 00:10:52 +02:00
adam closed this issue 2026-04-25 00:10:52 +02:00
Author
Owner

@Vito0912 commented on GitHub (Jun 3, 2025):

Afaik this is an iOS limitation.

Note: AAC or Opus are both far better codeces than MP3. There will be a bit of loss between conversions, but "dramatically" is a bit dramatic

@Vito0912 commented on GitHub (Jun 3, 2025): Afaik this is an iOS limitation. Note: AAC or Opus are both far better codeces than MP3. There will be a bit of loss between conversions, but "dramatically" is a bit dramatic
Author
Owner

@Vito0912 commented on GitHub (Jun 3, 2025):

See also here:
https://github.com/advplyr/audiobookshelf/pull/4214#issuecomment-2832502178
https://github.com/advplyr/audiobookshelf/pull/4214#issuecomment-2832516063

The solution is to use another OS or hit Apple why they don't follow specifications. You could also try to rename the file to .mp3, because mp3 is supported by the container and maybe it tricks iOS into thinking it can play it

@Vito0912 commented on GitHub (Jun 3, 2025): See also here: https://github.com/advplyr/audiobookshelf/pull/4214#issuecomment-2832502178 https://github.com/advplyr/audiobookshelf/pull/4214#issuecomment-2832516063 The solution is to use another OS or hit Apple why they don't follow specifications. You could also try to rename the file to .mp3, because mp3 is supported by the container and maybe it tricks iOS into thinking it can play it
Author
Owner

@nicktheone commented on GitHub (Jun 3, 2025):

Afaik this is an iOS limitation.

Note: AAC or Opus are both far better codeces than MP3. There will be a bit of loss between conversions, but "dramatically" is a bit dramatic

Given that the initial file is a lossy format wouldn't that kill the quality? I've yet to try and do it but I thought that going from lossy to lossy was a really bad idea, independently from how performing the target codec is.

@nicktheone commented on GitHub (Jun 3, 2025): > Afaik this is an iOS limitation. > > Note: AAC or Opus are both far better codeces than MP3. There will be a bit of loss between conversions, but "dramatically" is a bit dramatic Given that the initial file is a lossy format wouldn't that kill the quality? I've yet to try and do it but I thought that going from lossy to lossy was a really bad idea, independently from how performing the target codec is.
Author
Owner

@nicktheone commented on GitHub (Jun 3, 2025):

See also here: #4214 (comment) #4214 (comment)

The solution is to use another OS or hit Apple why they don't follow specifications. You could also try to rename the file to .mp3, because mp3 is supported by the container and maybe it tricks iOS into thinking it can play it

Ok thanks, I'll try and report back as soon as I can.

@nicktheone commented on GitHub (Jun 3, 2025): > See also here: [#4214 (comment)](https://github.com/advplyr/audiobookshelf/pull/4214#issuecomment-2832502178) [#4214 (comment)](https://github.com/advplyr/audiobookshelf/pull/4214#issuecomment-2832516063) > > The solution is to use another OS or hit Apple why they don't follow specifications. You could also try to rename the file to .mp3, because mp3 is supported by the container and maybe it tricks iOS into thinking it can play it Ok thanks, I'll try and report back as soon as I can.
Author
Owner

@Vito0912 commented on GitHub (Jun 3, 2025):

Given that the initial file is a lossy format wouldn't that kill the quality? I've yet to try and do it but I thought that going from lossy to lossy was a really bad idea, independently from how performing the target codec is.

Why not try it and listen for yourself? I don't notice any difference at all, and I convert all my MP3 files to Opus as soon as they are added to my library. Also, audio quality is very subjective, so it's hard to say: No you won't notice any difference.

@Vito0912 commented on GitHub (Jun 3, 2025): > Given that the initial file is a lossy format wouldn't that kill the quality? I've yet to try and do it but I thought that going from lossy to lossy was a really bad idea, independently from how performing the target codec is. Why not try it and listen for yourself? I don't notice any difference at all, and I convert all my MP3 files to Opus as soon as they are added to my library. Also, audio quality is very subjective, so it's hard to say: No you won't notice any difference.
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/audiobookshelf#2818