Jellyfin reads your movie and television files from the filesystem; it does not normally make a second, permanent copy of every video. It does, however, maintain a separate server data set: a library database, configuration, logs, cache, web-client files, metadata, artwork, chapter previews, subtitles, trickplay data, and temporary transcoded output. The exact directories depend on your operating system, installation method, and library settings. Treat original media, persistent server data, and disposable transcode space as three different storage and backup responsibilities.
What Jellyfin stores—and what it does not
Your source movies and shows remain ordinary files in folders that Jellyfin can read. The server indexes those files and serves them to clients; it is not designed to replace them with an opaque proprietary copy. That distinction matters when you estimate disk use or plan a backup: losing the database can damage the library’s organization and settings, while losing the source files removes the actual media.
As an Amazon Associate I earn from qualifying purchases.
Alongside the source tree, Jellyfin can create data used to identify, sort, display, search, and play the library. Some of it is persistent, such as the SQLite database and downloaded artwork. Some is optional, such as chapter preview images or trickplay thumbnails. Some is temporary, such as a video generated for a particular playback session. A server can therefore consume substantially more space than the visible size of its movie and show folders, but the amount depends on enabled features, library size, client compatibility, and bitrate choices.
Free tools Windows power users keep installed
One-click scans. No signup required.
Jellyfin’s main storage areas
Jellyfin separates the roles of its data, configuration, cache, web, and log directories. Defaults vary by platform and deployment, and administrators can override them with command-line switches or environment variables. Do not assume that a path shown in a guide for Linux, Windows, or a container applies to your installation.
#1 Best Overall
- Read Before You Buy — No Video Output: These adapters support charging and USB 2.0 data transfer, but cannot transmit video signals. Except for standard USB webcams (which use USB data only), they are not compatible with HDMI/DisplayPort cables, video-capable USB-C hubs, or docking stations with video output.
- Convert USB-A Ports to USB-C: Designed to connect USB-C earphones, cables, flash drives, card readers, and other USB-C accessories to standard USB-A ports. Plug-and-play with no drivers or software required.
- Aluminum Alloy Housing: Built with a sturdy aluminum alloy shell that aids in heat dissipation and protects against daily wear and scratches. Designed to maintain a stable and secure connection.
- Compact & Travel-Friendly: The ultra-compact design allows the adapter to stay plugged into your device without blocking adjacent ports or adding bulk, reducing wear and tear on your original USB ports.
- 12-Month Warranty: Backed by a 12-month manufacturer warranty for peace of mind. Designed to meet strict quality control standards for reliable everyday performance.
| Area | What it contains | How to treat it |
|---|---|---|
| Source media | Your original movie, episode, music, and other media files read from the filesystem. | Primary content. Back it up separately from Jellyfin’s server data. |
| Data directory | The library database and generated server data. The default SQLite database is <Data Directory>/jellyfin.db. |
Persistent and important. Keep the database on local storage, not a network storage device, according to Jellyfin’s storage guidance. |
| Configuration directory | Server and feature settings, including library and playback configuration. | Back up if you want to rebuild the same server configuration. |
| Metadata directory | Downloaded or generated metadata, artwork, and chapter images, depending on settings. | Back up the portions you want to preserve, especially if redownloading would be difficult. |
| Cache directory | Cached data used to improve operation and, in some deployments, web-client assets or processing intermediates. | Usually rebuildable, but it can be large and should have adequate free space. |
| Web directory | Built files for Jellyfin’s hosted web client when that deployment uses a separate web directory. | Deployment-dependent; do not treat one platform’s path as universal. |
| Log directory | Server and task logs used for diagnosis. | Useful for troubleshooting; rotate or retain them according to your operational needs. |
| Transcode directory | Temporary encoded video, audio, and related playback output. | Scratch space. It can grow quickly and is not a replacement copy of your library. |
The configuration documentation describes advanced database options as non-stable interfaces. In practice, that means you should not build an automated migration or backup design around undocumented database behavior; use the supported configuration for your installed release and verify paths in that deployment.
Metadata: database records, NFO files, and provider data
The library database
Jellyfin records library relationships and state in its database: which files belong to which movies or series, titles and IDs, playback positions, user-related library state, provider identifiers, and other server information. The default database is SQLite in the data directory. It is separate from the video files, even when the videos are stored on a different volume.
A database entry is not the same as a downloaded poster or a sidecar file. It points to and organizes information that may also be represented in files, allowing Jellyfin to rescan and present the collection efficiently. If the database is lost, the media files can still exist, but you may need to rebuild indexes, settings, and watched-state information.
Do these 3 things before closing this tab:
1Scan for outdated or missing drivers - takes under a minute2Repair Windows errors before they cause bigger problems3Fix the driver behind crashes, sound loss and screen glitchesRemote providers and local NFO metadata
Jellyfin can obtain titles, descriptions, cast, ratings, release information, and artwork from configured remote providers. It can also read local NFO files stored with the media. The Jellyfin Project’s local NFO documentation states: “Local metadata will always be fetched and has priority over remote metadata providers like TMDb.” This lets you keep a deliberately curated title, sort name, plot, or identifier instead of allowing a later provider refresh to replace it.
Artwork follows an additional precedence rule. Artwork paths or URLs referenced in an NFO take priority over remote artwork providers and over images found in the media folders. Consequently, deleting or editing an NFO can change what appears in the client even though the video itself has not changed. If a poster seems “stuck,” inspect the local metadata and artwork references before repeatedly refreshing remote providers.
Rank #2
- 5-in-1 USB-C Hub: Experience comprehensive connectivity featuring a Power Delivery input, two USB-A 2.0 ports, a USB-A 3.0 port, and an HDMI port. (Note: The USB-C power delivery input port is only for connecting an external wall charger to power your laptop and cannot power peripheral devices.)
- 90W Pass-Through Charging: Achieve optimal charging with 90W pass-through power to your laptop, supported by a total input of 100W, with the hub reserving 10W for operational efficiency. (Note: Wall charger not included.)
- Quick Data Transfers: Accelerate your productivity with rapid data transfers using a high-speed 5Gbps USB 3.0 port and two 480Mbps USB 2.0 ports.
- 4K HDMI Display: Enhance your visual experience with a hub capable of delivering 4K resolution at 30Hz in both mirror and extend modes. Please note that this hub is compatible with MacBook (macOS 12 and newer), Windows 10 and 11, ChromeOS, and laptops equipped with DP Alt Mode and Power Delivery. Note: This device is not compatible with Linux.
- What You Get: Anker USB-C Hub (5-in-1, 4K HDMI), welcome guide, 18-month warranty, and our friendly customer service.
Where metadata files appear
Depending on library settings, Jellyfin may write metadata and images into its metadata area, beside the media, or both. A sidecar NFO and poster next to an episode are ordinary filesystem files and must be included in a backup if you rely on them. Generated server metadata kept outside the media tree belongs in the Jellyfin data backup instead. The precise behavior is controlled by your library configuration and can differ between libraries.
Artwork and chapter images are different kinds of data
Posters, backdrops, logos, season art, thumbnails, and other images can come from providers, local files, or NFO references. High-resolution collections and multiple artwork types add up over time, particularly when you retain several images per item or allow automatic downloads after a metadata refresh.
Quick wins for a faster PC:
Repair Windows errors before they cause bigger problemsFix Now →Fix the driver behind crashes, sound loss and screen glitchesFind Drivers →Clear out junk files and repair common Windows errorsFree Scan →Chapter images
Chapter images are generated preview pictures associated with video chapters and stored in Jellyfin’s metadata directory. The project describes them as “a type of metadata for video media files stored in Jellyfin.” They are not the same as chapter markers. A client can display chapter names and time positions without a preview image when chapter-image extraction is disabled.
Generating previews requires reading and processing video frames. It can lengthen scans and consume additional CPU, I/O, and storage, especially in a large film library. Enable it when visual chapter navigation is worth the cost; otherwise, disabling extraction avoids creating that image set while preserving ordinary chapter markers.
Media segments add labels, not replacement videos
Since Jellyfin version 10.10, segment metadata can label intervals such as intro, commercial, recap, outro, preview, or other available types. Plugins provide the segment information, and compatible clients decide whether to show or skip those intervals. Segment records describe portions of existing media; they are not duplicate movie files. Their usefulness therefore depends on both the plugin that supplies them and the client used for playback.
Rank #3
- Sleek 7-in-1 USB-C Hub: Features an HDMI port, two USB-A 3.0 ports, and a USB-C data port, each providing 5Gbps transfer speeds. It also includes a USB-C PD input port for charging up to 100W and dual SD and TF card slots, all in a compact design.
- Flawless 4K@60Hz Video with HDMI: Delivers exceptional clarity and smoothness with its 4K@60Hz HDMI port, making it ideal for high-definition presentations and entertainment. (Note: Only the HDMI port supports video projection; the USB-C port is for data transfer only.)
- Double Up on Efficiency: The two USB-A 3.0 ports and a USB-C port support a fast 5Gbps data rate, significantly boosting your transfer speeds and improving productivity.
- Fast and Reliable 85W Charging: Offers high-capacity, speedy charging for laptops up to 85W, so you spend less time tethered to an outlet and more time being productive.
- What You Get: Anker USB-C Hub (7-in-1), welcome guide, 18-month warranty, and our friendly customer service.
Subtitles and trickplay data
Subtitles may be embedded in a source file, extracted during library processing, or downloaded and stored as separate files. Whether a subtitle becomes a persistent sidecar, remains inside the media container, or is cached elsewhere depends on the source and your settings. If subtitles are important to your household, include downloaded or extracted subtitle files in the backup set rather than assuming they can always be recreated.
Recommended Free Tools
Trickplay data consists of seek-preview images or related indexes that let a compatible client show a thumbnail timeline while you scrub. Jellyfin’s built-in backup allows subtitles and trickplay to be selected as backup contents in addition to the database and metadata. Trickplay can be stored outside the media tree, so check the configured data locations before excluding it from a backup.
Why the transcode folder gets so large
Transcoding is demand-driven playback output
A client reports a transcoding profile describing capabilities such as supported codecs, resolutions, bitrate, and additional constraints. Jellyfin compares those capabilities with the source file and the requested playback conditions. If the client cannot direct-play the source, the server may generate a compatible video, audio stream, or both. The resulting files are playback output, not replacement copies of your original library.
Different users and devices can trigger different outputs from the same source. A phone on a constrained connection may request a lower-resolution, lower-bitrate encode, while a modern television may direct-play the original. Seeking, subtitles that must be burned into video, incompatible audio codecs, and bandwidth limits can also change the amount of temporary data produced.
Space and lifetime
The transcode path is configurable and should be considered scratch space with enough headroom for concurrent sessions. A stopped session may leave files until Jellyfin cleans them up, and an interrupted process can leave residue that warrants inspection. Never delete source media to solve a transcode-space emergency; identify the configured transcode directory and clear only files that are no longer in use.
Rank #4
- Dual Converters, Infinite Potential：Includes 2× USB C male to USB A female adapters and 2× USB A male to USB C female adapters. Perfect for a wide range of uses—tablets with Bluetooth keyboards, expand USB ports on macbook, and more. Two different converters for all your daily needs
- Next-Level 10Gbps & 3A Charging: No more slow 480Mbps, this usb to usb c adapter has a transfer speed of up to 10Gbps, allowing you to do more transferring in less time. This usb adapter fits both USB A and USB C charger, supporting up to 3A fast charging
- Upgraded Exquisite Craftsmanship: With an aluminum alloy housing and metal connector, the usbc to usb adapter is extremely durable and sturdy. Rigorously tested to withstand more than 10,000 times of plugging and unplugging, ensuring long-lasting performance
- Broad Compatible: The usb c to usb adapter widely supports all USB C/ USB A devices like laptops, tablets, cellphones, car chargers, and phone chargers. Such as compatible with MacBook Pro/Air 2023/2022, Thunderbolt 4/3 Devices,Apple MagSafe Watch 9/8/7/SE/Ultra, iPad Pro 2022/2021, Samsung Galaxy S23/S20/S10, and iPhone 17/16/15 Pro. Plug and play
- Please Note: To reach 10Gbps speed, keep the cable under 3.3 ft. For USB A Male to USB C adapters, try flipping the USB C connector. USB C Male to USB A adapters support bidirectional 10Gbps transfer within 3.3 ft
Jellyfin’s storage documentation gives planning examples rather than guarantees. It says a transcode folder typically needs about as much space as the original media when transcoding at an equivalent bitrate. A 50 GB Blu-ray remux could produce roughly 60 GB at one output bitrate or roughly 15 GB at another. The source, codec, resolution, duration, selected bitrate, and number of simultaneous sessions determine the real result.
How much extra capacity should you plan?
Use measurements from your own library after enabling the features you actually need. The following figures are Jellyfin Project documentation examples, not promises for every installation.
| Item | Published example or rule of thumb | Qualification |
|---|---|---|
| Database | 10–100 GB for a moderate-sized library | A broad planning range from Jellyfin’s storage documentation; actual size varies with library contents and enabled data. |
| Equivalent-bitrate transcode | About the same space as the original media | Applies to the documentation’s equivalent-bitrate example, not every encode. |
| 50 GB Blu-ray remux | About 15 GB to about 60 GB of transcode output | The range reflects different output bitrates; it is an illustration, not a fixed conversion ratio. |
Leave free space for scans, artwork refreshes, database maintenance, and simultaneous transcodes. A volume that is technically large enough for today’s files can still fail when a scan and several playback sessions need temporary working room.
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.Backup strategy: separate irreplaceable media from rebuildable data
Use separate decisions for the source library and the Jellyfin server. The source files are the irreplaceable content; Jellyfin’s database and configuration preserve organization, users, playback state, and settings. A practical backup set should include:
- Original media: back up according to your own retention and off-site plan.
- Database: include
jellyfin.dband follow a consistent, application-safe backup procedure. - Configuration: preserve server and library settings so a rebuild does not require manual recreation.
- Selected metadata and artwork: include generated data you do not want to redownload and any sidecar NFO or image files you intentionally maintain.
- Subtitles and trickplay: select these in Jellyfin’s built-in backup when they matter to your setup.
- Logs and cache: retain them only when their diagnostic or operational value justifies the space; they are generally less critical than the database and source media.
Do not treat the transcode directory as a backup. It can be regenerated from the source files and playback request, whereas a deleted film cannot.
Best Value
- 5-in-1 Connectivity: Equipped with a 4K HDMI port, a 5 Gbps USB-C data port, two 5 Gbps USB-A ports, and a USB C 100W PD-IN port. Note: The USB C 100W PD-IN port supports only charging and does not support data transfer devices such as headphones or speakers.
- Powerful Pass-Through Charging: Supports up to 85W pass-through charging so you can power up your laptop while you use the hub. Note: Pass-through charging requires a charger (not included). Note: To achieve full power for iPad, we recommend using a 45W wall charger.
- Transfer Files in Seconds: Move files to and from your laptop at speeds of up to 5 Gbps via the USB-C and USB-A data ports. Note: The USB C 5Gbps Data port does not support video output.
- HD Display: Connect to the HDMI port to stream or mirror content to an external monitor in resolutions of up to 4K@30Hz. Note: The USB-C ports do not support video output.
- What You Get: Anker 332 USB-C Hub (5-in-1), welcome guide, our worry-free 18-month warranty, and friendly customer service.
Storage placement and performance choices
Keep the database local
Jellyfin’s storage guidance says, “The Jellyfin database should also be stored locally and not on a network storage device.” Network-attached media can be appropriate when throughput and reliability are sufficient, but database latency and locking behavior make a local disk a safer default for the server data. Keep a tested backup elsewhere even when the working database is local.
ZFS-specific considerations
Jellyfin’s current storage page gives ZFS-specific record-size recommendations for the SQLite database dataset and for large media datasets. It also warns against placing server data other than media on ZFS-formatted mechanical drives because of performance. These are ZFS and hardware-context recommendations, not universal filesystem rules. Check the current Jellyfin guidance and your ZFS layout before changing record sizes or moving datasets.
TrueNAS SCALE deployments
The Jellyfin guide for TrueNAS SCALE describes separate configuration, cache, and transcode storage, with SSD storage recommended for configuration and cache. It warns that RAM-backed transcode storage can run out of room and cause a transcode to fail. That advice is specific to the platform’s deployment model; do not infer that every Jellyfin server needs a RAM disk or that an SSD is mandatory.
When an SSD is justified
An SSD can be useful for the database, configuration, cache, or transcode scratch area when scans, concurrent users, thumbnail generation, or random I/O are bottlenecks. It is a capacity-and-performance choice, not a Jellyfin requirement. Match the device to measured workload and free-space needs, and keep the original media on storage suited to its size, redundancy, and access pattern.
Diagnosing unexpected disk usage
- Identify the configured directories. Check the installation’s data, config, cache, web, log, metadata, and transcode settings rather than searching only beside the movies.
- Measure each area separately. A large metadata tree, database, or transcode directory has a different remedy from a growing source library.
- Check active sessions. Confirm that no user is currently transcoding before removing temporary output.
- Review optional generators. Chapter images, trickplay, downloaded artwork, and extracted subtitles can each account for growth.
- Inspect local metadata precedence. NFO files and their artwork references can cause Jellyfin to retain or display files you did not expect a remote provider to control.
- Protect free space. Leave room for scans and concurrent playback; a full cache or transcode volume can cause failures even when the source volume still has capacity.
The key question is not “Why did Jellyfin duplicate my movies?” It is “Which category is consuming space, and is that category persistent, optional, or temporary?” Once those roles are separated, you can clean scratch data safely, preserve the metadata you value, and size backups around the files that actually matter.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
