The one architecture decision that matters
Before any install, settle where the DAM runs — this single choice makes or breaks a NAS-DAM project. Consumer NAS CPUs are fine at serving files but slow at the CPU-heavy work of thumbnailing 80 MB RAW files and extracting metadata. So the proven pattern separates the two jobs: the NAS keeps serving files over SMB/NFS exactly as today, and a separate DAM server — a modest always-on PC or VM — indexes those shares over the network. Files never move; folder structures and backups are untouched. The DAM stores only a catalog of metadata and previews.
Native NAS apps aren't DAMs. Synology Photos and QNAP QuMagie are photo viewers — good for family albums and phone backups, but with no controlled vocabulary, no IPTC/XMP editing, no versioning and album-level rather than team permissions. Our Synology photo management guide draws the exact line between viewer and DAM.
Two ways to run it
Server beside the NAS (robust)
- DAM server on a spare PC/VM (Daminion on Windows; ResourceSpace on Linux)
- Indexes NAS shares over SMB/NFS; NAS just serves files
- Handles RAW/CAD-heavy and team libraries without stalling
- Best for teams and archives past ~50k assets
Docker on the NAS (light)
- ResourceSpace or Razuna in Synology Container Manager / QNAP Container Station / TrueNAS
- No extra hardware; everything on one box
- Thumbnail generation is slow on NAS CPUs for RAW archives
- Fine for smaller or lightly-used libraries
Step by step: index-beside-the-NAS
- Expose the shares. On the NAS, make sure your media folders are shared over SMB (or NFS) with a service account the DAM server can read. Read-only is enough if you only want to catalog; read-write lets the DAM write back metadata.
- Stand up the DAM server. Install the DAM on the always-on machine — a modest Windows VM or mini-PC for Daminion, a Linux/LAMP host or Docker for ResourceSpace. A roughly $500–600 mini-PC is plenty if you don't have a spare.
- Mount and point. Mount the NAS shares on the DAM server and point the catalog at them. This is where files-in-place matters: you're registering paths, not copying data.
- Run the first index overnight. Budget about 45 minutes per 25,000 RAW files over gigabit, so a few hundred thousand images finish by morning. 10GbE and an SSD cache speed the first pass.
- Turn on folder watching. Once indexed, enable the watch-folder so new or changed files are picked up within minutes — no manual re-scan.
- Add roles and a keyword tree. Define team permissions and a controlled vocabulary so search stays consistent as the archive grows.
Synology, QNAP and TrueNAS specifics
Synology. Share over SMB, and if you want the light path, Container Manager runs ResourceSpace or Razuna; for anything RAW-heavy, index from a separate box instead. Keep Synology Photos for phone backups alongside the real DAM.
QNAP. Same shape: Container Station runs the Docker tools, QuMagie stays the family viewer, and a beside-the-NAS server does the heavy indexing. QNAP's higher-end Intel units cope better with in-container thumbnailing than ARM models — our QNAP photo management guide covers the four setups in full.
TrueNAS. Expose datasets over SMB/NFS and either run a DAM in a VM/jail on the box (if it has the cores and RAM) or, more commonly, from a separate host. TrueNAS's ZFS snapshots pair well with a files-in-place DAM — your versioning and the catalog stay independent.
Why not just upload to a cloud DAM? Because moving terabytes up an office connection takes weeks and then bills you monthly for storage you already own. The files-in-place NAS pattern avoids both. If you're weighing the two models, our on-premise vs cloud DAM guide runs the trade-offs, and what DAM storage really costs does the three-year math.
FAQ
Can I install a DAM directly on my Synology or QNAP?
Lightweight, open-source tools like ResourceSpace and Razuna run in Docker through Synology Container Manager or QNAP Container Station, which is fine for smaller libraries. But consumer NAS CPUs are slow at generating thumbnails for RAW-heavy archives, so the robust pattern is a small server or VM beside the NAS that indexes the shares while the NAS just serves files. Native NAS apps (Synology Photos, QuMagie) are photo viewers, not DAMs.
Do my files move when a DAM indexes my NAS?
No. Tools built for this — Daminion, Portfolio DAM, digiKam — catalog files in place over SMB/NFS. Your folder structure, backup jobs and other apps keep working unchanged; the DAM stores only a catalog of metadata and thumbnails, not copies of your originals. That files-in-place behavior is the whole point of running a DAM over a NAS rather than uploading to a cloud DAM.
What do I need to run a DAM over a NAS?
Three things: the NAS you already have, serving files over SMB or NFS; a machine for the DAM server (a modest always-on Windows PC or VM for Daminion, or a Linux box/Docker host for ResourceSpace), which can be a roughly $500-600 mini-PC if you don't have a spare; and a gigabit or faster LAN between them. The DAM server does the indexing and thumbnailing; the NAS does nothing but serve bytes.
How long does it take to index a NAS library?
Plan for roughly 45 minutes per 25,000 RAW files over a gigabit LAN, so a few hundred thousand images index overnight. The first pass is the slow part; after that, folder watching picks up new or changed files within minutes. Ten-gigabit networking and an SSD cache on the DAM server shorten the initial run.