Nextcloud vs Immich for Photos: Keep Them in Your File Cloud or Give Them a Dedicated App

Leona Hart

Leona Hart

November 19, 2026

Nextcloud vs Immich for Photos: Keep Them in Your File Cloud or Give Them a Dedicated App

You already run Nextcloud, or you are about to, and your phone has thousands of photos that need somewhere better to live than a cloud subscription. Nextcloud can take those photos today: its mobile app uploads them, and a couple of server apps turn the folder into a gallery. Immich is the other path, a server built only for photos and videos that many self-hosters now treat as the default Google Photos replacement. The real question is whether your photos should be one more folder in your file cloud or a library inside a dedicated app, and whether you can have both without doubling your storage.

What Nextcloud’s photo stack is made of: Photos, Memories and Recognize

Nextcloud does not have a single photo product. It has a set of apps that each add a layer on top of ordinary files.

  • Photos is the bundled gallery. It shows images from your files in a timeline view and lets you build albums and share them.
  • Memories is a third-party app by Varun Patil (GitHub: pulsejet/memories) that most people install when they want something closer to Google Photos. Its README lists a timeline sorted by EXIF date, albums, a map view with reverse geocoding, and grouping by people and objects “powered by recognize and facerecognition.” It is actively maintained: as of November 2026 the Nextcloud App Store lists version 11.1.4 for Nextcloud 34 and 35, with older branches kept for earlier server versions. Memories is not abandoned, but it does track Nextcloud releases closely, so check the App Store compatibility list before a major server upgrade.
  • Recognize is Nextcloud’s own on-device classification app. According to its README it groups photos by faces, tags objects (animals, food, vehicles, landscapes), detects landmarks, and can even classify music genres and human actions in video. Results are stored as Nextcloud collaborative tags, and the README states that “All image processing is done on your nextcloud machine.” Face results are browsed through Memories.

Getting photos onto the server is the job of the Nextcloud mobile apps for Android and iOS, which have an auto upload feature that copies new camera images into a folder you choose. From then on they are normal files that you can sync, share or move, and Memories and Recognize simply index whatever is there. The folder is the source of truth: remove the gallery apps and your photos are still sitting in a tidy directory tree.

What Immich adds as a dedicated photo server

Immich takes the opposite stance. It owns the library, and the interface is built around photos rather than files. Its documented feature set includes:

  • Mobile backup from the Immich Android and iOS apps, by album, with Wi-Fi-only uploads by default.
  • A timeline with memories, favorites, archive and trash, plus photo editing on mobile, which arrived with v3.0.0.
  • Face recognition with a People view, and since v3.3.0 the ability to share people between users.
  • Smart search using CLIP-style models. The search docs describe it as allowing “freeform searches without requiring specific keywords in the image or video metadata,” alongside filters for people, OCR text, location, camera, dates and tags. You can swap the model under Administration, including multilingual options.
  • A map view of geotagged photos.
  • Shared albums and shared links for family members or people without an account.
  • Partner sharing, which gives another user one-way access to all of your non-archived photos. The docs note that favorites, existing albums and face data are not included, and that the other person has to share back if you want to see theirs.
  • External libraries that index folders already on disk without importing them, covered in detail below.

The project’s maturity also changed. For years Immich warned users not to treat it as their only copy because it was under heavy development. That ended with v2.0.0 on October 1, 2025, the first stable release, after which the project adopted semantic versioning. v3.0.0 followed on July 1, 2026 with a migration guide for its breaking changes, and the most recent release on the Immich blog at the time of writing is v3.4.0 from November 10, 2026. Breaking changes now come with major version numbers instead of arriving in any random update.

Hands holding printed photos at a kitchen table

Phone backup: Nextcloud auto upload versus Immich’s backup engine

Both projects are bound by the same rule on iOS: the operating system decides when background work runs. Immich’s mobile backup docs say it plainly, “iOS automatically manages background tasks; the app cannot control when the background upload task will run,” and require Background App Refresh to be enabled. On Android, the same docs warn that “some Android models are very strict with battery optimization settings” and point to the Don’t Kill My App site for vendor-specific fixes.

Nextcloud’s iOS app runs into the same constraint, and the Nextcloud community forum has a long series of user threads reporting auto uploads that only progress while the app is open in the foreground. Those are user reports, not official documentation, but they match the iOS behavior both projects describe. With either app, open it now and then so the queue catches up.

Where the two differ is what the app does beyond copying files. Immich’s app is a full photo browser that merges local and server items into one timeline, and since v2.5.0 it can free up space on the phone by removing local copies that are already backed up. Nextcloud’s app is a file browser with an upload feature. It works well as a pipe into a folder, but browsing a large library on the phone is something Memories handles better through its own Android app or the web interface.

RAM and CPU: Recognize’s 4 GB versus Immich’s machine learning container

Immich runs as several containers: the server, a PostgreSQL database with a vector extension, Redis-compatible caching and a separate machine learning container. Its requirements page sets a minimum of 6 GB of RAM (8 GB recommended) and 2 CPU cores (4 recommended). On a 4 GB machine the docs say you can run Immich with machine learning disabled, which means no faces and no smart search. As of v3, the machine learning image on amd64 requires a CPU that supports the x86-64-v2 instruction level, so very old hardware may need ML turned off or moved to another machine.

The database has its own rules: the docs say Postgres “should ideally use local SSD storage, and never a network share of any kind,” and it will not run on NTFS or exFAT. Thumbnails and transcoded video add roughly 10 to 20 percent on top of your library size.

Nextcloud itself is lighter, but Recognize is not free. Its README asks for about 4 GB of free RAM, around 1 GB of disk for the object model, and an x86-64 CPU with AVX on a glibc system for native speed. On other setups, including arm64, Alpine and Nextcloud AIO, it falls back to a slower WASM mode. The models run in Node.js inside the app, and the first classification pass over a large library takes a long time on modest hardware either way.

Once you add Recognize, a Nextcloud server ends up in a similar memory range to Immich. The difference is that Immich’s models can be swapped from the admin panel, while Recognize ships a fixed set.

Backing up the server that backs up your phone

Neither tool is a backup by itself. It is the second copy of your photos, and you still need a third.

With Nextcloud, photos live as plain files in the data directory under each user’s folder, and the database holds shares, tags, album definitions and Recognize results. A file-level backup of the data directory gets your photos back even if you lose the database, although you lose the albums and face groups. If you enable Nextcloud’s server-side encryption, that changes: files on disk are encrypted and a raw copy of the folder is useless without the keys.

Immich stores originals under its upload location, organized by its storage template, and keeps everything else (albums, people, descriptions, sharing) in Postgres. Its quick start is explicit that the built-in database backups cover metadata only: “You must setup manual backups of the images and videos stored in UPLOAD_LOCATION.” Since v2.5.0 you can also restore those database backups from the web interface. A restore without the database still leaves you with your original files, but without the organization you built inside Immich.

The practical rule is the same for both: back up the photo directory and the database together, with a tool that keeps versions, to a disk or service that is not the server itself.

Running Immich on top of Nextcloud’s photo folder with an external library

Many households end up wanting Nextcloud for files and Immich for browsing photos. You can avoid two copies by letting Nextcloud keep receiving uploads and having Immich index the same folder as an external library.

Immich’s library docs describe external libraries as tracking “assets stored in the filesystem outside of Immich.” You mount the folder into the Immich containers and add it as an import path. Mount it read-only:

services:
  immich-server:
    volumes:
      - ${UPLOAD_LOCATION}:/data
      - /srv/nextcloud/data/alex/files/Photos:/mnt/nextcloud/alex:ro

An open photo album with blank pages next to a phone

Then create a library for that user in the Immich admin panel with /mnt/nextcloud/alex as the import path. Several caveats follow from how both apps work:

  • Keep it read-only. The docs warn that without :ro, “Immich will be able to delete the files in this folder.” Nextcloud expects to be the only thing writing to its data directory, and files changed behind its back do not show up correctly until you run occ files:scan. A read-only mount keeps Immich from creating that problem.
  • Permissions. Nextcloud’s data directory is normally owned by the web server user with restrictive permissions. The Immich container needs read access, which usually means a group or ACL change on the host. Avoid loosening permissions on the whole data directory.
  • Metadata stays in Immich. Albums, descriptions and face names you add in Immich are “only stored inside Immich and will not be persisted to the external asset file.” If you move a file in Nextcloud, Immich treats it as a new asset on the next scan and that metadata is lost.
  • Deletes flow one way. If a file disappears from disk, Immich moves it to trash on rescan and removes it after 30 days. You cannot delete from Immich through a read-only mount.
  • Scanning. Immich runs a nightly library scan by default. Its file watcher is marked experimental, and the docs warn it likely will not work on network drives.
  • Uploads go through Nextcloud. In this setup the Immich mobile app is for viewing, not backup. If you also turn on Immich backup, you get two copies of every photo.
  • Encryption breaks it. With Nextcloud server-side encryption enabled, Immich will read encrypted files it cannot display.

How Nextcloud AIO versus a plain install affects photos

Nextcloud All-in-One (AIO) is the Docker-based installation method maintained by the Nextcloud project. A mastercontainer manages Nextcloud, PostgreSQL, Redis and optional services such as Imaginary for HEIC previews, plus a built-in BorgBackup-based backup. It is started like this, per the AIO README:

sudo docker run 
  --init 
  --sig-proxy=false 
  --name nextcloud-aio-mastercontainer 
  --restart always 
  --publish 80:80 
  --publish 8080:8080 
  --publish 8443:8443 
  --volume nextcloud_aio_mastercontainer:/mnt/docker-aio-config 
  --volume /var/run/docker.sock:/var/run/docker.sock:ro 
  ghcr.io/nextcloud-releases/all-in-one:latest

For photo work, AIO has trade-offs. Its README notes GPU passthrough options that can speed up Memories’ video transcoding, and Recognize works there in WASM mode. The built-in backup is convenient, but folders mounted through NEXTCLOUD_MOUNT are “not covered by the built-in backup solution.” The data directory sits in a Docker volume unless you set NEXTCLOUD_DATADIR before the first install; the README says not to change it afterward. If you plan to point Immich at Nextcloud’s files, decide on a host path for the data directory before you install AIO.

A plain install gives you direct control over the data path and file ownership, which makes the external library setup easier to reason about, in exchange for handling upgrades, cron and backups yourself.

Matching the setup to your household

One or two people who already run Nextcloud

Auto upload into a Photos folder, install Memories, and add Recognize if you have about 4 GB of RAM to spare. You get a timeline, a map and face grouping without a second stack to maintain.

A family where photos are the main reason for self-hosting

Run Immich as the primary library. Its mobile app, shared albums, partner sharing and smart search are built for people who will never see the server, and its stable release line since October 2025 makes upgrades predictable. Keep Nextcloud, if you use it, for documents. Earlier futurion comparisons cover Immich vs PhotoPrism and Immich vs Ente Photos if you are still choosing a photo app.

A household that wants files and photos without duplicates

Let Nextcloud handle uploads and point a read-only Immich external library at each user’s photo folder. Accept that Immich-only metadata is fragile if files move, and that the Immich app becomes a viewer. This works best on a plain install or an AIO install with a host data path.

A Synology owner or a small box with 4 GB of RAM

On a NAS with its own photo app, the trade-offs are different; see Immich vs Synology Photos. On a 4 GB machine, neither Recognize nor Immich’s machine learning fits comfortably. Plain Nextcloud with Photos or Memories and no classification, or Immich with ML disabled, are the realistic options. If you are still deciding whether Nextcloud is the right file layer at all, the Seafile vs Nextcloud comparison covers that choice.

More articles for you