On this page
Read
The useful mental model
Prompting changes what a model sees for one request. Retrieval adds temporary evidence. Fine-tuning changes learned parameters through a separate training run, producing a model version whose behavior must be tested before it replaces the previous version.
In plain English
It changes an existing model by training it on examples of how you want a particular task performed.
Where builders use it
- 01Consistent structured outputs
- 02Task-specific classification
- 03Specialized response behavior
Why it matters
Fine-tuning can make a repeated behavior more consistent or reduce the instructions needed at inference time. It also creates a new model version that must be evaluated, deployed, and maintained like any other trained artifact.
Why now
Current model platforms offer supervised and preference-based tuning for specialized behavior. Their guidance still starts with a prompt baseline, representative evaluation data, and high-quality training examples before adding the cost and operational work of tuning.
A common misconception
“Fine-tuning is the best way to upload documents so a model always knows their latest facts.”
Fine-tuning changes model behavior through training. Current or frequently changing facts are usually better supplied at request time through prompts or retrieval, where the source can be updated and inspected.
See
See the mental model
The visual is generated from the same structured knowledge as the written explanation.
A base model and reviewed examples enter a separate parameter-update process that produces a tuned model version, which is tested on a holdout evaluation before deployment.
Watch
Watch the explainer
A short visual explanation built from the same reviewed knowledge object.
Fine-tuning: change behavior through training
See how reviewed examples update model parameters, how holdout evaluation protects deployment, and why current facts still belong in the runtime evidence path.
Read transcript
A support prompt fills in the right fields most of the time. Sometimes it misses. Fine-tuning is extra training that teaches an existing model your exact task. First, the team gathers reviewed examples of correct results. They keep some back, called a holdout, to test with later. Training then adjusts the model's internal settings, called parameters, and produces a new version. That version is not trusted yet. It runs on the held-back examples, next to the old prompt. If it does worse, the team blocks it. If it does better, the fields come out more consistently, with shorter instructions. But current policies still arrive with each request, through the prompt or a search step. Fine-tuning changes how a model behaves. It is not where changing facts should live.
Builder example
Improve a repeated extraction task without baking in current facts
A support workflow repeatedly converts varied customer messages into the same reviewed JSON schema, but a prompt with several examples is long and still produces recurring format errors.
Failure
The team fine-tunes on a small, inconsistent dataset and assumes the new model will also remember every future policy change, so format regressions remain and answers become stale.
Intervention
Create representative training and holdout sets from reviewed examples, fine-tune for the extraction behavior, evaluate the new model against the prompt baseline, and continue supplying current policy evidence separately.
Observable result
The evaluated tuned model returns the required schema more consistently with shorter instructions, while policy updates remain available immediately through the runtime evidence path.
Sources
Go deeper
- Google Cloud - Introduction to tuning
- Google for Developers - Fine-tuning, distillation, and prompt engineering
- OpenAI API - Optimizing LLM accuracy
Last researched 11 October 2026