[Enhancement]: User Concurrent Stream Limiting #2705

Open
opened 2026-04-25 00:09:43 +02:00 by adam · 3 comments
Owner

Originally created by @aipudong on GitHub (Apr 3, 2025).

Type of Enhancement

Server Backend

Describe the Feature/Enhancement

I would like to request a feature that allows administrators to set a limit on the number of concurrent streams per user. This means that each user would only be able to stream a certain number of audiobooks at the same time, as defined by the admin.

The limit could be configurable in the server settings, allowing the admin to set the maximum number of simultaneous streams per user. If a user tries to exceed this limit, they would receive a message preventing additional streams from starting.

Why would this be helpful?

Currently, Audiobookshelf does not have any restrictions on the number of simultaneous streams per user. If an account is shared with others, there is no way to prevent multiple people from streaming different audiobooks at the same time, which could lead to excessive server usage and unfair resource distribution.

By implementing this feature, admins would have better control over user activity, prevent account abuse, and ensure fair access to audiobooks for all users. This would be especially useful for those who share their library with friends but want to prevent unrestricted access.

Future Implementation (Screenshot)

Since this feature does not exist yet, I do not have a screenshot. However, I imagine the implementation could be added to the Server Settings > Streaming section.

It could include an option like:
🔲 Max concurrent streams per user: [ 2 ] (Default: unlimited)

If a user exceeds the limit, they would see an error message like:
"You have reached the maximum number of concurrent streams allowed. Please stop an active stream before starting a new one."

Audiobookshelf Server Version

v2.20.0 Windows

Current Implementation (Screenshot)

No response

Originally created by @aipudong on GitHub (Apr 3, 2025). ### Type of Enhancement Server Backend ### Describe the Feature/Enhancement I would like to request a feature that allows administrators to set a limit on the number of concurrent streams per user. This means that each user would only be able to stream a certain number of audiobooks at the same time, as defined by the admin. The limit could be configurable in the server settings, allowing the admin to set the maximum number of simultaneous streams per user. If a user tries to exceed this limit, they would receive a message preventing additional streams from starting. ### Why would this be helpful? Currently, Audiobookshelf does not have any restrictions on the number of simultaneous streams per user. If an account is shared with others, there is no way to prevent multiple people from streaming different audiobooks at the same time, which could lead to excessive server usage and unfair resource distribution. By implementing this feature, admins would have better control over user activity, prevent account abuse, and ensure fair access to audiobooks for all users. This would be especially useful for those who share their library with friends but want to prevent unrestricted access. ### Future Implementation (Screenshot) Since this feature does not exist yet, I do not have a screenshot. However, I imagine the implementation could be added to the Server Settings > Streaming section. It could include an option like: 🔲 Max concurrent streams per user: [ 2 ] (Default: unlimited) If a user exceeds the limit, they would see an error message like: "You have reached the maximum number of concurrent streams allowed. Please stop an active stream before starting a new one." ### Audiobookshelf Server Version v2.20.0 Windows ### Current Implementation (Screenshot) _No response_
adam added the enhancement label 2026-04-25 00:09:43 +02:00
Author
Owner

@ZLoth commented on GitHub (Apr 7, 2025):

This would be helpful in preventing account sharing.

@ZLoth commented on GitHub (Apr 7, 2025): This would be helpful in preventing account sharing.
Author
Owner

@Vito0912 commented on GitHub (Apr 11, 2025):

I just want to leave a note:

This idea was discussed on Discord some time back, and while it was generally considered a good one, it is basically impossible with ABS right now.

There is no way to determine if a user is currently streaming.

Websockets are completely optional, so they cannot be taken into consideration.

Sessions do not close reliably (for third-party and first-party apps), and users cannot close them themselves, so if they have bad luck, they could be locked out of their own account.

@Vito0912 commented on GitHub (Apr 11, 2025): I just want to leave a note: This idea was discussed on Discord some time back, and while it was generally considered a good one, it is basically impossible with ABS right now. There is no way to determine if a user is currently streaming. Websockets are completely optional, so they cannot be taken into consideration. Sessions do not close reliably (for third-party and first-party apps), and users cannot close them themselves, so if they have bad luck, they could be locked out of their own account.
Author
Owner

@nichwall commented on GitHub (Apr 23, 2025):

Duplicate of https://github.com/advplyr/audiobookshelf/issues/2591, but uses the new issue template and has more discussion

@nichwall commented on GitHub (Apr 23, 2025): Duplicate of https://github.com/advplyr/audiobookshelf/issues/2591, but uses the new issue template and has more discussion
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/audiobookshelf#2705