Search for a comparison of these two and you will find them presented as competitors. That framing is what makes the choice feel hard, because the honest answer is not that one wins. They replace different Google products.
Short answer
Immich replaces Google Photos. Nextcloud replaces Google Drive - and, if you want, Calendar and Contacts with it.
Immich is a photo and video application: a timeline, automatic backup from your phone, faces grouped together, and search that finds pictures by what is in them. Nextcloud is a general-purpose platform for files and collaboration, with photo features available as apps on top of it.
So the question to ask is not "which is better". It is which service am I actually trying to leave.
Why the distinction shows up everywhere
Once you know the shape of each project, most of the differences stop being surprising.
Immich is built around photos, so photo-specific things work by default. The mobile app backs up your camera roll in the background. The timeline is the main screen rather than a folder. Faces are detected and grouped. Search runs against the content of images, so a word describing a scene brings back pictures of it, whether or not anything is named that way. None of this is a feature list bolted to a file store - it is what the application is.
Nextcloud is built around files, so file-specific things work by default. Sharing links with expiry and passwords, versioning, a desktop sync client, and a large ecosystem of apps that do everything from calendars to office documents. Its photo handling - the built-in Photos app, and the widely used community app Memories - gives you a timeline, albums, a map view and face recognition on top of that file store. It is genuinely good. It is also, underneath, a folder of files with an interface over it.
What each one costs you to run
Whichever you pick, plan the backup before you fill it: backing up Immich explains why the media files alone are not enough.
Immich is the hungrier of the two, and the reason is the part people most want: its search and face recognition run machine-learning models on your own hardware. That takes real memory, and the ML container is usually the first thing people disable when a small server starts struggling. Disabling it leaves you with a good photo timeline and no smart search - which is a fair trade on a small box, but worth knowing before you pick the machine.
Nextcloud is lighter at rest and fussier to tune. It wants a properly configured PHP setup and database to feel quick, and a Nextcloud that has never been tuned is the single most common reason people describe it as slow. The work is mostly one-off, but it is real work.
If you are choosing hardware for either, the practical guidance is in our guide to self-hosted cloud storage; if you have already settled on Immich, the Docker Compose setup covers getting it running.
Running both
Plenty of people do, and it is a coherent setup rather than a compromise: Nextcloud for documents, calendar and contacts, Immich for the camera roll. The two are separate services and do not interfere with each other.
The cost is honest and worth stating: you now maintain two applications, two databases and two upgrade paths. Self-hosting is rarely hard to start and consistently tiring to keep up, and running two of these doubles the part that gets tiring.
The thing neither of them does
This is the part most comparisons leave out, and it matters more than any feature in the list above.
Neither Immich nor Nextcloud is a backup. Both are services running on one machine. If that machine's disk fails, if the filesystem corrupts, if a bad upgrade takes the database with it, or if the flat floods, the photos are gone - and they are gone in a way that no amount of choosing the better application would have prevented.
Self-hosting changes who holds your data. It does not change how many copies exist. Those are separate problems and it is easy to feel you have solved the second by solving the first. Before you delete anything from the service you are migrating away from, the collection needs to exist in at least one other place - which can be an external disk you keep elsewhere, or an encrypted account with a provider who cannot read what you store. What it cannot be is the same machine, or a second disk in the same box.
How to decide
- Leaving Google Photos, and photos are the whole problem → Immich. It is the closest thing to a like-for-like replacement, and its search is the feature you would miss.
- Leaving Google Drive, or Drive plus Calendar plus Contacts → Nextcloud. Photos come along as part of it, at a quality most people find sufficient. If file sync is the whole job and the platform features are not, read how Seafile compares with Nextcloud before committing - the two write your data to disk in fundamentally different ways, and that difference decides what you can recover without the server running.
- Both, and you accept the maintenance → run both, Nextcloud for files and Immich for the camera roll.
- Not sure you want to administer a server at all → neither, yet. A zero-knowledge hosted provider gives you a provider that cannot read your files without making you responsible for uptime, and that is a legitimate answer rather than a lesser one.
The mistake worth avoiding is picking on feature lists. Pick on which service you are replacing, then make sure whichever you chose is not the only copy.
Frequently asked questions
- Is Immich better than Nextcloud?
- Neither is better, because they are not answering the same question. Immich is a photo and video application, built to do what Google Photos does: timeline browsing, automatic phone backup, face grouping and search by what appears in an image. Nextcloud is a general self-hosted platform - files, calendar, contacts, documents - with photo handling available as an app on top. If the service you want to leave is Google Photos, Immich replaces it directly. If it is Google Drive, or Drive and Calendar and Contacts together, Nextcloud is the one that covers that.
- Can Nextcloud replace Google Photos?
- It can, with caveats. Nextcloud's own Photos app plus the community Memories app give you a timeline, albums, map view and face recognition, and the Nextcloud mobile app can auto-upload your camera roll. What you are working with underneath is still a file store with a photo interface over it, rather than an application designed around photos from the start. People who have tried both usually describe Nextcloud's photo experience as good enough and Immich's as noticeably closer to what they left.
- Do I have to choose? Can I run both?
- Running both is a common and sensible setup: Nextcloud for documents, calendar and contacts, Immich for the camera roll. They are separate services and do not conflict. The cost is that you are now maintaining two applications, two databases and two upgrade paths on the same machine, which roughly doubles the part of self-hosting that people actually find tiring.
- Which one needs a more powerful server?
- Immich is generally the hungrier of the two, because its search and face recognition run machine-learning models locally. That work is what makes searching for a word and getting matching photos possible, and it needs real memory - the ML component is usually the first thing people disable on a small machine. Nextcloud is lighter at rest but wants a properly tuned PHP setup and database to feel responsive under load. Neither is comfortable on the very smallest instances.
- Is Immich stable enough to trust with my photos?
- Treat the question as being about your backups rather than about the software. Immich is developed at a fast pace, so read the release notes before upgrading - breaking changes between versions are part of how the project moves. But the deeper point applies to both tools equally: a self-hosted service running on one machine is not a backup, whatever its quality. The photos need a second copy somewhere else before you delete anything from the service you are leaving.
- Does self-hosting mean my photos are private?
- It means no company holds them, which is a real and meaningful change. It does not by itself mean they are safe or encrypted. The data sits on a machine you administer, and its privacy now depends on your disk encryption, your access controls, your updates and how you handle any offsite copy. Self-hosting moves the trust from a provider to yourself - which is the point, and also the responsibility.
Your server is one copy - add an offsite one → pCloud Crypto
Client-side encrypted, so the provider cannot read the copy it holds
