QW

Endy Qwen3.6 CyberSec 35B A3B

QwenGGUF by endystrikeUpdated 2026-07-16
Download on Hugging Face
Parameters35.5B
Context256K
Layers41
Architectureqwen35moe
Smallest quant13.2 GB
Quick answer

Endy Qwen3.6 CyberSec 35B A3B needs about 22.9 GB of memory at Q4_K_M (a 21.7 GB file) with an 8K context window, so it fits on a 24 GB GPU. This repository has 6 quants, from 13.2 GB (Q2_K) to 37.8 GB (Q8_0). Longer context needs more: at 32K tokens the KV cache alone adds about 2.8 GB.

Endy Qwen3.6 CyberSec 35B A3B – uncensored coding and cybersecurity LLM with vision

Endy Qwen3.6 CyberSec 35B A3B is a QLoRA fine‑tune of huihui‑ai/Huihui‑Qwen3.6‑35B‑A3B‑Claude‑4.7‑Opus‑abliterated. It retains a 35.5B total parameter MoE architecture with 3.0B active parameters and supports vision via an mmproj file. The model is released under AGPL‑3.0.

Good at

  • Coding and cybersecurity dialogue
  • Vision‑enabled image analysis
  • Reasoning and tool use

Limits

  • Uncensored outputs may generate sensitive content
  • Requires 32 GB GPU for full performance
  • No speculative decoding support

Best for

  • Security researchers testing code
  • Developers building agentic tools
  • Educational labs exploring vision‑LLM integration

Who it’s for. Researchers, developers, and security professionals who need a powerful, uncensored LLM with vision for controlled environments. The model is best used in research or testing, not in production or public‑facing applications.

Quants & memory

QuantFileEst. memoryvs VRAMResultDownload
Q2_K13.2 GB 14.4 GB
Too big Get file →
Q3_K_M17.2 GB 18.4 GB
Too big Get file →
Q4_K_M21.7 GB 22.9 GB
Too big Get file →
Q5_K_M25.3 GB 26.5 GB
Too big Get file →
Q6_K29.2 GB 30.4 GB
Too big Get file →
Q8_037.8 GB 39.0 GB
Too big Get file →

For 8 GB VRAM use Q2_K (13.25 GB file, ~14.4 GB memory at 8 k context). For 16 GB VRAM use Q4_K_M (21.71 GB file, ~22.9 GB memory). For 32 GB VRAM use Q8_0 (37.8 GB file, ~39 GB memory). Estimates are approximate.

What GPU do you need for Endy Qwen3.6 CyberSec 35B A3B?

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 Q2_K (13.2 GB file, about 14.4 GB in use).
  • 24 GB VRAM: the best quant that fits is Q4_K_M (21.7 GB file, about 22.9 GB in use).
  • 32 GB VRAM: the best quant that fits is Q6_K (29.2 GB file, about 30.4 GB in use).
  • 48 GB VRAM: the best quant that fits is Q8_0 (37.8 GB file, about 39.0 GB in use).

Which Endy Qwen3.6 CyberSec 35B A3B quant should you choose?

Q4_K_M is the usual starting point for Endy Qwen3.6 CyberSec 35B A3B: it balances file size and quality well. Here it is a 21.7 GB file.

The Q8_0 file is 37.8 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 13.2 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

Architectureqwen35moe
Parameters35.5B (approximate, mixture of experts)
Active parameters3B
Layers41
Trained context262,144 tokens
KV cache (fp16)82 KB per token

Source

Quantized byendystrike
FamilyQwen
Licenseagpl-3.0
Downloads (HF)1,423
Last updated2026-07-16

Frequently asked questions about Endy Qwen3.6 CyberSec 35B A3B

How much VRAM does Endy Qwen3.6 CyberSec 35B A3B need?

About 22.9 GB at Q4_K_M with an 8K context window. That is the 21.7 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 Endy Qwen3.6 CyberSec 35B A3B on an 8 GB GPU?

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

What is the file size of Endy Qwen3.6 CyberSec 35B A3B GGUF?

It depends on the quant: Q2_K is 13.2 GB, Q3_K_M is 17.2 GB, Q4_K_M is 21.7 GB, Q5_K_M is 25.3 GB, Q6_K is 29.2 GB, Q8_0 is 37.8 GB.

What context length does Endy Qwen3.6 CyberSec 35B A3B support?

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

Where can I download Endy Qwen3.6 CyberSec 35B A3B GGUF?

The files are on Hugging Face in the endystrike/Endy-Qwen3.6-CyberSec-35B-A3B-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 Endy Qwen3.6 CyberSec 35B A3B use?

Hugging Face lists the license as agpl-3.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 this model on 8 GB VRAM?

Use the Q2_K quantization; it requires about 14.4 GB of VRAM at 8 k context, so it will not fit on 8 GB. You would need a larger GPU.

Does this model support image input?

Yes, vision works via the paired mmproj file. Use --mmproj to enable image input in llama.cpp.

Is the model safe for public deployment?

No. The model is uncensored and may produce sensitive or inappropriate content; it is intended for research or controlled environments only.

Other GGUFs of Huihui-Qwen3.6-35B-A3B-Claude-4.7-Opus-abliterated

Similar models

Browse all →

More Qwen models

All Qwen →

Other large models

All large models →