ZE

zephyr orpo 141b A35b v0.1 GGUF smashed

ZephyrGGUF by PrunaAIUpdated 2026-03-25
Download on Hugging Face
Parameters141B
Context64K
Layers56
Architecturellama
Smallest quant29.6 GB
Quick answer

zephyr orpo 141b A35b v0.1 GGUF smashed needs about 88.0 GB of memory at Q4_K_M (a 85.6 GB file) with an 8K context window, which is more than a 48 GB GPU holds. This repository has 15 quants, from 29.6 GB (IQ1_S) to 281.2 GB. Longer context needs more: at 32K tokens the KV cache alone adds about 7.5 GB.

141B Zephyr MOE model compressed to GGUF format

Zephyr orpo 141b A35b v0.1 GGUF smashed is a 141 billion‑parameter mixture of experts model. It supports a 65 536‑token context window and is available in multiple quantisations ranging from IQ1_S to Q8_0. The model is hosted on the PrunaAI Hugging Face repository.

Good at

  • Large context handling
  • High‑parameter capacity
  • Mixture of experts architecture

Limits

  • No license information provided
  • No vision support
  • Requires large VRAM for higher quants

Best for

  • Long‑form content generation
  • Complex reasoning tasks
  • Large‑scale data summarisation

Who it’s for. Developers and researchers needing a high‑parameter, long‑context model for text‑only workloads. Suitable for local deployment with sufficient GPU memory.

Quants & memory

QuantFileEst. memoryvs VRAMResultDownload
IQ1_S29.6 GB 32.0 GB
Too big Get file →
IQ1_M32.7 GB 35.1 GB
Too big Get file →
Q2_K52.1 GB (5 parts) 54.5 GB
Too big Get file →
IQ3_XS58.2 GB (5 parts) 60.6 GB
Too big Get file →
Q3_K_S61.5 GB (5 parts) 63.9 GB
Too big Get file →
Q3_K_M67.8 GB (5 parts) 70.2 GB
Too big Get file →
Q3_K_L72.6 GB (5 parts) 75.0 GB
Too big Get file →
IQ4_XS76.4 GB (5 parts) 78.7 GB
Too big Get file →
Q4_K_S80.5 GB (5 parts) 82.9 GB
Too big Get file →
Q4_K_M85.6 GB (5 parts) 88.0 GB
Too big Get file →
Q5_K_S97.0 GB (5 parts) 99.4 GB
Too big Get file →
Q5_K_M100.0 GB (5 parts) 102.3 GB
Too big Get file →
Q8_0115.5 GB (4 parts) 117.9 GB
Too big Get file →
Q6_K115.5 GB (5 parts) 117.9 GB
Too big Get file →
—281.2 GB (7 parts) 283.6 GB
Too big Get file →

For 8 GB VRAM, use IQ1_S (29.64 GB file, ~32 GB VRAM). For 12 GB VRAM, IQ1_M (32.73 GB file, ~35 GB VRAM). For 24 GB VRAM, Q4_K_M (85.59 GB file, ~88 GB VRAM).

What GPU do you need for zephyr orpo 141b A35b v0.1 GGUF smashed?

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: no quant fits at an 8K context.
  • 16 GB VRAM: no quant fits at an 8K context.
  • 24 GB VRAM: no quant fits at an 8K context.
  • 32 GB VRAM: the best quant that fits is IQ1_S (29.6 GB file, about 32.0 GB in use).
  • 48 GB VRAM: the best quant that fits is IQ1_M (32.7 GB file, about 35.1 GB in use).

Which zephyr orpo 141b A35b v0.1 GGUF smashed quant should you choose?

Q4_K_M is the usual starting point for zephyr orpo 141b A35b v0.1 GGUF smashed: it balances file size and quality well. Here it is a 85.6 GB file.

The Q8_0 file is 115.5 GB, about 1.3 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 IQ1_S at 29.6 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

Architecturellama
Parameters141B (approximate, mixture of experts)
Layers56
Trained context65,536 tokens
KV cache (fp16)224 KB per token

Source

Quantized byPrunaAI
FamilyZephyr
Downloads (HF)5,509
Last updated2026-03-25

Frequently asked questions about zephyr orpo 141b A35b v0.1 GGUF smashed

How much VRAM does zephyr orpo 141b A35b v0.1 GGUF smashed need?

About 88.0 GB at Q4_K_M with an 8K context window. That is the 85.6 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 zephyr orpo 141b A35b v0.1 GGUF smashed on an 8 GB GPU?

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

What is the file size of zephyr orpo 141b A35b v0.1 GGUF smashed GGUF?

It depends on the quant: IQ1_S is 29.6 GB, IQ1_M is 32.7 GB, Q2_K is 52.1 GB, IQ3_XS is 58.2 GB, Q3_K_S is 61.5 GB, Q3_K_M is 67.8 GB and 9 more.

What context length does zephyr orpo 141b A35b v0.1 GGUF smashed support?

The GGUF header lists a trained context length of 65,536 tokens (64K). The KV cache grows with the context you use: about 1.9 GB at 8K and 7.5 GB at 32K.

Where can I download zephyr orpo 141b A35b v0.1 GGUF smashed GGUF?

The files are on Hugging Face in the PrunaAI/zephyr-orpo-141b-A35b-v0.1-GGUF-smashed repository. The download buttons on this page open the file on Hugging Face. ggufmodels.com does not host any model files.

Can I run this model on 8 GB VRAM?

Use the IQ1_S quantisation; it requires about 32 GB VRAM at 8 k context, so 8 GB VRAM is insufficient.

Does this model support vision?

No, the model is text‑only and does not include vision capabilities.

What is the maximum context length?

The model supports up to 65,536 tokens of context.

Similar models

Browse all →

More from PrunaAI

All by PrunaAI →

More Zephyr models

All Zephyr →

Other large models

All large models →