on

Can the Intel Core Ultra X7 358H NAS (64 GB) run MiniMax H3 Image?

93Excellent quality (A+) · 93 of 100: how capable the model is at FP16, whatever it runs on. Match score 74/100 (quality, fit, speed and memory use) sets the ranking.

Yes, but slowly (CPU offload)

Slow (CPU offload). At FP16 it needs about 27.5 GB of 36.5 GB usable and takes about 73 s per image.

Best precision
FP16
Memory mode
Sequential CPU offload
Time per image
73 s
Output
2048×2048, 6 steps

Download MiniMax H3 Image

Original weights · Hugging Face

Full-precision files from MiniMax, for fine-tuning, vLLM, Transformers, Diffusers or ComfyUI.

huggingface.co/MiniMaxAI/MiniMax-H3-Image (opens in a new tab)

No sign-in needed.

Official repo · GitHub

Reference code, inference scripts and docs from MiniMax. The weights themselves download from Hugging Face.

github.com/MiniMax-AI/MiniMax-H3-Image (opens in a new tab)

git clone https://github.com/MiniMax-AI/MiniMax-H3-Image

How it’s rated

Quality 93Excellent quality (A+) · 93 of 100: how capable the model is at FP16, whatever it runs on. Match score 74/100 (quality, fit, speed and memory use) sets the ranking.
How capable the model itself is at FP16, from its editorial quality tier scaled by the quantization or precision. It’s the same on any hardware that runs this variant. Scale: A+ 85+ · A 70+ · B 55+ · C 40+ · D under 40.
Runs SlowCPU offload
How well it runs on the Intel Core Ultra X7 358H NAS (64 GB): speed, capped by how well it fits in memory. Runs great: 30+ tokens/s (or near the image, video or decision speed target) · Runs well: 10+ tokens/s · Slow: 3+ tokens/s · Very slow: under 3 · Won’t run: doesn’t fit even with offload. A tight fit or RAM offload caps it at Runs well; heavy offload caps it at Slow.

Match score

To order lists, each result also gets a match score out of 100 from four parts. It favors the most capable model that still runs well.

Model qualityEditorial quality tier of the model, scaled by the quantization or precision used.41.9 / 45
Memory fitFull marks when the model fits in the share of the NAS’s memory that models can use (the rest stays with the NAS system and its storage services); fewer when it goes past that limit.12.0 / 25
SpeedGeneration speed against a 40 tokens/s target for LLMs, or render time against a target for image and video.5.5 / 15
Memory useRewards using the memory you have, so a bigger, better variant beats a tiny one that leaves most memory idle.15.0 / 15
Match score74.4 / 100

The match score orders results; it is not shown as a grade. Quality and Runs are the two ratings in the tables.

Every precision on the Intel Core Ultra X7 358H NAS (64 GB)

Quant Memory needed Available Speed Memory mode Runs Quality Download
FP16 27.5 GB 36.5 GB 73 s Sequential CPU offload SlowCPU offload 93Excellent quality (A+) · 93 of 100: how capable the model is at FP16, whatever it runs on. Match score 74/100 (quality, fit, speed and memory use) sets the ranking. Original weights (opens in a new tab)
FP8 16.0 GB 36.5 GB 66 s Sequential CPU offload SlowCPU offload 91Excellent quality (A+) · 91 of 100: how capable the model is at FP8, whatever it runs on. Match score 68/100 (quality, fit, speed and memory use) sets the ranking. Original weights (opens in a new tab)

Other hardware that runs it

Quick answers

How much memory does MiniMax H3 Image need on the Intel Core Ultra X7 358H NAS 64GB?

At FP16 it needs about 27.5 GB. The Intel Core Ultra X7 358H NAS 64GB has 36.5 GB usable.

How long does MiniMax H3 Image take on the Intel Core Ultra X7 358H NAS 64GB?

About 73 s per image at FP16 and default settings, an estimate scaled from a reference timing by this hardware’s compute speed.

Estimates come from published hardware specs and our open formulas, not from running the model on your machine. Real speed varies with runtime, drivers and settings. Numbers marked “Measured” come from a linked benchmark.

Was this page helpful?