Docker ConsiderationsIf you are running NZBGet in a Docker container, your "Download Folder" inside the NZBGet settings must match the "Container Path" you mapped in your Docker configuration. If you map /mnt/user/downloads to /downloads, you must enter /downloads in the NZBGet settings. Final Verification
Before changing paths, it is important to understand how NZBGet handles files. It uses two primary folders: nzbget set download folder
If you want it in a completely different location, enter the full path (e.g., D:\Downloads\Completed). Click Save Changes at the bottom of the page. Click Reload to apply the new settings. Essential Sub-Directory Settings Docker ConsiderationsIf you are running NZBGet in a
Locate the MainDir field. If you want everything (logs, temporary files, and downloads) in one place, enter your preferred path here (e.g., /mnt/downloads/nzbget). It uses two primary folders: If you want
Absolute vs. Relative PathsOn Windows, always use absolute paths including the drive letter (e.g., E:\Downloads). On Linux, ensure you use the full mount path. Avoid using relative paths like ./downloads as they can become "lost" if the service restarts from a different working directory.
InterDir (Intermediate Directory)This is where files sit while they are being downloaded and par-verified. If you have an SSD, set your InterDir there. This speeds up the "Repair" and "Unpack" phases significantly because these tasks are heavy on disk I/O.
While the DestDir is the "final" home for your files, two other paths are critical for performance: