Immich Kiosk vs PiGallery 2
| Tagline | Lightweight Immich-powered photo slideshow for kiosk displays and browsers | Directory-first photo gallery optimised for low-resource Raspberry Pi servers |
| Category | Photo Management | Photo Management |
| Replaces | Google Photos, iCloud Photos | Google Photos, iCloud Photos |
| GitHub stars | 1.6k | 2.2k |
| Language | Docker | Docker |
| License | GPL-3.0 | MIT |
| Self-host difficulty | 2/5 Easy | 2/5 Easy |
| Deploy options | Docker | Docker Manual |
| Managed hosting | ||
| Last updated | 6 days ago | 27 days ago |
| View repo | View repo |
Where each falls short
The honest trade-offs — what you give up with each, versus the proprietary tools they replace.
Immich Kiosk
- Requires a running Immich server — not a standalone photo solution
- No built-in photo management, editing, or upload capabilities
- Slideshow customisation is limited to what Immich exposes via its API
- No offline mode; depends entirely on network access to the Immich backend
PiGallery 2
- No automatic mobile backup functionality; read-only gallery view only
- No AI-based face recognition or object tagging
- Multi-user support with per-user permissions is limited
- No photo editing, sharing links with expiry, or album collaboration features
Bottom line
Both are a similar lift to self-host; choose PiGallery 2 for the larger community and ecosystem. Immich Kiosk has seen more recent development. Open each guide below for deploy steps and the full feature gap.
Immich Kiosk
Lightweight Immich-powered photo slideshow for kiosk displays and browsers
PiGallery 2
Directory-first photo gallery optimised for low-resource Raspberry Pi servers