March 31, 2026
— Immich Team
A recap of March, 2026, including an update on upcoming features, releases, developer updates, and more.
Hello everyone!
March was a great month for the team. Most of us were able to fly out to Austin, Texas, for FUTO's Don't Be Evil conference during SXSW. It's always fun to meet together in person, and we did some fun team-building activities. Besides the conference, we also had a few releases and continued working on some upcoming features. Continue below to read the full recap.
FUTO started building an encrypted backup service this year and they plan to integrate it directly into Immich. They are currently running a survey to gather information about setups, library sizes, hardware & network capabilities, etc. Please fill out the survey if you haven't already. Also, if you are interested in joining the closed beta later this year there is a place to leave your email address.
At the Don't Be Evil FUTO conference Alex used Immich to give a presentation about Immich, which included what's changed since last year, and what's planned for this year. The presentation was recorded and should be available soon™️ on FUTO's Youtube channel. You can also find the slides here, on our public Immich instance. One take away from the presentation was that Immich is where it is today because of the awesome community and external contributors, so thank YOU!
We published 1 minor release this month:
schema-check command, and OAuth claims in idTokenOur team members' unfiltered thoughts on the good, the bad, and the frustration about the current tasks they are working on.
Recently, I've seen an increase in vibe-code projects trying to implement some features or mechanisms that the team hasn't gotten to yet. While those projects seem interesting, after looking at the code, many shortcomings and questions arose for vibe-code implementation that I don't think an LLM agent can understand correctly, which could degrade the experience or rack up huge billing costs for users from those external integrations.
As someone who cares so much about the experience and the feeling about using the app as a whole, from every pixel and alignment, how the font size and the colors should look for the project, seeing those projects get implemented is like witnessing something close and personal to me get butchered into Frankenstein style.
This month I spent a decent amount of time going through bug reports and was able to fix a handful of items, worked on adding CSP support, and made some progress on workflows and plugins.
I fixed one issue, which I thought was pretty interesting. A user was getting this strange error message when trying to use the CLI:
It turns out the error was caused by the Immich server returning HTML where JSON was expected and then the client basically coerced it to a string for reasons, eventually leading to this runtime error. Once I had figured out what was happening the solution was pretty straightforward: return a 406 Not Acceptable response, instead of a 200 OK. Basically, if the client is requesting application/json, don't response with text/html. In hindsight, it seemed so obvious 😄.
I also worked on making it possible to configure the Immich server with helmet, a library for managing security headers, such as Content-Security-Policy , Strict-Transport-Security, etc. There will be more information about this feature in v2.7.0.
This is turning out to be a pretty big feature to build. I made a lot of progress this month on dynamic configuration, which means that we can generate entire forms from JSON configuration, which is important because configuration options are defined on a per plugin method basis.
This configuration, for example, generates something like this in the web application now: 
Now that dynamic configuration exists, I'll be moving on to writing tests for the core plugin, and looking into additional triggers, like PersonRecognized.
For me, besides flying out to Austin for a week, March has been mostly around chores. Briefly peaking at >200 open PRs, I had (and still have 😅) lots of review work to do. But don't get me wrong; I strongly appreciate every single contribution, and I love that so many people find joy in working on the Immich code base. Barely being able to keep up with contributions is definitely one of the better problems to have! :P
Other than that, I fixed some bugs and updated a bunch of packages.
Notably, I was finally upgrade Kysely, our SQL query builder of choice, to its latest version. Hidden behind a small fix(helpers), 0.28.3 changed the return types of nested queries. Now, for a selected JSON column (e.g., from a sub-select), the fields in that object can only be strings, numbers, objects, arrays, or booleans. After all, that's the types JSON supports. For instance, there is no concept of something like a JavaScript Date.
However, both our previous ORM as well as Kysely on versions <= 0.28.2 did type those fields based on their actual types. This resulted in our code base relying on wrong types forever basically, causing it to be deeply spread within all of Immich server. After a bunch of prior refactoring to untangle our types, primarily in unit tests (which led me down a path of refactoring most of our unit tests in fact), I was finally able to upgrade Kysely in #26744 with a somewhat reasonable diff (it's still not the prettiest, but prior attempts were horrible in comparison lol). We didn't have to give up any type safety, and I didn't have to elude to any ugly casts. 🎉
This month I made some more progress on the editing experience in Immich. My goal for the past 2 months has been to fix some of the limitations in the editing feature.
The new mobile editing experience is in its final stages of review and should be coming soon to a phone near you ™️. We merged the majority of underlying requirements for mobile editing (websocket events, sync entities, API changes) for v2.6.0. The only part that remains in the new user interface.
I made some significant headway on bringing editing support to Live Photos. This will allow you to edit an image that includes a live video portion and have the edits apply to both parts (photo and video). The changes in the PR also lay the groundwork for full video editing support in the future.
We recently sold the remaining retro DVDs from our stable release back in October. As such, we have released the source code for building the Alpine Linux based ISO that was burned onto the DVDs. You can check out the source code at https://github.com/immich-app/retro!
I worked on this project all the way back in August of 2025. It was the last week of my summer internship with Immich and originally started as a "Wouldn't it be funny if…." joke. I did some digging on how to make a bootable live DVD and I had a working image by the end of the week!
Huge shoutout to Zack for setting up the fulfillment pipeline to take orders from our merch store and forwarding them on to the DVD vendors in both the US and Europe. In addition we gave the option to purchase a product key with your DVD.
We sold over 500 DVDs since they were released! This was a super fun project to work on and now I, along with many others in the community, have a cool piece of Immich history!
Looking forward into April, we hope to have a final v2.7.0 release, and then start work on v3, which will include a handful of API breaking changes, and🤞 hopefully an initial release of workflows!
Well, that's it for this month. As always, if you find the project helpful, you can support us at https://buy.immich.app/.
Cheers,
The Immich Team
此内容由惯性聚合(RSS阅读器)自动聚合整理，仅供阅读参考。 原文来自 — 版权归原作者所有。