Nextcloud Memories

TL;DR

• What it is: A free, open-source (AGPL-3.0) photo management Nextcloud app — not a standalone product. Adds a timeline, AI tagging, albums, maps, video transcoding, and face recognition on top of an existing Nextcloud instance. Built by Varun Patil.
• Who it’s for: People who already run Nextcloud (or are willing to) and want a photo management experience closer to Google Photos on top of their existing infrastructure. Not the right pick if you want a standalone photo app — that’s Immich territory.
• Cost savings: Google One 2TB is $9.99/mo = $120/year. Google One 5TB is $24.99/mo = $300/year. iCloud+ 2TB is $9.99/mo = $120/year. Self-hosted Memories is $0 software plus whatever storage costs you — 2TB NAS drives run ~$50–80 one-time.
• Key strength: No lock-in. Memories stores metadata in EXIF headers and uses your existing filesystem structure. Migration out is filesystem copy, not database dump + transform. Tested on libraries over 1 million photos.
• Key weakness: Nextcloud-dependent complexity. The app inherits Nextcloud’s operational burden — Redis for file locking, APCu caching, PHP Opcache + JIT, HTTP/2, cron properly configured. Face recognition runs out of memory on libraries over 100K photos unless you raise memory_limit to 16GB+. Reverse geocoding requires MySQL/MariaDB/Postgres — SQLite is not supported for Places.

---

What is Nextcloud Memories

Memories is a Nextcloud app — not a standalone photo server — created by Varun Patil and currently sitting at 3,726 GitHub stars under AGPL-3.0. The README’s feature list reads like a Google Photos feature parity checklist:

• Timeline sorted by EXIF date
• Rewind to jump to any time in the past
• AI Tagging via the Recognize and Face Recognition Nextcloud apps (group by people and objects)
• Albums with sharing (including external, public link sharing)
• Mobile support via responsive web app + third-party Android and iOS options
• Metadata editing in bulk
• Archive for photos you don’t want in your main timeline
• Video transcoding with HLS streaming, VA-API and NVENC hardware acceleration
• Map view with reverse geocoding
• Migration tools for importing from Nextcloud Photos and Google Takeout
• Performance: “Tested on instances with over a million photos”

The dependency model matters. AI tagging is not built into Memories — it hooks into two other Nextcloud apps: Recognize (built by the Nextcloud team) and FaceRecognition (by Matías De Lellis). Those are the apps that actually run the computer vision models. This is a pattern throughout Memories: it’s integration and UX on top of Nextcloud’s primitives, not a monolithic rebuild.

No lock-in is the other headline claim: “Memories stores most of the metadata in the EXIF headers of your photos, which means that you can easily migrate to other solutions without losing your data. It also utilizes your existing filesystem structure for organization without converting it to any specialized format.” That’s genuinely different from Immich (which uses a Postgres database as the source of truth for metadata) and from Google Photos (which doesn’t give you clean EXIF-embedded metadata on export).

---

Why people choose it over Immich, PhotoPrism, and Google Photos

Versus Google Photos

Google Photos is the benchmark. Korbin Brown at XDA Developers laid out the motivation: “I don’t trust Google to protect my private photos… I’d still rather be totally in charge of that irreplaceable data than delegate the responsibility to Google.” That’s the universal pitch — not specific to Memories.

Memories gives you your data on your hardware, no scanning by Google’s ML models for ad targeting, no “we’re shutting down the service” risk. What Google Photos gives you that Memories doesn’t: world-class ML (face recognition, object detection, OCR on photos, natural language search), a polished mobile app, automatic upload from every phone, and zero operational burden. The honest version: Memories is Google Photos’ feature set at roughly 80% fidelity, at $0/month software cost, with all the Nextcloud operational work you’re signing up for.

Versus Immich

This is the most useful comparison. Immich is a standalone photo server with its own database, its own mobile apps, its own user management. It’s the Google Photos replacement most reviewers pick for pure feature depth. If you’re starting from zero and only need a photo app, Immich is usually the answer.

Memories is an add-on to Nextcloud. If you already run Nextcloud for files, calendar, contacts, and tasks, Memories bolts onto that stack without adding another database, another auth system, or another backup surface. One reddit user explicitly valued this: “I run the AIO image and I’ve made it so everything works as it should. I’ve invited my family… I take backups using NextCloud’s built in borg module.”

The rule: Immich if photos are the only thing, Memories if Nextcloud is already running.

Versus Ente Photos (self-hosted)

Ente has cleaner, more polished native mobile apps, end-to-end encryption by default, and is simpler. Memories has better integration with an existing Nextcloud stack and stores photos on disk in their original form. For families where ease of use for non-technical relatives matters, whichever interface is simpler for your users should win.

---

Features: what it actually does

Photo browsing and organization:

• Timeline sorted by EXIF date taken
• Rewind to jump to any time in the past instantly
• Albums — create, share with other Nextcloud users, share externally with public links
• Archive — hide photos from main timeline in a separate folder
• Map view with reverse geocoding and GPS extraction from EXIF
• Metadata editing — titles, descriptions, GPS, date/time, tags, bulk editing

AI features (via other apps):

• Object tagging via the Recognize Nextcloud app
• Face recognition via the FaceRecognition Nextcloud app
• Both are separate Nextcloud apps you install — Memories integrates with them rather than running its own ML

Video handling:

• On-demand video transcoder bundled with the app
• HLS streaming for adaptive quality
• VA-API hardware acceleration (Intel QSV, AMD)
• NVENC hardware acceleration (NVIDIA)

Storage and file handling:

• Uses Nextcloud’s existing filesystem — no conversion, no import process that transforms files
• Metadata in EXIF headers, not a proprietary database
• Supports common formats, HEIC, TIFF, video, RAW images
• Migration tools from Nextcloud Photos and Google Takeout

Mobile access:

• Responsive web app, works on any device
• Android client in early access on Google Play, F-Droid, and GitHub Releases
• iOS: no native Memories app — use the official Nextcloud iOS app for auto-upload

---

Pricing: SaaS vs self-hosted math

Cloud photo storage SaaS:

• Google One 2TB: $9.99/mo = $120/year
• Google One 5TB: $24.99/mo = $300/year
• iCloud+ 2TB: $9.99/mo = $120/year
• Ente Photos 2TB (managed): $11.99/mo = $144/year

Self-hosted Nextcloud Memories:

• Software: $0 (AGPL-3.0 for both Memories and Nextcloud)
• Storage: you supply the drives. 2TB HDD: ~$50–80. 4TB HDD: ~$80–120. These are one-time costs with maybe a 5-year replacement cycle.
• Compute: a Raspberry Pi 4 ($50), old laptop, or small NUC — whatever you’re already running for Nextcloud

Concrete math for a family with 2TB of photos:

• Google One 2TB: $120/year × 5 years = $600 over five years
• Self-hosted Memories on existing Nextcloud: ~$80 for a 4TB drive + $50 Raspberry Pi + $0 software = ~$130 one-time, amortized over 5 years is roughly $26/year equivalent

The dollar savings are ~$400–500 over 5 years. The stronger argument is data ownership and resistance to vendor pricing changes — Google and Apple both have a pattern of raising prices or changing terms.

Hidden cost warning: The operational overhead of running Nextcloud (security updates, PHP version upgrades, occasional database migrations, Redis and Postgres tuning) is real. For users who don’t already run Nextcloud, adding that maintenance load for photos alone is usually the wrong call — pick Immich instead.

---

Deployment reality check

If you already run Nextcloud, installation is:

1. Install Memories from the Nextcloud app store
2. Perform the recommended configuration steps at memories.gallery/config/
3. Run php occ memories:index to generate metadata indices for existing photos
4. Open the Memories app and set the directory containing your photos

What you actually need:

• A working Nextcloud instance (Hub 9/Nextcloud 30+ recommended)
• PostgreSQL, MySQL, or MariaDB — SQLite is explicitly not supported for the Places (reverse geocoding) feature
• utf8mb4 character encoding if using MySQL/MariaDB
• Redis for file locking
• APCu caching
• PHP Opcache with JIT compilation enabled
• HTTP/2 or HTTP/3 on your reverse proxy
• Nextcloud cron properly configured — indexing happens asynchronously; if cron is broken, photos don’t show up

What can go sideways (the critical section):

• Face recognition fails at scale: “Known issues include memory exhaustion on libraries over 100K photos (error: Allowed memory exhausted)” — raise PHP memory_limit to 16000M+ (16GB+) and pre-warm indexing in batches.
• Reverse geocoding (Places) is broken on SQLite — requires MySQL, MariaDB, or PostgreSQL.
• Docker-specific: OCC commands fail without interactive TTY flags — you need docker exec -it not just docker exec.
• External storage indexing is slow because all files must be downloaded for EXIF extraction.
• “No photos are shown” usually means indexing hasn’t run, cron isn’t working, or config steps weren’t completed.

Realistic time estimate:

• 30 minutes if you already have a well-tuned Nextcloud instance with MariaDB, Redis, APCu, and cron all working
• 4–8 hours for a first-time Nextcloud deployment including Memories
• An afternoon of indexing for a 50K-photo library
• Days of indexing for a 500K+ photo library, especially with face recognition

---

Who should use this (and who shouldn’t)

Use Nextcloud Memories if:

• You already run Nextcloud for files, calendar, contacts, or collaborative docs, and photos are one more use case.
• You want your photos on disk in their native filesystem structure with EXIF metadata, not in a proprietary database.
• You’re running Nextcloud AIO with borg backups and want one backup strategy for everything.
• You need video transcoding with hardware acceleration on your existing Nextcloud box.

Don’t use Nextcloud Memories if:

• You’re starting from zero and only want a photo app — use Immich.
• You have a 500K+ photo library and you don’t want to deal with memory tuning for face recognition.
• You want the polished native mobile app experience of Google Photos or iCloud.
• Your photos live on external storage (S3, SFTP) that Nextcloud treats as external — indexing will be painfully slow.
• You need end-to-end encryption by default. Ente is the stronger E2EE option.

---

Alternatives worth considering

• Immich — the standalone open-source photo server most reviewers recommend if Nextcloud isn’t already in your life. Active development, polished mobile apps, Google Photos-like experience.
• PhotoPrism — Go-based standalone photo server with strong ML for face and object detection. Serious alternative to Immich.
• Ente Photos (self-hosted) — newer E2EE-first option with clean native mobile apps. Simpler than Nextcloud, fewer features than Memories for power users.
• Piwigo — the oldest open-source photo gallery project. PHP-based, mature, less feature-dense than Memories or Immich, but stable.
• Synology Photos — if you already own a Synology NAS, this is included and well-polished.

For a Nextcloud user, the realistic shortlist is Memories (stay in Nextcloud) vs Immich (add a second service). Memories wins on integration and unified backup. Immich wins on feature depth and active development.

---

Bottom line

Nextcloud Memories is the correct choice if — and only if — you already run Nextcloud. It takes a working Nextcloud stack and adds the photo management UX that Nextcloud Photos never quite delivered, with timeline views, albums, maps, video transcoding, and optional face recognition via third-party Nextcloud apps. The “no lock-in” design (metadata in EXIF, files on disk in native format) is genuinely differentiating and matters a lot for long-term data ownership. The operational complexity inherited from Nextcloud is real, and the failure modes at 100K+ photos are documented and sharp. If you’re not already running Nextcloud, stop reading this review and evaluate Immich instead — adding Nextcloud to your life just for a photo app is a bad trade.

If you do want to run Nextcloud properly — with Memories, Talk, Calendar, Contacts, and Office all working together on your own hardware — that’s the kind of integrated self-hosting project upready.dev deploys for clients. One-time setup, annual maintenance optional, you own the stack.

Sources

This review synthesizes 5 independent third-party articles along with primary sources from the project itself. Inline references throughout the review map to the numbered list below.

1. [1] aicybr.com (2026) — “The Ultimate Guide to Self-Hosting Nextcloud in 2025 | AiCybr Blog” (link)
2. [2] xda-developers.com (2026) — “I don’t pay for these 3 Google services anymore, and here’s what I use instead” (link)
3. [3] redditmedia.com (2026) — “Reddit - The heart of the internet” (link)
4. [4] apps.nextcloud.com (2026) — “Memories - Apps - App Store - Nextcloud” (link)
5. [5] memories.gallery (2026) — “Nextcloud Memories Troubleshooting Guide” — operational troubleshooting / failure modes at scale (link)
6. [6] GitHub repository — official source code, README, releases, and issue tracker (https://github.com/pulsejet/memories)
7. [7] Official website — Nextcloud Memories project homepage and docs (https://memories.gallery)

References [1]–[7] above were used to cross-check claims about features, pricing, deployment, and limitations in this review.