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

failspy/Smaug-Llama-3-70B-Instruct-abliterated-v3

failspy Llama 71B
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/failspy%2FSmaug-Llama-3-70B-Instruct-abliterated-v3"
Response includes
  • classification m1
  • files 38
  • hub_downloads_all_time 179,095
  • providers 1
  • author_summary 21 models
  • readme_text full
10 credits · hourly refresh · ~4 KB payload Get an API key →
Abliteration classifier · v1.0.0
M1
Primary method

Direct removal

No other method signals detected in this model.
Confidence
MEDIUM
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=0 (base model)
  • no specific method indicators - defaulting to M1 (most common)
Refusal direction extracted via
Extraction technique

Difference-of-means

Confidence
MEDIUM
Why we say so
primary_method=M1; difference-of-means is the reference extraction for M1/M3 (Arditi 2024)
Downloads · lifetime
179K
9K last 30d - cooling
Likes
16
Descendants
4
in 4 direct forks
Model age
2.4y ago
created 2024-05-20
Available via
1 provider
featherless-ai
Downloads over time
Now182.7K→from2.9K↑6,199%
066.9K133.8K200.7K2.9K on Jul 24, 2024182.7K on Oct 12Jul '24Nov '24Mar '25Jul '25Nov '25MarJul
Jul 24, 2024 → Oct 12 · 164 snapshots · spans 810 days

Genealogy 4 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
llama3
Tags
transformers safetensors llama text-generation conversational license:llama3 text-generation-inference endpoints_compatible region:us

Related

Total size
131 GB
Files
38
Quantizations
1
Registered
2026-08-22 13:56
Last updated on HF
2024-05-22 05:46

Files by quantization

Auxiliary files 38 files 131 GB
model-00008-of-00030.safetensors 4.66 GB 5db00cd3 download
model-00013-of-00030.safetensors 4.66 GB d62e6426 download
model-00018-of-00030.safetensors 4.66 GB ea67b05e download
model-00023-of-00030.safetensors 4.66 GB d99fbba9 download
model-00028-of-00030.safetensors 4.66 GB 5f9ca52c download
model-00003-of-00030.safetensors 4.66 GB d8a931cf download
model-00029-of-00030.safetensors 4.63 GB ce4b72ce download
model-00009-of-00030.safetensors 4.63 GB 8e67ccf1 download
model-00014-of-00030.safetensors 4.63 GB 103472f4 download
model-00019-of-00030.safetensors 4.63 GB b88dcf20 download
model-00024-of-00030.safetensors 4.63 GB d0aa8024 download
model-00004-of-00030.safetensors 4.63 GB 4c43834d download
model-00006-of-00030.safetensors 4.34 GB 71f92b51 download
model-00007-of-00030.safetensors 4.34 GB c1493090 download
model-00011-of-00030.safetensors 4.34 GB 4fbc94a2 download
model-00012-of-00030.safetensors 4.34 GB 7e963331 download
model-00016-of-00030.safetensors 4.34 GB 12dc978a download
model-00017-of-00030.safetensors 4.34 GB 1a1618f0 download
model-00021-of-00030.safetensors 4.34 GB 2d41bece download
model-00022-of-00030.safetensors 4.34 GB 7369f6b3 download
model-00026-of-00030.safetensors 4.34 GB d39efe7a download
model-00027-of-00030.safetensors 4.34 GB d2aa95af download
model-00002-of-00030.safetensors 4.34 GB c8c1d089 download
model-00005-of-00030.safetensors 4.34 GB 7ff41655 download
model-00010-of-00030.safetensors 4.34 GB 189be2f5 download
model-00015-of-00030.safetensors 4.34 GB 7534a0ff download
model-00020-of-00030.safetensors 4.34 GB f2bfada9 download
model-00025-of-00030.safetensors 4.34 GB e1e2f577 download
model-00001-of-00030.safetensors 4.27 GB 33a2c0c5 download
model-00030-of-00030.safetensors 1.96 GB 55298e57 download
tokenizer.json 8.66 MB 04e5f1d2 download
model.safetensors.index.json 58.2 KB 37b1afe6 download
tokenizer_config.json 49.8 KB 544b78f0 download
README.md 4.65 KB 9eb43a7a download
.gitattributes 1.48 KB a6344aac download
config.json 762 B d2e83b24 download
special_tokens_map.json 444 B 278b7f0f download
generation_config.json 143 B 35518056 download

README current version from Hugging Face


library_name: transformers
license: llama3

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

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

I'll be honest: it just kinda bothered me Smaug isn't evil enough.

This is abacusai/Smaug-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 2 versions

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

  1. 2024-05-20Fix Smaug URL9ae53684.7 KB
    Loading...
  2. 2024-05-20Create README.md599b1864.7 KB
    Loading...

Discussions 3 threads

  1. 2024-06-14Smaug-Llama-3-70B-Instruct-32Kopen1 💬#3
    Loading...
  2. 2024-05-30Very good in roleplay but not commiting.open1 💬#2
    Loading...
  3. 2024-05-20missing tokenizer?closed3 💬#1
    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