Free tools Windows power users keep installed
One-click scans. No signup required.
Move Jellyfin’s data, configuration and cache directories as a controlled relocation, not as a new-server migration: identify the paths Jellyfin is actually using, stop the server, make a recoverable copy, copy the directories to the destination drive, update the path settings or container mounts, fix ownership and permissions, then start Jellyfin and verify the existing libraries, users and settings before deleting the original.
Metadata is normally part of Jellyfin’s data and database state, while the cache is a separate path. They may already be on different volumes, so check each configured path instead of assuming one default folder contains everything.
As an Amazon Associate I earn from qualifying purchases.
What you are moving
Jellyfin keeps server state in several locations rather than one universal “metadata folder.” The important locations are data, configuration, cache, web files and logs. Library metadata and the internal database are part of the data state; configuration contains server settings; cache contains replaceable generated files. The exact directories depend on the operating system, installation method and any overrides you have set.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
A same-server relocation should preserve the existing files. That is different from creating a new Jellyfin instance or migrating between unrelated servers. Jellyfin cautions that its internal databases are not easy to copy or adjust as part of a general migration. For a drive relocation, keep the database and configuration intact and point Jellyfin to their new locations instead of allowing it to rebuild them.
#1 Best Overall
- Get NVMe solid state performance with up to 1050MB/s read and 1000MB/s write speeds in a portable, high-capacity drive(1) (Based on internal testing; performance may be lower depending on host device & other factors. 1MB=1,000,000 bytes.)
- Up to 3-meter drop protection and IP65 water and dust resistance mean this tough drive can take a beating(3) (Previously rated for 2-meter drop protection and IP55 rating. Now qualified for the higher, stated specs.)
- Use the handy carabiner loop to secure it to your belt loop or backpack for extra peace of mind.
- Help keep private content private with the included password protection featuring 256‐bit AES hardware encryption.(3)
- Easily manage files and automatically free up space with the SanDisk Memory Zone app.(5). Non-Operating Temperature -20°C to 85°C
Find Jellyfin’s real paths before touching files
Do not start by copying a directory from a forum example. First record the Jellyfin version and the paths currently in use. Jellyfin’s Dashboard Paths view is useful for mapping the active locations, and the path documentation explains the precedence rules.
Path precedence
For the data directory, Jellyfin checks an explicit --datadir command-line option first, then the JELLYFIN_DATA_DIR environment variable, then the platform default. Configuration and cache follow the same pattern with --configdir/JELLYFIN_CONFIG_DIR and --cachedir/JELLYFIN_CACHE_DIR. A service file, container definition or launcher can therefore override what you expect from a default installation.
| State | Controls to check | Why it matters |
|---|---|---|
| Data | --datadir or JELLYFIN_DATA_DIR |
Contains the database and server data, including the state that describes libraries and metadata. |
| Configuration | --configdir or JELLYFIN_CONFIG_DIR |
Preserves server configuration and related settings. |
| Cache | --cachedir or JELLYFIN_CACHE_DIR |
Stores cache data that Jellyfin can regenerate, but which may still be large and useful to retain during a move. |
On non-Windows systems, defaults can follow XDG locations. Windows defaults differ between a tray application and a directly launched server. Linux packages, Windows services, portable builds and containers can all place these directories differently.
Common examples, not universal answers
| Installation type | Documented example | Qualification |
|---|---|---|
| Debian or Ubuntu package | Data: /var/lib/jellyfin; configuration: /etc/jellyfin |
Use these only when your package installation is using its defaults. |
| Windows service | C:ProgramDataJellyfinServer |
The service account and any configured overrides still determine access and active paths. |
| Official container | Wherever the host directory or volume mapped to /config is sourced |
The host path and the path visible inside the container are both significant. |
Record all three active paths, plus the media paths shown in your libraries. You are not required to move media merely because metadata is moving; you must ensure existing media remains reachable at the paths Jellyfin expects.
Prepare a safe relocation
Check the destination drive
Measure the current data, configuration and cache directories, then leave free space for growth and a second backup copy. Jellyfin’s storage documentation says a database for a moderate-sized library can grow anywhere from 10 to 100 GB. That is a broad possible range, not a capacity requirement for every server.
Rank #2
- Solid state performance with up to 800MB/s read speeds in a portable drive. (Based on internal testing; performance may be lower depending on host device, interface, usage conditions and other factors. 1MB=1,000,000 bytes.)
- Back up your content and memories on a storage solution that fits seamlessly into your mobile lifestyle.
- Take it with you on your adventures—up to two-meter drop protection means this durable drive can take a beating. (Based on internal testing.)
- Secure it to your belt loop or backpack for extra peace of mind thanks to the tough rubber hook.
- From Sandisk, a brand professional photographers trust to take on assignments.
Keep the database on storage directly attached to the server. Jellyfin states that the database should be stored locally rather than on a network storage device. Network storage can still be used for media when your setup supports it, but do not place the database itself on a network share as part of this move.
For TrueNAS SCALE, Jellyfin recommends SSD datasets for configuration and cache. The documentation does not prescribe a particular consumer drive, interface, capacity or speed. Choose an SSD when your host and workload justify it, while comparing capacity, local attachment, interface compatibility, expected read/write activity and how the drive will be backed up.
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 →Plan for rollback
- Keep the original directories untouched until the new location has passed verification.
- Have enough space for a complete copy, not just selected database files.
- Write down the old and new paths and the account that runs Jellyfin.
- Do not perform the move while Jellyfin is writing to its database.
Step-by-step move on a package, service or portable installation
- Record the current state. Note the Jellyfin version, active data, configuration and cache paths, service or launcher type, and the account that runs it. Capture the library paths as well so you can distinguish a metadata move from a media-path change.
- Stop Jellyfin completely. Stop the operating-system service or close the application, then confirm that the process has exited before copying anything. Jellyfin’s manual backup guidance begins by stopping the server, because a live database copy can be inconsistent.
- Make a recoverable copy. Copy each directory you intend to move, preserving its directory structure and file metadata. Treat the copy as your rollback point. A full copy of data, configuration and cache is safer than selecting only files that appear to be metadata.
- Check the destination. Browse the copied directories and verify that expected database, configuration and plugin files are present. Compare sizes or file counts where practical. Do not change Jellyfin’s settings until the destination copy is readable by the account that will run the server.
- Change the path controls. Set the appropriate
--datadir,--configdirand--cachediroptions, or setJELLYFIN_DATA_DIR,JELLYFIN_CONFIG_DIRandJELLYFIN_CACHE_DIRin the service or launcher environment. Modify the service definition or startup configuration used by your installation, not an unrelated shell profile. - Fix ownership and permissions. Grant the Jellyfin runtime account read and write access to the new data, configuration and cache paths. On Windows services, the documented default is the Network Service account; ensure that account can access the destination directory and every parent folder. On Unix-like systems, use the account and group assigned by your package or service rather than assuming your login account is correct.
- Start Jellyfin and verify the existing state. Confirm that the server opens the same libraries, users, plugins, schedules and settings. Check that metadata appears normally and that new cache files can be created. Watch the server logs for path, database or permission errors.
- Retain the old copy. Only after successful verification should you archive or remove the original directories. If the server starts as a blank instance, stop it, restore the previous path settings or point them back to the untouched copy, and investigate before trying again.
There is no single copy-and-paste service command that applies to every Jellyfin package, Windows setup and portable build. The exact service-editing procedure depends on how Jellyfin was installed, so adapt the path controls to that installation instead of applying commands intended for another one.
Moving Jellyfin in Docker or Podman
A container move has two path layers: the host location and the path inside the container. Moving a host directory without changing the bind mount or persistent volume leaves the container pointed at the old source. Conversely, changing an environment variable without mounting the new directory leaves Jellyfin with an empty or inaccessible path.
Use matching container paths
- Stop the container so files are not changing during the copy.
- Copy the host directories that back the configuration and cache volumes, preserving their contents.
- Update the compose file, container command or volume definition so the new host directories are mounted at the paths Jellyfin will use inside the container.
- Set
JELLYFIN_CACHE_DIR,JELLYFIN_CONFIG_DIRandJELLYFIN_DATA_DIRwhen your container layout requires explicit locations. - Recreate or restart the container, then verify that the internal paths contain the copied files rather than newly created empty directories.
For a Linux-to-container move, Jellyfin’s migration guidance emphasizes that the paths inside the container must match the paths Jellyfin uses. If media paths are also changed, mount the media under the paths expected by the existing library definitions or update those library paths deliberately; otherwise the libraries can appear empty even though metadata was moved correctly.
Rank #3
- Easily store and access 2TB to content on the go with the Seagate Portable Drive, a USB external hard drive
- Designed to work with Windows or Mac computers, this external hard drive makes backup a snap just drag and drop
- To get set up, connect the portable hard drive to a computer for automatic recognition no software required
- This USB drive provides plug and play simplicity with the included 18 inch USB 3.0 cable
- The available storage capacity may vary.
How to tell whether the move worked
- Libraries: Existing libraries are listed with their previous names and item counts, and media can be scanned without asking you to create new libraries.
- Metadata: Posters, descriptions, artwork and other existing metadata appear instead of being regenerated from scratch.
- Users: User accounts, permissions and viewing history remain present.
- Configuration: Server name, networking choices, scheduled tasks and plugin settings remain as before.
- Database writes: A new scan, setting change or user change persists after restarting Jellyfin.
- Cache writes: The new cache location receives files and Jellyfin does not report that the directory is read-only.
- Logs: Startup logs do not show a fallback to the old path, a missing database, a failed mount or an access-denied error.
Test a controlled change, such as updating a harmless server setting, then restart and confirm that it remains. This verifies that Jellyfin is writing to the new database and configuration paths, not merely reading a copied snapshot.
Troubleshooting common failures
Jellyfin starts with no libraries or users
This usually means Jellyfin is reading a new empty data directory. Stop the server and recheck the effective --datadir or JELLYFIN_DATA_DIR value, the service definition that supplies it, and the container-side mount if applicable. Confirm that the copied database is directly inside the configured data path rather than one directory deeper because of an extra copy level.
Metadata is missing but the server settings remain
Check that data and configuration were not accidentally pointed to different generations of the copy. Metadata state and the database belong to the data directory, while configuration is separate. Both must come from the same consistent stopped-server backup.
The service will not start after the move
Inspect ownership, permissions and parent-directory access first. A path can look readable to your administrator account while remaining inaccessible to the service account. On Windows, verify access for Network Service when that is the account configured by the service guide. On Linux, verify the package’s Jellyfin user and group. For containers, verify that the container user can access the mounted host directories.
The container shows an empty cache or configuration directory
Compare the host source and container target in the volume mapping. The directory must be mounted at the same internal path referenced by the environment variables or command-line options. A correct host copy at an unmounted location is invisible to the container.
The Tool Desk
Outbyte PC Repair FREEClear out junk files and repair common Windows errorsFree Scan →Outbyte Driver Updater FREEFix the driver behind crashes, sound loss and screen glitchesFind Drivers →Rank #4
- NEARLY 2X FASTER THAN OUR PREVIOUS GENERATION(8) – move 1,000 high-res photos in under 60 seconds(6) with up to 2000MB/s transfer speeds(2).
- IP65 RATING AND UP TO 3M DROP PROTECTION(3) – protects against spills and drops.
- POCKET-SIZED – fits easily in pockets and small bags.
- SPACE TO OWN YOUR AI CONTENT – speed and capacity to download your high-res clips and photo edits.
- 256-BIT AES ENCRYPTION(4) – helps keep private files secure with password protection.
Media appears offline after the move
Metadata relocation does not automatically rewrite library media paths. Ensure the media mount is still available at the path stored in the library definitions. When moving from a host installation to a container, expose the media inside the container under the expected path or intentionally update the libraries after the server state is confirmed.
The old drive is still receiving files
Jellyfin is still using an old override, a different service definition or a fallback default. Stop the server, inspect the effective startup arguments and environment, and check the logs for the path Jellyfin opened. Do not delete the old directory until the new location is demonstrably active.
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.Should you move data, configuration and cache together?
They are separate settings, so they do not have to share one drive. Moving them together is simpler when the destination has enough capacity and you want one clearly managed Jellyfin state volume. Splitting them can be sensible when you have a fast local SSD for database, configuration and cache but a different local disk for other server data.
| Layout | Advantages | Points to check |
|---|---|---|
| All three on one local drive | Fewer path overrides and one backup target. | Capacity, drive health and backup availability become shared dependencies. |
| Data and configuration on local SSD; cache on the same SSD | Matches the TrueNAS guidance favoring SSD datasets for configuration and cache and keeps the database local. | Confirm the SSD has adequate free space and is included in backup planning. |
| Data/configuration on one local drive; cache on another local drive | Separates cache growth from the database volume. | Set and verify both path overrides and keep both drives available at startup. |
| Database on network storage | No supported advantage for this task. | Jellyfin’s storage guidance says the database should remain local, so use local storage instead. |
Backup and rollback after the move
Keep a backup schedule for the new data and configuration paths. Cache can usually be regenerated, but retaining it during the first move makes rollback and comparison easier. The database and configuration are the critical state; back them up while Jellyfin is stopped when performing a manual copy or restore.
Recommended Free Tools
If verification fails, stop Jellyfin, restore the original path settings or the previous service/container mapping, and start it against the untouched original directories. Once the original instance is confirmed, correct one issue at a time—path precedence, copy layout, mount target or permissions—before repeating the move. Do not attempt to repair a questionable database by mixing files from the old and new copies.
Best Value
- Easily store and access 5TB of content on the go with the Seagate portable drive, a USB external hard Drive
- Designed to work with Windows or Mac computers, this external hard drive makes backup a snap just drag and drop
- To get set up, connect the portable hard drive to a computer for automatic recognition software required
- This USB drive provides plug and play simplicity with the included 18 inch USB 3.0 cable
- The available storage capacity may vary.
Frequently asked questions
How do I change Jellyfin’s cache directory?
Set the cache override used by your installation: --cachedir or JELLYFIN_CACHE_DIR. Stop Jellyfin first, copy the existing cache if you want to retain it, update the service, launcher or container configuration, grant access to the runtime account, and verify after restart that new cache files appear at the destination.
Where does Jellyfin store metadata?
Metadata is part of Jellyfin’s data and database state, but the complete data path varies by installation. Identify the active data directory in the Dashboard Paths view or from the effective --datadir/JELLYFIN_DATA_DIR setting rather than relying on a platform default.
Can I move only the cache?
Yes. Cache has its own path control, so it can be moved without relocating data or configuration. The same stop, copy, path-update and permission checks apply; leave the database on local storage.
Do I need to move my media files too?
No. Moving Jellyfin’s metadata, data or cache does not require moving media. Preserve the existing media paths or update mounts and library definitions separately if the media location changes.
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.
