← back to catalog · registered 2026-08-22 13:56

Iambackup/gemma-2-9b-it-abliterated-GGUF

Iambackup Gemma 9B GGUF second-order 8K ctx
Your rig guess connected
? Why do I need an app?
Reading your rig…

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/Iambackup%2Fgemma-2-9b-it-abliterated-GGUF"
Response includes
  • classification m8
  • files 4
  • benchmarks 5 entries
  • hub_downloads_all_time 373
  • author_summary 36 models
  • readme_text full
10 credits · hourly refresh · ~4 KB payload Get an API key →
Abliteration classifier · v1.0.0
M8
Primary method

Repackaging (quantization)

Applied on top of direct removal inherited from the base model.
Confidence
MEDIUM
Inherited from base model
Why this label 3 signals
Method inferred from partial signals - repository name, related files, or tag patterns. Producer identity not confirmed; label may sharpen or shift as we gather more evidence.
  • 'abliterated' in name/tags
  • is_gguf=1
  • assume M1 (base ablation) + M8 (GGUF quant) - default when producer unknown
Refusal direction extraction

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? →
Downloads · lifetime
373
21 last 30d - cooling
Likes
0
Model age
4mo ago
created 2026-06-12
Downloads over time
Now387→from0↑0%
01422844260 on Jun 10387 on Oct 11JunJulAugSepOct
Jun 10 → Oct 11 · 57 snapshots · spans 123 days

Benchmarks

Benchmark Score Source
BBH average 0.5336619535607732 OpenLLM-v2
IFEval instruct 0.7865707434052758 OpenLLM-v2
IFEval-Prompt 0.7079482439926063 OpenLLM-v2
MATH lvl 5 0.0007552870090634441 OpenLLM-v2
MMLU-Pro 0.39153922872340424 OpenLLM-v2

Genealogy 0 direct forks

Full fork graph →

This model's place in the market. Above: what it was derived from. Below: the tree of everything derived from it.

Metadata

License
gemma
Languages
en
Quantizations
Q6_K Q8_0
Tags
gguf text-generation en base_model:IlyaGusev/gemma-2-9b-it-abliterated base_model:quantized:IlyaGusev/gemma-2-9b-it-abliterated license:gemma endpoints_compatible region:us imatrix conversational

Related

Total size
16.4 GB
Files
4
Quantizations
3
Registered
2026-08-22 13:56
Last updated on HF
2026-06-12 17:28

Files by quantization

Q8_0 1 file 9.15 GB
gemma-2-9b-it-abliterated-Q8_0.gguf 9.15 GB 820716d0 download
Q6_K 1 file 7.27 GB
gemma-2-9b-it-abliterated-Q6_K_L.gguf 7.27 GB b28c4a2e download
Auxiliary files 2 files 13.8 KB
README.md 10.5 KB d58708eb download
.gitattributes 3.28 KB 7e3285eb download

README current version from Hugging Face


base_model: IlyaGusev/gemma-2-9b-it-abliterated
language:

  • en
    license: gemma
    pipeline_tag: text-generation
    quantized_by: bartowski

Llamacpp imatrix Quantizations of gemma-2-9b-it-abliterated

Using llama.cpp release b3878 for quantization.

Original model: https://huggingface.co/IlyaGusev/gemma-2-9b-it-abliterated

All quants made using imatrix option with dataset from here

Run them in LM Studio

Prompt format

<bos><start_of_turn>system
{system_prompt}<end_of_turn>
<start_of_turn>user
{prompt}<end_of_turn>
<start_of_turn>model
<end_of_turn>
<start_of_turn>model

Download a file (not the whole branch) from below:

Filename Quant type File Size Split Description
gemma-2-9b-it-abliterated-f32.gguf f32 36.97GB false Full F32 weights.
gemma-2-9b-it-abliterated-f32.gguf f32 36.97GB false Full F32 weights.
gemma-2-9b-it-abliterated-Q8_0.gguf Q8_0 9.83GB false Extremely high quality, generally unneeded but max available quant.
gemma-2-9b-it-abliterated-Q6_K_L.gguf Q6_K_L 7.81GB false Uses Q8_0 for embed and output weights. Very high quality, near perfect, recommended.
gemma-2-9b-it-abliterated-Q6_K.gguf Q6_K 7.59GB false Very high quality, near perfect, recommended.
gemma-2-9b-it-abliterated-Q5_K_L.gguf Q5_K_L 6.87GB false Uses Q8_0 for embed and output weights. High quality, recommended.
gemma-2-9b-it-abliterated-Q5_K_M.gguf Q5_K_M 6.65GB false High quality, recommended.
gemma-2-9b-it-abliterated-Q5_K_S.gguf Q5_K_S 6.48GB false High quality, recommended.
gemma-2-9b-it-abliterated-Q4_K_L.gguf Q4_K_L 5.98GB false Uses Q8_0 for embed and output weights. Good quality, recommended.
gemma-2-9b-it-abliterated-Q4_K_M.gguf Q4_K_M 5.76GB false Good quality, default size for must use cases, recommended.
gemma-2-9b-it-abliterated-Q4_K_S.gguf Q4_K_S 5.48GB false Slightly lower quality with more space savings, recommended.
gemma-2-9b-it-abliterated-Q4_0.gguf Q4_0 5.46GB false Legacy format, offers online repacking for ARM and AVX inference.
gemma-2-9b-it-abliterated-Q4_0_8_8.gguf Q4_0_8_8 5.44GB false Optimized for ARM inference. Requires 'sve' support (see link below).
gemma-2-9b-it-abliterated-Q4_0_4_8.gguf Q4_0_4_8 5.44GB false Optimized for ARM inference. Requires 'i8mm' support (see link below).
gemma-2-9b-it-abliterated-Q4_0_4_4.gguf Q4_0_4_4 5.44GB false Optimized for ARM inference. Should work well on all ARM chips, pick this if you're unsure.
gemma-2-9b-it-abliterated-Q3_K_XL.gguf Q3_K_XL 5.35GB false Uses Q8_0 for embed and output weights. Lower quality but usable, good for low RAM availability.
gemma-2-9b-it-abliterated-IQ4_XS.gguf IQ4_XS 5.18GB false Decent quality, smaller than Q4_K_S with similar performance, recommended.
gemma-2-9b-it-abliterated-Q3_K_L.gguf Q3_K_L 5.13GB false Lower quality but usable, good for low RAM availability.
gemma-2-9b-it-abliterated-Q3_K_M.gguf Q3_K_M 4.76GB false Low quality.
gemma-2-9b-it-abliterated-IQ3_M.gguf IQ3_M 4.49GB false Medium-low quality, new method with decent performance comparable to Q3_K_M.
gemma-2-9b-it-abliterated-Q3_K_S.gguf Q3_K_S 4.34GB false Low quality, not recommended.
gemma-2-9b-it-abliterated-IQ3_XS.gguf IQ3_XS 4.14GB false Lower quality, new method with decent performance, slightly better than Q3_K_S.
gemma-2-9b-it-abliterated-Q2_K_L.gguf Q2_K_L 4.03GB false Uses Q8_0 for embed and output weights. Very low quality but surprisingly usable.
gemma-2-9b-it-abliterated-Q2_K.gguf Q2_K 3.81GB false Very low quality but surprisingly usable.
gemma-2-9b-it-abliterated-IQ2_M.gguf IQ2_M 3.43GB false Relatively low quality, uses SOTA techniques to be surprisingly usable.

Embed/output weights

Some of these quants (Q3_K_XL, Q4_K_L etc) are the standard quantization method with the embeddings and output weights quantized to Q8_0 instead of what they would normally default to.

Some say that this improves the quality, others don't notice any difference. If you use these models PLEASE COMMENT with your findings. I would like feedback that these are actually used and useful so I don't keep uploading quants no one is using.

Thanks!

Downloading using huggingface-cli

First, make sure you have hugginface-cli installed:

pip install -U "huggingface_hub[cli]"

Then, you can target the specific file you want:

huggingface-cli download bartowski/gemma-2-9b-it-abliterated-GGUF --include "gemma-2-9b-it-abliterated-Q4_K_M.gguf" --local-dir ./

If the model is bigger than 50GB, it will have been split into multiple files. In order to download them all to a local folder, run:

huggingface-cli download bartowski/gemma-2-9b-it-abliterated-GGUF --include "gemma-2-9b-it-abliterated-Q8_0/*" --local-dir ./

You can either specify a new local-dir (gemma-2-9b-it-abliterated-Q8_0) or download them all in place (./)

Q4_0_X_X

These are NOT for Metal (Apple) offloading, only ARM chips.

If you're using an ARM chip, the Q4_0_X_X quants will have a substantial speedup. Check out Q4_0_4_4 speed comparisons on the original pull request

To check which one would work best for your ARM chip, you can check AArch64 SoC features (thanks EloyOn!).

Which file should I choose?

A great write up with charts showing various performances is provided by Artefact2 here

The first thing to figure out is how big a model you can run. To do this, you'll need to figure out how much RAM and/or VRAM you have.

If you want your model running as FAST as possible, you'll want to fit the whole thing on your GPU's VRAM. Aim for a quant with a file size 1-2GB smaller than your GPU's total VRAM.

If you want the absolute maximum quality, add both your system RAM and your GPU's VRAM together, then similarly grab a quant with a file size 1-2GB Smaller than that total.

Next, you'll need to decide if you want to use an 'I-quant' or a 'K-quant'.

If you don't want to think too much, grab one of the K-quants. These are in format 'QX_K_X', like Q5_K_M.

If you want to get more into the weeds, you can check out this extremely useful feature chart:

llama.cpp feature matrix

But basically, if you're aiming for below Q4, and you're running cuBLAS (Nvidia) or rocBLAS (AMD), you should look towards the I-quants. These are in format IQX_X, like IQ3_M. These are newer and offer better performance for their size.

These I-quants can also be used on CPU and Apple Metal, but will be slower than their K-quant equivalent, so speed vs performance is a tradeoff you'll have to decide.

The I-quants are not compatible with Vulcan, which is also AMD, so if you have an AMD card double check if you're using the rocBLAS build or the Vulcan build. At the time of writing this, LM Studio has a preview with ROCm support, and other inference engines have specific builds for ROCm.

Credits

Thank you kalomaze and Dampf for assistance in creating the imatrix calibration dataset

Thank you ZeroWw for the inspiration to experiment with embed/output

Want to support my work? Visit my ko-fi page here: https://ko-fi.com/bartowski

README history 1 version

The author's README evolved over time. Click a version to see its content at that point.

  1. 2026-06-12Duplicate from bartowski/gemma-2-9b-it-abliterated-GGUF779e4af10.5 KB
    Loading...
Catalog is the map. Apps are the tools.

Run models on your own machine, not in the cloud.

Every model page has an "Open in Abliteration" button that hands the model directly to the first-party desktop client, at the quantization your rig can actually run. No API keys, no subscription, no prompt leakage.

Open in Abliteration