Base model vs instruction-tuned model: what does the user actually feel?
Base = raw next-token predictor over pre-training data. Instruct = base plus SFT on prompt-response pairs plus usually preference tuning. The difference lives in the weights, not in templates or classifiers.
Picture two musicians who graduated from the same conservatory. The base musician knows how to play every scale and copy any style they have heard, but if you ask them to perform at your wedding they might just keep practising scales because nobody told them that a request means perform. The instruction-tuned musician went through extra coaching after the conservatory: a teacher sat with them and walked through 'when someone asks for a wedding song, this is how you respond'. They also learned 'when someone asks you to do something harmful, decline politely'. Both musicians have the same instrument and the same training in music theory. The instruction-tuned one has additional habits baked in through that follow-up coaching.
Detailed answer & concept explanation~9 min readEverything you need to truly understand this topic: intuition, mechanics, step by step explanation, code, formulas, and worked example. Click to expand.
Everything you need to truly understand this topic: intuition, mechanics, step by step explanation, code, formulas, and worked example. Click to expand.
Everything you need to truly understand this topic: intuition, mechanics, step by step explanation, code, formulas, and worked example.
Everything important, quickly.
4 min: pre-training objective + SFT and preference tuning stages + two emergent behaviours (chat-following and refusals) + why the weights actually differ + when to start from base versus instruct.
| Aspect | Base model | Instruction-tuned model |
|---|---|---|
| Training stages | Pre-training only | Pre-training + SFT + usually preference tuning |
| Treats user input as | Document to continue | Request to answer |
| Follows chat templates | Weakly, by pattern matching | Reliably, learned behaviour |
| Refuses unsafe asks | No (unless prompt engineered) | Yes, learned into the weights |
| Right starting point for | Custom fine-tunes with divergent persona | Incremental fine-tunes preserving vendor alignment |
Real products, models, and research that use this idea.
- Llama 4 ships as both Llama 4 Maverick (base) and Llama 4 Maverick Instruct (post-trained); they share architecture and parameter count and differ in the post-training passes Meta applied.
- Qwen 3.5 has the same base/instruct split, with the instruct variant explicitly intended for chat use and the base recommended as a starting point for custom fine-tunes.
- Hugging Face TRL's SFTTrainer plus DPOTrainer is the canonical open-source recipe for taking a base model and producing an instruct variant.
- Anthropic's Claude Opus 4.7 and OpenAI's GPT-5.5 are not released as base models at all; only the post-trained variants are exposed via API, reflecting a deliberate product decision to ship only the instruct-style model.
What an interviewer would ask next. Try answering before peeking at the approach.
QWhy does post-training change behaviour so much when it touches relatively few parameters by tokens-seen?
QWhat is lost when you fine-tune an instruct model further versus fine-tuning the base?
Don't say thisRed flags and common mistakes that signal junior thinking. Click to expand.
Red flags and common mistakes that signal junior thinking. Click to expand.
Thinking the difference is just a chat template or a runtime safety filter. Post-training genuinely updates the weights; the same parameters produce different behaviour because they were optimised for a different objective.
The night-before-the-interview bullets. Scan these on the way to the call.
Primary sources. Skim if you want the original framing.
Same topic, related formats. Practice these next.