Dear Kometa Developers, I am writing to propose a feature that would significantly enhance Kometa's utility for users who also utilize or plan to utilize Jellyfin, the open-source media server. This enhancement would allow Kometa to save the final, overlaid artwork files (posters, backgrounds, etc.) directly into the media folders alongside the media itself. Currently, when Kometa applies overlays to artwork in Plex, these changes are stored within Plex's internal database. While this works seamlessly within the Plex ecosystem, it creates a disconnect for users who also want consistent, custom artwork in Jellyfin. Jellyfin, like Plex with local media assets enabled, can read artwork files (such as poster.jpg , fanart.jpg , etc.) stored directly within the movie and TV show folders. Proposed Solution: I request the addition of a configuration option within Kometa that, when enabled, would instruct Kometa to save the final, overlaid artwork files into the corresponding media folder after the overlay process is complete in Plex. This option could potentially allow users to specify a naming convention for these saved files (e.g., mirroring Plex's internal type names or allowing custom names like poster.jpg ). Benefits: * Enhanced Jellyfin Compatibility: This feature would provide a straightforward way to have Kometa-generated custom artwork seamlessly recognized by Jellyfin without requiring separate, manual extraction and saving processes or complex scripting. This offers a significant improvement in interoperability between the two platforms, especially for artwork management. * Streamlined Workflow: Users who desire consistent artwork across both Plex and Jellyfin would benefit from a more automated and integrated workflow. Kometa would become a central tool for managing artwork for both servers. * No Major Architectural Changes: This feature could likely be implemented by leveraging the Plex API to retrieve the final overlaid artwork and then performing a file write operation. It wouldn't necessitate a fundamental rewrite of Kometa's core overlay logic, focusing instead on an additional output step. * Potential for Local Backups: Saving artwork locally could also provide users with an easier way to back up their custom artwork. By implementing this feature, Kometa would offer a valuable bridge between Plex and Jellyfin, making it an even more powerful and versatile tool for media library management. This approach allows for a degree of "integration" with Jellyfin without requiring a deep overhaul of Kometa's existing Plex-centric architecture, at least concerning artwork. Thank you for considering this feature request. I believe it would be a valuable addition to Kometa and greatly benefit a growing number of users.
