QW

qwen2.5 coder 32b combined verilog c i1

QwenGGUF by mradermacherUpdated 2025-12-16
Download on Hugging Face
Parameters32.8B
Context32K
Layers64
Architectureqwen2
Smallest quant0.0 GB
Quick answer

qwen2.5 coder 32b combined verilog c i1 needs about 22.5 GB of memory at Q4_K_M (a 19.8 GB file) with an 8K context window, so it fits on a 24 GB GPU. This repository has 24 quants, from 0.0 GB to 26.9 GB (Q6_K). Longer context needs more: at 32K tokens the KV cache alone adds about 8.6 GB.

Qwen2.5 Coder 32B for Verilog and C code generation

This 32.8B parameter model is fine‑tuned for coding tasks. It supports a 32768 token context and is available in multiple GGUF quantizations. The base architecture is Qwen2.

Good at

  • Verilog code generation
  • C programming
  • Large context handling

Limits

  • No vision support
  • License not specified
  • Requires large VRAM for full precision

Best for

  • Embedded firmware development
  • Hardware description language synthesis
  • Complex software debugging

Who it’s for. Developers and engineers needing accurate code generation for Verilog and C. The model is suitable for projects that can accommodate its memory footprint.

Quants & memory

QuantFileEst. memoryvs VRAMResultDownload
—0.0 GB 2.7 GB
Fits Get file →
IQ1_S7.3 GB 9.9 GB
Too big Get file →
IQ1_M7.9 GB 10.6 GB
Too big Get file →
IQ2_XXS9.0 GB 11.7 GB
Too big Get file →
IQ2_XS10.0 GB 12.6 GB
Too big Get file →
IQ2_S10.4 GB 13.0 GB
Too big Get file →
IQ2_M11.3 GB 13.9 GB
Too big Get file →
Q2_K_S11.5 GB 14.1 GB
Too big Get file →
Q2_K12.3 GB 15.0 GB
Too big Get file →
IQ3_XXS12.8 GB 15.5 GB
Too big Get file →
IQ3_XS13.7 GB 16.4 GB
Too big Get file →
Q3_K_S14.4 GB 17.0 GB
Too big Get file →
IQ3_S14.4 GB 17.1 GB
Too big Get file →
IQ3_M14.8 GB 17.5 GB
Too big Get file →
Q3_K_M15.9 GB 18.6 GB
Too big Get file →
Q3_K_L17.2 GB 19.9 GB
Too big Get file →
IQ4_XS17.7 GB 20.3 GB
Too big Get file →
Q4_018.7 GB 21.4 GB
Too big Get file →
Q4_K_S18.8 GB 21.4 GB
Too big Get file →
Q4_K_M19.8 GB 22.5 GB
Too big Get file →
Q4_120.6 GB 23.3 GB
Too big Get file →
Q5_K_S22.6 GB 25.3 GB
Too big Get file →
Q5_K_M23.3 GB 25.9 GB
Too big Get file →
Q6_K26.9 GB 29.5 GB
Too big Get file →

For 8 GB VRAM, use IQ1_S (7.27 GB file, 9.9 GB memory at 8 k context). For 12 GB VRAM, IQ2_XS (9.96 GB file, 12.6 GB memory). For 16 GB VRAM, Q3_K_S (14.39 GB file, 17 GB memory).

What GPU do you need for qwen2.5 coder 32b combined verilog c i1?

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: the best quant that fits is the main file (0.0 GB file, about 2.7 GB in use).
  • 6 GB VRAM: the best quant that fits is the main file (0.0 GB file, about 2.7 GB in use).
  • 8 GB VRAM: the best quant that fits is the main file (0.0 GB file, about 2.7 GB in use).
  • 12 GB VRAM: the best quant that fits is IQ2_XXS (9.0 GB file, about 11.7 GB in use).
  • 16 GB VRAM: the best quant that fits is IQ3_XXS (12.8 GB file, about 15.5 GB in use).
  • 24 GB VRAM: the best quant that fits is Q4_1 (20.6 GB file, about 23.3 GB in use).
  • 32 GB VRAM: the best quant that fits is Q6_K (26.9 GB file, about 29.5 GB in use).

Which qwen2.5 coder 32b combined verilog c i1 quant should you choose?

Q4_K_M is the usual starting point for qwen2.5 coder 32b combined verilog c i1: it balances file size and quality well. Here it is a 19.8 GB file.

If memory is tight, the smallest file is the first one in the table at 0.0 GB, with the quality trade-offs that come with fewer bits.

New to quant names? Read GGUF quantization explained.

Specifications

Architecture from the GGUF header

Architectureqwen2
Parameters32.8B
Layers64
Trained context32,768 tokens
KV cache (fp16)256 KB per token

Source

Quantized bymradermacher
FamilyQwen
Downloads (HF)2,072
Last updated2025-12-16

Frequently asked questions about qwen2.5 coder 32b combined verilog c i1

How much VRAM does qwen2.5 coder 32b combined verilog c i1 need?

About 22.5 GB at Q4_K_M with an 8K context window. That is the 19.8 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 qwen2.5 coder 32b combined verilog c i1 on an 8 GB GPU?

Yes, with the smaller files: the 0.0 GB file needs about 2.7 GB at 8K context. Larger quants in this repository do not fit in 8 GB.

What is the file size of qwen2.5 coder 32b combined verilog c i1 GGUF?

It depends on the quant: file is 0.0 GB, IQ1_S is 7.3 GB, IQ1_M is 7.9 GB, IQ2_XXS is 9.0 GB, IQ2_XS is 10.0 GB, IQ2_S is 10.4 GB and 18 more.

What context length does qwen2.5 coder 32b combined verilog c i1 support?

The GGUF header lists a trained context length of 32,768 tokens (32K). The KV cache grows with the context you use: about 2.1 GB at 8K and 8.6 GB at 32K.

Where can I download qwen2.5 coder 32b combined verilog c i1 GGUF?

The files are on Hugging Face in the mradermacher/qwen2.5-coder-32b-combined-verilog-c-i1-GGUF 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?

Yes, with the IQ1_S quantization it requires about 9.9 GB memory at 8 k context, which fits within 8 GB VRAM when using efficient batching.

Does this model support image input?

No, the model is purely text‑based and does not handle vision tasks.

What context length does it support?

It supports up to 32768 tokens, allowing long code or document processing.

Other GGUFs of qwen2.5-coder-32b-combined-verilog-c

Similar models

Browse all →

More from mradermacher

All by mradermacher →

More Qwen models

All Qwen →

Other medium models

All medium models →