How to Show a Folder in Emby on Roku: Setup Guide

If you've been trying to figure out how to show folder in emby on roku and nothing appears no matter what you try, you're not alone. This is one of the most common Emby headaches — and the fix usually isn't where you'd expect it. The problem almost always comes down to three separate things: server-side library configuration, a toggle inside the Roku app that nobody tells you about, and per-user permissions that silently block content. This guide covers all three, plus the edge cases most articles skip entirely.

Why Folders Don't Always Show in Emby on Roku

Default Emby views vs. raw folder view

Emby Server doesn't show you a raw directory tree by default. It organizes content into curated "views" — Movies, TV Shows, Music — based on the library type you assigned during setup. What appears in the Roku app is a filtered, metadata-enriched presentation of that content. Not the actual folder structure on disk.

Raw folder browsing is a completely separate feature that has to be enabled in two places: on the server, and in the Roku client. Skip either step and the folder just won't appear — or you'll see the library but not the directory hierarchy inside it.

Library visibility per user account

Emby has per-user library access control. Each user profile has a checkbox list of libraries they're allowed to see. If the admin created a new library but didn't grant access to your specific user account, the Roku app won't show it. No error message. It just doesn't appear. This is the step that most guides skip, and it catches more people than any other issue.

Roku app caching behavior

The Roku Emby app caches the library list aggressively. Even after you fix everything on the server, the Roku app might still show the old view. You need to explicitly restart the channel — not just close it — for changes to take effect. On Roku OS 13+: press Home, navigate to the Emby channel icon, press the * key, then select "Restart channel."

Configure the Library on Emby Server First

Before touching the Roku at all, the folder needs to be properly configured as a library on the server. This is where the majority of problems start.

Add a new library with content type 'Mixed' or 'Folder'

Open the Emby Server dashboard (usually at http://your-server-ip:8096), go to Library, and click Add Media Library. For raw folder browsing, set the content type to Mixed Content. This tells Emby not to assume everything inside is a movie or a TV episode, and it unlocks the folder display option that doesn't appear under other content types.

If you set the content type to "Movies" or "TV Shows," Emby will try to match files to metadata and display them as a curated grid. You won't get folder view that way.

Set 'Display as folder' option

After selecting Mixed Content, look for the option labeled "Display this library using its folder structure". Enable it. This is what makes Emby present the actual directory tree instead of the flattened metadata view. The exact label has shifted slightly between Emby 4.7, 4.8, and 4.9 but the option is always there — just check the library's advanced settings if you don't see it immediately.

Confirm folder paths and permissions

Add your folder path in the library setup screen:

• Windows: D:\Media\Custom
• Linux: /mnt/media/custom
• NAS (SMB): \\NAS\Media\Custom or a locally mounted path like /mnt/nas/media

The Emby service account needs read access to that path. On Linux, the emby user needs at minimum r-x on the directory and r-- on the files. On Windows, verify the "Emby Server" service is running as an account with actual read permissions on that folder, not just Local System.

Running Emby in Docker? The folder must be bind-mounted inside the container. A very common mistake: you enter /mnt/media/custom as the library path, but that path was never mapped into the container. Inside Docker it's empty — Emby sees nothing. Fix it by adding -v /mnt/media/custom:/mnt/media/custom:ro to your docker run command or the equivalent in Compose.

SMB paths with spaces or special characters in the share name are also a recurring problem. If your share is \\NAS\My Media Files, map it to a clean mount point (/mnt/mymedia) and point Emby there instead.

Trigger a library scan

After saving, click the three-dot menu on the library and select Scan Library Files. Wait for it to complete. For a full metadata rebuild, use Refresh Metadata with "Replace existing" checked — slower, but it catches anything the initial scan missed.

Enable Folder View in the Roku Emby App

This is where the actual answer to how to show folder in emby on roku diverges from standard Emby documentation. The server configuration alone doesn't do it — the Roku client has its own separate toggle.

Sign in with the correct Emby user

Confirm you're signed into the Roku app with the Emby user account that has access to the library. If multiple Emby users share one Roku device, switching profiles doesn't automatically reload the library list. You need to fully restart the Roku channel after switching accounts for the permissions to take effect.

Open Settings inside the Roku app

Inside the Emby channel itself — not the Roku OS settings — navigate to the gear/Settings icon, then Display. You're looking for a setting specifically inside the Emby app, not anywhere in Roku's system menus.

Toggle 'Display Folders' or 'Show Folder View'

Find the setting called Display Folders or Show Folder View and enable it. This is a per-device client setting. It only affects this Roku. Other Emby clients (web browser, phone app, TV apps) have their own separate settings and won't be changed.

Restart the Roku channel to refresh

After enabling the setting, restart the channel. Press Home, highlight Emby, press *, choose Restart. Just pressing Back or exiting to the home screen doesn't flush the cache — you need a full channel restart for the library structure to reload correctly.

Check Library Permissions for the User Profile

Still nothing? This section covers the fix that solves probably 40% of cases where everything else looks correct.

Emby Server → Users → Library Access

In the Emby Server dashboard, go to Users, click the relevant user account, and scroll down to Library Access. You'll see a list of all libraries with checkboxes. If the box for your custom library is unchecked, that user cannot see it anywhere — not on Roku, not on the web, not on the phone app. It's completely invisible to them.

Check the box, save the user settings, then restart the Roku channel. The folder will appear.

Hidden libraries vs. blocked libraries

There's a meaningful difference here. A library set to "Hidden from main view" just removes it from the home screen but it's still accessible via folder browsing and direct navigation. A library blocked via user permissions means that user can't see it at all. If you set a library to hidden-from-main-view during setup and forgot, that explains why it's missing from the home screen but might still be reachable through folder browse mode.

Parental controls and content rating filters

Parental controls can silently wipe out content. If you have a content rating filter on the user profile — blocking unrated content, for instance — any media without proper metadata ratings just vanishes from the view. Check the user's parental control settings in the Emby dashboard and either disable the filters or make sure your media has ratings assigned via a metadata scan.

Troubleshooting: Folder Still Not Showing

Worked through everything above and still stuck? Here's how to actually diagnose what's going wrong rather than guessing.

Force a full library scan

Dashboard → Libraries → three-dot menu → Refresh Metadata → Replace existing. This forces Emby to re-read every file path from scratch. It catches timing issues where the initial scan ran before the folder was fully written, and it also updates metadata that might be filtering content out of view.

Clear Roku app cache or reinstall the channel

Roku OS 13+: Settings → System → Advanced system settings → Channel data and storage → clear cache for Emby. If that's not available per-channel, remove the Emby channel entirely (Home → highlight → * → Remove channel), then re-add it from the Channel Store. You won't lose server data — just re-enter your server address and credentials after reinstalling.

Check Emby Server logs for path errors

Emby's logs show exactly which paths were scanned and why they failed. Log locations:

• Windows: %ProgramData%\Emby-Server\logs\
• Linux: /var/lib/emby/logs/
• Docker: check your mapped logs volume, or run docker logs emby-server

Search the log for your folder path. "Access denied" or "Path not found" means a permissions problem. Path found but 0 files? Either the folder is empty, there's a Docker bind mount issue, or files are being filtered by content type rules.

Verify network share is mounted at server boot

This one catches NAS users constantly. The SMB or NFS share mounts fine manually, Emby scans it, everything works — then the server reboots. The share isn't mounted at boot, so Emby sees an empty directory or a missing path. Fix: add the mount to /etc/fstab on Linux, or use a systemd mount unit with _netdev and x-systemd.automount options. On Windows, map the network drive to a letter, set it to reconnect at login, and run the Emby service as a domain/local user account that has access — not Local System, which can't see mapped drives.

Confirm Roku and server are on the same network or Emby Premiere is active for remote

The how to show folder in emby on roku process assumes both devices are on the same local network. If your Roku is on a different VLAN from the Emby Server, mDNS discovery won't cross the boundary — you'll need to enter the server IP manually in the Roku app's server settings. For streaming from outside your LAN entirely, Emby Premiere is required for transcoding; without it, only files that direct-play on Roku will work, and everything else will fail with a generic error.

Best Practices for Organizing Folders for Roku Playback

Getting the folder to appear is half the battle. Getting things to actually play back smoothly is the other half.

Recommended folder structure for movies and TV

For reliable metadata matching, stick to these patterns:

• Movies: Movie Name (Year)/Movie Name (Year).mkv
• TV Shows: Show Name/Season 01/Show Name S01E01.mkv

Emby matches against TheTVDB and TMDb. Names that don't follow the expected pattern often match wrong or don't match at all. Unmatched items still appear in folder view but show no posters, descriptions, or episode data. Not a dealbreaker, but worth fixing.

Container and codec compatibility with Roku

What Roku handles natively without requiring transcoding:

• Video: H.264 (all Roku models), H.265/HEVC (4K-capable models only — Roku Ultra, Streaming Stick 4K, Express 4K+)
• Audio: AAC, AC3/Dolby Digital, EAC3 on most current models
• Containers: MP4, MKV, MOV

DTS audio is garbage on Roku — it won't play natively on any current model. Emby has to transcode the audio track to AC3 before sending it. If you see video playing silently or get "incompatible media" errors, DTS is almost certainly the cause. Make sure Emby Server has either enough CPU or hardware acceleration (Intel Quick Sync, NVENC) enabled to handle real-time audio transcoding.

For 4K content, anything above around 40 Mbps will stutter on Wi-Fi. The Roku Ultra has a physical Ethernet port — use it for large files. Streaming Stick models are Wi-Fi only, so high-bitrate 4K remuxes will be a problem regardless of how good your router is.

When direct play works vs. when transcoding kicks in

Direct play means Emby sends the original file unmodified and Roku decodes it natively. This is always the better path — zero CPU load on the server, no quality loss, lower latency. Transcoding starts when the codec isn't natively supported by Roku, the estimated bitrate exceeds Roku's limit, or subtitles require burning in (ASS/SSA subtitles always trigger transcoding; SRT and PGS usually direct play fine).

In the Emby Server dashboard under Transcoding, enabling hardware acceleration dramatically reduces the CPU hit when transcoding is unavoidable. Worth setting up if your server supports it.