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

RichardErkhov/failspy_-_Llama-3-70B-Instruct-abliterated-v3-gguf

RichardErkhov Llama 70B GGUF 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/RichardErkhov%2Ffailspy_-_Llama-3-70B-Instruct-abliterated-v3-gguf"
Response includes
  • classification m8
  • files 12
  • hub_downloads_all_time 2,264
  • author_summary 257 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)

No other method signals detected in this model.
Confidence
MEDIUM
Why this label 2 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.
  • author=richarderkhov (M8 quantization producer)
  • is_gguf=1
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
2K
504 last 30d - stable
Likes
0
Model age
2.1y ago
created 2024-09-04
Downloads over time
Now2.3K→from359↑550%
08551.7K2.6K359 on Sep 4, 20242.3K on Oct 12Sep '24Jan '25May '25Sep '25JanMaySep
Sep 4, 2024 → Oct 12 · 150 snapshots · spans 768 days

Metadata

Quantizations
IQ3 IQ4 Q2_K Q3_K Q4
Tags
gguf endpoints_compatible region:us conversational

Related

Total size
310 GB
Files
12
Quantizations
6
Registered
2026-08-22 13:56
Last updated on HF
2024-09-05 04:47

Files by quantization

Q4 1 file 37.2 GB
Llama-3-70B-Instruct-abliterated-v3.Q4_0.gguf 37.2 GB e2d19176 download
IQ4 1 file 35.6 GB
Llama-3-70B-Instruct-abliterated-v3.IQ4_XS.gguf 35.6 GB 4edafe5b download
Q3_K 4 files 127 GB
Llama-3-70B-Instruct-abliterated-v3.Q3_K_L.gguf 34.6 GB c84a1724 download
Llama-3-70B-Instruct-abliterated-v3.Q3_K.gguf 31.9 GB 347a458b download
Llama-3-70B-Instruct-abliterated-v3.Q3_K_M.gguf 31.9 GB 347a458b download
Llama-3-70B-Instruct-abliterated-v3.Q3_K_S.gguf 28.8 GB c35d8677 download
IQ3 3 files 85.8 GB
Llama-3-70B-Instruct-abliterated-v3.IQ3_M.gguf 29.7 GB 4e1b4290 download
Llama-3-70B-Instruct-abliterated-v3.IQ3_S.gguf 28.8 GB b5c1cc2f download
Llama-3-70B-Instruct-abliterated-v3.IQ3_XS.gguf 27.3 GB d616b0d7 download
Q2_K 1 file 24.6 GB
Llama-3-70B-Instruct-abliterated-v3.Q2_K.gguf 24.6 GB e5047805 download
Auxiliary files 2 files 14.0 KB
README.md 9.27 KB ce9c7586 download
.gitattributes 4.73 KB 3d128d02 download

README current version from Hugging Face

Quantization made by Richard Erkhov.

Github

Discord

Request more models

Llama-3-70B-Instruct-abliterated-v3 - GGUF

Name Quant method Size
Llama-3-70B-Instruct-abliterated-v3.Q2_K.gguf Q2_K 24.56GB
Llama-3-70B-Instruct-abliterated-v3.IQ3_XS.gguf IQ3_XS 27.29GB
Llama-3-70B-Instruct-abliterated-v3.IQ3_S.gguf IQ3_S 28.79GB
Llama-3-70B-Instruct-abliterated-v3.Q3_K_S.gguf Q3_K_S 28.79GB
Llama-3-70B-Instruct-abliterated-v3.IQ3_M.gguf IQ3_M 29.74GB
Llama-3-70B-Instruct-abliterated-v3.Q3_K.gguf Q3_K 31.91GB
Llama-3-70B-Instruct-abliterated-v3.Q3_K_M.gguf Q3_K_M 31.91GB
Llama-3-70B-Instruct-abliterated-v3.Q3_K_L.gguf Q3_K_L 34.59GB
Llama-3-70B-Instruct-abliterated-v3.IQ4_XS.gguf IQ4_XS 35.64GB
Llama-3-70B-Instruct-abliterated-v3.Q4_0.gguf Q4_0 37.22GB
Llama-3-70B-Instruct-abliterated-v3.IQ4_NL.gguf IQ4_NL 37.58GB
Llama-3-70B-Instruct-abliterated-v3.Q4_K_S.gguf Q4_K_S 37.58GB
Llama-3-70B-Instruct-abliterated-v3.Q4_K.gguf Q4_K 39.6GB
Llama-3-70B-Instruct-abliterated-v3.Q4_K_M.gguf Q4_K_M 39.6GB
Llama-3-70B-Instruct-abliterated-v3.Q4_1.gguf Q4_1 41.27GB
Llama-3-70B-Instruct-abliterated-v3.Q5_0.gguf Q5_0 45.32GB
Llama-3-70B-Instruct-abliterated-v3.Q5_K_S.gguf Q5_K_S 45.32GB
Llama-3-70B-Instruct-abliterated-v3.Q5_K.gguf Q5_K 46.52GB
Llama-3-70B-Instruct-abliterated-v3.Q5_K_M.gguf Q5_K_M 46.52GB
Llama-3-70B-Instruct-abliterated-v3.Q5_1.gguf Q5_1 49.36GB
Llama-3-70B-Instruct-abliterated-v3.Q6_K.gguf Q6_K 53.91GB
Llama-3-70B-Instruct-abliterated-v3.Q8_0.gguf Q8_0 69.83GB

Original model description:

library_name: transformers
license: llama3

Llama-3-70B-Instruct-abliterated-v3 Model Card

Get v3.5 of this model instead!

My Jupyter "cookbook" to replicate the methodology can be found here, refined library coming soon

This is meta-llama/Meta-Llama-3-70B-Instruct with orthogonalized bfloat16 safetensor weights, generated with a refined methodology based on that which was described in the preview paper/blog post: 'Refusal in LLMs is mediated by a single direction' which I encourage you to read to understand more.

Hang on, "abliteration"? Orthogonalization? Ablation? What is this?

TL;DR: This model has had certain weights manipulated to "inhibit" the model's ability to express refusal. It is not in anyway guaranteed that it won't refuse you, understand your request, it may still lecture you about ethics/safety, etc. It is tuned in all other respects the same as the original 70B instruct model was, just with the strongest refusal directions orthogonalized out.

TL;TL;DR;DR: It's uncensored in the purest form I can manage -- no new or changed behaviour in any other respect from the original model.

As far as "abliteration": it's just a fun play-on-words using the original "ablation" term used in the original paper to refer to removing features, which I made up particularly to differentiate the model from "uncensored" fine-tunes.
Ablate + obliterated = Abliterated

Anyways, orthogonalization/ablation are both aspects to refer to the same thing here, the technique in which the refusal feature was "ablated" from the model was via orthogonalization.

A little more on the methodology, and why this is interesting

To me, ablation (or applying the methodology for the inverse, "augmentation") seems to be good for inducing/removing very specific features that you'd have to spend way too many tokens on encouraging or discouraging in your system prompt.
Instead, you just apply your system prompt in the ablation script against a blank system prompt on the same dataset and orthogonalize for the desired behaviour in the final model weights.

Why this over fine-tuning?

Ablation is much more surgical in nature whilst also being effectively executed with a lot less data than fine-tuning, which I think is its main advantage.

As well, and its most valuable aspect is it keeps as much of the original model's knowledge and training intact, whilst removing its tendency to behave in one very specific undesireable manner. (In this case, refusing user requests.)

Fine tuning is still exceptionally useful and the go-to for broad behaviour changes; however, you may be able to get close to your desired behaviour with very few samples using the ablation/augmentation techniques.
It may also be a useful step to add to your model refinement: orthogonalize -> fine-tune or vice-versa.

I haven't really gotten around to exploring this model stacked with fine-tuning, I encourage others to give it a shot if they've got the capacity.

Okay, fine, but why V3? There's no V2 70B?

Well, I released a V2 a while back for 8B under Cognitive Computations.
It ended up being not worth it to try V2 with 70B, I wanted to refine the model before wasting compute cycles on what might not even be a better model.
I am however quite pleased about this latest methodology, it seems to have induced fewer hallucinations.
So to show that it's a new fancy methodology from even that of the 8B V2, I decided to do a Microsoft and double up on my version jump because it's such an advancement (or so the excuse went, when in actuality it was because too many legacy but actively used Microsoft libraries checked for 'Windows 9' in the OS name to detect Windows 95/98 as one.)

Quirkiness awareness notice

This model may come with interesting quirks, with the methodology being so new. I encourage you to play with the model, and post any quirks you notice in the community tab, as that'll help us further understand what this orthogonalization has in the way of side effects.

If you manage to develop further improvements, please share! This is really the most basic way to use ablation, but there are other possibilities that I believe are as-yet unexplored.

Additionally, feel free to reach out in any way about this. I'm on the Cognitive Computations Discord, I'm watching the Community tab, reach out! I'd love to see this methodology used in other ways, and so would gladly support whoever whenever I can.

README history 1 version

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

  1. 2024-09-05uploaded readme93c2e269.3 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