mmh3-image
MiniMax-H3-Image (33B DiT, GGUF) as a one-command CLI. It installs a private ComfyUI with the GGUF loader, downloads the quantization you pick plus the required 24-channel VAE and Qwen3-VL-32B text encoder, starts the server and writes a PNG. Everything is cached, so only the first run pays the setup cost.
uvx --from mmh3-image mmh3-image "a clay badger baker outside a tiny bakery, warm lantern light" -o badger.png
What it sets up
~/.cache/mmh3-image/ComfyUI— ComfyUI checkout, venv, ComfyUI-GGUF node~/.cache/mmh3-image/models— DiT GGUF, text encoder, VAE- an
extra_model_paths.yamlin that checkout pointing at the cache
Need git and Python 3.9+. Weights are 20–28 GB and the model needs roughly
24 GB of RAM or VRAM; Apple silicon uses MPS, NVIDIA uses CUDA.
Usage
# recommended quantization, native-quality 2048px
mmh3-image "prompt" -q q4 -r 2048
# smallest weights, 16:9 at 1080p, fixed seed
mmh3-image "prompt" -q q2 -r 1080p --seed 42 -o shot.png
# 4K still (slow: about 12 min on an M5 Pro)
mmh3-image "prompt" -r 4k -s 6
# prefetch only, no generation
mmh3-image -q q5 --download-only
# reuse an existing ComfyUI checkout or an already running server
mmh3-image "prompt" --comfyui ~/projects/ComfyUI
mmh3-image "prompt" --server-url http://127.0.0.1:8188
-r takes a preset (720p, 1080p, 1440p, 4k, square), a single number
for a square, or WIDTHxHEIGHT. Values snap to 32 pixels, which is why 1080p
is 1920x1088 — 1080 is not a multiple of 32 and would otherwise be floored.
Defaults matter for this model: 6 steps, euler / simple, CFG 1.0.
It is a distilled 6-step model; more steps or a higher CFG degrade the result.
Quantizations
-q |
File | Size | Notes |
|---|---|---|---|
q2 |
Q2_K | 6.9 GB | smallest, but unusable on this model — output melts into smears |
q3 |
Q3_K_M | 8.9 GB | 12 GB VRAM |
q4s |
Q4_K_S | 11.6 GB | fast 4-bit |
q4 |
Q4_K_M | 11.6 GB | recommended sweet spot (default) |
q5 |
Q5_K_M | 14.1 GB | closest to BF16 |
Text encoder: --text-encoder q3 (12 GB, default) or q4 (14.6 GB).
List everything
mmh3-image --list
Notes
- Weights come from
Abiray/MiniMax-H3-Image-GGUFandComfy-Org/MiniMax-H3-Image. The model itself is under the MiniMax-H3-Image Community License; this CLI is MIT and ships code only. --hf-endpoint https://hf-mirror.comswitches the download mirror.- The CLI leaves the server running only with
--keep-server;--serveskips generation and just serves. - The package does not enable the optional Qwen3.5-9B prompt-expansion branch; the prompt is used verbatim, which is what the model card examples assume.
Metadata
Release files for mmh3-image 0.1.1
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| mmh3_image-0.1.1.tar.gz | 12.3 kB | Without provenance | Details for mmh3_image-0.1.1.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| mmh3_image-0.1.1-py3-none-any.whl | Python 3 | none | any | Details for mmh3_image-0.1.1-py3-none-any.whl |
Total release size: 25.2 kB
Release files / mmh3_image-0.1.1.tar.gz
| Download URL | mmh3_image-0.1.1.tar.gz |
|---|---|
| Size | 12.3 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
8a2335241901a4c2fb89df8f62cb99801e00f2f6bdee3369fe0aa1dda9ccfb0d
|
|
BLAKE2b-256 checksum How to use checksums |
9d7a41a240505516f5317385efb27c03835e169ecef9e7bbe8b2283f7af5b00d
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Release files / mmh3_image-0.1.1-py3-none-any.whl
| Download URL | mmh3_image-0.1.1-py3-none-any.whl |
|---|---|
| Size | 12.9 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
76b4868a27299413b987797faecd33c3330395d66a394baca609d01b49a4cc71
|
|
BLAKE2b-256 checksum How to use checksums |
91d24b2fb60397f7d2f4d27080025415cef0766dd485ea5d70e6fe4bc1ca0902
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Security for mmh3-image 0.1.1
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.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.