GLWS · Photos and media
Organise and browse a personal photo library with mobile uploads and searchable albums.
Common uses of Immich.
The documented deployment uses Docker Compose. Check current memory, CPU and database requirements before importing a library; machine learning and video processing add resource demand.
Planning examples, not official minimum requirements.
Photos and media
Check the current supported operating systems, deployment methods, dependencies and licence terms. What you need depends on your workload, not just the application's name.
Large datasets and busy workloads can need far more memory, storage or different hardware. Any external API or service subscriptions are separate.
Read the Immich documentation ↗ (opens in a new tab)Advice specific to this application.
Importing photos can trigger thumbnail generation, metadata processing, video conversion and machine learning. Choose resources for that work as well as everyday browsing. Keep room for generated files and verify the CPU features required by the current release.
A photo application is one copy of your collection, not the entire backup plan. Keep original media and database backups outside the instance, and follow the documented restoration process. Check release notes before updates so changes to the Compose stack and storage paths are deliberate.
Linux guides that help with this setup.
Size a server for Immich, install it with the official Compose files, keep it private, update it deliberately and back up photos and database.
Read guide →Pin image versions, back up persistent data, pull and check an update, and roll back to the previous version if it fails.
Read guide →Back up to a second server over SFTP with restic, encrypt everything, schedule it with a systemd timer and prove you can restore.
Read guide →Four steps that make the environment easier to maintain.
Read the publisher's instructions and choose a supported installation method.
Protect the dashboard, credentials and network endpoints before you expose any service.
Work out where the application keeps its state and store it separately from replaceable runtime files.
Back up the data and configuration, then check that you can restore them.
Run through it before and after you install.
$ application-checklist --name immich
[ ] Supported deployment method
[ ] Authentication and access restrictions
[ ] Independent data backup
[ ] Updates and restoration tested
root@glws:~#
Quick answers before you choose resources.
No. The configurator only saves your application preference. It does not connect to any infrastructure or run an installer.
Use the planning example as a starting point only. Check the publisher's requirements and measure the whole stack under a realistic workload.
You do. Self-hosted applications need updates, configuration and recovery planning from the operator. The publisher's documentation describes supported maintenance.
The knowledge base covers Linux access, packages, services, firewalls and backups.
Other tools you might run alongside or instead.
Build a personal media library and stream it to supported clients.
Explore application →Website, email, DNS and database management in a hosting dashboard.
Explore application →A self-hosted assistant for connecting model-powered tasks with tools and messaging.
Explore application →An agent workspace for conversations, tools and automation on infrastructure you control.
Explore application →