Release: 1.0.0 · Published: 18 October 2026
Release notes and installation files · Installation guide · Upgrade guide
Frameleaf Server brings the photo library, web app and API together on your own hardware. Originals remain ordinary files on your storage, with organization, search and background work managed by Frameleaf.
Release highlights
- A library for photographs and videos: timeline views, folders, stacks, Live and Motion Photos, RAW support and Best Photos.
- Find a remembered moment: visual search, text in photos, people and pets, places and memories. Recognition runs on your server or your own-network workers.
- Organize and share: albums, shared spaces, tags, partner sharing and public links with controls for expiry, downloads and photo details.
- Edit without replacing the original: saved photo versions and a built-in Studio workflow for video, colour, audio, captions and export.
- Keep the collection healthy: Library Care brings together duplicate review, integrity checks and missing-original recovery.
- Operate the server from Command Center: storage, backups, workers, hardware and background jobs are gathered into task-focused settings.
Database and migration
This release uses PostgreSQL 19 and database-backed background queues. A separate Redis queue service is not required for the photo application.
For an Immich library, use Manager’s one-time import into a fresh Frameleaf database. Keep the original database separate, preserve database and media backups, and leave Immich stopped after Frameleaf takes over the media. Use the complete migration walkthrough for preparation, cutover and acceptance checks.
Install or update
Use the matching release bundle, including its Compose files, environment example, manifests and checksums. The release also includes rootless, isolated-machine-learning and hardware-acceleration files for the corresponding installation choices. Verify the manifest and signed images as described in the release instructions.
With Manager, review the offered application release and recovery checkpoint before applying it. For manual Compose, keep the project, media mappings and persistent volumes, and use the database image from the matching bundle. Update separate machine-learning services to the matching release too.
Back up the database and media before changing the installation. Keep existing recovery points until you have checked sign-in, representative originals, video playback, albums, sharing, a small new upload and background work.
Release discussion
Reply with your previous release, installation method, hardware/storage, approximate library size and the result of those checks. Link a focused Bug reports topic for a reproducible defect, including the first sanitized error.
More: Safe-update checklist · Backup and restore · Full feature reference