Navidrome Daily: The Artwork Pipeline Rewrite Lands
Deluan shipped phases 2 and 3 of a major artwork pipeline redesign, moving artwork resolution into a background worker and cutting serving over to it, while a related fix stops placeholder images from Deezer and Last.fm being cached as real artist art.
Duration: PT2M16S
Episode overview
This episode is a short developer briefing from Navidrome Daily.
It explains recent repository work in plain language.
- Show: Navidrome Daily
- Published: 2026-07-23T10:01:16Z
- Audio duration: PT2M16S
Transcript excerpt
This excerpt keeps the crawler page concise. Listen to the episode or use the RSS feed for the full update.
Good morning. It's July 23rd, and today's story is a single, coordinated overhaul of how Navidrome handles artwork.
The headline: the artwork pipeline redesign moved from dark launch to full cutover in less than a day. PR 5836 introduced a background worker that drains the artwork queue set up in phase one, resolving album, artist, and track art through the same priority logic the current code uses, but storing results quietly on…
The second theme is data quality. PR 5837 found that Deezer and Last.fm were serving generic placeholder images — a person silhouette and a gray star — for artists without real photos, and Navidrome was caching them as genuine artist art. On a production database copy, close to a third of resolved artist images…
Separately, kgarner7 opened PR 5839, giving plugins their own sandboxed storage path through a new permission and host function. It's unrelated to the artwork work but worth noting for anyone building plugins.
And a small housekeeping commit from Deluan added an OpenCollective funding option to the repo.
What's next: watch for the promised phase three cutover behavior in production, and expect more review activity on 5838 given its size. If you…
Nearby episodes from Navidrome Daily
- Laying Groundwork for a New Artwork Pipeline
- Foundations Work — IDs, Formatting, and Housekeeping
- Better Errors, Better Persistence
- Weekly Recap - Jellyfin Compatibility Takes Center Stage
- Jellyfin Compatibility Push
- Cover Art Gets an Overhaul
- Hardening the Jellyfin API Under Real Client Load
- Closing the Jellyfin Memory Leaks