Plain-language explainer
Fine-tuning vs prompting
When should you fine-tune a model, and when is prompting enough?
Prompting changes the input: instructions, examples, retrieved documents, all with frozen weights, instant and reversible. Fine-tuning changes the weights: extra training on your data, often through small LoRA adapters, slower and stickier. The working rule: prompting plus retrieval for knowledge and one-off behavior, fine-tuning for form, when you need a consistent style, format or skill baked in across thousands of calls. Most production systems never need fine-tuning at all.
Do not just read it. Operate the mechanism yourself in a short interactive lesson.
See it work: Fine-tuning vs. prompting →Free, no code, no signup.
What people get wrong
- Fine-tuning is how you teach a model new facts. It is unreliable for knowledge; retrieval into the prompt is the fix for facts.
- Prompting is the amateur option. The strongest production stacks are mostly prompts, examples and retrieval on a frozen model.
- Fine-tuning rewrites the whole model. Modern fine-tuning usually trains a small adapter on top of frozen weights.
Where you see it in real products
- Custom assistant builders are prompt configuration, no weights touched.
- Provider fine-tuning APIs exist for the format-consistency cases.
- Brand bots with a locked voice across millions of replies are the classic fine-tune.
Related explainers
Part of See How AI Works, a free interactive course, where you learn how modern AI works by operating it, not watching videos.