Fine-tuning is the process of further training an already-trained language model on a smaller, task-specific dataset so it adapts its behavior, tone, or output format to a narrow use case, changing the model's weights rather than what it is told at call time.
Do you actually need to fine-tune a model?
Probably not first. Most problems people reach for fine-tuning to solve, the model does not know our data, the model does not follow our format, are solved faster and more cheaply by better context engineering: retrieving the right facts through RAG, or simply describing the format in the prompt with a structured output schema. Fine-tuning is the expensive, slow-to-iterate option, best saved for what context alone cannot fix, a consistent voice across thousands of calls, or a narrow classification task run at a cost a frontier model cannot justify.
What does fine-tuning actually change?
It bakes a pattern into the model’s weights instead of supplying it fresh at call time. That trade cuts both ways: the pattern survives without a prompt reminding it every call, but it also stops adapting the moment your data or requirements shift, and retraining means a new dataset, a new training run, and a new evaluation pass, not a one-line prompt edit.
Frequently asked questions
Is fine-tuning the same as prompt engineering?
No. Prompt engineering changes what you tell the model at call time; fine-tuning changes the model's weights through additional training. Prompt engineering is faster to test and reverse, which is why most teams start there.
When does fine-tuning actually pay off?
When context alone cannot fix the problem, usually a consistent style across huge volumes of calls, or a narrow, repetitive task run cheaply on a smaller fine-tuned model instead of a large general one.