MU

Muse Glimmer 30B CRACK Fp16

MuseGGUF by dealignaiUpdated 2026-08-11
Download on Hugging Face
Parameters27.9B
Context128K
Layers52
Architecturemuse-glimmer
Smallest quant10.7 GB
Quick answer

Muse Glimmer 30B CRACK Fp16 needs about 17.9 GB of memory at Q4_K_M (a 16.9 GB file) with an 8K context window, so it fits on a 24 GB GPU. This repository has 3 quants, from 10.7 GB (Q2_K) to 29.6 GB (Q8_0). Longer context needs more: at 32K tokens the KV cache alone adds about 1.7 GB.

Muse Glimmer 30B CRACK Fp16 – 27.9B parameter multimodal LLM for local agentic tasks

Muse Glimmer 30B CRACK Fp16 is a 27.9‑billion‑parameter causal language model with a dedicated perception encoder. It supports reasoning, tool use, and vision in a single local model. The model is released under Apache 2.0 and can run on consumer hardware with llama.cpp.

Good at

  • Multimodal reasoning with text and images
  • Reliable tool calling via ATEM format
  • End‑to‑end agentic task completion

Limits

  • No safety guardrails – use responsibly
  • Requires a vision projector file for image input
  • Large memory footprint for higher‑precision quants

Best for

  • Building autonomous agents on local machines
  • Multimodal content analysis
  • Complex code‑generation workflows

Who it’s for. Developers and researchers who need a fully local, multimodal LLM for agentic applications. The model is suitable for projects that require reliable tool use, multi‑step reasoning, and vision understanding without cloud dependency.

Quants & memory

QuantFileEst. memoryvs VRAMResultDownload
Q2_K10.7 GB 11.6 GB
Too big Get file →
Q4_K_M16.9 GB 17.9 GB
Too big Get file →
Q8_029.6 GB 30.5 GB
Too big Get file →

For 8 GB VRAM, use the Q2_K quant (10.69 GB file, ~11.6 GB memory at 8k context). For 12 GB VRAM, Q4_K_M (16.94 GB file, ~17.9 GB memory) offers a good balance. If you have 16 GB or more, Q8_0 (29.61 GB file, ~30.5 GB memory) gives near‑lossless performance.

What GPU do you need for Muse Glimmer 30B CRACK Fp16?

These figures add the file size, an fp16 KV cache at an 8K context window (worked out from this model’s own header) and about 0.5 GB for the runtime. They are estimates, so leave a little headroom, and expect to use less context or a smaller quant if you are right at the limit.

  • 4 GB VRAM: no quant fits at an 8K context.
  • 6 GB VRAM: no quant fits at an 8K context.
  • 8 GB VRAM: no quant fits at an 8K context.
  • 12 GB VRAM: the best quant that fits is Q2_K (10.7 GB file, about 11.6 GB in use).
  • 16 GB VRAM: the best quant that fits is Q2_K (10.7 GB file, about 11.6 GB in use).
  • 24 GB VRAM: the best quant that fits is Q4_K_M (16.9 GB file, about 17.9 GB in use).
  • 32 GB VRAM: the best quant that fits is Q8_0 (29.6 GB file, about 30.5 GB in use).

Which Muse Glimmer 30B CRACK Fp16 quant should you choose?

Q4_K_M is the usual starting point for Muse Glimmer 30B CRACK Fp16: it balances file size and quality well. Here it is a 16.9 GB file.

The Q8_0 file is 29.6 GB, about 1.7 times the size of Q4_K_M. It keeps the weights closer to the original, which only matters if you have the memory to spare.

If memory is tight, the smallest file is Q2_K at 10.7 GB, with the quality trade-offs that come with fewer bits. Use it only when memory is very tight. Expect a clear drop in quality, which is usually worse on small models and easier to live with on large ones.

New to quant names? Read GGUF quantization explained.

Specifications

Architecture from the GGUF header

Architecturemuse-glimmer
Parameters27.9B
Layers52
Trained context131,072 tokens
KV cache (fp16)52 KB per token

Source

Quantized bydealignai
FamilyMuse
Licenseapache-2.0
Downloads (HF)2,204
Last updated2026-08-11

Frequently asked questions about Muse Glimmer 30B CRACK Fp16

How much VRAM does Muse Glimmer 30B CRACK Fp16 need?

About 17.9 GB at Q4_K_M with an 8K context window. That is the 16.9 GB file, plus the KV cache and roughly 0.5 GB of runtime overhead. Smaller quants need less and longer context needs more.

Can I run Muse Glimmer 30B CRACK Fp16 on an 8 GB GPU?

Not at an 8K context. The smallest file needs about 11.6 GB, so you would need a larger GPU or CPU offloading.

What is the file size of Muse Glimmer 30B CRACK Fp16 GGUF?

It depends on the quant: Q2_K is 10.7 GB, Q4_K_M is 16.9 GB, Q8_0 is 29.6 GB.

What context length does Muse Glimmer 30B CRACK Fp16 support?

The GGUF header lists a trained context length of 131,072 tokens (128K). The KV cache grows with the context you use: about 0.4 GB at 8K and 1.7 GB at 32K.

Where can I download Muse Glimmer 30B CRACK Fp16 GGUF?

The files are on Hugging Face in the dealignai/Muse-Glimmer-30B-CRACK-GGUF repository. The download buttons on this page open the file on Hugging Face. ggufmodels.com does not host any model files.

What license does Muse Glimmer 30B CRACK Fp16 use?

Hugging Face lists the license as apache-2.0. Licenses can differ between the quantized files and the original model, so check the repository and the base model before commercial use.

Can I run Muse Glimmer 30B CRACK on 8 GB VRAM?

The Q2_K quant is 10.69 GB, which is close to 8 GB VRAM but may require swapping. It is the smallest available quant.

Do I need a separate vision projector file?

Yes, download the mmproj-Muse-Glimmer-30B-f16.gguf (3.8 GB) to enable image input.

Is there any safety guardrail in this model?

The CRACK version removes refusal behavior; use responsibly and lawfully.

Other GGUFs of Muse-Glimmer-30B

Similar models

Browse all →

More from dealignai

All by dealignai →

More Muse models

All Muse →

Other medium models

All medium models →