Mediux Posters
Fetches Show, Movie, and Collection cover art from Mediux and updates Plex/Jellyfin using TMDB IDs.
Jellyfin Collections are not yet supported.
Installation
Pipx
- Ensure you have Pipx installed:
pipx --version - Install the project:
pipx install Mediux-Posters
Usage
mediux-posters Commands
mediux-posters sync
mediux-posters media
mediux-posters set
mediux-posters settings
Notes
- When running a sync/show/collection/movie it will keep downloading sets until all the needed posters are found.
- Show, Collection, Movie: Poster, Backdrop, Logo (and Album/SquareArt only on Plex)
- Season: Poster, Backdrop
- Episode: TitleCard, Backdrop
- To enable support for Collections in Plex, each Collection needs to have a label with its tmdb-id, in the format of
tmdb-<number>
If using Kometa, refer to this comment to have Kometa add these labels.
Settings
To set Plex and/or Jellyfin details, update the file: ~/.config/mediux-posters/settings.toml.
File will be created on first run.
Example File
exclude_usernames = []
kometa_integration = false
only_priority_usernames = false
priority_usernames = []
[covers]
path = "~/.cache/mediux-posters/covers"
store = true
[jellyfin]
base_url = "http://127.0.0.1:8096"
token = "<Token>"
[mediux]
base_url = "https://images.mediux.io"
token = "<Token>"
[plex]
base_url = "http://127.0.0.1:32400"
token = "<Token>"
Details
-
covers.pathFolder location as to where to store downloaded covers.
-
covers.storeWether to store the images in the cache between runs, useful when running multiple services to not have to redownload images.
-
exclude_usernamesA list of usernames whose sets should be ignored when running a sync.
-
kometa_integrationIf enabled, will remove the
Overlaylabel from any media Mediux-Posters uploads a poster/backdrop/title-card to. -
only_priority_usernamesA boolean flag that limits downloading sets to ones created by the users specified in
priority_usernames. If set tofalse, all sets will be considered unless explicitly excluded inexclude_usernames. -
priority_usernamesA list of usernames whose sets should take priority when running a sync. If
only_priority_usernamesis set totrue, only sets from these users will be used.
Socials
Metadata
Release files for mediux-posters 2026.2.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| mediux_posters-2026.2.0.tar.gz | 2.4 MB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| mediux_posters-2026.2.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 2.5 MB
Release files / mediux_posters-2026.2.0.tar.gz
| Download URL | mediux_posters-2026.2.0.tar.gz |
|---|---|
| Size | 2.4 MB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
11ad52278b392b4ef9c6d163f22bca00248ec7c3d5527be6da491ac9dd4115f2
|
|
BLAKE2b-256 checksum How to use checksums |
a16f29ed3876d85a17b1aa9d3fe02c0a9a6f2cdd204b2895a8f169ceb4329de6
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Sep 30, 2026.
Transparency logRelease files / mediux_posters-2026.2.0-py3-none-any.whl
| Download URL | mediux_posters-2026.2.0-py3-none-any.whl |
|---|---|
| Size | 34.6 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
9b6b9ccfa06fd1bc96f18281f1e2c5d6c42f57c48f719e175be3f2ac50617392
|
|
BLAKE2b-256 checksum How to use checksums |
b28500085578039af66d98ea0932a9570692beedf8ef1a4fa17000a9aa2e0641
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Sep 30, 2026.
Transparency log