QW

cortiq qwopus dev

QwopusGGUF by infosaveUpdated 2026-10-22
Download on Hugging Face
Parameters15.1B
Context256K
Layers65
Architectureqwen35
Smallest quant9.4 GB
Quick answer

cortiq qwopus dev needs about 12.1 GB of memory at Q4_K_M (a 9.4 GB file) with an 8K context window, so it fits on a 16 GB GPU. This repository has 4 quants, from 9.4 GB (Q4_K_M) to 30.1 GB (F16). Longer context needs more: at 32K tokens the KV cache alone adds about 8.7 GB.

cortiq qwopus dev is a 15.1B-parameter Qwopus model in GGUF format, quantized by infosave. Its trained context length is 256K tokens. The repository has 4 quant files, from 9.4 GB (Q4_K_M) to 30.1 GB (F16).

Quants & memory

QuantFileEst. memoryvs VRAMResultDownload
Q4_K_M9.4 GB 12.1 GB
Too big Get file →
Q5_K_M10.8 GB 13.5 GB
Too big Get file →
Q8_016.0 GB 18.7 GB
Too big Get file →
F1630.1 GB 32.8 GB
Too big Get file →

What GPU do you need for cortiq qwopus dev?

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: the best quant that fits is Q5_K_M (10.8 GB file, about 13.5 GB in use).
  • 24 GB VRAM: the best quant that fits is Q8_0 (16.0 GB file, about 18.7 GB in use).
  • 32 GB VRAM: the best quant that fits is Q8_0 (16.0 GB file, about 18.7 GB in use).
  • 48 GB VRAM: the best quant that fits is F16 (30.1 GB file, about 32.8 GB in use).

Which cortiq qwopus dev quant should you choose?

Q4_K_M is the usual starting point for cortiq qwopus dev: it balances file size and quality well. Here it is a 9.4 GB file.

The Q8_0 file is 16.0 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.

New to quant names? Read GGUF quantization explained.

Specifications

Architecture from the GGUF header

Architectureqwen35
Parameters15.1B
Layers65
Trained context262,144 tokens
KV cache (fp16)260 KB per token

Source

Quantized byinfosave
FamilyQwopus
Licensemit
Downloads (HF)140
Last updated2026-10-22

Frequently asked questions about cortiq qwopus dev

How much VRAM does cortiq qwopus dev need?

About 12.1 GB at Q4_K_M with an 8K context window. That is the 9.4 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 cortiq qwopus dev on an 8 GB GPU?

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

What is the file size of cortiq qwopus dev GGUF?

It depends on the quant: Q4_K_M is 9.4 GB, Q5_K_M is 10.8 GB, Q8_0 is 16.0 GB, F16 is 30.1 GB.

What context length does cortiq qwopus dev support?

The GGUF header lists a trained context length of 262,144 tokens (256K). The KV cache grows with the context you use: about 2.2 GB at 8K and 8.7 GB at 32K.

Where can I download cortiq qwopus dev GGUF?

The files are on Hugging Face in the infosave/cortiq_qwopus_dev repository. The download buttons on this page open the file on Hugging Face. ggufmodels.com does not host any model files.

What license does cortiq qwopus dev use?

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

Other GGUFs of Qwopus3.6-27B-v2-MTP-GGUF

Similar models

Browse all →

More from infosave

All by infosave →

More Qwopus models

All Qwopus →

Other medium models

All medium models →