Latest Blog
Why Does Immich Reprocess Existing Data After an Upgrade?
Immich may reprocess assets when an upgrade invalidates earlier derivatives, metadata, models, or job state; repeated endless work is a separate fault.
What Dependencies Most Often Set the Real Immich Performance Ceiling?
Immich is capped by the slowest dependency on each measured path, so upload, search, browsing, and playback can have different ceilings.
Immich Networking: How Discovery, DNS, and Routing Produce Reachability
Immich is reachable only when endpoint selection, DNS, routing, NAT or proxy handling, TLS, and application response form one valid path.
Immich for Families: How Identity and Permissions Shape the Experience
Immich family use depends on separate identities, asset ownership, intentional sharing, limited administration, and tested revocation.
Why Is Immich Becoming More Relevant to Privacy-First Home Infrastructure?
Immich fits privacy-first homes by keeping photo workflows locally controlled, but security still depends on access, encryption, backups, and updates.
How to Benchmark Immich With a Repeatable Home-Server Workload
A repeatable Immich benchmark fixes the dataset, endpoints, cache state, client path, background overlap, and one changed variable per run.
How Much Storage Overhead Does Immich Add Beyond Source Data?
Immich overhead varies with asset count, video mix, derivative settings, database state, ML artifacts, backups, and temporary working space.
Why Does Immich Output Differ Between Native and Browser Clients?
Native and browser Immich clients can show different timing or media results because their request, cache, decode, permission, and rendering paths differ.
