SELF-HOSTED PHOTOS
Immich, from a test library to a backup you can restore.
Immich is photo and video software you run on a server you control. The useful question is whether you will look after the disks, the database and a second copy, or whether Google Photos still fits the library you actually have.
Reviewed 30 October 2026. Hardware and backup steps below follow Immich's own documentation. How we separate sourced figures from planning sums.

What you are taking on
Immich gives you a browser and mobile apps for a library that lives on your hardware. People use it for phone uploads, albums, search and face-related features. The project publishes install requirements, and it expects Docker with the Compose plugin. The supported command is docker compose. The older docker-compose command is no longer supported.
A hosted photo service hides disk failure, software updates and geographic copies. Immich does not. If the only copy of a holiday video sits on the same machine as the app, you have a library, and you do not yet have a backup. Immich says a 3-2-1 approach is the right shape: more than one copy, more than one type of storage, and one copy somewhere else.
Google Photos and Immich do different jobs
Google's plan page says a Google Account includes up to 15 GB, shared by Photos, Drive and Gmail. Larger quotas are Google One plans. On 30 October 2026 a fetch of the en-GB plans URL displayed a Basic plan of 100 GB at US$1.99 a month. That currency means the fetch was not a confirmed UK checkout. Open the plan page while signed in before you treat any pound figure as yours.
| Question | Google Photos | Immich |
|---|---|---|
| Who replaces a failed disk? | You | |
| What limits the library? | The account quota, shared with Gmail and Drive | The disks you attach, plus space for previews and the database |
| Where do originals live? | On Google's storage | In your upload location, which you must copy elsewhere |
| What breaks a restore? | An expired account or a missed download | A database backup that does not match the files, or no second copy at all |
| Phone upload | Built into the Google apps | Immich's own mobile apps, pointed at your server |
Control is the reason to switch. A 15 GB shared allowance fills quickly once phone video is included, and the next step on Google's side is a paid quota. The next step on Immich's side is a disk, a Postgres database on local SSD, and a backup that is not the same disk.
Three picks, for three different households
Stay on Google Photos
Choose this when the library fits a quota you are willing to pay, and you do not want a server in the house. You still need an export plan. A provider account is not a family archive if nobody else can download it.
Immich on a machine you already trust
Choose this when you already run a small Linux server or a NAS that can run Docker properly, and you will keep a second copy. Start with a few thousand photos, not the only copy of the library. Immich runs on amd64 and arm64. Since version 3 the machine-learning container on amd64 needs x86-64-v2, which covers most CPUs from about 2012 onwards. A virtual machine has to expose that instruction set. The last release that still supported x86-64-v1 is v2.7.5, and Immich no longer supports that release.
A dedicated box once the library is the point of the server
Choose a mini PC or a small NAS when phone backup is the reason the machine stays on. Put Postgres on a local SSD. Bulk photos can live on larger disks. Do not put the database on a network share. Immich is explicit about that, because the database is usually 1 to 3 GB and the app is sensitive to a slow or unstable connection.
Hardware Immich actually documents
The requirements page, checked 30 October 2026, asks for a 64-bit Linux or Unix-like system. Minimum memory is 6 GB, with 8 GB recommended. Minimum CPU is 2 cores, with 4 recommended. Machines with only 4 GB of RAM can run Immich if machine-learning features are turned off. If you set a Docker memory limit on Postgres, that container needs at least 2 GB.
Windows and macOS are discouraged because Docker Desktop is a poor fit. If you still try Windows, the database directory cannot sit on NTFS or exFAT, and a WSL mount under /mnt is a known failure. The documented workaround is a Docker volume for DB_DATA_LOCATION instead of a bind mount on the Windows filesystem. Immich also prefers a Unix filesystem such as ext4, ZFS, APFS, Btrfs or XFS, because it relies on user and group permissions.
A GPU is not required to store and view photos. Machine-learning jobs can use the CPU. Hardware acceleration for that work is documented separately and depends on the backend. Read Immich's machine-learning acceleration page for the current support list before you buy a card for this app alone.
Check the live numbers before you install:
free -h
nproc
df -hfree -h shows whether you are near the 6 GB floor once the desktop and other containers are running. nproc is the CPU count Immich is talking about. df -h is the disk the database and the library will share. Run them on the server, not on your laptop.
A worked storage sum
Immich says thumbnails and transcoded video add about 10 to 20 percent on average, on top of the originals. Take a 500 GB library of original photos and videos. At 10 percent, generated files add 50 GB. At 20 percent they add 100 GB. Add the common database size of 1 to 3 GB on SSD. The live working set is then about 551 to 603 GB, before a backup copy.
A backup of the originals is another 500 GB somewhere else, and a restorable backup of the whole upload location is closer to the 551 to 603 GB figure. Two full copies of a 600 GB working set are 1.2 TB. That is the number to take to the photo storage calculator, then replace our round 500 GB with the size of your own library:
du -sh /path/to/your/photosThe 10 to 20 percent band is an average from the project, not a promise for a library that is mostly 4K video. Video transcodes land in encoded-video. Previews land in thumbs. If you only have disk space for one extra copy, copy the originals and the database first. You can rebuild thumbnails and transcodes after a restore. You cannot rebuild a video that was never copied.
For a new install on version 1.92.0 or later, UPLOAD_LOCATION/library stays unused until an administrator turns on the storage template. Originals uploaded from the browser, the mobile apps or the CLI then sit in UPLOAD_LOCATION/upload. Profile images sit in profile. Automatic database dumps sit in backups. If you enable the storage template, originals move under library and they stay there even if you later turn the template off. New uploads would go back to upload. A backup script that only knows one of those folders will miss files. Immich's own advice is to back up the whole upload location, and to treat library, upload and profile as the critical originals if you ever split the job.
Do not rearrange files inside those folders by hand. Immich does not scan the folder to rediscover photos. Paths live in the database. Moving a file in a file manager creates missing assets.
Back up the database and the files, in that order
Immich stores paths and metadata in Postgres. It does not rebuild the library by reading the disk. A folder of JPEGs without the matching database is not a working Immich install. A database without the files is a catalogue of broken links.
The app can dump the database for you. The default schedule keeps the last 14 dumps and creates one daily at 02:00. Change that under Administration, Settings, Database Dump Settings. You can also create one immediately: Administration, Job Queues, Create job, Create Database Dump. Those dumps land in UPLOAD_LOCATION/backups and they count towards the retention limit. They contain metadata only. They do not contain photos or videos.
The safest file copy is taken while immich-server is stopped, so nothing changes halfway through. If you cannot stop it, Immich says to copy the database first and the files second. The worst case is then an extra file the database does not know about, which you can upload again. The other order can restore a database that points at a photo the file copy never captured.
For a manual dump from the server, the project documents this pattern. Replace the database name and user if you changed the defaults. They are usually immich and postgres.
docker exec -t immich_postgres pg_dump --clean --if-exists --dbname=immich --username=postgres | gzip > /path/to/backup/dump.sql.gzKeep that .sql.gz with the file copy, on a disk that is not the live volume, and preferably in another building. A dump sitting only inside UPLOAD_LOCATION/backups dies with the disk you were trying to protect.
Restore is deliberately fussy. The command-line path wants a fresh database: the Immich server should not have already migrated an empty install, or Postgres will complain that relations already exist. The documented sequence brings the stack down, starts only immich_postgres, waits for it, and pipes the dump back through psql in a single transaction. Immich's backup page includes the exact sed adjustment for search_path and the warning that docker compose down -v deletes data. Follow that page on the day you restore, because the process changed in v2.5.0 and older dumps use older instructions. There is also a web restore under Administration, Maintenance, and a welcome-screen restore for a new install once the old folders have been moved into place.
Before you depend on Immich, restore one dump onto a spare machine or a spare folder and open a photo. A backup you have never restored is a hope. The web restore shows integrity checks for the storage folders. Read them. A green database and an empty upload folder is a failed recovery even if the button said it worked.
A sensible first weekend
Use copies. Point the phone app at the server only after you have uploaded a sample from the browser and confirmed the files appeared under the upload location. Then pull one database dump and copy those sample files to a second disk. Upgrade once, on purpose, while the library is still small. Immich moves quickly. An upgrade you have never practised is a poor thing to meet on a Sunday night with a full disk.
Remote access is a separate project. The server does not need to be on the public internet for uploads at home. If you do publish it, give it HTTPS, keep Docker updated, and do not forward the database port. Our HTTPS guide covers the certificate half. The backup half is still yours.
Power is usually the small cost. A photo server that is also a NAS with spinning disks is a different bill from a mini PC. Measure it, then use the electricity calculator. Do not compare a 15 GB Google quota with a 4 TB disk and call the disk cheaper until the second copy and the drive replacement are in the sum.
Questions people ask before they install
Is Immich a backup of my phone?
It can be one copy of the camera roll, if the upload finishes and you keep another copy of that library. The phone, the Immich disk and an off-site copy are three different things. Two of them in the same room still fail together in a fire or a theft.
Can I put the photos on a network share?
The originals are often stored that way. The Postgres files should not be. Immich says the database location should use local SSD and never a network share. If Docker resource limits are in use, give that database at least 2 GB of RAM.
Do I need a GPU for search and faces?
No. The CPU can do the machine-learning work. A GPU or other accelerator is an optional way to reduce that load. Check the current acceleration document before you buy hardware for it.
What if my CPU is very old?
If it lacks x86-64-v2, current Immich machine-learning images on amd64 will not suit it. Arm64 is a separate supported platform. Check the requirements page rather than a forum post from 2024.
Will Google Photos and Immich stay in sync by themselves?
No. They are separate libraries. A move means an export from Google and an import into Immich, then a check that the counts and a sample of albums match. Keep the Google copy until the Immich backup has been restored once.
Verdict
Use Immich when you want the library on disks you can unplug, and you will actually run the dump and the second copy. Use Google Photos when you want Google to operate the storage and your library fits a quota you accept. A mini PC with 8 GB of RAM and a local SSD for Postgres meets the published recommendation. The disk sum is originals, plus roughly 10 to 20 percent, plus 1 to 3 GB for the database, plus another copy that does not live on that machine.
Sources checked 30 October 2026: Immich requirements, Immich backup and restore, machine-learning acceleration, and Google One plans.