Quick Summary (TL;DR): Choose Synology Photos when you already own a compatible Synology NASAliExpress price and want straightforward family phone backups, personal and shared spaces, and little day-to-day administration. Choose Immich when the priority is a Google Photos-like experience, first-class Android/iPhone upload apps, semantic image search and a portable Docker deployment; budget for its database, machine-learning workload and more involved maintenance. Choose PhotoPrism when you already have a carefully organised folder-based photo archive and want powerful indexing, metadata filters, maps and a browser-first catalogue without surrendering control of the original filenames. None replaces a proper backup. The most important decision is where originals live, how each phone uploads, and whether you can restore the library plus its metadata.
This is a documentation-based comparison, not a claim that we benchmarked three installations. Features and minimum requirements were checked against the vendors’ documentation in October 2026; model-specific Synology functions, app versions and membership features can change. The hardware buying shortlist belongs in our separate NAS for Immich and family photo backups guide.
Synology Photos vs Immich vs PhotoPrism: At a Glance
| Decision point | Synology Photos | Immich | PhotoPrism |
|---|---|---|---|
| Where it runs | Supported Synology DSM NASAliExpress price | Docker on compatible Linux/NASAliExpress price/home server | Docker on Linux, NASAliExpress price and other supported hosts |
| Best fit | Family NASAliExpress price already using DSM | Phone-first private cloud | Existing, curated folder archive |
| Phone uploads | Dedicated iOS/Android Photos app | Dedicated iOS/Android Immich app | Typically third-party WebDAV-capable app such as PhotoSync |
| Browsing | Timeline, folders, albums | Timeline, albums, optional folder view | Web/PWA catalogue, folders, filters, maps |
| People/AI | People and Subjects on supported models | Face recognition and contextual search with ML service | Face recognition, labels and detailed filters |
| Original file control | DSM-managed personal/shared photo locations | Managed uploads or separately indexed external libraries | Can index originals in place without renaming |
| Multiple users | DSM accounts, personal/shared spaces | Separate users, shared albums, partner sharing | Capabilities and admin UI depend on edition |
| Administration | Lowest if you already run DSM | Docker, Postgres, ML, updates and backup | Docker, database/indexing, updates and backup |
| Portability | Tied to Synology ecosystem | Cross-platform with database-aware migration | Cross-platform with database-aware migration |
Our default verdict: If a supported Synology NAS is already your primary family storage, start with Synology Photos before adding another application. For a new photo-first server, Immich is usually the better fit for a household that expects automatic phone uploads and intelligent search. PhotoPrism is especially compelling when the archive already exists in an organised directory tree and you want to catalogue it in place.
The Three Different Philosophies
Synology Photos: an integrated NAS application
Synology Photos is installed through DSM Package Center and uses Synology account permissions and storage conventions. Its Personal Space and Shared Space make sense for a household where adults want private libraries but also contribute to a common family collection. Shared Space files are held in the /photo shared folder; personal libraries depend on enabled user-home services. A DSM administrator must understand both Photos permissions and filesystem permissions: they are not identical.
You gain a coherent DSM workflow and a dedicated mobile application, but the application is not a portable package for arbitrary non-Synology servers. Before buying a Synology solely for its photo features, check the exact model’s supported functions: Synology explicitly limits face and object recognition to certain models. The official Photos specification and setup guide explain those distinctions.
Immich: a phone-first self-hosted photo cloud
Immich centres on a timeline, mobile uploads, shared albums and machine-learning-assisted discovery. Its iOS and Android apps can back up selected albums, while content hashes help avoid re-uploading identical items in the managed upload library. The server maintains asset records and relationships in PostgreSQL. That makes it powerful, but it also means copying only the JPEG and video files is not a complete disaster-recovery plan.
The software supports external libraries for existing files, although those behave differently from Immich-managed uploads. An external library is assigned to one owner; scanning imports asset references rather than necessarily copying the files. Metadata added inside Immich to an external asset may be stored only in Immich, not in the original image. Moving that asset outside Immich can cause its catalogue metadata to be lost on a subsequent scan. These are crucial differences when deciding whether to point Immich at a carefully curated archive.
PhotoPrism: a catalogue built around your originals
PhotoPrism is particularly strong when the files already live in a folder hierarchy you trust. Its index operation catalogues originals in place, preserving existing filenames and directory structure; its separate import workflow can move files from a staging area into an organised originals tree. These are intentionally different operations. PhotoPrism combines metadata search, face recognition, maps, labels and RAW-related browsing with a browser/PWA interface.
For mobile backup, PhotoPrism documents third-party clients such as PhotoSync communicating via WebDAV rather than an equivalent first-party automatic camera-upload app. The free Community edition is useful, while paid editions offer additional features, including account-management conveniences. Check the current edition comparison before budgeting; do not assume every user-management or sharing feature is included in Community.
Phone Backup: Which One Will Your Household Actually Use?
| Everyday task | Synology Photos | Immich | PhotoPrism |
|---|---|---|---|
| iPhone camera-roll backup | Native app; iOS background restrictions still apply | Native app; periodic background and foreground uploads | Configure PhotoSync or another WebDAV-capable client |
| Android camera folders | Native app | Choose included/excluded albums | Configure folder sync in the client |
| Uploads over mobile data | App settings/network access need checking | App settings/network access need checking | Depends on chosen sync client |
| Family members | Individual DSM accounts and shared spaces | Individual users, shared albums and partner sharing | Account model depends on edition; sync clients configured per device |
| If app is force-closed | Cannot promise immediate background uploads | Cannot promise immediate background uploads | Depends on phone OS and third-party app |
A photo system fails quietly when one family member’s phone stops uploading. On iOS, background execution is controlled by the operating system; no vendor can guarantee instant uploads after every shot. Immich documents uploads when the app opens or resumes, plus periodic background activity. Synology recommends notifications and charging to improve iOS backup reliability. Whatever the product, verify the newest ten photos and one video from each phone in the server library before trusting it.
- Create a separate account for each adult. Do not share the administrator password with every phone.
- Choose the correct source albums and decide whether screenshots, messaging-app media and large videos belong in the archive.
- Check Wi-Fi-only versus mobile-data behaviour, charging and battery optimisation on each device.
- Confirm that a newly captured HEIC photo, a short video and a Live Photo (if used) arrive and are viewable.
- Repeat the test after a phone OS upgrade, application upgrade or changed server address.
Be careful with any “free up space” or deletion option. Confirm whether it removes only the phone’s local copy, the server copy, or both. A synchronisation tool and a backup tool are not always the same thing.
Search, Faces, Maps and Duplicate Handling
| Capability | Synology Photos | Immich | PhotoPrism |
|---|---|---|---|
| Face grouping | Yes, on supported NAS models | Yes, machine-learning service | Yes, indexing/recognition |
| Object/semantic discovery | Subjects on supported models | Contextual CLIP-based search; OCR and filters documented | Labels and extensive property filters |
| Location/map browsing | Places from metadata | Map and location search | Maps and geocoding |
| Folder-based navigation | Yes | Optional folder view | Yes; indexing preserves existing tree |
| Duplicate protection | Do not assume global deduplication | Upload hashes; external-library duplicates have separate caveats | Import can skip duplicates; indexing and imports differ |
| CPU/RAM demand | Model-dependent, integrated into DSM | ML and database increase resources | Indexing, face recognition and RAW processing increase resources |
The phrase “AI search” hides several different techniques. Face recognition groups images of the same person; object recognition classifies common subjects; contextual search can retrieve a photograph from a description even when no matching keyword is stored in its metadata. Immich documents contextual search using CLIP-based embeddings. PhotoPrism emphasises labels, visual analysis and combined search filters. Synology’s Subjects feature is not universal across NAS models.
For a library with 100,000 images, the useful question is not which marketing page has the longest feature list. Test representative searches: a person whose name you assign, a beach trip with GPS metadata, a RAW+JPEG pair, a scanned document and an older video. Then check whether the result can be exported and understood outside the application.
Existing Folders and Migration: The Biggest Hidden Difference
Suppose your existing archive is organised as Family/2020/Holiday, Photography/RAW and Scans. If that structure is the source of truth, do not import everything blindly into a new managed-upload folder. First determine whether you want the application to manage storage or merely index existing storage.
| Situation | Lower-risk approach | Reason |
|---|---|---|
| Existing Synology /photo archive | Assess Synology Photos Shared Space | Avoid unnecessary duplicate storage and permissions churn |
| Curated NAS folders; must retain exact paths | PhotoPrism index in place or Immich external library | Original filenames and folder tree can remain authoritative |
| Phone uploads are primary source | Immich managed upload library or Synology mobile backup | App controls ingestion and mobile experience |
| Move from one photo app to another | Export originals and metadata; pilot with a copy | Album membership, face labels and favourites may not migrate |
| Same folders shared by two apps | Use read-only mounts for secondary indexer initially | Reduces accidental modifications and conflicting moves |
Immich external libraries can expose existing files without re-uploading them. However, its own documentation warns that external-library metadata such as album membership may be lost if files are moved outside the application and rescanned. The documentation also notes that duplicate detection for external libraries is not global. PhotoPrism’s index-in-place approach avoids renaming originals; its separate import workflow intentionally reorganises files and skips duplicates. These are design choices, not universal guarantees about how every file will be handled.
A safe trial migration
- Inventory the existing collection: number of files, total size, video formats, RAW formats, Live Photos and any sidecar XMP files.
- Create a verified backup of the originals before enabling an import or synchronisation job.
- Choose a representative copy of 500–2,000 mixed files; include odd dates, duplicates, non-ASCII filenames and videos. This is a suggested test set, not a performance benchmark.
- Install the candidate software using a dedicated non-admin account where practical. Mount the test originals read-only if the application supports that mode.
- Compare file counts, capture dates, orientation, GPS locations, albums, face assignments and shared permissions.
- Export or recover the pilot collection, then document exactly which metadata survives without the application database.
- Only then move the full archive, in batches with checksums or another independent integrity method.
Do not assume an album in Synology Photos maps to an Immich album or PhotoPrism album. Albums can be application database objects rather than physical directories. Likewise, a named face is not necessarily written back to an image in a format that another application can read. If that information matters, keep an export or backup of the originating application’s database and sidecar metadata.
Hardware Requirements: NAS CPU, RAM and SSD Placement
| Resource | Synology Photos | Immich | PhotoPrism |
|---|---|---|---|
| Host | Compatible Synology NAS running supported DSM | 64-bit Linux/*nix preferred; amd64 or arm64 | 64-bit host; NAS and Docker options |
| Published RAM guidance | Check exact Synology model and feature support | 6 GB minimum, 8 GB recommended | 3 GB minimum; more for large RAW libraries |
| Published CPU guidance | Model-dependent | 2 cores minimum, 4 recommended | At least 2 cores |
| Database placement | Managed by DSM | Local SSD recommended; not network share for Postgres data | SSD recommended for database/cache |
| Initial indexing | Background DSM work | ML jobs, thumbnails and video processing | Indexing/RAW conversion/face analysis |
| GPU use | Feature support depends on NAS | Optional experimental ML acceleration; verify backend | Not required to use core catalogue |
The published Immich requirements specify at least 6 GB RAM and two CPU cores, recommending 8 GB and four cores. The project advises keeping PostgreSQL data on a local SSD, not a network share. It also notes thumbnails and transcoded media can increase storage needs by roughly 10–20% on average; treat that as project guidance, not a guaranteed figure for your archive. A small NAS that barely runs Docker may not be a good all-in-one Immich server.
PhotoPrism recommends a 64-bit host with at least two cores and 3 GB physical RAM; its documentation calls for at least 4 GB swap and notes that indexing large RAW and panoramic collections may require more memory. On Synology, its installation guide suggests 4 GB RAM plus swap as a practical baseline. Its database, thumbnails and cache benefit from SSD storage. A machine that meets minimum requirements can still be slow when ingesting a large library.
Synology Photos avoids a separate Docker database deployment, but do not confuse package availability with full feature availability. Facial and subject recognition depend on supported hardware and DSM. If buying specifically for face recognition, verify the exact Synology model against the current support list, not just the model family name.
A Practical Architecture for Each Choice
Option A: one Synology NAS, minimum administration
Phones (individual DSM accounts)
|
Synology Photos mobile backup
|
Synology NAS: Personal Space + Shared Space
|
NAS backup job -> separate/off-site destinationThis suits a family that values an appliance-like system. Keep DSM and packages updated, enable multifactor authentication where supported, and use a separate backup target. Shared Space permissions should be tested with a non-admin family account, not only the NAS administrator.
Option B: Immich on mini PC, originals on NAS
iPhone / Android -> Immich server (mini PC)
|
local SSD: Postgres + app data
|
NAS: media storage
|
separate backup of media + DB + configThis architecture can separate compute from bulk storage, but do not place the PostgreSQL database on an SMB/NFS share. Follow the current Immich storage documentation for supported media mounts and backup/restore requirements. Network storage outages must be considered: a mounted NAS share that disappears during a write is not a harmless event. See our Immich installation, storage and backup guide for deployment detail.
Option C: PhotoPrism indexing a read-only archive
Phones -> PhotoSync / WebDAV upload folder
|
optional import workflow
|
NAS originals (curated folder tree)
|
PhotoPrism index + cache/database on SSD
|
backup originals + database + sidecarsA read-only mount is useful when PhotoPrism is a secondary viewer of an existing archive. If you want PhotoPrism to ingest or reorganise photos, design a separate writable import path and verify permissions. Do not make an archive writable merely because the app requests it; understand the workflow first.
Family Accounts, Sharing and Remote Access
For households, sharing permissions matter as much as face search. Synology Photos has Personal and Shared Spaces, configurable album permissions and photo-request links. Immich offers shared albums, partner sharing and public links with configurable restrictions. PhotoPrism’s user-management interface and other advanced capabilities differ by edition; verify the current Community/Essentials/Plus matrix before promising a family the same experience as a paid deployment.
| Sharing requirement | Check before committing |
|---|---|
| Two adults, separate private libraries | Separate accounts, private timelines and recovery permissions |
| Shared children/family album | Who can add, delete, download and re-share |
| Grandparents viewing photos | Expiring links, password protection and low-friction access |
| Contributor uploading photos | Photo request/upload permissions; risk of unwanted uploads |
| Remote access from abroad | HTTPS/VPN or supported relay, DNS and certificate maintenance |
| Account compromise | MFA where available, strong passwords and recovery plan |
Avoid forwarding an unauthenticated photo-app port directly from the router to the internet. Prefer a maintained HTTPS reverse proxy with appropriate authentication or a VPN-based remote access path. Do not assume a VPN protects public share links if the links are separately exposed. For a broader comparison of remote connectivity, read Remote NAS Access: Tailscale, WireGuard or the Manufacturer’s App?.
Backups: Originals Are Only Half the Recovery Job
Photo software adds useful information that may exist only in a database: album membership, recognised people, favourites, sharing settings, file paths and application state. A backup that contains only original photographs may recover the pictures but not the experience you spent years organising. Conversely, a perfect database dump is worthless if the referenced media files have vanished.
| What to protect | Synology Photos | Immich | PhotoPrism |
|---|---|---|---|
| Original photos/videos | Personal and shared photo folders | Upload location and any external originals | Originals directory and any import staging you rely on |
| Database/app state | DSM/application-aware backup method | PostgreSQL backup plus relevant app state | Database dump/file and storage/sidecars |
| Configuration | DSM settings, accounts, package state | Compose file, environment settings and secrets | Compose file, environment settings and secrets |
| Thumbnails/transcodes | Usually rebuildable but may take time | Back up per official recovery procedure | Rebuildable caches may take time |
| Restore verification | Restore into a safe test target | Test matched DB + media restore | Test database + originals + storage restore |
Immich explicitly warns that it does not reconstruct all its records by merely rescanning its managed library: database backups are essential. Its current documentation describes automatic database backups, but these are stored under the upload location and still need to be copied to a separate backup destination. For PhotoPrism, preserve the database, originals and relevant storage/sidecar data. For Synology, use a documented DSM backup workflow that includes the right application data and photo shares; verify the backup package’s current support for the specific Photos version.
A robust home setup uses a versioned local backup plus an off-site or offline copy. RAID redundancy, snapshots and sync alone do not protect against every form of accidental deletion, ransomware, hardware failure or theft. Our 3-2-1 NAS backup plan explains the storage layers. A quarterly restore drill is a sensible operating target; the interval is a recommendation, not a vendor requirement.
Total Ownership Cost: Compare the Whole System
It is tempting to compare “free” software with a paid NAS, but a private photo library has hardware, storage, backup, power and administration costs. Synology Photos is included with compatible DSM systems, while you pay for the NAS and drives. Immich can run without a software subscription on your hardware, but still requires an adequately provisioned host and maintenance. PhotoPrism has a free Community edition and optional paid memberships. Do not assume a paid PhotoPrism membership or an Immich donation buys any particular feature without checking the official plan details.
| Cost element | Questions to answer |
|---|---|
| Host hardware | Already-owned NAS or additional mini PC? CPU/RAM enough for indexing? |
| Primary storage | Usable capacity after RAID; free space for growth and previews? |
| Database/SSD | Do you need a local SSD for Postgres or indexing cache? |
| Backups | Second drive, second NAS, off-site storage and restore testing? |
| Network and power | Switch ports, UPS, electricity, safe shutdown? |
| Software plans | Which PhotoPrism edition features are essential? Any changing subscription terms? |
| Maintenance | Who handles security updates, expiring certificates, app/database migrations? |
As a transparent illustration rather than a price forecast: a 25 W always-on mini PC uses 0.025 kW × 24 × 365 = 219 kWh per year. Multiply by your actual electricity tariff and add the NAS, switches and UPS losses. The 25 W figure is an example assumption, not a measured consumption figure for a particular mini PC. Hardware power draw varies with CPU, disks, sleep policy and workload. If your NAS already runs 24/7, the incremental cost of Synology Photos may be small compared with adding a dedicated computer.
Mistakes That Cause Photo-Library Regret
- Using sync as the only backup. Deleting a photo can propagate to every synced device. Keep independently recoverable versions.
- Importing a whole archive without a pilot. Different applications treat folders, Live Photos, RAW pairs, duplicates and metadata differently.
- Moving Immich external-library files outside the app. Rescanning can treat moved files as new assets and discard app-only metadata.
- Assuming every Synology NAS supports People and Subjects. Confirm the exact model and DSM requirements.
- Putting a database on unreliable network storage. Immich specifically advises local SSD for PostgreSQL data.
- Giving every phone the administrator account. Use least-privilege family accounts and separate credentials.
- Exposing HTTP/WebDAV to the internet. Use encrypted connections and appropriate access controls.
- Forgetting that albums may not be portable. Export originals, metadata and app database; test migration before decommissioning the old system.
Which Private Photo Library Should You Choose?
| Your situation | Recommendation | Why |
|---|---|---|
| You already have a compatible Synology and want low maintenance | Synology Photos | Native DSM accounts, sharing and phone app |
| Your family wants Google Photos-style backup and search on your own server | Immich | Mobile-first uploads, contextual search and collaboration |
| You have years of carefully organised folders and RAW photos | PhotoPrism | Index-in-place and rich metadata-based catalogue |
| Your Synology is underpowered for advanced AI features | Test Immich/PhotoPrism on a separate host | Move compute without immediately replacing NAS storage |
| You want the least risk of moving files | Trial an index-only workflow | Keep originals authoritative and avoid bulk rewrites |
| You need extensive family-user administration in PhotoPrism | Verify edition first | User-management features vary by plan |
Bottom line: Synology Photos is the practical default for an existing Synology household; Immich is the strongest starting point for a new phone-first private cloud; PhotoPrism is a particularly good choice for people who already curate their photo files and want a powerful catalogue over them. Choose the system you can operate and restore, not the one with the flashiest demo. There is no benefit in clever face search if your last verified backup is a year old.
Frequently Asked Questions
Can I run Immich or PhotoPrism on a Synology NAS?
Often yes, on a model with compatible container support and sufficient CPU/RAM, but check the exact NAS architecture and DSM package support. PhotoPrism publishes a Synology Container Manager guide. Immich recommends a suitable Docker host and has its own resource and database requirements. A low-memory NAS may be better used for storage with the application running on a mini PC.
Will Immich automatically import my existing Synology Photos albums?
Do not assume so. Immich can index existing files through external libraries, but Synology album membership, recognised people and favourites may be application-specific metadata rather than universally portable file properties. Pilot a migration and plan for manual reconstruction of some organisational data.
Is PhotoPrism better than Immich for RAW photographers?
PhotoPrism is attractive for folder-based and RAW-heavy archives because it is designed to index existing originals and offers extensive metadata filters. Immich also supports a range of media formats and external libraries. Check the exact camera RAW variants, paired JPEGs and sidecar behaviour using a representative test set rather than assuming universal compatibility.
Can I keep the same photo folders in two applications?
Yes, it can be sensible to let a secondary application index an existing collection. Start with a read-only mount for the secondary indexer, avoid competing importers or automatic file moves, and back up application databases separately. Changes made inside one application do not automatically transfer album and face metadata to the other.
Is a private photo library a replacement for Google Photos or iCloud?
It can replace many browsing, backup and sharing workflows, but you become responsible for server uptime, secure remote access, updates and recoverable off-site copies. Also check family sharing, background uploads, phone storage optimisation and accessibility before cancelling an existing cloud plan. Our five-year private-cloud cost comparison explains broader ownership trade-offs.
Related NAS and Photo Guides
- Best NAS for Immich and Family Photo Backups
- Install Immich on a NAS: Storage, Hardware Acceleration and Backups
- A 3-2-1 NAS Backup Plan: USB Drive, Second NAS and Cloud
- Remote NAS Access: Tailscale, WireGuard or the Manufacturer’s App?
Official Documentation and Further Reading
- Synology Photos – official technical specification
- Synology Photos – quick-start guide
- Synology Photos – FAQ and permissions
- Immich – hardware and storage requirements
- Immich – mobile backup
- Immich – external libraries
- Immich – searching and machine learning
- Immich – backup and restore
- PhotoPrism – features and overview
- PhotoPrism – index versus import
- PhotoPrism – mobile-device synchronisation
- PhotoPrism – Synology installation requirements
- PhotoPrism – editions and memberships