Skip to content
PocketWebToolsPocketWebTools
PocketWebTools for Mac

Can you run Muse Spark Open on a Mac?

Only on big Mac Studios: the 4‑bit build Meta and Apple use is a 533 GB download (about 545 GB with context and runtime, our estimate), more than the 478 GB the GPU can use even on a 512 GB Mac, so Apple split it across two M5 Ultra Mac Studios at 16 to 25 tokens per second and four at 37 (measured).

One 512 GB Mac runs a 2‑bit build at 18 tokens per second (measured on an M3 Ultra), a 256 GB Mac fits at best a 2‑bit build nobody has timed, and every other Mac should run Meta's Muse Glimmer 30B instead: Meta measured its 17 GB file at about 25.9 GB, which takes a 32 GB Mac with room to spare from 36 GB, while a 24 GB Mac can run it text only and a 16 GB Mac a 2‑bit build (our estimate).

Updated

Muse Spark Open on one Mac

Meta's 4‑bit build, the 2‑bit and 3‑bit builds Hugging Face timed, and the smallest builds, against what macOS lets the GPU use. Context is 8,192 tokens.

Muse Spark Open on one Mac
ModelMachineNeeds / GPU can useReply speedVerdict
Muse Spark Open 816B‑A42BNVFP4, 8,192 tokens512 GB M5 Ultra (not on sale yet)544.6 GB of 478.3 GBDoes not fitWon't fit
Muse Spark Open 816B‑A42BQ2_K, 8,192 tokens512 GB M3 Ultra311.1 GB of 478.3 GB18 tok/s1Measured at short contextRuns well
Muse Spark Open 816B‑A42BoQ3e, 8,192 tokens512 GB M3 Ultra379.9 GB of 478.3 GB21 tok/s2Measured at short contextRuns well
Muse Spark Open 816B‑A42BQ2_K, 8,192 tokens512 GB M5 Ultra (not on sale yet)311.1 GB of 478.3 GBNot measuredTight
Muse Spark Open 816B‑A42BUD-IQ2_XXS, 8,192 tokens256 GB M5 Ultra231.0 GB of 239.1 GBNot measuredTight
Muse Spark Open 816B‑A42BUD-IQ1_S, 8,192 tokens128 GB M5 Max (40-core GPU)180.0 GB of 115.4 GBDoes not fitWon't fit

No single-Mac speed is estimated for a model this size: rows show a measured speed or "Not measured". A Mac with no published speed is graded Tight at best, even when the build fits easily, which is why Q2_K on the 512 GB M5 Ultra ranks below the same build on the older M3 Ultra. The 512 GB limit is assumed, since no log confirms it yet. Reply speed is in tokens per second at short context. Measured figures come from the published runs listed below; estimates come from memory bandwidth, as explained under How we estimate.

  1. 1. Measured: 18 tok/s, Muse Spark Open 816B‑A42B Q2_K on Mac Studio, M3 Ultra, 512 GB. huggingface.co. Hugging Face, a launch partner: llama.cpp, imatrix 2‑bit build, 304 GB used by the model.
  2. 2. Measured: 21 tok/s, Muse Spark Open 816B‑A42B oQ3e on Mac Studio, M3 Ultra, 512 GB. huggingface.co. Hugging Face, a launch partner: oMLX, 1,024-token prompt, 128 generated tokens, about 225 tok/s prompt reading.

Not this machine?

The checker opens set to 32 GB M6. Change it to your own machine to see what fits and how fast it should reply.

Check your Mac

What Meta released on October 15

On October 15, 2026, Meta released Muse Spark Open, an open-weight mixture-of-experts model with 816B parameters, of which about 42B work on each token. It has 62 layers and a 1,048,576-token context window, and it is natively multimodal.

It is not the Muse Spark you chat with on meta.ai, which stays closed. The open model "shares the same base model as Muse Spark 1.3" (PyTorch).

  • Licence: the Muse Model License. Open weights, not open source. Products built on it must show "Built with Muse Spark Open". Offering it to others as a model service needs a separate agreement with Meta once your company's revenue passes $20M a year. Gated download. Meta approves each download request by hand on Hugging Face.
  • Meta's own builds: BF16 (1,644.3 GB) and NVFP4 (533.0 GB). The MLX builds come from mlx-community; the GGUF builds for llama.cpp come from ggml-org and unsloth.
  • Ollama lists Muse Spark Open only as a cloud model, run on Ollama's servers and billed per use, not as a local download.

Mark Zuckerberg posted on launch day: "Muse Spark Open -- weights releasing today -- runs great on new Mac Studios thanks to work with @johnternus and Apple." John Ternus, Apple's CEO (Apple leadership), replied the same day. Apple's side of the launch is a research post that measures the model on M5 Ultra Mac Studios.

How much memory each build needs

The limit is what macOS lets the GPU use, not the RAM on the box: about 239.1 GB on a 256 GB Mac and 478.3 GB on a 512 GB Mac by default (macOS 26 and later). The 256 GB figure rests on weak evidence and the 512 GB one is assumed, since no log confirms it yet.

Muse Spark Open builds against one Mac
BuildDownloadNeeds at 8,192 tokensFits a 256 GB MacFits a 512 GB Mac
BF16 (Meta)1,644.3 GB1,678.1 GBNo, 1,439.0 GB shortNo, 1,199.8 GB short
Q8_0 (ggml-org)871.6 GB890.0 GBNo, 650.8 GB shortNo, 411.7 GB short
NVFP4 (Meta)533.0 GB544.6 GBNo, 305.4 GB shortNo, 66.3 GB short
MLX 4‑bit (mlx-community)532.8 GB544.4 GBNo, 305.2 GB shortNo, 66.1 GB short
UD-Q4_K_XL (unsloth)505.5 GB516.5 GBNo, 277.4 GB shortNo, 38.2 GB short
Q4_K_S (ggml-org)470.1 GB480.4 GBNo, 241.3 GB shortNo, 2.1 GB short
MLX 3‑bit (mlx-community)436.1 GB445.7 GBNo, 206.6 GB shortYes, at 93% of the limit
oQ3e (mlx-community)371.5 GB379.9 GBNo, 140.7 GB shortYes
Q2_K (ggml-org)304.1 GB311.1 GBNo, 72.0 GB shortYes
UD-IQ2_XXS (unsloth)225.6 GB231.0 GBYes, at 97% of the limitYes
UD-IQ1_M (unsloth)208.9 GB214.0 GBYesYes
UD-IQ1_S (unsloth)175.6 GB180.0 GBYesYes

Needs = weights + context memory + runtime, as explained under How we estimate. Other pages quote smaller numbers, such as Apple's "about 493GB" for the 4‑bit footprint, mostly because they count in binary gigabytes; this page uses decimal GB and the real download sizes.

Q4_K_S misses a 512 GB Mac by 2.1 GB

You can try raising the GPU limit with the command below. It may still fail, it resets on restart, and macOS needs memory of its own.

Raise the GPU memory limit
sudo sysctl iogpu.wired_limit_mb=459122

Context memory is small for a model this size. 46 of the 62 layers only look back 2,048 tokens, so only 16 layers keep the whole conversation, 65,536 bytes per token at 16‑bit. That comes to 0.9 GB at 8,192 tokens, 4.7 GB at 65,536 and 69.1 GB at the full 1,048,576. mlx-lm caps the windowed layers this way; estimates of hundreds of GB at full context ignore the window.

Measured speeds

The 4‑bit build does not fit one Mac, so its only speeds are Apple's, with the model split across M5 Ultra Mac Studios: 16 to 25 tokens per second on two Macs and 37 on four, at 8,192 tokens of context.

Muse Spark Open NVFP4 across linked Mac Studios (Apple, measured)
Setup8,192 tokens65,536 tokens
2 Mac Studios, M5 Ultra, pipeline parallel15.74 tok/s14.37 tok/s
2 Mac Studios, M5 Ultra, tensor parallel24.99 tok/s23.84 tok/s
4 Mac Studios, M5 Ultra, tensor parallel36.73 tok/s34.66 tok/s

Apple, MLX, one request, 128 generated tokens (Apple Machine Learning Research, October 15, 2026). Apple linked each pair of Macs with two Thunderbolt cables and does not state each Mac's memory; Meta's setups are two 512 GB or four 256 GB Macs. Cabling and pipeline vs tensor parallel: Mac Studio cluster guide.

On a single Mac, the only published speeds come from Hugging Face, a launch partner, on a 512 GB M3 Ultra: 18 tokens per second with ggml-org's 2‑bit Q2_K build in llama.cpp (304 GB used by the model), and 21 with the 3‑bit oQ3e build in oMLX, both at short context. We found no independent repeat of Apple's or Hugging Face's numbers.

We do not estimate Muse speeds. Our memory-bandwidth formula predicts 25 tokens per second for the 2‑bit run Hugging Face measured at 18, about 40% too fast, so for mixtures of experts above 120B parameters this page shows measured speeds or "Not measured".

One 512 GB or 256 GB Mac

The 512 GB M5 Ultra is not on sale yet

Apple: 512GB memory option for M5 Ultra coming late October. The price is not published, and it needs the M5 Ultra, 36-core CPU, 80-core GPU chip (Mac Studio). Apple no longer sells the M3 Ultra Mac Studio, the 512 GB Mac Hugging Face tested.

On one 512 GB Mac, every build from Q2_K (311.1 GB) to MLX 3‑bit (445.7 GB) fits under the 478.3 GB default. Speeds exist only for the M3 Ultra (18 and 21 tokens per second, above); no single M5 Ultra figure has been published.

On one 256 GB Mac (any M5 Ultra, on sale today), only UD-IQ2_XXS (231.0 GB, 97% of the 239.1 GB default) and the two 1‑bit builds fit, with the macOS 26 and later default; a 256 GB M3 Ultra still on macOS 15 or earlier gives the GPU only 206.2 GB, and the 2‑bit build no longer fits. Hugging Face notes that "even the 3‑bit quantization requires more than 256 GB of RAM". Nobody has published a speed or quality figure for these builds.

Commands for one 512 GB Mac, from Hugging Face's launch post. llama.cpp with ggml-org's 2‑bit build (a 304.1 GB download):

Install llama.cpp
curl -LsSf https://llama.app/install.sh | sh
Serve the 2-bit build
llama serve -hf ggml-org/Muse-Spark-Open-816B-A42B-GGUF:Q2_K

Or mlx-lm with the 3‑bit oQ3e build (371.5 GB). On one Mac, mlx_lm.generate is fine. Hugging Face's 21 tokens per second for this build was measured with oMLX, not mlx-lm.

Run the 3-bit build
mlx_lm.generate --model mlx-community/Muse-Spark-Open-816B-A42B-oQ3e --prompt "Explain convolutional networks like I am 5" --max-tokens 5000

Choosing between the Mac Studios: which Mac Studio to buy for AI.

What your Mac can run: Muse Glimmer 30B

Muse Glimmer 30B is Meta's smaller open model, released in August 2026 under Apache 2.0 with no download gate. It is dense, not a mixture of experts: all 29.78B parameters (1.8B of them a vision encoder that ships as a separate file) work on every token. It has 52 layers, 39 of them windowed, a 131,072-token context, and reads text and images.

Muse Glimmer 30B on 16 to 48 GB Macs

Meta's 17 GB file (KQuant-17GB-Q4_K_M), unsloth's smaller 4‑bit and 2‑bit files, at 8,192 tokens.

Muse Glimmer 30B on 16 to 48 GB Macs
ModelMachineNeeds / GPU can useReply speedVerdict
Muse Glimmer 30BUD-IQ2_XXS, 8,192 tokens16 GB M511.6 GB of 12.7 GB11 to 12 tok/sEstimateTight
Muse Glimmer 30BKQuant-17GB-Q4_K_M, 8,192 tokens24 GB M525.8 GB of 19.1 GBDoes not fitWon't fit
Muse Glimmer 30BUD-Q4_K_XL, 8,192 tokens24 GB M516.8 GB of 19.1 GB7.2 to 8.5 tok/sEstimateRuns well
Muse Glimmer 30BKQuant-17GB-Q4_K_M, 8,192 tokens32 GB M625.8 GB of 26.8 GB7.6 to 8.9 tok/sEstimateTight
Muse Glimmer 30BKQuant-17GB-Q4_K_M, 8,192 tokens48 GB M5 Pro25.8 GB of 40.2 GB13 to 16 tok/sEstimateRuns well
Muse Glimmer 30BKQuant-17GB-Q4_K_M, 8,192 tokens48 GB M5 Max (40-core GPU)25.8 GB of 40.2 GB26 to 31 tok/sEstimateRuns well

Meta's 17 GB file is graded on Meta's own LM Studio measurement, moved to 8,192 tokens, and Meta does not say what that figure includes. The unsloth files use our formula, which counts the text model only; on that basis Meta's file needs about 17.7 GB, so the 24 GB rows differ by setup, not by file. Reply speed is in tokens per second at short context. Measured figures come from published runs; estimates come from memory bandwidth, as explained under How we estimate.

For comparison, not used for the grade

  • 27 tok/s, Muse Glimmer 30B KQuant-17GB-Q4_K_M on M5 Max. huggingface.co. Meta, with ExecuTorch rather than llama.cpp, LM Studio or Ollama; GPU cores not stated. Batch 1, greedy. With the DFlash draft model: 50.2 tok/s.

Meta's deploy guide says its Q4_K_M file "measured about 24.1 GiB at one request and 16K context, so leave room for the OS and Bionic". That is 25.9 GB, 8.1 GB more than our formula gives for the same file and context (17.8 GB), and Meta does not say whether the vision file was loaded. We grade Meta's file on Meta's figure: it does not fit a 24 GB Mac (19.1 GB for the GPU), takes 96% of the 26.8 GB a 32 GB Mac allows, and leaves room on 36 GB (30.2 GB). SGLang's team, in the same guide, verified Muse Glimmer on an M5 Pro with 64 GB and lists 48 GB as the minimum for its MLX builds; the 32 GB figure here rests on Meta's LM Studio measurement, not on a verified setup.

  • 24 GB: run text only in llama.cpp, with --no-mmproj (which skips the vision file) and a short context. By our formula, not measured, Meta's 17 GB file then needs about 17.7 GB, 93% of the 19.1 GB the GPU can use, and unsloth's UD-Q4_K_XL file (15.9 GB) about 16.8 GB (88%), a little more headroom. Meta's file with its vision file and DFlash draft model is 19.8 GB of files, more than a 24 GB Mac gives the GPU.
  • Meta says its 17 GB quantization targets 24 GB of VRAM. That means a graphics card with 24 GB to itself; a 24 GB Mac shares its memory with macOS and lets the GPU use 19.1 GB.
  • 16 GB: only the 2‑bit build fits (11.6 GB of the 12.7 GB the GPU can use), and nobody has published how much quality it loses.
  • Speed: a dense 30B model is slow on base chips. Our estimate for Meta's file is 7.6 to 8.9 tokens per second on a 32 GB M6 and 26 to 31 on a 48 GB M5 Max with the 40-core GPU. Meta measured 23.7 on an M4 Max and 26.6 on an M5 Max, faster still with its DFlash draft model, but with ExecuTorch rather than llama.cpp, LM Studio or Ollama, and without naming the GPU.

To run it with Ollama 0.32.7 or later, use Ollama's MLX build for Apple silicon (4‑bit NVFP4 with the DFlash draft model, a 19 GB download), or the standard 18 GB build. Both include the vision model, so on a 24 GB Mac use llama.cpp text only, below. Ollama serves an API at http://localhost:11434.

Ollama, MLX build
ollama run muse-glimmer:30b-mlx
Ollama, standard build
ollama run muse-glimmer:30b

In LM Studio, download Muse Glimmer from the model search, then start the local server on port 1234:

LM Studio server
lms server start

llama.cpp needs build b10353 or newer. Meta's command uses a 131,072-token context; keep it shorter on 32 GB, where Meta's figure at full context would not fit.

llama.cpp, Meta's 17 GB file
llama serve -hf meta-models/Muse-Glimmer-30B-GGUF --hf-file Muse-Glimmer-30B-KQuant-17GB-Q4_K_M.gguf -ngl 99 -c 32768
llama.cpp on a 24 GB Mac, text only
llama serve -hf unsloth/Muse-Glimmer-30B-GGUF:UD-Q4_K_XL --no-mmproj -ngl 99 -c 8192

How to run Muse Spark Open on two or four Mac Studios

This is the setup from Meta's Mac cookbook, with the RDMA steps from the MLX docs and Apple's technote, and one fix to the last step.

  1. Get the Macs: Two M5 Ultra Mac Studios with 512 GB each (not on sale until Apple ships the option) or four with 256 GB each, two Thunderbolt 5 cables between every pair of Macs (Apple's measured setup; one cable works but is slower), and room for the 533.0 GB download on each Mac.
  2. Update macOS: Install macOS 26.2 or later on every Mac. RDMA over Thunderbolt, the fast link MLX uses, starts there.
  3. Turn on RDMA: On each Mac, start up in macOS Recovery, choose Utilities, Terminal, run rdma_ctl enable and restart. Check it with ibv_devices. This cannot be done remotely.
  4. Turn off the Thunderbolt bridge: In System Settings, Network, make Thunderbolt Bridge inactive on every Mac, as Apple advises for Macs cabled in loops.
  5. Set up SSH: From the first Mac, set up passwordless SSH to every other Mac with ssh-keygen and ssh-copy-id.
  6. Request the weights: Ask for access to Meta's NVFP4 repo on Hugging Face (Meta approves each request by hand), then log in with your Hugging Face access token on every Mac.
  7. Install mlx-lm: Install mlx-lm 0.32.2 or later on every Mac. It is the first release that loads the public checkpoint, and it brings MLX 0.32.2 or later with it.
  8. Write the host file: On the first Mac, run mlx.distributed_config over Thunderbolt with the jaccl backend to write hostfile.json.
  9. Start the model: Run mlx.launch with mlx_lm.server for an OpenAI-compatible API on port 8080, or with mlx_lm.chat to chat in Terminal. Never with mlx_lm.generate.
Step 3, in macOS Recovery on each Mac
rdma_ctl enable
Step 3, check after restarting
ibv_devices
Step 5, repeat ssh-copy-id for each Mac
ssh-keygen -t ed25519
ssh-copy-id mac-studio-2.local
ssh mac-studio-2.local 'echo ok'
Step 7, on every Mac
pip install -U "mlx-lm>=0.32.2"
Step 8, list all your Macs; --auto-setup needs passwordless sudo
mlx.distributed_config --verbose --hosts mac-studio-1,mac-studio-2 --over thunderbolt --backend jaccl --auto-setup --output hostfile.json
Step 9, serve an API on port 8080
mlx.launch --hostfile hostfile.json --backend jaccl -- mlx_lm.server --model meta-models/Muse-Spark-Open-816B-A42B-NVFP4 --port 8080
Step 9, or chat in Terminal
mlx.launch --hostfile hostfile.json --backend jaccl -- mlx_lm.chat --model meta-models/Muse-Spark-Open-816B-A42B-NVFP4

Do not use mlx_lm.generate across Macs

Meta's cookbook tests the cluster with mlx_lm.generate under mlx.launch. In mlx-lm 0.32.2 that command has no code for splitting a model, so each Mac would try to load all 533.0 GB. mlx_lm.chat and mlx_lm.server do split it. We read the mlx-lm source; we did not run it on a cluster.

MLX_METAL_FAST_SYNCH is left out on purpose

Meta and Apple add --env MLX_METAL_FAST_SYNCH=1 to mlx.launch for faster syncing. The MLX docs say it "is however not reliable that can lead to deadlock and leave the GPU wedged", and it is off by default. Add it only if you accept that risk.

The model reasons at its highest level by default, so leave plenty of room for output tokens, as Meta's cookbook advises.

Can PocketWebTools for Mac run Muse?

No. PocketWebTools for Mac runs 6 fixed chat models on llama.cpp, the largest Qwen3.6 35B‑A3B (a 22.4 GB download). It cannot load your own model files, run MLX or link Macs, and it does not ship Muse Spark Open or Muse Glimmer. Use the free tools above for those.

What it does instead: private chat with its own models (Qwen3.6 35B‑A3B measured at 25 to 27 tokens per second on a 32 GB Mac mini M4), transcription with speaker labels, text to speech and voice cloning, OCR and photo upscaling, all offline. See what the app does.

What we recommend

If you have two 512 GB or four 256 GB M5 Ultra Mac Studios, run Meta's 4‑bit build with mlx-lm 0.32.2 or later and expect Apple's measured 16 to 25 tokens per second on two Macs and 37 on four. One 512 GB Mac runs the 2‑bit build at about the 18 tokens per second Hugging Face measured; a 256 GB Mac is an untimed squeeze.

On any other Mac, run Muse Glimmer 30B with Ollama, LM Studio or llama.cpp: 32 GB at the least by Meta's LM Studio figure, 36 GB or more for room to spare, and 48 GB for the setup SGLang verified. A 24 GB Mac can run it text only in llama.cpp with --no-mmproj (our estimate).

MLX LM

Runs Muse Spark Open split across two or four Mac Studios (mlx_lm.server or mlx_lm.chat, version 0.32.2 or later), and the 3‑bit build on one 512 GB Mac.

Free and open source (MIT licence), from Apple. Made by another developer, not PocketWebTools.

Get MLX LM

Ollama

The simplest way to run Muse Glimmer 30B on your Mac: one command, with an MLX build for Apple silicon. Its Muse Spark Open model is cloud only.

Free and open source (MIT licence). Made by another developer, not PocketWebTools.

Get Ollama

LM Studio

Runs Muse Glimmer 30B in a desktop app with a local server; Meta measured its memory use here.

Free download, closed source. Its terms allow some features to cost extra. Made by another developer, not PocketWebTools.

Get LM Studio

llama.cpp

Runs the 2‑bit Muse Spark Open build on one 512 GB Mac, and the smaller Muse Glimmer files on 16 and 24 GB Macs.

Free and open source (MIT licence). Made by another developer, not PocketWebTools.

Get llama.cpp
Can I Run AICheck what your own Mac can run, with Muse Glimmer 30B preselected.Open Can I Run AI

PocketWebTools for Mac

Runs 6 open chat models, up to Qwen3.6 35B‑A3B (a 22.4 GB download), plus transcription with speaker labels, text to speech and voice cloning, OCR, photo upscaling and cutouts, all offline on Apple Silicon. It does not generate images, read images in chat, load your own model files, run MLX, link several Macs or serve a local API for coding tools.

It does not run Muse Spark Open or Muse Glimmer. For everyday private chat it runs Qwen3.6 35B‑A3B, measured at 25 to 27 tokens per second on a 32 GB Mac mini M4.

Version 1.0.0. Needs Apple Silicon (M1 or later), macOS 14 Sonoma or later.

Buy for $99$49

Already have a key? Download the app. It asks for the key the first time it opens.

14-day money-back guarantee. Your license key is shown right after checkout and stays on your purchase page; one key works on up to 3 Macs.

See everything the app does

How we estimate

Show the formulas, constants and sources

Memory a model needs

Memory = weights + context memory + runtime. Weights are the real download size of the file you pick, read from Hugging Face. When a size is unknown we use parameters x bits per weight / 8, with typical averages per quant type (Q2_K 2.96, Q3_K_M 3.91, Q4_K_M 4.8, UD-Q4_K_XL 4.9, MXFP4 4.25, NVFP4 4.5, Q5_K_M 5.7, Q6_K 6.56, Q8_0 8.5, BF16 16). Runtime is 0.7 GB, or 2% of the weights when that is more, for compute buffers and allocator slack: measured buffers stay near that size whatever the model. Against our own Mac app's measured memory for six models, and Apple's published totals for two models at 65,536 tokens, this lands within 15%. Where someone measured the memory of the exact file, we use that run instead and say so. Checked 2026-10-19.

Context memory (KV cache)

Each token of context stores keys and values: 2 x layers x KV heads x head size x 2 bytes (16‑bit cache, the default in llama.cpp and MLX), read from each model's config.json. Sliding-window layers keep at most their window (2,048 tokens on Muse Spark Open, for example), so they add a fixed amount instead of growing. MLX is confirmed to cap them on Muse Spark Open; whether llama.cpp does for that model is not verified, so its GGUF figures may run low at long context. Models with compressed attention (MLA) store one small latent per layer. Linear-attention layers keep a small fixed state, counted in the runtime share. In llama.cpp you can store the cache at lower precision with --cache-type-k and --cache-type-v (-ctk and -ctv): per element that is q8_0 1.0625 bytes, q4_0 0.5625 bytes, from the size of each type's data blocks. A lower-precision V cache needs flash attention, which llama.cpp turns on by itself unless you switch it off. Measured runs are taken to use the 16‑bit default. Checked 2026-10-19.

How much memory a Mac's GPU can use

macOS only lets the GPU use part of a Mac's memory. Apple publishes no formula, so we read the default from public llama.cpp, Ollama and MLX logs where one exists. On macOS 26 and later: 8 GB: 2/3, about 5.7 GB (medium evidence); 16 GB: 0.74, about 12.7 GB (strong evidence); 18 GB: 0.74, about 14.3 GB (medium evidence); 24 GB: 0.74, about 19.1 GB (strong evidence); 32 GB: 0.78, about 26.8 GB (strong evidence); 36 GB: 0.78, about 30.2 GB (medium evidence); 48 GB: 0.78, about 40.2 GB (strong evidence); 64 GB: 0.81, about 55.7 GB (strong evidence); 96 GB: 0.81, about 83.5 GB (weak evidence); 128 GB: 0.84, about 115.4 GB (strong evidence); 192 GB: 0.84, about 173.2 GB (weak evidence); 256 GB: 0.87, about 239.1 GB (weak evidence); 512 GB: 0.87 (assumed), about 478.3 GB (unconfirmed evidence). Why the weaker rows are weaker: 96 GB: One log, from 2026-09-30. 192 GB: One M2 Ultra log, from 2025-10-30. 256 GB: Two M3 Ultra logs, possibly from the same person. 512 GB: No confirmed default. Logs show 464 GiB (about 0.906), but the same value appears on a macOS 15 Mac, so it is probably a manual override. We use 0.87, the 256 GB ratio, which may understate a 512 GB Mac by about 20 GB. On macOS 15 or earlier it was 2/3 up to 32 GB and 3/4 above. The limit can be raised with sudo sysctl iogpu.wired_limit_mb=<MiB>; it resets on restart and macOS needs memory of its own, so leave headroom. The setting cannot go past a second limit, the kernel's cap on all locked memory, which Apple's open-source macOS kernel sets by memory size (16 GB: 13.1 GB; 32 GB: 27.1 GB; 64 GB: 56.3 GB; 128 GB: 116.8 GB; 256 GB: 241.9 GB; 512 GB: 515.4 GB) and two measured Macs match exactly. That cap sits a little above the default at every size, so the default is what a model gets, and we suggest the setting only when a model fits under the cap. It may still fail. Checked 2026-10-19.

Several Macs linked together

For a group of Macs with the same memory, we add up what each one's GPU can use: two 256 GB Macs on macOS 26 and later come to about 478.3 GB. Assumes the model splits evenly across Macs of the same memory size (as exo and MLX distributed do) and that linking them costs no memory on any one Mac. Neither is measured. We give no estimated speed for a group; only published runs, each with its number of Macs. Checked 2026-10-19.

How much memory a PC can use

On a graphics card we take its video memory minus 0.5 GB for the display. Runtimes like llama.cpp, LM Studio and Ollama can put layers that do not fit into system memory; we allow up to 60% of it, and any model that needs it is graded Tight. Both numbers are our assumptions, not measurements. AMD documents up to 96 GB of GPU memory on a 128 GB Ryzen AI Max machine; on smaller ones we assume the same 75% share. NVIDIA publishes no GPU limit for DGX Spark, so we assume 84% of its memory, the share macOS gives a 128 GB Mac. Checked 2026-10-19.

Reply speed

Writing each token reads the model's active weights once, so speed follows memory bandwidth: seconds per token = active GB / (bandwidth x 0.85) + a fixed cost per token of 2 ms on Apple for standard models, 5 ms for hybrid linear-attention models (Qwen3.5 and 3.8), 6 ms for mixture of experts; 1.3 ms on NVIDIA and DGX Spark for standard models and 2 ms for mixture of experts. Active GB comes from the file's tensor table where we computed it, else from a similar file of the same model whose table we read, scaled by file size, else from the active parameters at the file's own bits per weight. When a PC spills into system memory, that part reads at 60 GB/s x 0.6 (assumed dual-channel DDR5). Fitted to 53 published llama.cpp and MLX runs, it had a median error of 6% and every point within 20%; that fit is in-sample. AMD and Intel cards borrow the NVIDIA values and are marked rough. Speeds are at short context; long chats run slower. Checked 2026-10-19.

Why speeds are a range

The top of the range is the formula above. The bottom is 65% of it on M1 and M2 chips, where our own Mac app ran about a third under the formula on two mid-size models, and 85% everywhere else. The M1 and M2 rule rests on those two points only. Checked 2026-10-19.

When we do not estimate speed

We show no estimated speed for weights under 2 bits each, which are limited by computation rather than bandwidth (a 1‑bit 27B model ran at about a quarter of the bandwidth limit), or for mixture-of-experts models above 120B total parameters, where the formula ran 40% fast on Muse Spark Open against a measured 18 tokens per second. Those rows show measured speeds where someone published them, and "not measured" otherwise, and a model with no speed figure is graded Tight at best. Checked 2026-10-19.

Measured beats estimated

When someone published a speed for the same model, quant and chip, we show that number, labelled measured, with its source and caveats, instead of the formula. A run on another runtime (Meta's ExecuTorch numbers for a GGUF, for example) or one that does not say which GPU-core version of a chip it used is shown for comparison only. Our own measurements come from PocketWebTools for Mac on a 16 GB M1 Pro and a 32 GB Mac mini M4. A speed measured at a context more than 4 times shorter than the one you picked (or at an unstated one, which usually means a short test) is labelled measured at short context, since long chats run slower. Measurements of several Macs linked together never stand in for one Mac, and each is shown with its number of Macs. Model data checked 2026-10-19.

Grades

Won't fit: the model needs more than the GPU can use (plus the allowed system memory on a PC). Tight: it fits but needs more than 90% of that memory, spills into system memory, replies under 8 tokens per second, or has no speed figure for that machine. Runs well: everything else. Every grade states the quant, the context length (8,192 tokens unless you change it) and the memory figure it assumed. Speech, voice and image models are graded on memory only. Checked 2026-10-19.

Time to the first word

Reading your prompt is limited by computation, not bandwidth. We scale each chip's published llama.cpp prompt speed on a 7B model by 6.6B / the model's active parameters, x 0.75 for mixture of experts. It matched measured runs within 8% for standard models. Checked 2026-10-19.

Questions

Can I run Muse Spark locally?
The open version, Muse Spark Open, yes, but only on very large Macs or GPU servers: its 4‑bit build is a 533 GB download (about 545 GB in use, our estimate), so two 512 GB or four 256 GB Mac Studios. One 512 GB Mac runs a 2‑bit build at 18 tokens per second (measured on an M3 Ultra). The closed Muse Spark models on meta.ai have no downloadable weights.
Is Muse Spark an open model?
Muse Spark Open is open-weight under Meta's own Muse Model License, not open source. The weights are free to download once Meta approves your request, products built on it must show "Built with Muse Spark Open", and large companies offering it as a model service need a separate agreement. The Muse Spark models on meta.ai are closed.
What is the parameter size of Muse Spark?
Muse Spark Open has 816B parameters, about 42B of them active per token. Meta has not published the size of the closed Muse Spark models.
Can I run Muse Glimmer?
On a Mac with 32 GB or more, yes: Meta measured its 17 GB build at about 25.9 GB in LM Studio, against 26.8 GB the GPU can use on a 32 GB Mac (SGLang's verified Mac setup starts at 48 GB). A 24 GB Mac (19.1 GB) can run it text only in llama.cpp, about 17.7 GB for Meta's file or 16.8 GB for unsloth's UD-Q4_K_XL by our estimate, and a 16 GB Mac fits only the 2‑bit build.
Is Muse Glimmer a mixture of experts (MoE)?
No. Muse Glimmer 30B is a dense model: all of its roughly 30B parameters work on every token. That makes it slower than a mixture of experts of similar size: on a 32 GB M6 we estimate 7.6 to 8.9 tokens per second for Muse Glimmer against 34 to 40 for Qwen3.6 35B‑A3B.
Is Muse Spark completely free?
The Muse Spark Open weights cost nothing to download and use under the licence; you pay for the hardware, or per use if you run a hosted version such as Ollama's cloud model.

Where to go next

Sources

Changelog

  • : Published: what each Muse Spark Open build needs on 256 and 512 GB Macs, the speeds Apple and Hugging Face measured, a corrected multi-Mac setup, and what Muse Glimmer 30B needs on 16 to 48 GB Macs.