Immich's folder handling: a poor fit for existing structured photo libraries

This review examines Immich's approach to photo organization, specifically its interaction with pre-existing folder structures, based on a user's experience with a 60,000-photo library.

TL;DR

Best for: Users starting a new photo library who prefer a date-based, AI-curated timeline, and are comfortable with manual album creation for specific events. Skip if: You have an existing, meticulously organized photo library in folders by event and require that structure to be mirrored directly into albums with automatic updates. Bottom line: Immich prioritizes a modern, flattened timeline view over direct synchronization with filesystem folder structures, making it unsuitable for users with strong folder-based organizational needs.

METHODOLOGY

This v0 review draws on the reported experience of Reddit user /u/Spoons896, who shared their observations of Immich's behavior with an existing photo library. The analysis also incorporates common architectural patterns and stated goals of self-hosted photo management tools. We covered the user's specific requirements for folder-based organization, sharing, and upload permissions, and how Immich's observed behavior addresses or fails to address these. What is not covered in this review includes independent performance benchmarks, long-term workflow integration, or an exhaustive evaluation of Immich's full feature set beyond the scope of the user's immediate problem. Direct testing of Immich's current version is pending. Update cadence: re-tested when claims diverge from observed behavior or significant new features are released.

WHAT IT DOES

File system integration

Immich is a self-hosted photo and video backup solution, often deployed via Docker. It can be configured to scan existing file shares, allowing it to ingest and manage media without requiring a full re-upload. User /u/Spoons896 successfully set up Immich to use their Windows server share as storage, indicating its compatibility with common network storage solutions. This feature is crucial for users with large, existing libraries who want to avoid data migration.

Timeline-centric display

Immich's primary organizational paradigm, as observed by /u/Spoons896, is a date-based timeline. Like commercial services such as Google Photos or iCloud Photos, it aggregates all ingested media and presents them chronologically. This approach simplifies browsing for many users, offering a unified view regardless of the original file location. However, it flattens any pre-existing folder hierarchy, which can lead to a perceived lack of organization for users accustomed to structured directories.

User management and sharing

The user's request highlights the need for sharing capabilities and controlled upload permissions for family members. Immich does offer user management and the ability to create shared albums. The intent is to allow users like /u/Spoons896's wife to upload photos directly to specific, shared albums. The challenge, as noted, is the manual effort required to create these albums and keep them synchronized with the underlying folder structure.

WHAT'S INTERESTING / WHAT'S NOT

What's interesting about Immich, based on the user's signal, is its modern architecture and active development within the self-hosted community. Its Docker-first approach simplifies deployment for many users, and its ability to integrate with existing file shares is a significant advantage, preventing the need to duplicate or move 60,000 photos. The project's focus on AI-driven features, while not explicitly detailed by the user, is a known aspect that contributes to its appeal for automated tagging and search. This aligns with the