AtomicChat / Muse-Glimmer-30B-GGUF

huggingface.co
Total runs: 4.6K
24-hour runs: -3.7K
7-day runs: -6.0K
30-day runs: -1.9K
Model's Last Updated: August 12 2026
image-text-to-text

Introduction of Muse-Glimmer-30B-GGUF

Model Details of Muse-Glimmer-30B-GGUF

Muse Glimmer 30B — GGUF

GGUF builds of Meta's Muse Glimmer 30B, made from the original BF16 weights.

This is the first stage: full-precision base, 8-bit builds, and measurements. The full quant ladder with a calibrated imatrix and NVFP4 is in progress.

Support was merged into llama.cpp master in #26841 (commit 62bf73d ). You need a build from master — the last tagged release predates it.

Files
File Size bpw VRAM needed What's inside
Muse-Glimmer-30B-Q8_0.gguf 29.6 GB 8.50 32 GB everything Q8_0
Muse-Glimmer-30B-AD-Q8_0.gguf 32.1 GB 9.23 40 GB Q8_0, token_embd + output in BF16
BF16/ (2 shards) 55.7 GB 16.0 64 GB original weights, reference for all metrics
mmproj-Muse-Glimmer-30B-BF16.gguf 3.9 GB +3.7 GB required for image input
dflash-Muse-Glimmer-30B-BF16.gguf 5.1 GB +5.0 GB drafter, ~1.9x faster generation
experiments/…-Q8_0-embd-bf16.gguf 30.9 GB 8.87 34 GB Q8_0, only token_embd in BF16
experiments/…-Q8_0-out-bf16.gguf 30.9 GB 8.87 34 GB Q8_0, only output in BF16

Q8_0 fits on a single RTX 5090 and runs at 35.7 t/s. Adding the mmproj for image input pushes you to a second card.

The two experiments/ files exist to answer one question — which of the two big tensors is worth keeping in BF16 — and are measured below. For normal use pick Q8_0 or AD-Q8_0 .

Per-tensor composition of every file is in layouts/*.json . Raw logs behind every number on this page: AtomicChat/Muse-Glimmer-30B-GGUF-metrics .

Running it

Build from master (or grab a nightly binary from the llama.cpp releases page once one includes commit 62bf73d ):

git clone https://github.com/ggml-org/llama.cpp && cd llama.cpp
cmake -B build -DCMAKE_BUILD_TYPE=Release -DGGML_CUDA=ON
cmake --build build -j --target llama-server llama-mtmd-cli

--jinja is required. Without it neither the chat template nor tool-call parsing works.

llama-server -m Muse-Glimmer-30B-Q8_0.gguf \
    --mmproj mmproj-Muse-Glimmer-30B-BF16.gguf \
    --jinja -ngl 99 -c 16384 -fa on \
    --temp 1.0 --top-p 0.95 --top-k 64

With speculative decoding:

llama-server -m Muse-Glimmer-30B-Q8_0.gguf \
    -md dflash-Muse-Glimmer-30B-BF16.gguf \
    --spec-type draft-dflash --spec-draft-n-max 15 \
    --mmproj mmproj-Muse-Glimmer-30B-BF16.gguf \
    --jinja -ngl 99 -c 16384 -fa on

Reasoning depth is set by a line in the system prompt, not a flag: Reasoning strength: low|medium|high|xhigh. Default is high .

Speed

Hardware: 4x RTX 5090, 2x EPYC 9654, driver 590.48.01.

Without the drafter llama-bench -p 512,4096 -n 128 -r 3 -ngl 99 -fa 1 :

Build Size GPUs Drafter pp512 pp4096 tg128
BF16 55.7 GB 4 off 2138 5757 20.3 t/s
Q8_0 29.6 GB 4 off 3125 7864 35.5 t/s
Q8_0-embd-bf16 30.9 GB 4 off 3120 7854 35.5 t/s
Q8_0-out-bf16 30.9 GB 4 off 3104 7853 34.2 t/s
AD-Q8_0 32.1 GB 4 off 3103 7846 34.2 t/s
Q8_0 29.6 GB 1 off 3077 3105 35.7 t/s

With the DFlash drafter llama-server , 9-prompt set (code / prose / reasoning), greedy sampling. Generation speed here is measured end to end by the server, so it is not directly comparable to llama-bench tg128 above:

Build Size GPUs Drafter Generation Acceptance Mean accepted
Q8_0 29.6 GB 4 off 35.5 t/s
Q8_0 29.6 GB + 5.1 4 dflash BF16 68.3 t/s 0.211 3.74

Acceptance depends heavily on the task: code prompts reach 0.37, free prose drops to 0.12. Meta reports 3.1x on a single 5090; we see 1.9x, most likely because a 4-GPU layer split makes each target forward pass relatively more expensive against drafter overhead.

Quality

Reference is our own BF16 GGUF, which is bit-identical to the original weights (verified by UUID and all 731 tensor hashes). Measured with llama-perplexity --kl-divergence . Lower KLD is better, higher top-1 is better.

Neutral text — 30 languages, 97 windows of 4096, base PPL 5.4614:

Build Size bpw Mean KLD Top-1 match RMS dp
Q8_0 29.6 GB 8.50 0.000861 98.945 % 0.998 %
Q8_0 + token_embd BF16 * 30.9 GB 8.87 0.000838 98.970 % 0.953 %
Q8_0 + output BF16 * 30.9 GB 8.87 0.000842 98.975 % 0.993 %
AD-Q8_0 (both) 32.1 GB 9.23 0.000819 98.987 % 0.947 %

Agentic dialogues — native chat markup with tool calls, 85 windows of 4096, base PPL 2.4462:

Build Size bpw Mean KLD Top-1 match RMS dp
Q8_0 29.6 GB 8.50 0.019968 98.580 % 4.377 %
Q8_0 + output BF16 * 30.9 GB 8.87 0.019949 98.584 % 4.376 %
Q8_0 + token_embd BF16 * 30.9 GB 8.87 0.018397 98.575 % 4.271 %
AD-Q8_0 (both) 32.1 GB 9.23 0.018382 98.579 % 4.270 %

* these two builds live in experiments/ — they isolate one tensor each and are not meant for general use.

Calibration

imatrix/muse-glimmer.imatrix.gguf is the importance matrix used for the quant ladder. It is published so anyone can rebuild these files, or build their own quants on the same calibration.

How it was collected

An importance matrix records, for every weight matrix in the model, the mean squared activation arriving on each of its input channels. The quantiser uses those numbers to weight reconstruction error when it searches for block scales: error on a channel that usually carries large activations is penalised more than error on a channel that is usually near zero.

Source our BF16 GGUF, bit-identical to the original weights
Corpus 5.64 M tokens over 689 windows
Composition 25% agentic dialogue in native chat markup, 18% code, 15% long chain-of-thought, 12% long-context documents, 12% multilingual, 10% vocabulary sweep, 5% structured, 3% graphics
Context 8192 for short documents, 32768 for the long-context slice, merged
Flags --parse-special so chat control tokens are real tokens, --process-output so output.weight is collected
Coverage all 417 collected tensors woke up more than 99.9% of their input channels

Two flags there are off by default and both matter. Without --parse-special , <|start|> and friends are tokenized as literal punctuation, so 40% of the corpus would have been calibrated on sequences the model never produces. Without --process-output , output.weight — 1.34 B parameters sitting directly under the logit softcap — gets no importance data at all.

Corpus and raw logs: AtomicChat/calib-corpora and AtomicChat/Muse-Glimmer-30B-GGUF-metrics .

What the calibration shows

Muse Glimmer has 52 layers with 8 collected matrices each, plus the output matrix, for 417 importance vectors. They reduce to five distinct profiles per layer : attn_q , attn_k , attn_v and attn_gate all read the output of attn_norm , so their importance vectors are identical to the last digit, and ffn_gate and ffn_up likewise share the output of ffn_pre_norm .

For each vector we measured how much of the total importance sits in its strongest channels.

image

The Y axis lists the five profiles. The X axis is the percentage of a tensor's total importance held by its 10 strongest input channels, and by its strongest 1% of channels, averaged over all 52 layers.

Read against a uniform distribution, the numbers are extreme. Ten channels out of 6656 would hold 0.15% of importance if it were spread evenly; on the attention input they hold 38.8%, a factor of 259. For ffn_down the ten strongest of 19 968 channels hold 19.8% against a uniform 0.05%, a factor of 396. Every group is at least two orders of magnitude away from uniform.

Concentration is not constant with depth.

image

Here the X axis is the layer index, 0 to 51, and the Y axis is the share of ffn_down importance held by its 10 strongest channels out of 19 968. Layers 5 through 11 sit between 1.6% and 3.6%. Layers 41 and 42 reach 59% and 60% — ten channels out of nearly twenty thousand carrying three fifths of everything, some 1200 times a uniform share. Layers 0 and 4 are isolated spikes in an otherwise flat early region.

Why this matters for quantization

K-quants assign one scale to a block of 32 adjacent weights along the input dimension. A single dominant channel inside a block forces that scale upward and costs precision on the other 31 weights. Concentration therefore makes a block harder to quantize, not easier, and it marks where calibration has the most leverage: the gap between a calibrated and an uncalibrated quant should be widest exactly where the top-10 share is highest.

That is a prediction, not a result. The ladder below tests it by holding everything constant except ffn_down in layers 36 through 47.

One further note on attn_gate . Gated attention is new to this architecture and adds a 6656 x 4096 matrix per layer, roughly a third of the attention parameters. No published quantization work has had importance data for it. Its profile is identical to attn_q , attn_k and attn_v , which means it cannot be distinguished from them by importance alone — any differentiation has to come from measurement, not from the matrix.

Reproducing it
llama-imatrix -m Muse-Glimmer-30B-BF16-00001-of-00002.gguf \
    -f calib_train.txt -o part.gguf \
    -c 8192 -b 2048 -ngl 99 \
    --parse-special --process-output --no-ppl

--no-ppl is required at long context: the perplexity path allocates n_ctx x n_vocab x 4 bytes for logits, which is 26.5 GB at 32768 context with this model's 202 048 token vocabulary. Perplexity is not used by the importance collection, so disabling it costs nothing.

Merging is exact addition of sums and counts, so the corpus can be split across machines and recombined:

llama-imatrix -m any-model.gguf -c 8192 \
    --in-file part-00.gguf,part-01.gguf,part-long.gguf \
    -o muse-glimmer.imatrix.gguf

Per-tensor statistics for the merged file are in imatrix/imatrix-stats.txt in the metrics dataset, produced with llama-imatrix --show-statistics .

What's next
  • Full ladder, roughly 20 rungs, with a calibrated imatrix
  • NVFP4 for Blackwell
  • Code corpus metrics, per-task acceptance breakdown, drafter quantization sweep
  • Republished once PR #26841 is merged
Credits

Model by Meta Superintelligence Lab. llama.cpp support by @pcuenca and the ggml-org reviewers.

Runs of AtomicChat Muse-Glimmer-30B-GGUF on huggingface.co

4.6K
Total runs
-3.7K
24-hour runs
-6.2K
3-day runs
-6.0K
7-day runs
-1.9K
30-day runs

More Information About Muse-Glimmer-30B-GGUF huggingface.co Model

More Muse-Glimmer-30B-GGUF license Visit here:

https://choosealicense.com/licenses/apache-2.0

Muse-Glimmer-30B-GGUF huggingface.co

Muse-Glimmer-30B-GGUF huggingface.co is an AI model on huggingface.co that provides Muse-Glimmer-30B-GGUF's model effect (), which can be used instantly with this AtomicChat Muse-Glimmer-30B-GGUF model. huggingface.co supports a free trial of the Muse-Glimmer-30B-GGUF model, and also provides paid use of the Muse-Glimmer-30B-GGUF. Support call Muse-Glimmer-30B-GGUF model through api, including Node.js, Python, http.

Muse-Glimmer-30B-GGUF huggingface.co Url

https://huggingface.co/AtomicChat/Muse-Glimmer-30B-GGUF

AtomicChat Muse-Glimmer-30B-GGUF online free

Muse-Glimmer-30B-GGUF huggingface.co is an online trial and call api platform, which integrates Muse-Glimmer-30B-GGUF's modeling effects, including api services, and provides a free online trial of Muse-Glimmer-30B-GGUF, you can try Muse-Glimmer-30B-GGUF online for free by clicking the link below.

AtomicChat Muse-Glimmer-30B-GGUF online free url in huggingface.co:

https://huggingface.co/AtomicChat/Muse-Glimmer-30B-GGUF

Muse-Glimmer-30B-GGUF install

Muse-Glimmer-30B-GGUF is an open source model from GitHub that offers a free installation service, and any user can find Muse-Glimmer-30B-GGUF on GitHub to install. At the same time, huggingface.co provides the effect of Muse-Glimmer-30B-GGUF install, users can directly use Muse-Glimmer-30B-GGUF installed effect in huggingface.co for debugging and trial. It also supports api for free installation.

Muse-Glimmer-30B-GGUF install url in huggingface.co:

https://huggingface.co/AtomicChat/Muse-Glimmer-30B-GGUF

Url of Muse-Glimmer-30B-GGUF

Muse-Glimmer-30B-GGUF huggingface.co Url

Provider of Muse-Glimmer-30B-GGUF huggingface.co

AtomicChat
ORGANIZATIONS

Other API from AtomicChat

huggingface.co

Total runs: 395
Run Growth: -576
Growth Rate: -145.82%
Updated:July 23 2026
huggingface.co

Total runs: 32
Run Growth: -40
Growth Rate: -125.00%
Updated:July 28 2026