Set Up Plex for Multiple Users and Simultaneous Streams

Published 2026-10-14 · PlexBeam

Plex is built for sharing — one server can serve your household and remote friends simultaneously. But adding users means more concurrent streams, more bandwidth consumption, and more server load. This guide covers how to set up user accounts, manage permissions, plan hardware for concurrent streams, and keep everyone's experience smooth.

Types of Plex Users

Plex has three user types, each with different capabilities:

Managed Users (Home Users)

Managed users are part of your Plex Home — they appear on the user selection screen and can switch between accounts without signing in. Best for family members who share a TV.

Shared Users (Friends)

Shared users have their own Plex account and access your server remotely. They sign in with their own credentials.

Guest Access

Plex does not have a formal guest mode, but you can create a managed user with a simple name ("Guest") and restrict it to specific content. Useful for visitors who want to browse your library on the living room TV.

Setting Up Managed Users

  1. Go to Settings > Users & Sharing > Plex Home.
  2. Click Create Managed User.
  3. Enter a name and optionally set a PIN (to prevent other household members from switching into this account).
  4. Configure library access: choose which libraries this user can see. Hide your horror collection from the kids' account.
  5. Set content restrictions: filter by content rating (G, PG, PG-13, R, etc.). Content above the allowed rating is hidden from the user.

Sharing With Remote Friends

  1. Go to Settings > Users & Sharing.
  2. Click Share Libraries.
  3. Enter the friend's Plex username or email address.
  4. Select which libraries to share. You can share your Movies library without sharing your personal home videos library.
  5. Optionally set a maximum streaming bitrate for this user under their sharing settings. This caps their quality to protect your upload bandwidth.

Per-User Bandwidth Limits

When multiple people stream simultaneously, your upload bandwidth is the bottleneck for remote users. Control this per-user:

  1. Go to Settings > Users & Sharing.
  2. Click on a shared user's name.
  3. Under Restrictions, set Remote Streaming to a specific bitrate limit.

Example: You have 50 Mbps upload. You share with 3 friends. Set each friend to a maximum of 12 Mbps — this ensures all three can stream 1080p simultaneously with bandwidth to spare for your own use.

Local users (on your home network) do not consume upload bandwidth and do not need limits unless your LAN is congested.

Hardware Sizing for Concurrent Streams

How powerful does your server need to be? It depends on whether streams are direct play or transcode.

Direct Play Streams

Direct play requires almost no CPU. The server reads the file from storage and sends it over the network. A Raspberry Pi can handle 3-5 concurrent direct play streams. The bottleneck is storage I/O and network bandwidth, not CPU.

Transcode Streams

Each transcode stream requires significant processing power. The standard benchmark:

Transcode TypeCPU PassMark per StreamNVIDIA NVENC per Stream
1080p software transcode~2,000 PassMarkN/A
4K to 1080p software transcode~12,000 PassMarkN/A
1080p hardware transcodeMinimal CPU1 NVENC session
4K to 1080p hardware transcodeModerate CPU1-2 NVENC sessions

An NVIDIA GPU with NVENC handles multiple hardware transcodes far more efficiently than a CPU. A GeForce GTX 1660 or newer supports unlimited simultaneous NVENC sessions (Plex Pass required, driver patch may be needed on consumer GPUs). An Intel CPU with Quick Sync handles 2-10+ transcodes depending on the generation.

Sizing Examples

Optimizing for Multiple Streams

Reduce Transcoding Demand

The fewer transcodes your server has to do, the more users it can serve:

Pre-Transcode With Tdarr

Tdarr is a distributed transcoding tool that pre-converts your media library to a target format. Set it to convert everything to H.264 + AAC or H.265 + AAC. Once converted, most clients will direct-play everything — dramatically reducing real-time transcoding demand.

Separate Plex Database From Media Storage

Put the Plex database on an SSD and media files on HDDs. When multiple users browse the library simultaneously, database queries hit the SSD (fast random I/O) while media streams read from HDDs (fast sequential I/O). Mixing both on the same drive creates I/O contention.

Monitoring Multi-User Activity

Use Tautulli (free, open-source) to monitor who is streaming, what they are watching, and how the server is performing:

Tautulli's insights help you make informed decisions about hardware upgrades and user limits.

Content Access Policies

Not every user should see everything. Configure per-library and per-user access:

Review sharing settings periodically. Remove users who no longer need access — an unused shared account is an unnecessary security exposure.

More from LuxuriousComputers: LuxuriousComputers · Computer Repair · Remote Fix · Phone Repair · HVAC · Plex Support