Adobe Premiere Pro on NAS: Productions Setup, Cache Rules, and Fixing Media Pending (2026)

Most Premiere Pro NAS problems trace back to two configuration mistakes: putting the Media Cache on the NAS when it must be local, and not understanding how Premiere's Productions system handles shared projects. Get those two things right and most "Media Pending" errors, project corruption issues, and shared-project conflicts disappear. This guide covers Productions setup on NAS, the exact cache configuration table for each file type Premiere generates, SMB settings for multi-editor workflows, and the definitive Media Pending troubleshooting checklist. It applies to Synology, QNAP, and any NAS with SMB3 support. Australian model pricing and recommendations are in the AU section below.

For a full overview covering hardware, setup, and workflow planning, see our complete NAS video editing guide.

How Premiere Pro Handles Shared Storage. The Productions Model

Premiere Pro's collaborative model changed fundamentally with Productions (introduced in version 14.2, 2020). Most forum advice predates this and describes workflows that are no longer optimal. If you are following a guide from before 2021, you are working with an outdated architecture.

The old approach was shared project files: one .prproj file on the NAS, with file locking preventing simultaneous access. Two editors could not work at the same time. Productions changes this. A Production creates a root folder on the NAS containing a Production.json file and individual .prproj files. One per editor, per sequence, or per deliverable. Each editor opens their own project file. Premiere uses lock files (.prlock) to prevent two people from opening the same .prproj simultaneously, but the Production structure means editors generally have their own project files and share media, not project files.

The practical limit remains: two editors cannot work in the same .prproj file at the same time. Unlike DaVinci Resolve's bin locking model, Premiere locks at the project file level. The Productions model works around this by giving each editor their own project file within the shared Production structure. Compare to Final Cut Pro. Which has no collaborative model at all. And Resolve, which uses a database server for true simultaneous multi-user access.

The Cache Truth Table. What Goes Where in Premiere

This is the section that fixes most Premiere NAS problems. Every file type Premiere generates has a correct home. And the consequences of putting any of them in the wrong place range from slow performance to project corruption.

File / Setting	Correct Location	Why
Source media (camera files)	NAS	Shared access, large sequential reads
Project files (.prproj)	NAS. Inside Productions folder	Shared editing; lock files manage access
Media Cache (waveforms, peak files)	Local NVMe/SSD. Never NAS	High IOPS, user-specific; shared cache corrupts
Preview / Render files	Local NVMe/SSD	Fast read/write needed; user-specific
Auto Save / Backups	NAS. Separate folder	Accessible, doesn't need speed
Proxy files	NAS. Shared volume	Generated once, used by all editors
Exported deliverables	NAS	Client access and archiving
Motion Graphics Templates	Local. Each workstation	Plugin and version consistency required

Setting Up Productions on NAS. Step by Step

Once your hardware is in place, set up the Productions structure before any editor opens a project:

1. Create a root folder on the NAS share. Use a consistent path such as \\NAS\Video\Productions\ on Windows or /Volumes/Video/Productions/ on Mac. This is where all Productions will live.
2. Create a new Production in Premiere. File → New → Production → name it and point it to the NAS root folder. Premiere creates a Production.json file at that location.
3. Create individual project files within the Production for each editor or deliverable sequence. Each .prproj file gets its own lock file. Editors work in separate project files within the shared Production.
4. On every workstation: change Media Cache location to local NVMe. Premiere Preferences → Media → set Media Cache Files and Media Cache Database to a local NVMe path. Do this on every machine before anyone opens a project.
5. On every workstation: change Preview Files location to local NVMe. Same section of Preferences. Preview Files should never go on the NAS.
6. Enable NTP time sync on all workstations and the NAS. Premiere uses timestamps for cache validation. Timestamp drift between machines causes cache failures that look identical to corruption. Most NAS units can be configured as an NTP server for the studio network.
7. Map the NAS share to the same drive letter or volume name on every machine. On Windows, always map to P:\ (or whatever you choose). Use the same letter on every workstation. On Mac, ensure the volume name is consistent. Inconsistent mount points cause Media Offline errors that have nothing to do with the actual files.

Productions Folder Structure Template

A clean, consistent folder structure prevents most project management problems before they start. Here is a ready-to-use template. Adapt the names to your studio's convention, but keep the hierarchy consistent across all projects:

\\NAS\Video\Productions\
└── [ClientName_ProjectName]\
    ├── Production.json          <-- auto-created by Premiere
    ├── _MEDIA\                  <-- camera originals
    │   ├── RAW\
    │   └── PROXIES\
    ├── _PROJECTS\               <-- one .prproj per editor or deliverable
    │   ├── Editor1_Assembly.prproj
    │   └── Editor2_Graphics.prproj
    ├── _EXPORTS\                <-- deliverables and client review files
    ├── _ASSETS\                 <-- music, logos, motion graphics sources
    └── _ARCHIVE\                <-- Auto Save backups (point Premiere here)

Keep Motion Graphics Templates local on each workstation. Version mismatches break projects when they reference a template that is not installed on the opening machine.

SMB Configuration for Premiere Pro

"Use SMB3" is the advice you see everywhere. It is correct but incomplete. These are the specific settings that make a difference to Premiere performance and stability:

• SMB version: SMB3 on the NAS share. Disable SMB1 entirely. It is slow and causes instability with modern Premiere.
• Opportunistic Locking: Enable on the NAS share. Improves caching efficiency for project file access.
• Jumbo Frames (MTU 9000): Enable on the NAS and all workstation NICs. They must match. If the NAS is at 9000 and a workstation is at 1500, throughput degrades. Configure at the NIC level on each machine and confirm via the NAS network settings.
• Spotlight / Windows Search indexing exclusion: Add the NAS share to the exclusion list on every workstation. Indexer locks files during import, causing Premiere's Media Pending state. On Mac: System Settings → Siri and Spotlight → Spotlight Privacy → add the NAS volume. On Windows: exclude the mapped drive letter from Windows Search.
• Antivirus exclusions: Add NAS share paths to your antivirus exclusion list on all workstations. AV scanning a .prproj file mid-save causes corruption. This is especially relevant in studios with centralised AV management.

Per-brand settings:

• Synology (DSM): Control Panel → File Services → SMB → Advanced → enable Large MTU, confirm Opportunistic Locking is on.
• QNAP (QTS/QuTS): Control Panel → Network and File Services → Win/Mac/NFS → Advanced Options → enable Jumbo Frame. For the full brand comparison, see the dedicated guide.

Fixing Media Pending. The Definitive Checklist

Media Pending is Premiere's holding state while it processes or conforms incoming media. It is normal to see it briefly on import. It is not normal to see it for minutes every time you open a project, or to see it on media that has not changed. Work through this checklist in order:

Step 1. Is Media Cache on the NAS?
Go to Preferences → Media and check the Media Cache Files and Media Cache Database locations. If either points to a NAS share or a network drive, move them to local NVMe immediately. This resolves Media Pending in the majority of cases.

Step 2. Are codecs mixed in your sequence?
Mixed H.264, HEVC, and MXF in the same sequence forces Premiere to conform media on import. Conforming generates peak files. Which goes back to Media Cache. If you are working with a mix of camera formats, creating proxies (ProRes or DNxHR) eliminates the conform step and Media Pending disappears.

Step 3. Is Spotlight or Windows Search indexing the NAS share?
The indexer locks files while scanning. Exclude the NAS share from indexing on every workstation as described in the SMB section above.

Step 4. Is antivirus scanning the project files?
Add the NAS share paths to AV exclusions on every workstation. Confirm with your IT administrator if AV is centrally managed.

Step 5. Are system clocks out of sync?
Enable NTP on all workstations and confirm the NAS is also syncing to NTP. Timestamp drift causes cache validation failures that trigger Media Pending on otherwise clean imports.

Step 6. Is SMB1 enabled on the NAS?
Disable SMB1. It is slow and causes intermittent instability with current Premiere versions. Find this in NAS network/file services settings.

Step 7. Still happening?
Clear the Media Cache database entirely: Preferences → Media → Clean. Then delete the cache files from the local NVMe folder on all workstations. Premiere will regenerate on next open. This takes time but leaves you with a clean state.

Network Requirements for Multi-Editor Premiere Workflows

Bandwidth requirements scale with editor count, format, and whether you are working with proxies or native media:

• 1GbE: Single editor, H.264/HEVC with proxies only. Not adequate for native 4K ProRes or any collaborative setup.
• 2.5GbE: Single editor native 4K ProRes 422, or 2 editors with proxies.
• 10GbE: 3-5 editors native 4K, multicam, or any serious collaborative workflow. This is the baseline for professional team setups.
• 25GbE+: 6+ editors, or any workflow using 6K/8K native or ProRes 4444.

The aggregate bandwidth figure is the one to watch. Four editors each needing 500 MB/s of sustained throughput creates a 2 GB/s aggregate demand. A single 10GbE link delivers approximately 1.1-1.2 GB/s under real conditions. Either size your format to fit the link, use proxies to reduce per-editor bandwidth, or move to 25GbE. The network upgrade ROI calculator can help you model whether a switch upgrade is worth the cost for your setup. For a deeper look at connection options, see the Thunderbolt vs 10GbE vs 2.5GbE guide.

Recommended NAS for Premiere Pro Teams (2026)

NAS selection for Premiere is less constrained than for DaVinci Resolve. Premiere does not require Docker or a database server, so the hardware floor is lower. For a full buying guide, see best NAS for video editing Australia. For Premiere specifically:

• 2 editors: Synology DS925+ or QNAP TS-464 with a 10GbE add-in card. 4-bay is adequate for most 2-editor setups if you manage archive separately.
• 4-6 editors: QNAP TVS-h874 or Synology DS1825+. 8-bay gives you room to grow the media pool without rebuilding the array. Both support 10GbE and perform well under concurrent Premiere load.
• 6+ editors or high-resolution formats: OWC Jellyfish or a dedicated shared storage server. At this scale, the NAS-as-production-storage model reaches its limits and purpose-built hardware starts to make economic sense.

DaVinci Resolve NAS setup guide. For Mac-only teams using Final Cut Pro, see the Final Cut Pro NAS setup guide.

---

🇦🇺 Australian Buyers: NAS Models and Pricing for Premiere Pro

For Premiere Pro workflows, the Synology DS925+ and QNAP TS-464 are the core recommendations for 2-editor setups. Both are available from Scorptec, Mwave, and PLE with current AU pricing around $995 and $999 respectively. For 4-6 editor teams, the QNAP TVS-h874 is available through Scorptec and specialist resellers. The Synology DS1825+ ($1,799 from Scorptec) is the Synology equivalent. For NBN-connected studios: remote collaboration via Teams or Frame.io is typically more practical than remote NAS access. Australian NBN upload speeds (17-20 Mbps on NBN100) make real-time remote NAS editing impractical for anything above 1080p proxies.

Related reading: our NAS buyer's guide.

Related reading: our NAS explainer.

Can Premiere Pro run directly from a NAS?

Source media and project files can live on the NAS. And should, for collaborative setups. Media Cache, Preview files, and Auto Save should be on local NVMe on each workstation. Premiere itself (the application) installs locally and runs locally on every machine. What the NAS hosts is your media library and the Productions folder structure, not the application.

Why does Premiere say Media Pending when opening from a NAS?

Almost always caused by Media Cache stored on the NAS rather than local NVMe. Go to Preferences → Media and confirm the Media Cache Files and Media Cache Database locations point to a local NVMe path, not a network drive. If Media Cache is already local, check whether Spotlight or Windows Search is indexing the NAS share. The indexer locks files during scanning, causing Media Pending. Disabling indexing on the NAS share resolves this.

Can two editors work on the same Premiere project at the same time?

Not on the same .prproj file. Premiere locks at the project file level. With Productions, each editor works in their own project file within the shared Production. They can reference the same media, share the same Productions folder, and their work combines into the master Production. But they each have their own project file. True simultaneous bin-level editing on the same project requires DaVinci Resolve's database model, not Premiere's file-locking model.

Is Premiere Pro compatible with Synology NAS?

Yes. Synology NAS units work well with Premiere. Use SMB3, disable SMB1, enable Jumbo Frames (MTU 9000), and keep Media Cache off the NAS. The DS1825+ and DS925+ are commonly used in Premiere workflows. Synology does not support Thunderbolt, so 10GbE is the high-speed connection option for Mac editors. Which is the right infrastructure for team setups regardless.

If you're still deciding on a brand, our Synology vs QNAP comparison guide breaks down which platform suits different use cases in Australia.

Should I use Team Projects or Productions for NAS collaboration in Premiere?

Productions for on-premise NAS workflows. Productions is designed for a shared local server. It stores everything in a folder you control, works offline, and has no subscription requirement beyond your Premiere licence. Team Projects uses Adobe's cloud infrastructure and is better suited for geographically distributed teams without a shared NAS. On Australian NBN upload speeds (17-20 Mbps residential), Team Projects sync for large media projects is slow and impractical. Productions on local NAS is the right tool for most AU studios.