Community Apps

Browse our large and growing catalog of applications to run in your Unraid server. 

Download the Plugin  |  Become a Community Developer


Community-built

All the applications you love—built and maintained by a community member who understands what you need on Unraid. Love a particular app or plugin? Donate directly to the developer to support their work.

Created by a Legend

Andrew (aka Squid) has worked tirelessly to build and enhance the experience of Community Apps for users like you.

Moderated and Vetted

Moderators ensure that apps listed in the store offer a safe, compatible, and consistent experience. 


tvh-iptv-config's Icon

tvh-iptv-config

Media ServersVideo

TVH-IPTV-Config - A simple IPTV config frontend for playlist filtering providing a M3U proxy for Plex, Emby, Jellyfin and (of course) Tvheadend. TVH-IPTV-Config (TIC) attempts to provide a simple IPTV config frontend for a Tvheadend (TVH) backend. In addition to this, it provides HDHomeRun tuner emulation, an HLS playlist proxy/caching and custom channel mapping from multipl playlist sources. Note: This template is a stand-alone installation of TIC and requires that you, the user, also install and maintain a seperate Tvheadend container. Currently, only TVH v4.3+ is tested and supported, though 4.2.8 may work fine. You will need to ensure you have the 'XMLTV URL grabber' module installed with your TVH server. If you want to run TIC without managing your own TVH backend, then you should look at using the "tvh-iptv" template which provides an AIO docker container solution. Features: Easily import/configure channels from playlists. Assign and locally cache logos per channel. Assign EPG sources for each channel. Configure channel numbers and ordering for channels. Configure multiple stream sources per channel. Manage and search through playlists that contain tens of thousands of streams without crashing the UI. Provide an ffmpeg buffer for your streams so multiple devices playing back the same stream will only use one playlist connection. Serve an HDHomeRun emulator for each playlist so Plex, Emby, and Jellyfin can connect to it an saturate the number of configured connections per playlist. Automatically fetch missing metada for your EPG programme schedule like icons, description, etc. Configure and automatically actively maintain a Tvheadend backend for IPTV without the fuss. Automatically generate IPTV networks in TVH per playlist configured with a number of connections allowed. Automatically manage a custom EPG based on channel selection. Automatically create muxes in TVH for each stream asssociated with a configured channel. Configure muxes with FFmpeg pipes to improve compatibility and provide a local buffer. Automatically map mux services to channels in TVH. Automaticlaly configure optimal streaming and timeseries settings. Automaticlaly configure optimal recording settings. Much more little tweaks behind the scenes... How it works: Tvheadend(https://www.tvheadend.org/), AKA "TVH", is a TV streaming server and recorder supporting, among other things, IPTV input sources. Tvheadend offers the HTTP (VLC, MPlayer), HTSP (Kodi, Movian) and SAT>IP streaming and there are a bunch of clients out there to use as clients for watching. The catch is that on its own, Tvheadend can be complicated to setup for IPTV. Once you read through all the documentation and forum posts on how to do it, it works well. But that is a steep learning curve. In addition to this, if you were to just throw a IPTV playlist of thousands of channels at the thing, well... good luck with that mess. To get it working really well, there is a lot of mouse clicking here and there and perhaps the odd ffmpeg pipe to configure on each MUX and... who as time for that! TIC should make life easy(ish) when setting up IPTV on Tvheadend. Advanced Configuration: LIMIT CPU USE: 1) Toggle this Docker Container template editor to "Advanced View". 2) In the "Extra Parameters" field, add "--cpus='1'". This value depends on the number of cores available to the container. To limit to 50%, set this value to 0.5 * n cores. If you have 2 cores available to this container, "--cpus='.5'" will equal 25% of that available CPU resources. To limit the CPU cores available to the continer, use "CPU Pinning" LIMIT RAM ALLOCATION: 1) Toggle this Docker Container template editor to "Advanced View". 2) In the "Extra Parameters" field, add "--memory='1g'". Tvheadend and TIC can use on average around 100Mib - 500 Mib of RAM for various tasks. Even though limiting RAM is unnecessary as this container should not ever need more that 1GB RAM it is good practice to do so.

tvheadend's Icon

tvheadend

Media ServersVideo, Other

Tvheadend(https://www.tvheadend.org/) works as a proxy server: is a TV streaming server and recorder for Linux, FreeBSD and Android supporting DVB-S, DVB-S2, DVB-C, DVB-T, ATSC, ISDB-T, IPTV, SATIP and HDHomeRun as input sources. Tvheadend offers the HTTP (VLC, MPlayer), HTSP (Kodi, Movian) and SATIP streaming. Multiple EPG sources are supported (over-the-air DVB and ATSC including OpenTV DVB extensions, XMLTV, PyXML).

twonky-server's Icon

TwonkyMedia server (TMS) is DLNA-compliant UPnP AV server software from PacketVideo. TwonkyMedia server can be used to share and stream media to most UPnP AV or DLNA-compliant clients, in addition to non-UPnP devices through the HTML, RSS, and JSON supported front ends.

Universal-Media-Server's Icon

Universal-Media-Server

Media ServersMusic, Photos, Video

Universal Media Server is a DLNA-compliant UPnP Media Server. It is capable of sharing video, audio and images between most modern devices. It was originally based on PS3 Media Server by shagrath, in order to ensure greater stability and file-compatibility. This is a headless install, you need to edit the file UMS.conf in oder to configure it. Refer to the default file below https://raw.githubusercontent.com/UniversalMediaServer/UniversalMediaServer/master/src/main/external-resources/UMS.conf Note: you may need to stop the container before editing the config file, otherwise your changes might not get saved.

Watchlistarr's Icon

Watchlistarr

Media ServersVideo

Sync RSS Plex watchlists in realtime with Sonarr and Radarr https://github.com/nylonee/watchlistarr

zappiti-server's Icon

zappiti-server

Media ServersMusic, Photos, Video

Docker container to install and run Zappiti Server app as a local Cloud to manage your library using your Unraid server. Your files used for the collection are saved only on your machine.

Zoneminder's Icon

Zoneminder is the top Linux video camera security and surveillance solution. ZoneMinder is intended for use in single or multi-camera video security applications, including commercial or home CCTV, theft prevention and child, family member or home monitoring and other domestic care scenarios such as nanny cam installations. It supports capture, analysis, recording, and monitoring of video data coming from one or more video or network cameras attached to a Linux system. ZoneMinder also support web and semi-automatic control of Pan/Tilt/Zoom cameras using a variety of protocols. It is suitable for use as a DIY home video security system and for commercial or professional video security and surveillance. It can also be integrated into a home automation system via X.10 or other protocols. If you're looking for a low cost CCTV system or a more flexible alternative to cheap DVR systems then give ZoneMinder a try. Configuration: Appdata Config Path - This is where the configuration and library files will reside Data Path - This is where events images/videos will reside WebUI Port - Port used to access Zoneminder using ssl security. Change the desired port for access to the Zoneminder WebUI if necessary. The default port of 8443 might not be appropriate for your system. Shared Memory - Turn on the advanced view and adjust the '--shm-size' in the Extra Parameters to half of your installed memory. zmNinja Event Notification Server Port - Port used for zmNinja events to iOS and Android devices. Change the desired port for the zmNinja Event Notification Server if necessary. The default port of 9000 might not be appropriate for your system. Click on "Show Docker Allocations" and confirm you do not have a port conflict with other Docker ports.