BU

BugTraceAI Apex G4 26B Master

BugtraceaiGGUF by piotreknow02Updated 2026-04-14
Download on Hugging Face
Parameters25.2B
Context256K
Layers30
Architecturegemma4
Smallest quant8.6 GB
Quick answer

BugTraceAI Apex G4 26B Master needs about 25.3 GB of memory at Q4_K_M (a 16.8 GB file) with an 8K context window, so it fits on a 32 GB GPU. This repository has 21 quants, from 8.6 GB (TQ1_0) to 50.5 GB (F16). Longer context needs more: at 32K tokens the KV cache alone adds about 32.2 GB.

BugTraceAI Apex G4 26B Master – a 26B Mixture‑of‑Experts Gemma4 model for technical reasoning

BugTraceAI Apex G4 26B Master is a 26B parameter MoE model based on Gemma4 architecture. It is fine‑tuned for reasoning and tool usage, with a 262144 token context window. The model is released under Apache‑2.0.

Good at

  • Deep technical reasoning
  • Tool‑based task execution
  • Large context handling

Limits

  • No vision support
  • Requires high VRAM or CPU offloading
  • Large memory footprint for full precision

Best for

  • Bug bounty analysis
  • Malware methodology research
  • WAF evasion strategy design

Who it’s for. Engineers and security researchers who need a large‑scale reasoning model for detailed technical tasks. The model is suited for users with GPUs that support 12GB VRAM or higher and sufficient system RAM for offloading.

Quants & memory

QuantFileEst. memoryvs VRAMResultDownload
TQ1_08.6 GB 17.1 GB
Too big Get file →
TQ2_09.4 GB 17.9 GB
Too big Get file →
Q2_K10.6 GB 19.1 GB
Too big Get file →
Q3_K_S12.2 GB 20.8 GB
Too big Get file →
Q3_K13.3 GB 21.8 GB
Too big Get file →
Q3_K_M13.3 GB 21.8 GB
Too big Get file →
Q3_K_L13.8 GB 22.4 GB
Too big Get file →
Q4_014.4 GB 23.0 GB
Too big Get file →
MXFP4_MOE14.7 GB 23.3 GB
Too big Get file →
Q4_K_S15.5 GB 24.0 GB
Too big Get file →
Q4_116.0 GB 24.5 GB
Too big Get file →
Q4_K16.8 GB 25.3 GB
Too big Get file →
Q4_K_M16.8 GB 25.3 GB
Too big Get file →
Q5_017.5 GB 26.1 GB
Too big Get file →
Q5_K_S18.0 GB 26.5 GB
Too big Get file →
Q5_119.0 GB 27.6 GB
Too big Get file →
Q5_K19.1 GB 27.7 GB
Too big Get file →
Q5_K_M19.1 GB 27.7 GB
Too big Get file →
Q6_K22.6 GB 31.2 GB
Too big Get file →
Q8_026.9 GB 35.4 GB
Too big Get file →
F1650.5 GB 59.1 GB
Too big Get file →

For 12GB VRAM GPUs, use the Q4_K_M quant (16.8 GB file, ~25.3 GB memory at 8k context). If more VRAM is available, Q3_K_M (13.29 GB, ~21.8 GB memory) or Q3_K_S (12.22 GB, ~20.8 GB memory) provide higher precision. For systems with 8GB VRAM, TQ1_0 (8.57 GB, ~17.1 GB memory) is the lightest option.

What GPU do you need for BugTraceAI Apex G4 26B Master?

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: the best quant that fits is Q4_K_S (15.5 GB file, about 24.0 GB in use).
  • 32 GB VRAM: the best quant that fits is Q6_K (22.6 GB file, about 31.2 GB in use).
  • 48 GB VRAM: the best quant that fits is Q8_0 (26.9 GB file, about 35.4 GB in use).

Which BugTraceAI Apex G4 26B Master quant should you choose?

Q4_K_M is the usual starting point for BugTraceAI Apex G4 26B Master: it balances file size and quality well. Here it is a 16.8 GB file.

The Q8_0 file is 26.9 GB, about 1.6 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 TQ1_0 at 8.6 GB, with the quality trade-offs that come with fewer bits. Lower bit counts mean smaller files and more quality loss.

New to quant names? Read GGUF quantization explained.

Specifications

Architecture from the GGUF header

Architecturegemma4
Parameters25.2B (approximate, mixture of experts)
Layers30
Trained context262,144 tokens
KV cache (fp16)960 KB per token

Source

Quantized bypiotreknow02
Licenseapache-2.0
Downloads (HF)489
Last updated2026-04-14

Frequently asked questions about BugTraceAI Apex G4 26B Master

How much VRAM does BugTraceAI Apex G4 26B Master need?

About 25.3 GB at Q4_K_M with an 8K context window. That is the 16.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 BugTraceAI Apex G4 26B Master on an 8 GB GPU?

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

What is the file size of BugTraceAI Apex G4 26B Master GGUF?

It depends on the quant: TQ1_0 is 8.6 GB, TQ2_0 is 9.4 GB, Q2_K is 10.6 GB, Q3_K_S is 12.2 GB, Q3_K is 13.3 GB, Q3_K_M is 13.3 GB and 15 more.

What context length does BugTraceAI Apex G4 26B Master support?

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

Where can I download BugTraceAI Apex G4 26B Master GGUF?

The files are on Hugging Face in the piotreknow02/BugTraceAI-Apex-G4-26B-Master-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 BugTraceAI Apex G4 26B Master 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 BugTraceAI Apex G4 26B Master on a 12GB VRAM GPU?

Yes, the Q4_K_M quant is optimized for 12GB VRAM GPUs with CPU offloading of expert layers.

Does the model support vision inputs?

No, the vision tower has been stripped; the model is text‑only.

What license applies to this model?

The model is released under the Apache‑2.0 license.

Other GGUFs of BugTraceAI-Apex-G4-26B-Master-f16

Similar models

Browse all →

More from piotreknow02

All by piotreknow02 →

More Bugtraceai models

All Bugtraceai →

Other medium models

All medium models →