RU

IMAGO: A Non-Destructive Photo Editor for Immich and Android/Windows Galleries

Published: 2026-10-06 · Author: AI Release · @ai_release1
IMAGO: A Non-Destructive Photo Editor for Immich and Android/Windows Galleries

⚡ The gist in 5 seconds - IMAGO has been published on GitHub — a non-destructive photo editor for an Immich library and a phone's local gallery: the original file is never overwritten, and all edits are stored as an editable recipe. - It's available on Android 12+ (OpenGL ES 3.1) and Windows (Compose Desktop); the code is open under AGPL-3.0 with an additional permission for linking to paid app store libraries. - All processing is fully local: photos are never sent to third-party servers, and the Immich address and API key are stored encrypted on the device. ### 🔍 What was found The project was created by user paulomarques742. IMAGO connects to an Immich server (version 2.6.0 or newer required) via its address and API key. For basic operation, the user.read, asset.read, asset.view, and asset.download permissions are enough — that's all it takes to edit and export without being able to change anything on the server. Optional permissions (album.read, asset.upload, stack.create, and others) only enable the corresponding features. On export, the finished photo is returned to Immich at full resolution and stacked with the original, without cluttering the timeline with copies. The editor uses the device's GPU and processes images at 16 bits per channel. Its toolkit includes exposure up to ±5 EV, a point curve with up to 16 points, color grading with separate wheels for shadows/highlights/midtones, radial and linear masks with 13 parameters, plus nine built-in recipes, custom recipes, and copying edits between photos. The entire process is recorded in history, and the original is one tap away. The build includes shared Kotlin Multiplatform code, and for the Windows version the UI and logic are largely shared with mobile. The repo also contains a Supabase schema for optional cross-device sync — it doesn't require Docker and is being tested on PGlite. ### 💡 Why it matters The main value is privacy and the non-destructive approach. All operations run locally, no photo ever leaves the device, and Immich interaction is limited to minimal permissions. Immich users get a full-fledged editor with stack-based export, without filling storage with duplicates. Support for multiple addresses for one library is handy when switching between a home and a remote server. And optional recipe syncing between devices lets you continue editing the same photo on another device — the files themselves aren't synced; identification is based on the photo's content. ### 🧩 Context IMAGO works with Immich servers but is not part of the Immich project and has no official affiliation with it. Under the AGPL license, the name "IMAGO" and the logo are not covered by the license — a fork must use its own name and icon before distributing. The repository also contains the author's example photos under CC BY 4.0 for recipe previews. Building the project requires no keys — sync simply becomes unavailable; if desired, it can be connected to your own Supabase project, but the secret

🔗 Read on github.com

🤖 AI summary
фоторедакторimmichopenandroidwindows
📖
Read the guide on this topic
Read →
← PreviousA PII Filter in Front of Cloud Models: Why Self-Hosting LLMs Isn't NecessaryNext →DNS-OTG: An Unofficial Android App for Managing Control D

Source: github.com · post in Telegram