on

Can the Apple M1 Max (64 GB) run RealVisXL V5.0?

60Good quality (B) · 60 of 100: how capable the model is at FP8, whatever it runs on. Match score 62/100 (quality, fit, speed and memory use) sets the ranking.

Yes, it runs well

Runs well. At FP8 it needs about 5.6 GB of 48.0 GB usable and takes about 36 s per image.

Best precision
FP8
Memory mode
Everything on GPU
Time per image
36 s
Output
1024×1024, 30 steps

Best app to run it on the Apple M1 Max (64 GB)

On macOS

Draw Things

Desktop app · runs on Draw Things (Metal FlashAttention)

  • Native Mac app with its own fast Metal engine and quantized downloads.

Open RealVisXL V5.0 in Draw Things

  • ComfyUI Runs this model with built-in or popular custom nodes; GGUF files load with ComfyUI-GGUF.
  • Invoke

How we choose: the files published for this model, your operating system and GPU, whether it fits fully in memory, and published speed tests (MLX vs llama.cpp on Apple silicon, vLLM vs llama.cpp vs Ollama on NVIDIA). Details.

Download RealVisXL V5.0

Original weights · Hugging Face

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

huggingface.co/SG161222/RealVisXL_V5.0 (opens in a new tab)

No sign-in needed.

How it’s rated

Quality 60Good quality (B) · 60 of 100: how capable the model is at FP8, whatever it runs on. Match score 62/100 (quality, fit, speed and memory use) sets the ranking.
How capable the model itself is at FP8, 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 Runs well
How well it runs on the Apple M1 Max (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.27.3 / 45
Memory fitFull marks when the model fits in the share of unified memory the GPU can use; fewer when it goes past that limit.25.0 / 25
SpeedGeneration speed against a 40 tokens/s target for LLMs, or render time against a target for image and video.7.9 / 15
Memory useRewards using the memory you have, so a bigger, better variant beats a tiny one that leaves most memory idle.2.7 / 15
Match score62.9 / 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 Apple M1 Max (64 GB)

Quant Memory needed Available Speed Memory mode Runs Quality Download
FP16 8.9 GB 48.0 GB 40 s Everything on GPU Slow 62Good quality (B) · 62 of 100: how capable the model is at FP16, whatever it runs on. Match score 64/100 (quality, fit, speed and memory use) sets the ranking. Original weights (opens in a new tab)
FP8 5.6 GB 48.0 GB 36 s Everything on GPU Runs well 60Good quality (B) · 60 of 100: how capable the model is at FP8, whatever it runs on. Match score 62/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 RealVisXL V5.0 need on the M1 Max 64GB?

At FP8 it needs about 5.6 GB. The M1 Max 64GB has 48.0 GB usable.

How long does RealVisXL V5.0 take on the M1 Max 64GB?

About 36 s per image at FP8 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?