If you are looking for a self hosted Google Photos alternative, you have probably seen two very different recommendations. One group tells you to install Immich on a server, set up Docker…
Both groups are right — for different people. This article is not a winner-takes-all comparison. It is a decision guide to help you answer one practical question: do I need to self host photos, or would a local-first setup fit my life better?
This guide is for you if you manage a large library on a desktop, care about privacy, and are tired of cloud storage fees. It is less useful if your main need is automatic phone backup for a whole family.
Most comparisons start with features: who has face recognition, who has a better mobile app, who supports more RAW formats. Those details matter, but they are the wrong starting point.
The real difference between self-hosted and local-first is not a feature list. It is a responsibility list.
A self-hosted photo manager is a small web service you run yourself. You install it, you keep it updated, you back up its database, you make sure it stays reachable from your phone, and you fix it when something breaks after an update. In exchange, you get a Google Photos-style experience that you control: mobile apps, automatic uploads, shared albums, and access from anywhere.
A local-first photo manager is a desktop app that works on the files already on your computer. You point it at your existing folders, it indexes them in place, and you browse, search, organize, and clean up without moving your photos into a new system. There is no server to keep alive. In exchange, you give up the always-on, anywhere-access part of the cloud experience. Your library lives where your files live.
That is why “is Immich better than Lap?” misses the point. They are built for different jobs. For a spec comparison, see our Lap vs Immich comparison. This article answers the earlier question: which system should you choose?
Self-hosted sounds simple: you host it yourself. In practice, it means you become the operator of a small photo service.
A typical self-hosted setup, such as Immich, runs as containers on a server, NAS, or mini-PC. You need a machine that stays on, storage, a database, and a way to reach it from your phone. The first install feels satisfying — timeline, mobile app, automatic uploads — like your own private Google Photos.
The ongoing work is where people enjoy the project or quietly regret it. You must update the service, database, and machine; back up photos plus the database and config; and handle a full disk, a failed restart, or a phone that cannot reach the server while traveling. That is normal for a home-server user, but it never fully goes away. Many self-hosted systems also keep their own library structure, so leaving later can mean an export project. Ask whether you accept that commitment, or prefer folders as the source of truth.
Local-first means the opposite trade-off: your folders stay the source of truth, and the app works around them.
With a local-first photo manager like Lap, there is no server to install, no Docker setup, no database to babysit, and no account to create. You download the desktop app, point it at the folders where your photos already live, and it builds an index in the background. Your files do not move. Your folder structure does not get rewritten. Tags, ratings, smart albums, face clusters, and search results live in a local catalog that sits alongside your files, not instead of them.
Day to day, you open the app and your library is there instantly, even offline. You can search by description, filter by camera, date, location, or rating, find duplicates, and clean up without uploading anything. If you stop using the app, your folders are unchanged. That reversibility is the core promise of local-first.
The trade-off is clear: a local-first desktop app is not a phone backup service. It does not auto-pull photos while you are out, and it does not provide a shared family album in a browser. If those are your main needs, local-first alone will disappoint you.
If you want to build a private library that never touches the cloud, our guide on how to build a private photo library walks through the folder-first workflow that local-first tools use.
You will likely be happy with self-hosted if most of these are true:
If that list fits you, self-hosted is not overkill. Immich is the most common choice here: actively developed, with mobile apps and a modern photo-service feel. Do not choose it only because it sounds more “complete” — if you do not need backup and sharing, you pay maintenance for features you will not use.
You will likely be happier with local-first if most of these are true:
If that sounds like you, local-first removes the biggest friction: setup. You start with the library you already have, without migrating it. Lap is built for this case — browsing, local AI search, duplicate cleanup, RAW and Live Photos, folder-first organizing — see the features page.
Mid-article check: If you already know you do not want a server, you can skip the rest of the decision process and try the local-first path directly — download Lap for free and point it at one existing folder. You will know within one session whether the workflow fits you.
If you are still torn, answer these five questions honestly. Do not answer with what you wish were true. Answer with what you will actually do next month.
| # | Question | If yes | If no |
|---|---|---|---|
| 1 | Do you have a machine that stays on, or are you willing to keep one on? | Self-hosted is viable | Local-first is simpler |
| 2 | Is automatic phone backup your main need? | Self-hosted fits better | Local-first is enough |
| 3 | Do other people need to browse or contribute to your library from their own devices? | Self-hosted fits better | Local-first is enough |
| 4 | Are you willing to update, back up, and troubleshoot a service yourself? | Self-hosted is realistic | Local-first avoids that work |
| 5 | Is your library mostly on one computer or external drive, and is organizing it the main job? | Local-first fits better | Self-hosted may still make sense if backup matters more |
How to read your answers: mostly “self-hosted” means you need a service, not just an app. Mostly “local-first” means you need an organizer, not a service. Mixed answers are common — you may want backup and a large archive — in which case read the next section; you may not need to pick only one.
The common mistake is answering Question 4 with optimism. Everyone will maintain a server on install day. The real test is six months later, after a failed update or a full disk. Choose the architecture you will actually keep running.
Both options are free and open source, but neither is free in time.
Self-hosted costs operator time: setup, updates, backups, and troubleshooting — plus attention, even when you are not using it. For a home-lab enthusiast that is fun; for someone who just wants to organize photos, it can feel like a second job.
Local-first costs manual transfer time and discipline: you must copy new photos to the main library, and sharing is less seamless than sending a cloud link.
Both need backups of photos plus the database or catalog. Your photos are only as safe as your backup. A photo manager makes a library searchable; it does not replace a backup.
The debate is often framed as either-or. In practice, many people use both, for different jobs.
A common, sensible split is:
In that setup they do not compete. One is the workshop where you organize; the other is the mailbox for new photos and the window for sharing. If you stop either tool, your master folders stay intact.
Do not start with both. Start with the job that hurts most: messy library → local-first first; phone full and nothing backed up → backup first. Add the second tool only when the first job is under control.
If you have answered the five questions above, you already have a decision. Here is the smallest next step for each path:
If you chose local-first: Download Lap, point it at one folder — not your entire life archive — and try three tasks: search for a photo by describing it, run a duplicate scan, and create one smart album from a rule you actually use. If those three feel fast and obvious, expand to the rest of your library.
If you chose self-hosted: First write a one-paragraph backup plan: where photos and the database live, how often backups run, and how you would restore them. If you cannot write it, set up backup before you rely on the service.
If you chose both: Organize locally for one weekend first, then add self-hosted backup after your folders are clean.
Whichever path you choose, keep folders as the long-term source of truth. Services come and go; folders with a clear rule and a backup survive.
Neither is universally better. Immich is better if you want a self-hosted photo cloud with mobile backup and sharing. Lap is better if you want to organize a large local library without running a server, creating an account, or uploading anything. The right question is not which app wins, but which job you need done. If you need a specification comparison, see our Lap vs Immich comparison.
No. Lap is a desktop app for macOS, Windows, and Linux. You download it, open it, and point it at your existing photo folders. There is no Docker setup, no server, and no account required. Docker is relevant only if you choose the self-hosted path, where a tool like Immich typically runs in containers.
It depends. For organizing and searching a large library on a computer, Lap can be simpler. For automatic phone backup, multi-user sharing, or access from anywhere, Lap alone does not replace those features — it is intentionally a local-first desktop app, not a cloud service. --- If you want no server, no account, and no upload — just a fast way to manage the photos already on your disk — download Lap for free and try it on one folder today.
Free and open source for macOS, Windows and Linux.
Download Lap
Lap