t8star/flux.1-dev-abliterated-V2-GGUF
? Why do I need an app?
The browser can't see your hardware
For privacy reasons a browser tells us at most "≥ 8 GB RAM, 8 cores" - same reading whether you have 8 GB or 128 GB. It has no idea how much RAM is free right now, which apps are open, or whether you have a GPU.
The Abliteration app is integrated with your machine
It reads your exact RAM, GPU model and VRAM, free memory right now, and picks the sharpest quant that still fits. Every model page lights up precisely for your rig.
And you can chat with any model, right now
The app is a full local runtime - no API keys, no subscription, everything runs on your machine. Click any model on this site and start a conversation in seconds.
Get the free app →This is a rough estimate. Install the free app - we'll show exact numbers.
Reading real hardware from your app right now. Numbers below are exact.
Below is the per-quantization compatibility for this model.
curl -H "Authorization: Bearer $ABL_KEY" \
"https://abliteration.org/api/v1/models/t8star%2Fflux.1-dev-abliterated-V2-GGUF" - classification m8
- files 4
- hub_downloads_all_time 64,938
- author_summary 1 models
- readme_text full
Repackaging (quantization)
Why this label 3 signals
- 'abliterated' in name/tags
- is_gguf=1
- assume M1 (base ablation) + M8 (GGUF quant) - default when producer unknown
No specific extraction method could be identified for this model. The producer either did not document it or used a proprietary pipeline.
What is a refusal direction? →Metadata
Files by quantization
Q8_0 1 file 11.8 GB - ★ recommended for you
| T8-flux.1-dev-abliterated-V2-GGUF-Q8_0.gguf | 11.8 GB | aba8163f | download |
Q6_K 1 file 9.18 GB - ★ recommended for you
| T8-flux.1-dev-abliterated-V2-GGUF-Q6_K.gguf | 9.18 GB | 9a7ef008 | download |
Q4_K 1 file 6.46 GB - ★ recommended for you
| T8-flux.1-dev-abliterated-V2-GGUF-Q4_K_M.gguf | 6.46 GB | f68579df | download |
Auxiliary files 1 file 1.72 KB
| .gitattributes | 1.72 KB | f791dcf0 | download |
README
The author did not publish a README.
Discussions
2026-06-25PRCreate README.md
Loading...