2024-07-19, 01:27 PM
(This post was last modified: 2024-07-19, 01:27 PM by TheDreadPirate.)
The size of your library in TB matters less than the number of items since the amount of metadata Jellyfin stores grows with each item added. 50GB is the bare minimum due to the size of the database, the size of the metadata folder (biggest contributor), caching, and then there's the transcode directory, which can grow very large for 4K media. The transcode directory can be relocated in Dashboard > Playback, but by default it is in /config/transcodes.
You can have jellyfin's /config directory on the same drive as your media. Just be aware of how much free space is left. Many, many, users have come here asking how their database got corrupted only to realize the disk is completely full.
Don't feel like you NEED to have the /config directory on a SSD. Many people run it from the SD card in their RPi.
You can have jellyfin's /config directory on the same drive as your media. Just be aware of how much free space is left. Many, many, users have come here asking how their database got corrupted only to realize the disk is completely full.
Don't feel like you NEED to have the /config directory on a SSD. Many people run it from the SD card in their RPi.
Jellyfin 10.10.3 (Docker)
Ubuntu 24.04 LTS
Intel i3 12100
Intel Arc A380
OS drive - SK Hynix P41 1TB
Storage
3x WD Red Pro 6TB CMR in RAIDZ1 (JF Library)
![[Image: GitHub%20Sponsors-grey?logo=github]](https://img.shields.io/badge/GitHub%20Sponsors-grey?logo=github)
Ubuntu 24.04 LTS
Intel i3 12100
Intel Arc A380
OS drive - SK Hynix P41 1TB
Storage
3x WD Red Pro 6TB CMR in RAIDZ1 (JF Library)