Every few months, the self-hosted photo storage conversation surges on Reddit, Hacker News, and photography forums. The trigger is usually a Google Photos policy change, a new AI feature that people find uncomfortable, or a pricing announcement.
The conversation has a consistent structure: half the participants are enthusiastic about Immich or PhotoPrism, half are warning about the maintenance overhead. Both groups are right about their respective positions.
This is a guide for people who are genuinely considering self-hosted photo storage and want an honest assessment of what it costs and what it delivers.
What Self-Hosted Photo Storage Actually Is
When photographers and privacy-conscious users talk about self-hosted photo storage, they typically mean running software on hardware you control — a home NAS (network-attached storage device), a dedicated server, or a Raspberry Pi — that provides the same features as a cloud service.
You own the hardware. You run the software. Your photos never leave a system you control. No third party can scan your images, use them to train AI, or change their terms of service in ways that affect your photos.
This is a meaningfully different privacy profile from any commercial cloud service. But the privacy benefit comes with a set of costs that are easy to underestimate if you have not run home server infrastructure before.
Immich
Immich is currently the most popular self-hosted alternative to Google Photos. It was designed explicitly to replicate the Google Photos experience: automatic phone backup, timeline browsing, shared albums, face recognition, object search, and a companion mobile app for iOS and Android.
The software is free and open source. It runs via Docker, which means it can be deployed on Linux, on a NAS with Docker support (Synology, QNAP, TrueNAS), or on any server you manage.
What Immich does well
- Automatic backup: the mobile app uploads new photos and videos in the background, just like Google Photos
- Face recognition: groups photos by recognized faces using local AI processing; no data leaves your server
- Object and scene search: you can search “beach” or “birthday cake” and find matching photos
- Album sharing: you can share albums with other people in your household or with specific external users
- Video support: handles video files, including the timeline view
What Immich requires
- A server with enough storage and processing power (a modern NAS or a small PC/server with at least 4GB RAM; 8GB+ recommended if using AI features)
- A basic comfort level with Docker and the command line for setup
- A plan for network access if you want to use Immich away from home (a VPN or reverse proxy with HTTPS)
- A backup strategy for the Immich database and photos themselves
That last requirement is the one people underestimate most often: if Immich is your only copy of your photos, you have not gained safety — you have just moved the single point of failure from Google’s servers to your hardware.
Maintenance reality
Immich is actively developed, which is a strength and a complexity. New features ship regularly. Breaking changes occasionally accompany major updates. The upgrade process requires running Docker commands and sometimes involves migration steps. For people comfortable with Linux and containers, this is a minor overhead — maybe 30 minutes a few times a year. For people who found the initial setup challenging, each upgrade can be a point of stress.
There is also the hardware failure dimension. Home NAS drives fail. Servers crash. If your NAS goes down on a weekend when you are traveling, your photos are inaccessible until you get home and fix the problem.
PhotoPrism
PhotoPrism is an older, more established self-hosted photo management tool. It has a different design philosophy from Immich: it is optimized for a large existing library rather than ongoing phone backup, and it does not assume you are replicating Google Photos.
What PhotoPrism does well
- Large library handling: designed to handle hundreds of thousands of photos without performance degradation
- Privacy-first design: all AI processing happens locally; no data leaves your server
- Extensive format support: handles RAW files from cameras, not just smartphone JPEGs
- Flexible import: can index photos in place on a file system, without copying them to a separate folder
Where PhotoPrism differs from Immich
- The automatic phone backup experience is less polished than Immich; it is better thought of as a browser-based library manager than a Google Photos replacement
- The setup is more involved for people who want to expose it over the internet securely
- The mobile experience is primarily a progressive web app rather than a native app
PhotoPrism is a better fit for people who have a large existing photo archive they want to browse and organize, and are less focused on real-time phone backup.
The Hardware and Hosting Options
Home NAS
A Synology or QNAP NAS running Docker is the most common home server choice for Immich. Both manufacturers have app stores, but Immich is not in them — it runs as a Docker container, which requires enabling Docker support on the NAS.
A Synology DS423+ or equivalent (4-bay, 4GB+ RAM) provides enough power to run Immich including the machine learning features. Entry-level NAS devices with 1-2GB RAM will run Immich but may struggle with AI processing.
Cost: a mid-range 4-bay NAS plus drives is a $400–800 investment before factoring in drives.
Dedicated home server
A small PC or mini PC running Ubuntu Server is another common choice. Systems like the Beelink Mini S12 Pro or similar mini-PCs can run Immich comfortably on low power draw. The benefit over a NAS is more processing power at lower cost; the drawback is the setup is more DIY.
VPS or cloud server
Running Immich on a VPS (Hetzner, DigitalOcean, Vultr) keeps your photos off your local hardware but puts them on a third-party server. This is technically self-hosted in that you control the software and data, but your photos now live on infrastructure you do not own. It does eliminate the hardware failure risk while retaining software control.
For large photo libraries, storage costs on a VPS can approach commercial cloud storage pricing.
The Backup-of-the-Backup Problem
This is the most important part of this guide.
Self-hosting your photos solves the “Google might use my photos for AI” problem. It does not solve the “my photos might be lost forever” problem. It arguably makes that problem harder to manage.
Commercial photo services include redundant infrastructure, off-site replication, and disaster recovery as a matter of course. Google Photos stores your photos in at least three geographically distributed copies without you doing anything. Losing your Google Photos library would require multiple simultaneous failures that Google would have to compensate you for.
Your home NAS is a single point of failure. If the building floods, or there is a fire, or the NAS fails due to a firmware bug at the same time the drives have accumulated bit rot — your photos are gone. The same photos that would have survived in Google’s infrastructure are now permanently lost because your home server failed.
The correct answer to this is the 3-2-1 backup rule applied to your self-hosted setup: three copies, two different media types, one off-site. In practice, for a self-hosted photo library, this means:
- The Immich installation itself (primary copy)
- A second local copy, ideally on a separate device (a second NAS, an external drive kept updated via rsync)
- An off-site copy (a cloud storage service, a friend’s house, a remote server)
This is the right approach and most people who run self-hosted infrastructure know it. But it means the “privacy win” of leaving Google Photos may involve paying for some form of cloud backup anyway — just one you have more control over (Backblaze B2, Wasabi, or similar object storage services).
Who Should Consider Self-Hosting
Self-hosting makes sense when:
- You are technically comfortable with Linux, Docker, and basic server administration
- You have an existing home lab or NAS setup and are adding photo management to it
- You have specific reasons to want photos off commercial cloud infrastructure — legal, professional, or personal
- You understand the backup requirements and have a plan to implement them
- You are willing to spend time on ongoing maintenance
Self-hosting does not make sense when:
- You want the privacy benefits without the technical overhead
- You have one device and no redundancy plan
- You are not comfortable troubleshooting server issues
- Your primary concern is ease of access from multiple devices and family sharing
The Alternative: A Privacy-Respecting Cloud
The choice is not binary between Google Photos and a home server. There are cloud services that take a different approach to privacy than Google — not processing your photos for AI training, not targeting you with ads based on your content, not scanning your uploads for commercial purposes.
A service that stores your files with AES-256 encryption at rest and TLS in transit, is GDPR and CCPA compliant, never sells your data, and explicitly does not train third-party AI on your content gives you most of the privacy benefit of self-hosting without the infrastructure burden.
The trade-off compared to self-hosting is that you are trusting the service’s privacy commitments rather than verifying them with physical control. The trade-off compared to Google Photos is that the privacy commitments are meaningfully different.
For most people who want a private home for their photos and files without the complexity of running a server, a privacy-focused cloud service is a more realistic fit than self-hosting — even if the self-hosting community rarely acknowledges this.
Making the Decision
Before committing to self-hosted photo storage, be honest about a few things:
- How much time per month are you willing to spend on infrastructure maintenance?
- Do you have a hardware budget for a NAS or server, plus redundant storage?
- What is your plan if the server goes down while you are away?
- Who takes over the infrastructure if you are no longer able to maintain it?
Self-hosting is a genuine solution to genuine privacy concerns. The people who run it successfully and recommend it are not wrong. But there is a difference between people who enjoy running home server infrastructure and find the photo management aspect incidental, and people who want private photo storage and are considering running a server as the means to get there.
If you enjoy the infrastructure work, self-hosting your photos is excellent. If you want the privacy outcome without the infrastructure work, there are better options.