https://github.com/thedinz/KAM

KAM is a small web app that makes Kometa/Plex artwork management painless. It lets you upload artwork for movies, TV series, seasons, and collections and will:

• Import existing Plex assets — movie posters/backgrounds, series posters/backgrounds, and season posters — into your mapped Kometa assets structure

• Convert uploads to .jpg

• Replace existing poster.*, background.*, or SeasonNN.* in the correct asset folder

• Keep everything in the same structure Kometa expects

• Provide a simple web UI with a fallback image to quickly spot missing artwork

⚠️ Important constraints

At the current moment the app does NOT allow you to user a myriad of different asset directories, for now you need to pair 1 library with 1 directory. Example Kids Movies with /assets/Kids Movies. Similarly all collections must reside in 1 Collections directory.

What this means in practice:

• Pick one assets root for a given library and stick with it.

• If you have multiple libraries, each should have its own mapped directory or its own container.

• Put all Collections in a single Collections directory under one assets root.

Required Kometa settings

For KAM to function properly, Kometa needs to be configured to create and manage asset folders ahead of time.
In your Kometa configuration (example shown for Movies), make sure these settings are enabled:

Movies:
  operations:
    assets_for_all: true
    assets_for_all_collections: truesettings:
    create_asset_folders: true

Why this is required

• KAM does not create folders. It only places artwork into existing Kometa asset folders.

• These Kometa options ensure asset folders are created automatically for every movie, show, and collection.

• Once the folders exist, KAM will safely upload and replace artwork inside them.

⚠️ If the folders don’t exist first, uploads from KAM will fail.

⚠️ REMEMBER, this is an addon for Kometa, not a stand alone application.

Paths: avoid /mnt/user (FUSE) for hot I/O

Unraid’s /mnt/user uses a FUSE layer (shfs) that’s noticeably slower for lots of small file ops (like checking asset folders) and can incur spin-up delays across disks.

• Fix: map your volumes to the cache SSD directly (or a single disk) for KAM’s hot paths:

  • Use /mnt/cache/... (preferred) or /mnt/diskX/... instead of /mnt/user/....

  • In your Unraid template, bind:

    • /mnt/cache/appdata/kam:/config

    • /mnt/cache/kometa/assets:/assets (or wherever your Kometa assets live)

• Also: ensure the share(s) backing those paths are set to Use cache: Prefer/Only so mover doesn’t push them to the array.

Please visit the github page for more information