open text detector qwen36 35b a3b oct10 needs about 22.3 GB of memory at Q4_K_M (a 21.2 GB file) with an 8K context window, so it fits on a 24 GB GPU. This repository has 11 quants, from 0.4 GB to 69.4 GB (BF16). Longer context needs more: at 32K tokens the KV cache alone adds about 2.7 GB.
Open Text Detector based on Qwen3.6-35B-A3B
The Open Text Detector token classifier uses Qwen3.6-35B-A3B weights merged with LoRA adapters. It scores each token for AI‑written probability. The model is not a chat model and is trained for classification, not generation.
Good at
- Detecting AI‑written tokens in English research papers
- Scoring sentences with token‑level probabilities
- Operating with a 262,144 token context length
Limits
- No vision support
- Not suitable for text generation
- Requires specific scoring pipeline
Best for
- Academic paper authenticity checks
- Research integrity monitoring
- Token‑level AI detection
Who it’s for. Developers and researchers who need to evaluate the authenticity of English research papers. The model is useful for building tools that flag AI‑generated content at the token level.
Quants & memory
| Quant | File | Est. memory | vs VRAM | Result | |
|---|---|---|---|---|---|
| — | 0.4 GB | 1.6 GB | Fits | Get file → | |
| IQ2_M | 11.7 GB | 12.8 GB | Too big | Get file → | |
| IQ3_XXS | 13.6 GB | 14.8 GB | Too big | Get file → | |
| Q3_K_M | 16.8 GB | 17.9 GB | Too big | Get file → | |
| IQ4_XS | 18.7 GB | 19.9 GB | Too big | Get file → | |
| Q4_K_M | 21.2 GB | 22.3 GB | Too big | Get file → | |
| Q4_K_M | 21.2 GB | 22.3 GB | Too big | Get file → | |
| Q5_K_M | 24.7 GB | 25.9 GB | Too big | Get file → | |
| Q6_K | 28.5 GB | 29.7 GB | Too big | Get file → | |
| Q8_0 | 36.9 GB | 38.1 GB | Too big | Get file → | |
| BF16 | 69.4 GB | 70.5 GB | Too big | Get file → |
For 8 GB VRAM, use IQ2_M (file size 11.66 GB, memory 12.8 GB). For 16 GB VRAM, Q4_K_M (21.17 GB, 22.3 GB) is suitable. For larger budgets, Q5_K_M or Q6_K provide higher precision with 24.73 GB/25.9 GB and 28.51 GB/29.7 GB respectively. Estimates are approximate.
What GPU do you need for open text detector qwen36 35b a3b oct10?
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.4 GB file, about 1.6 GB in use).
- 6 GB VRAM: the best quant that fits is the main file (0.4 GB file, about 1.6 GB in use).
- 8 GB VRAM: the best quant that fits is the main file (0.4 GB file, about 1.6 GB in use).
- 12 GB VRAM: the best quant that fits is the main file (0.4 GB file, about 1.6 GB in use).
- 16 GB VRAM: the best quant that fits is IQ3_XXS (13.6 GB file, about 14.8 GB in use).
- 24 GB VRAM: the best quant that fits is Q4_K_M (21.2 GB file, about 22.3 GB in use).
- 32 GB VRAM: the best quant that fits is Q6_K (28.5 GB file, about 29.7 GB in use).
- 48 GB VRAM: the best quant that fits is Q8_0 (36.9 GB file, about 38.1 GB in use).
Which open text detector qwen36 35b a3b oct10 quant should you choose?
Q4_K_M is the usual starting point for open text detector qwen36 35b a3b oct10: it balances file size and quality well. Here it is a 21.2 GB file.
The Q8_0 file is 36.9 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 the first one in the table at 0.4 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
Source
Frequently asked questions about open text detector qwen36 35b a3b oct10
How much VRAM does open text detector qwen36 35b a3b oct10 need?
About 22.3 GB at Q4_K_M with an 8K context window. That is the 21.2 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 open text detector qwen36 35b a3b oct10 on an 8 GB GPU?
Yes, with the smaller files: the 0.4 GB file needs about 1.6 GB at 8K context. Larger quants in this repository do not fit in 8 GB.
What is the file size of open text detector qwen36 35b a3b oct10 GGUF?
It depends on the quant: file is 0.4 GB, IQ2_M is 11.7 GB, IQ3_XXS is 13.6 GB, Q3_K_M is 16.8 GB, IQ4_XS is 18.7 GB, Q4_K_M is 21.2 GB and 5 more.
What context length does open text detector qwen36 35b a3b oct10 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.7 GB at 32K.
Where can I download open text detector qwen36 35b a3b oct10 GGUF?
The files are on Hugging Face in the woog/open-text-detector-qwen36-35b-a3b-oct10-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 open text detector qwen36 35b a3b oct10 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 the Open Text Detector on 8 GB VRAM?
Yes, the IQ2_M quantized file uses about 12.8 GB of VRAM at 8 k context, which fits within an 8 GB GPU with some headroom.
Does this model support vision tasks?
No, the model is a causal language model with no vision encoder and is not intended for image processing.
What is the context length of this model?
The model is trained with 262,144 tokens natively and can be extended up to 1,010,000 tokens.