Website profiles · Technology insights · Alternatives

memories.gallery

Fast, modern and advanced photo management suite. Free and open source Nextcloud app.

Image Tools Open Source

No paid content found

Visit website

Profile views 12 Outbound visits 4 Normal

At a glance

Category: Image Tools
Language: English
Paid-content signal: No paid content foundObserved
Registered: 2023
Hosting: FastlyInferred
HTTPS certificate trusted: PassedObserved
Last updated: 2026-10-01 05:50

Website review

This review may include AI-generated content and is not individually verified. Domain, certificate and other facts come from the observed data on this page.

What is Memories?

Memories is a free, open-source photo management app for Nextcloud. It runs on your own Nextcloud server rather than on a vendor's cloud, so your photos stay under your control, and you can optionally encrypt them with a secret key.

Who it suits

People already running Nextcloud who want a Google Photos–style experience without moving their library to a third party.
Households or small teams where several users share one server and want to collaborate on albums.
Anyone with a very large library — the app is built for large collections and is designed to run even on modest hardware such as a Raspberry Pi.

What you actually get

Timeline — a chronological view you can jump through, even with hundreds of thousands of photos.
Auto upload — the official Nextcloud mobile apps for Android and iOS send photos and videos to your server, and Memories extracts EXIF metadata on arrival.
Albums — organise photos and share albums with other users on the server or with anyone on the internet; multiple users can collaborate on the same album.
Automatic tagging — integrates with the Recognize and Face Recognition apps to tag keywords and faces using AI, with manual tagging available too.
Metadata editing — change title, description, GPS location, date/time and tags, including in bulk.
Map view — GPS data is plotted automatically, with reverse geocoding to find photos by place name.
Video transcoding — an on-demand transcoder supports a wider range of formats and adaptive streaming, with optional VA-API or NVENC hardware acceleration.

The main trade-off

Because Memories is self-hosted, you take on the server: installation, storage, backups and updates are yours to manage. In exchange, you avoid subscription fees and keep ownership of your data. If you don't already run Nextcloud, that setup cost is the real barrier; if you do, Memories is essentially an added app rather than a new platform.

Next step

If you have a Nextcloud instance, install Memories there and let the mobile app upload a test batch of photos. Check how the timeline and map view handle that batch before committing your full library — and confirm your backup routine covers the photo directory first.

How do I install Memories on my Nextcloud server?

Install Memories as a Nextcloud app. It is a self-hosted photo management suite that runs inside your existing Nextcloud instance, so the practical steps are: confirm your Nextcloud server is working, install the app, then point it at your photo library.

The official page lists "Installation" and "Configuration" under its Getting started docs, but the page itself doesn't include the exact commands. So use the app's own installation guide for the precise steps, and treat the outline below as the general shape of the process.

What you need first

A working Nextcloud server you can administer.
Admin access to the Nextcloud app store or the server's command line.
Enough storage for your photos, plus room for generated previews and transcoded video.
The official Nextcloud mobile apps if you want automatic upload from a phone.

Typical installation path

Log in to Nextcloud as an administrator.
Open the Apps section and search for "Memories."
Install and enable the app.
If you prefer the command line, use Nextcloud's occ tool to install and enable it.
Open Memories from the Nextcloud app menu and choose which folders to scan.
Wait for the initial indexing and metadata extraction to finish; large libraries take longer.

For a large or unusual setup, the command-line route is more reliable because you can see errors and rerun indexing. The app's own docs cover occ commands and config.php options.

Decisions that affect the install

Situation	What to consider
Small personal library	Web app-store install is usually enough
Hundreds of thousands of photos	Plan for indexing time and preview storage
Raspberry Pi or modest hardware	The app is designed for this, but transcoding will be slow without hardware acceleration
Lots of video	Consider VA-API or NVENC hardware acceleration for transcoding
Privacy-sensitive library	Keep it self-hosted and consider encrypting data with a secret key

A concrete example

If you run Nextcloud on a home server and want phone photos backed up automatically, install Memories, enable auto upload in the official Nextcloud mobile app, then let Memories extract EXIF metadata and plot GPS data on its map view. You can then organize shots into albums, share them with other users on your server or with a public link, and use the Recognize and Face Recognition apps for automatic tagging.

Next step

Read the "Installation" and "Configuration" pages in the app's Getting started section, then run the install. If you hit errors, check the "Troubleshooting" section and the FAQ. For broader context on the platform it depends on, see Nextcloud.

Is Memories a good alternative to Nextcloud's default Photos app?

Yes — for most self-hosters, Memories is a stronger choice than Nextcloud's built-in Photos app, especially if you have a large library or care about performance. It is a free, open-source Nextcloud app that stores your photos on your own Nextcloud instance rather than someone else's servers, and it is explicitly built for speed.

Where Memories pulls ahead

Timeline at scale. Memories shows a familiar timeline view and is designed to handle hundreds of thousands of photos, so you can jump to any point in time quickly. Nextcloud's default Photos app can feel sluggish on very large libraries.
Automatic tagging with AI. It integrates with the Recognize and Face Recognition apps to tag keywords and faces automatically, and you can also curate tags and faces manually.
Metadata editing. You can edit EXIF fields such as title, description, GPS location, date/time and tags — including bulk edits across multiple photos.
Maps and geocoding. GPS data is extracted automatically and plotted on a map, with reverse geocoding so you can find photos by place name.
Video support. An on-demand transcoder handles a wide range of video formats and adaptive streaming, with optional VA-API or NVENC hardware acceleration.
Sharing and collaboration. Albums can be shared with other users on your Nextcloud server or with anyone on the internet, and multiple users can collaborate on the same album.

Trade-offs to weigh

Memories is an add-on, not a replacement for Nextcloud itself — it relies on Nextcloud as the underlying storage layer. You need a working Nextcloud instance, and the mobile auto-upload experience depends on Nextcloud's official Android and iOS apps. Some features, particularly AI tagging, require installing and running additional apps (Recognize, Face Recognition), which adds setup and resource overhead. Video transcoding is also CPU- or GPU-intensive unless you enable hardware acceleration.

A practical decision rule

If your main complaint about the default Photos app is speed, large-library navigation, or missing tools like maps and metadata editing, install Memories and try it alongside Photos — they can coexist. If you only have a few hundred photos and want zero extra setup, the default app may be enough.

Next step: check the "Memories vs Photos" comparison page in the app's documentation, then install it from your Nextcloud app store and point it at an existing photo folder to test timeline performance with your own library.

How do I set up automatic photo uploads from my phone to Memories?

Memories itself does not upload anything from your phone. It is a photo management app that runs inside your own Nextcloud server, and the upload step is handled by the official Nextcloud mobile apps. So the setup is really two parts: a working Nextcloud instance with Memories installed, then the Nextcloud app on your phone configured to auto-upload into the folder Memories watches.

The short version

Install Memories on your Nextcloud server (it is a Nextcloud app, so it goes through your normal app installation route).
Install the official Nextcloud app for Android or iOS on your phone and log in to your server.
Turn on auto-upload in the Nextcloud app, and point it at the folder you want your camera roll to land in.
Let the upload run, then open Memories — it reads EXIF metadata from photos as they arrive and sorts them into the timeline automatically.

What to check when it doesn't behave

Nothing appears in Memories. The uploads are probably going to a folder Memories is not indexing. Check which folders are selected in the app's settings rather than assuming the whole account is scanned.
Photos arrive but look wrong in time. Memories relies on EXIF capture dates, and the Nextcloud app extracts that metadata on upload. Files stripped of EXIF — screenshots, some messaging-app exports, edited copies — may fall back to file dates.
Large first upload. The initial sync of a full camera roll is the slow part; after that it is incremental. If you are running the server on modest hardware, expect the first pass to take a while.

Practical notes

Auto-upload is a background convenience, not a backup guarantee. Mobile operating systems throttle background activity, so a phone that is low on battery, in low-power mode, or has the app force-closed may pause uploads for hours. If a photo matters, open the app and confirm it landed before you delete the local copy.

Privacy is the reason to do this at all: your photos sit on your own Nextcloud instance rather than someone else's servers, and Memories documents the option to encrypt data with a secret key. That is a real trade-off against the zero-effort experience of a commercial photo service — you own the storage, the backups, and the uptime.

If you have not chosen a server yet, the broader self-hosted photo landscape is worth a look before committing: Nextcloud for the platform itself, and Immich as an alternative that bundles its own mobile upload app instead of relying on Nextcloud's.

Next step: install the Nextcloud mobile app, log in, and enable auto-upload to a dedicated folder such as Photos/Camera. Keeping camera uploads in their own folder makes it easy to tell Memories which directories to index and keeps phone photos separate from anything you sync from a computer.

Can I share albums with people who don't have a Nextcloud account?

Yes. Memories lets you share an album with anyone on the internet, so recipients don't need a Nextcloud account on your server. The page also describes sharing albums with other users on the same Nextcloud server and collaborating on albums with multiple users there.

The trade-off is between convenience and control:

Public link sharing is best for sending a single album to family or friends who just want to view photos. No account, no setup on their side.
Internal sharing is better when you want the album to stay within your Nextcloud circle, with the server's user accounts handling access.
Collaborative albums suit groups already on your server who need to add or manage photos together.

A practical example: you return from a trip and want to send 200 photos to relatives. Create an album in Memories, share it via a public link, and send that link. They open it in a browser without installing anything. If you later want to limit access, you can rely on Nextcloud's link-sharing controls rather than adding them as users.

If your goal is a permanent shared library rather than a one-off link, consider giving those people accounts on your Nextcloud instance instead — then you can use internal album sharing and collaboration. For self-hosted photo management generally, see Nextcloud and Memories.

Does Memories support hardware acceleration for video transcoding?

Yes. Memories includes an on-demand video transcoder, and its documentation notes that you can speed up transcoding with VA-API or NVENC hardware acceleration. That matters most if your library contains a lot of high-bitrate or unusual video formats, since software transcoding can otherwise become the bottleneck on modest hardware.

H3 Practical considerations

On a small always-on server such as a Raspberry Pi, hardware acceleration can make the difference between smooth playback and constant buffering, but support depends on your CPU or GPU and the drivers available to your system.
If your server lacks compatible hardware, Memories still transcodes in software; expect slower processing and higher CPU use, especially with 4K footage.
Hardware acceleration is a transcoding performance feature, not a requirement for viewing photos or standard video playback.

A useful next step is to check whether your server's processor or graphics hardware supports VA-API or NVENC, then test transcoding with a single demanding video before relying on it for the whole library. Memories is a free, open-source app for Nextcloud, so you can also compare its approach with Nextcloud's own Photos app at Nextcloud.

What "open-source UI element library" actually means

The term gets used loosely, so it helps to separate the parts:

Open-source: the code is publicly available, and the license tells you what you may do with it—copy, modify, redistribute, or use commercially.
UI element: a single, self-contained piece of interface, usually small enough to read in one sitting. A button with hover states, a pricing card, a search field.
Library: a browsable, searchable collection of those elements, typically contributed by many different people.

On a site like Uiverse, elements are shared by a community and written in plain CSS or Tailwind. You find one you like, copy the markup and styles, paste them into your project, and adjust colors, spacing, and text to fit. There's no package to install and no build step required—which is exactly the appeal, and also the source of most of the confusion.

Element library vs. UI framework: the core differences

Dimension	Open-source UI element library	UI framework / design system
Unit of reuse	A single snippet you copy	A component you import or call
Installation	None; paste into your code	Package install, config, sometimes a provider
Consistency	Depends on you; each element may look different	Enforced by shared tokens and APIs
Theming	Manual edits per element	Central theme/config file
Updates	You own the copy; no upstream updates	Version bumps bring fixes and changes
Accessibility	Varies per contributor; must be checked	Usually tested and documented
Best for	Prototypes, landing pages, small sites, one-off needs	Multi-page apps, teams, long-lived products
Learning curve	Low—read the CSS	Higher—learn the API and conventions

The table isn't a verdict. It's a map of trade-offs. Element libraries win on speed and freedom; frameworks win on consistency and maintenance.

Licensing and attribution: what to check before you paste

This is where people get into trouble, and it's worth slowing down for.

Find the license. Every element or collection should state one. Common open-source licenses include MIT, Apache-2.0, and BSD. Some projects use copyleft licenses like GPL, which can impose obligations if you redistribute your code.
Understand what the license permits. MIT and Apache-2.0 are permissive: you can typically use the code in commercial and closed-source projects. Copyleft licenses may require you to release derivative source under the same terms.
Check attribution requirements. Permissive licenses usually require you to keep the copyright notice and license text somewhere in your project. That's a real obligation, not a formality.
Look for per-element terms. On community sites, the site's overall terms and the individual contributor's stated wishes may differ. If a contributor asks for credit, honor it.
When in doubt, ask or avoid. If a snippet has no license at all, you don't have clear permission to reuse it. Treat "no license" as "not open source," even if the code is publicly visible.

This article is general information, not legal advice. For commercial products with real exposure, have someone qualified review the licenses you're relying on.

How to use a community element in your project: a practical workflow

Here's a repeatable process that avoids most of the usual mess.

1. Start from a real need, not a browsing session

Decide what you need first—"a compact primary button with a loading state"—then search. Browsing aimlessly produces a pile of pretty snippets that don't fit together.

2. Copy the smallest version that works

Take the markup and the styles. Strip anything you don't need: demo wrappers, extra animations, decorative layers. Less code means fewer surprises.

3. Convert it to your conventions

If your project uses design tokens or CSS variables, replace hard-coded values:

/* Before: hard-coded */
.button { background: #4f46e5; border-radius: 8px; }

/* After: token-based */
.button { background: var(--color-primary); border-radius: var(--radius-md); }

This one step is what keeps a copied element from looking like a foreign object in your UI.

4. Check accessibility before you ship

Community elements vary widely here. Verify at minimum:

Keyboard focus is visible and the element is reachable by Tab.
Color contrast meets WCAG AA (4.5:1 for normal text).
Interactive elements use semantic HTML (<button>, not a clickable <div>).
Form inputs have associated labels.
Motion respects prefers-reduced-motion.

5. Test in context

Paste it into a real page with real content. Long labels, small screens, and dark mode break more copied elements than anything else.

6. Note where it came from

Keep a short comment or an internal credits file: source, license, date. Future you—and your legal reviewer—will be grateful.

Where element libraries genuinely shine

Prototypes and demos: you need something clickable today, not a design system.
Landing pages and marketing sites: a handful of distinctive elements, each custom.
Filling gaps: your framework lacks one specific component, and you don't want to build it from scratch.
Learning: reading well-made CSS is one of the fastest ways to improve.
Small projects: a personal site doesn't need a theming architecture.

Where they fall short

Consistency at scale: ten elements from ten contributors rarely look like one product.
Maintenance: you own every copy. When your design changes, you edit each one.
Accessibility debt: you inherit whatever the contributor did or didn't do.
No upstream fixes: a bug fixed in the original won't reach your copy.
Integration friction: different naming conventions, different units, different assumptions about resets.

When to choose which

Choose an element library when the scope is small, the timeline is short, or you need a few distinctive pieces rather than a whole system.

Choose a framework or design system when multiple people build multiple screens over months, when consistency is a product requirement, or when accessibility and theming need to be guaranteed rather than checked.

A hybrid works well for many teams: adopt a framework for the structural components—forms, navigation, layout—and borrow individual elements for the places where you want personality. Just route every borrowed element through the same token and accessibility checks, so it lands as part of your system rather than beside it.

The short version: open-source UI element libraries are a fast, flexible way to get good-looking interface pieces into a project. They are not a substitute for a design system, and the license and accessibility details are the part worth reading carefully.

Website Overview

Page metadata, canonical configuration and social previews work together to provide more consistent search and sharing presentation.

Domain and Registration

Transfer-protection status is present, helping reduce the risk of unauthorized domain transfers. The domain has about 3 years of registration history; its current configuration provides more context than age alone. The registrar is Cloudflare, Inc, a widely used domain service provider. The domain uses the common .gallery extension, which is not an independent safety signal.

DNS and Email

Nameservers are provided by Cloudflare, indicating managed DNS hosting. No CNAME was found; the observed records resolve directly to addresses. No MX record was found. A conventional explicit inbound-mail route is not configured. TXT records include verification markers for Google. Such markers may also remain after a service stops being used. DNSSEC signatures were not detected, so this additional DNS authenticity protection is not confirmed.

TLS and Certificates

The certificate uses an RSA 2048-bit public key, offering broad client compatibility. The server supplied a complete certificate chain. No organization name is present in the certificate; the available fields are consistent with domain validation. The certificate was issued by Let's Encrypt, commonly associated with automated certificate services. The certificate's total validity is about 89 days, consistent with a short renewal cycle.

HTTP and Browser Security

The checked browser-security headers were not detected, leaving fewer explicit browser-side safeguards. CORS permits any origin to read this response. This is common for public resources; sensitive responses need narrower handling. No X-Powered-By header was found, reducing one common source of backend fingerprinting information. The x-cache, x-served-by, via response header indicates a CDN or caching proxy in the delivery path. No obvious internal addresses or debug information were found in the headers.

Technology Stack Analysis

The public page identifies mkdocs-1.6.1, mkdocs-material-9.7.7, Fastly without precise versions, leaving fewer clues for version-specific scanning.

Search and Social Sharing

The Generator tag identifies mkdocs-1.6.1, mkdocs-material-9.7.7, making the publishing system easier to fingerprint. Twitter Card metadata is configured. The title has 19 characters, within a common display range. A meta description is present, with 85 characters. The observed directives allow indexing and link following.

Hosting and Email

DNSCloudflare

HostingFastly

EmailUnknown

Approximate IP geolocation (inferred; a CDN or proxy may differ from the origin server) United States Inferred 185.199.108.153

Open approximate map on OpenStreetMap

Registration details

RDAP / WHOIS

Registrar	Cloudflare, Inc
Registered	2023-05-01
Expires	2027-05-01
Domain status	client transfer prohibited
Nameservers	hal.ns.cloudflare.com、maria.ns.cloudflare.com
DNSSEC	unsigned

DNS records

DNS

Type	Name	Value	TTL	Priority
A	memories.gallery	185.199.108.153	300	—
A	memories.gallery	185.199.109.153	300	—
A	memories.gallery	185.199.110.153	300	—
A	memories.gallery	185.199.111.153	300	—
AAAA	memories.gallery	2606:50c0:8000::153	300	—
AAAA	memories.gallery	2606:50c0:8001::153	300	—
AAAA	memories.gallery	2606:50c0:8002::153	300	—
AAAA	memories.gallery	2606:50c0:8003::153	300	—
NS	memories.gallery	hal.ns.cloudflare.com	86400	—
NS	memories.gallery	maria.ns.cloudflare.com	86400	—
TXT	memories.gallery	google-site-verification=LcOTpFbQqd3Gn-w6FAP3CH_N4bR-fqTcYoWZZDttGwA	3600	—

TLS and certificates

TLS / SSL

Assessment	Normal configuration
Supported protocols	TLSv1.2、TLSv1.3
Negotiated protocol	TLSv1.3
Certificate subject	memories.gallery
Issuer	Let's Encrypt
Valid until	2026-11-21T14:49 · Remaining when checked: 51 days
Verification details	Certificate trust: Passed · Hostname match: Passed

HTTP response headers

HTTP

Header	Value
content-type	text/html; charset=utf-8
cache-control	max-age=600
server	GitHub.com
access-control-allow-origin	*

Identified technologies

mkdocs-1.6.1, mkdocs-material-9.7.7Fastly

Pages, Search and Sharing

Meta description	Fast, modern and advanced photo management suite. Free and open source Nextcloud app.
Canonical URL	https://memories.gallery/
Language	English (default)
Twitter Card	summary_large_image

Social Sharing Preview

12 fields

Sharing metadata

og:url	https://memories.gallery/(opens in a new tab)
og:type	website
og:image	https://memories.gallery/assets/images/social/index.png(opens in a new tab)
og:title	Memories
og:image:type	image/png
og:description	Fast, modern and advanced photo management suite. Free and open source Nextcloud app.
og:image:width	1200
og:image:height	630
twitter:card	summary_large_image
twitter:image	https://memories.gallery/assets/images/social/index.png(opens in a new tab)
twitter:title	Memories
twitter:description	Fast, modern and advanced photo management suite. Free and open source Nextcloud app.

robots.txt (opens in a new tab)

HTTP 404

No robots.txt found

Sitemaps

https://memories.gallery/sitemap.xml(opens in a new tab)

User reviews (0)

No reviews yet.