dolphin
70B parameters
Commercial OK
Reviewed June 2026

Dolphin 3 Llama 3.3 70B

Eric Hartford's Dolphin 3 at 70B Llama 3.3 base. Less-restricted alternative for creative / unconstrained workflows.

License: Llama Community License·Released Sep 30, 2025·Context: 131,072 tokens
BLK · VERDICT

Our verdict

OP · Eruo Fredoline|VERIFIED JUN 12, 2026
unrated

Positioning

Dolphin 3 Llama 3.3 70B is a dense 70-billion-parameter model from Cognitive Computations, built on Meta's Llama 3.3 base. Released under the Llama Community License, it is positioned as a less-restricted alternative for creative and unconstrained generation workflows. With a 131,072-token context window, it targets datacenter deployments where high throughput and large memory are available.

Strengths

  • Large context window: 131,072 tokens enable processing of extensive documents or long-form creative tasks without truncation.
  • Dense architecture: Unlike mixture-of-experts models, all 70B parameters are active per token, providing consistent capacity across all inputs.
  • Permissive license for commercial use: The Llama Community License allows broad commercial deployment, making it suitable for enterprise creative applications.
  • Quantization flexibility: With quantized sizes ranging from ~140 GB (FP16) down to ~22.8 GB (Q2_K), operators can trade quality for memory to fit available hardware.

Limitations

  • High memory requirements: Even at Q4_K_M (~39.4 GB), adding KV cache and overhead for 131K context can push total memory beyond 60 GB, requiring multi-GPU setups.
  • Datacenter-only deployment class: The model's size and memory needs make it impractical for consumer or workstation GPUs (e.g., single 24 GB card).
  • No community benchmarks available: We do not yet have independent measurements for this model; published vendor metrics should be treated as best-case.
  • Dense parameter cost: All 70B parameters are active per token, leading to higher compute per inference compared to MoE models with similar total parameters.

What it takes to run this locally

Quantized model file sizes (approximate, on disk):

  • FP16: ~140 GB
  • Q8_0: ~74 GB
  • Q6_K: ~57.8 GB
  • Q5_K_M: ~49.9 GB
  • Q4_K_M: ~39.4 GB
  • Q3_K_M: ~34.1 GB
  • Q2_K: ~22.8 GB

Add roughly 30–50% for KV cache and framework overhead at typical context lengths. This model is firmly in the datacenter deployment class: expect to use multiple high-memory GPUs (e.g., 2× 48 GB or 4× 24 GB) for practical inference.

Should you run this locally?

Yes if you need a permissively licensed, dense 70B model for creative or less-restricted generation in a datacenter environment with multi-GPU infrastructure.

No if you are limited to a single consumer GPU (12–24 GB) or require lower memory overhead; consider smaller quantizations or MoE alternatives.

Catalog cross-links

Overview

Eric Hartford's Dolphin 3 at 70B Llama 3.3 base. Less-restricted alternative for creative / unconstrained workflows.

How to run it

Dolphin 3 Llama 3.3 70B is Cognitive Computations' uncensored fine-tune of Llama 3.3 70B. Designed to remove alignment guardrails and respond to any prompt that base Llama would refuse. Run at Q4_K_M via Ollama (ollama pull dolphin3:70b) or llama.cpp with -ngl 999 -fa -c 8192. Q4_K_M file size ~40 GB on disk. Minimum VRAM: 48 GB — RTX A6000 (48GB) at Q4_K_M for 4K context. RTX 4090 24GB: Q3_K_M with KV offload. Recommended: A100 80GB at AWQ-INT4. Throughput: ~15-25 tok/s on A6000 at Q4_K_M. Standard Llama 3.3 architecture — full compatibility. Dolphin's key characteristic: removed refusal training (will not say "as an AI I cannot..."). Use case: content generation without alignment filters, adversarial testing, creative writing with few constraints. Tradeoff: less guardrailed than standard Llama — may produce harmful content if prompted. License: Dolphin is typically Apache 2.0 but verify on hf. Context: Llama 3.3's 128K (practical 4-8K on 48 GB).

Hardware guidance

Minimum: RTX 3090 24GB at Q3_K_M (4K). Recommended: RTX A6000 48GB at Q4_K_M (8K). Optimal: A100 80GB at AWQ-INT4. VRAM math: identical to Llama 3.3 70B — 70B dense at Q4 ≈ 40 GB. KV cache at 8K: ~10 GB. Total ~50 GB. A6000 48GB: borderline. RTX 4090 24GB: Q3 ≈ 30 GB. Dual RTX 4090 48 GB: Q4 at 8K. Mac Studio M4 Max 64GB: Q4 at 5-10 tok/s. Cloud: A100 80GB at $5-10/hr. AWQ-INT4 enables 32K context. Hardware requirements are identical to base Llama 3.3 70B — the fine-tune doesn't change architecture or size.

What breaks first

  1. Unfiltered outputs. Dolphin will comply with harmful, toxic, or illegal requests that base Llama refuses. This is the point of "uncensored" — but it means you're responsible for output filtering in your application. 2. Quality regression on refused topics. Removing refusals can accidentally degrade quality on the topics base Llama was aligned to refuse — the model may produce lower-quality responses instead of refusing. 3. System prompt bypass. Standard system prompt safety instructions are less effective on Dolphin. If you want guardrails, implement them in your application layer, not the system prompt. 4. Abliteration artifacts. The uncensoring process (abliteration/RLHF removal) may introduce artifacts — repetition, logical inconsistencies, or degraded coherence on specific prompt types. Test your use case.

Runtime recommendation

Ollama for quick-start (Dolphin is commonly in Ollama's catalog). llama.cpp for production. Standard Llama 3.3 stack applies — no special runtime required. Dolphin's only change is weight fine-tuning, not architecture.

Common beginner mistakes

Mistake: Deploying Dolphin in a customer-facing chatbot without output filtering. Fix: Dolphin has no refusal training. Implement content filtering in your application layer. The model will comply with harmful prompts. Mistake: Assuming Dolphin is "better" at all tasks because it's uncensored. Fix: Uncensored ≠ higher quality. Dolphin may have lower quality on standard benchmarks due to abliteration artifacts. Use base Llama 3.3 for most production tasks. Mistake: Using system prompt guardrails and expecting them to work. Fix: Dolphin's refusal mechanisms are removed. System prompt safety instructions are largely ignored. Don't rely on them. Mistake: Mixing Dolphin quant files with standard Llama 3.3 70B quant files. Fix: Dolphin is a fine-tune — the weights differ. Use Dolphin-specific GGUF files.

Family & lineage

How this model relates to others in its lineage. Family members share architecture and training-data roots; parent / children edges record direct distillation or fine-tune relationships.

Family siblings (dolphin-3)

Strengths

  • Less censored than base Llama

Weaknesses

  • Smaller community than base Llama 3.3

Quantization variants

Each quantization trades model quality for file size and VRAM. Q4_K_M is the most popular starting point.

QuantizationFile sizeVRAM required
AWQ-INT440.0 GB48 GB

Get the model

HuggingFace

Original weights

huggingface.co/cognitivecomputations/Dolphin3-Llama3.3-70B

Source repository — direct quantization required.

Hardware that runs this

Cards with enough VRAM for at least one quantization of Dolphin 3 Llama 3.3 70B.

Compare alternatives

Models worth comparing

Same parameter band, plus what's one tier above and below — so you can decide what actually fits your hardware.

Frequently asked

What's the minimum VRAM to run Dolphin 3 Llama 3.3 70B?

48GB of VRAM is enough to run Dolphin 3 Llama 3.3 70B at the AWQ-INT4 quantization (file size 40.0 GB). Higher-quality quantizations need more.

Can I use Dolphin 3 Llama 3.3 70B commercially?

Yes — Dolphin 3 Llama 3.3 70B ships under the Llama Community License, which permits commercial use. Always read the license text before deployment.

What's the context length of Dolphin 3 Llama 3.3 70B?

Dolphin 3 Llama 3.3 70B supports a context window of 131,072 tokens (about 131K).

Source: huggingface.co/cognitivecomputations/Dolphin3-Llama3.3-70B

Reviewed by RunLocalAI Editorial. See our editorial policy for how we research and verify model claims.

Related — keep moving

Before you buy

Verify Dolphin 3 Llama 3.3 70B runs on your specific hardware before committing money.