NZBGet Storage Guide: Improve Performance with Smarter Path Setup

NZBGet uses multiple directories behind the scenes to manage and process your downloads. Where you place these directories – on SSDs or HDDs – can make a big difference in speed, reliability, and system responsiveness.

In this guide, we’ll explain each NZBGet path, what it does, and how to configure your storage for peak performance.


Key NZBGet Directories and What They Do

Here’s a breakdown of the most important folders used by NZBGet:

DirectoryPurpose
MainDirRoot folder that contains all other NZBGet paths
InterDirTemporary location for active downloads and unpacking
DestDirFinal destination for completed downloads
NzbDirFolder where NZB files are picked up for processing
QueueDirStores the active download queue
TempDirTemporary files and cache overflow
ScriptDirHolds post-processing and automation scripts
nzbget.logMain log file for errors and system activity

Storage Speed Recommendations

To get the best performance, it’s important to match each directory with the appropriate storage type:

🟢 Use Fast Storage (SSD) – Critical for Speed

  • InterDir: This is the most disk-intensive directory. All unpacking and post-processing happens here. An SSD will drastically reduce wait times and prevent disk bottlenecks.

🟡 Fast or Slow Storage – Depends on Your Internet Speed and Setup

  • DestDir: If you have a fast Internet connection or use automation tools like VideoSort to process large volumes of data quickly, an SSD is ideal. For slower connections or less frequent transfers, an HDD should work just fine.
  • TempDir: Normally low usage, but if you hit cache limits or see memory warnings, placing this on faster storage can help.

🔴 Slow Storage (HDD) – Generally Fine

  • MainDir: Can reside on a slower drive, especially if you’re using absolute paths for all other directories. Just be mindful of where your automation tools (like Sonarr or Radarr) expect to find the final files.
  • NzbDir, QueueDir, ScriptDir: These experience minimal disk activity and are perfectly suitable for HDDs.
  • Automation Users: If you’re using post-processing tools like Sonarr, Radarr, or a Post-Process Extension like VideoSort, keep in mind how files are handled:
    • DestDir is where NZBGet temporarily places completed downloads.
    • Post-processing scripts or automation apps then move those files to a final destination folder, often on a large HDD for long-term storage.
    • For faster handoff and reduced delays during post-processing, it’s ideal to keep DestDir on an SSD — even if the final destination is slower storage.

Performance Tips for NZBGet Storage

  • Keep InterDir Separate: Ideally, place InterDir on a different physical drive from both DestDir and any folder used by automation tools like Sonarr or Radarr. This reduces disk contention and improves performance during unpacking.
  • Use Absolute Paths: This allows MainDir to live anywhere and gives you more flexibility when mapping drives.
  • High-Speed Internet Users: If you’re saturating your connection, use SSDs for both InterDir and DestDir to avoid slowdowns during unpacking and moving.
  • Update NZBGet Often: New versions include performance optimizations that can improve how NZBGet uses disk I/O and memory.

Where to Configure Storage Paths

To review or update your directory settings:

  1. Open NZBGet Web UI
  2. Go to Settings → Paths
  3. Update the directory paths as needed

Each path field includes a helpful tooltip, and most settings take effect after a quick reload of NZBGet.


What to Remember

Properly configuring NZBGet’s storage paths helps you avoid slow speeds, failed unpacking, and unnecessary disk wear. By assigning the right folders to the right types of storage, you give NZBGet the performance headroom it needs to run efficiently, especially on high-speed connections or low-resource systems.


Introduction

Installation manuals

Building manuals

Configuration

Usage

Development

Extensions

News server setup

Other helpful guides

/js/scripts.min.js