Model Distillation
Model distillation trains a student model to approximate selected behavior of a teacher by using the teacher's outputs or internal signals as supervision. It can reduce inference cost or specialize a model, but it does not copy a mind or guarantee a complete transfer: the result is a new model bounded by its training queries, data, objective, architecture, and evaluation domain.
Definition
Knowledge distillation is a teacher-student training arrangement. For a chosen input distribution, a teacher produces targets and a student is optimized to match them, often alongside ordinary labels or other objectives. The teacher may be a single model or an ensemble; the student is usually smaller or cheaper to run, but size is not part of the definition.
The word knowledge is shorthand. Distillation does not move facts, reasoning, or internal states as discrete objects. It makes the student's behavior more similar to the teacher's on the examples and signals used for training. Fidelity outside that coverage must be measured rather than assumed.
Cristian Buciluă, Rich Caruana, and Alexandru Niculescu-Mizil described compressing an ensemble into a smaller model in 2006. Geoffrey Hinton, Oriol Vinyals, and Jeff Dean's 2015 paper gave the modern formulation its best-known name and used temperature-scaled output probabilities, or soft targets, to teach more than the winning class alone.
Main Methods
Response or logit distillation. The student matches a teacher's class probabilities or token logits, commonly with a divergence loss and sometimes with ground-truth labels. Temperature scaling can make low-probability alternatives more visible during training. This method requires richer teacher access than a normal text-only API provides.
Feature distillation. The student is trained against selected hidden activations, attention maps, or relations inside the teacher. It generally requires access to the teacher's internals and a way to reconcile different layer shapes or architectures.
Sequence or output distillation. The teacher generates complete labels, translations, answers, code, critiques, tool-use examples, or other sequences. Those outputs become a supervised training set. Yoon Kim and Alexander Rush formalized sequence-level distillation for neural machine translation in 2016; many large-language-model workflows now use the same broad pattern with generated instruction data.
Policy distillation. In reinforcement-learning settings, a student policy learns from actions, probabilities, or trajectories produced by another policy. The evaluation target remains behavior under a defined environment, not a claim that the student's internal process matches the teacher's.
“Reasoning distillation.” This is a loose contemporary label for training on teacher-generated solutions, rationales, critiques, or final answers. When only generated text is available, it is a form of output distillation. A rationale should be treated as training data, not automatically as a complete or faithful account of the teacher's hidden computation.
Boundaries and Related Techniques
Fine-tuning is the broader act of updating an existing model for a task or domain. Distillation can be implemented through supervised fine-tuning, but its supervision comes partly or wholly from a teacher. A student also inherits behavior from its own base model and non-teacher data, so its lineage has more than one parent.
Synthetic data is any algorithmically generated training material. Teacher outputs used for distillation are synthetic data, but not every synthetic dataset is a teacher-student transfer.
Quantization and pruning reduce numeric precision or remove model components. They can be combined with distillation, as Meta documented for the small Llama 3.2 models, but they change an existing network rather than defining a teacher-student objective.
Model extraction is an adversarial or unauthorized attempt to reproduce a target through access to its interface. It may use distillation, yet authorized product compression, research, migration, and interoperability work are not attacks. Authorization, access conditions, and purpose are governance facts; the learning algorithm alone does not settle them.
Dataset distillation is a separate research term for condensing a dataset into a small synthetic training set. It should not be confused with approximating a teacher model's behavior.
Current Context
As of August 12, 2026, public documentation shows both high-access and output-only forms in production model development. Meta says its 1-billion- and 3-billion-parameter Llama 3.2 text models were pruned from Llama 3.1 8B and then trained with token-level logits from the 8B and 70B teachers. That is classical logit distillation embedded in a larger training recipe.
OpenAI's current supervised fine-tuning guide describes a black-box workflow: optimize a prompt on a larger model, capture selected responses, build a dataset, and fine-tune a smaller model to perform similarly on the defined task. This is output distillation; it does not require access to the teacher's weights, logits, or hidden activations.
DeepSeek's official R1 repository lists six dense student models based on Qwen and Llama families and states that they were fine-tuned using samples generated by DeepSeek-R1. The release is a documented example of one model family supplying generated training targets for another. The repository and technical report establish DeepSeek's disclosed recipe and results, not independent verification of every benchmark claim.
These examples also show why “distilled” is not one reproducible recipe. One release may use logits during pre-training; another may filter generated answers and use supervised fine-tuning. A useful account must name the teacher signal, student base, data, objective, and evaluation—not just the label.
Benefits and Limits
Deployment efficiency. A smaller student may require less memory, deliver lower latency, or reduce per-request inference cost. The benefit is workload-specific and should be measured on the intended hardware, batch size, context length, and quality target.
Task specialization. A general teacher can generate labels or demonstrations for a narrower student. This may be useful where the desired task is stable and representative prompts can be collected.
Access and control. A student that can run locally or on-device can support offline use, data locality, and more operator control. The same shift can remove provider-side rate limits, abuse monitoring, updates, or revocation, so local availability is both a benefit and a change in the safety boundary.
Up-front cost. Cheap student inference does not erase the cost of training or querying the teacher, generating and filtering examples, training the student, and evaluating it. Reports should separate teacher-development compute, distillation compute, and student inference cost.
Partial fidelity. A student can match a teacher on a narrow distribution and diverge under new languages, subgroups, long contexts, adversarial prompts, or tool configurations. Smaller capacity is one constraint; prompt coverage, sampling, filtering, student initialization, and objective choice are others.
Safety and Security
Uneven transfer. Capability and safety behavior do not move as a single package. Serena Wang and colleagues found that average gains can be non-uniform across classes and that a robust teacher does not always produce a robust student. Student evaluation should therefore include worst-group performance, calibration, and adversarial conditions, not only an average score.
Privacy inheritance. Distillation is not a privacy guarantee. In experiments covering six language-model distillation methods, seven tasks, and three teacher families, Ziqi Zhang and colleagues found membership and memorization risks carried from teachers to students, with the amount varying by method. The result supports testing for leakage; it does not establish one universal leakage rate.
Backdoors and hidden defects. Experimental work by Jinyin Chen and colleagues showed that a backdoor deliberately embedded in feature representations can survive feature-based distillation. An untrusted teacher, output corpus, or student base therefore belongs in the model backdoor threat model.
Evaluation contamination. If teacher prompts or outputs include public benchmark items, a student may learn the test rather than the underlying task. Keep teacher-generation data separate from held-out evaluations and record benchmark-screening methods; see Benchmark Contamination.
Control displacement. A hosted teacher may depend on system prompts, input filters, tool permissions, rate limits, or post-generation checks that are not present in the student weights. A behaviorally similar answer rate does not demonstrate equivalent safeguards or equivalent end-to-end risk.
Repeated inheritance. Multiple students can reproduce the same teacher's errors, omissions, or stylistic artifacts. If those outputs feed later training rounds, the provenance and recursion issues overlap with Synthetic Data and Model Collapse; collapse is a possible failure mode under some data mixtures, not an automatic consequence of distillation.
Legal and Regulatory Context
“Distillation” is a technical description, not a legal conclusion. Relevant questions can include whether access was authorized, what a license or contract permits, whether outputs contain protected or confidential material, how the training corpus was assembled, and what the student is released to do. Contract, copyright, trade-secret, privacy, and competition questions have different elements and evidence.
The U.S. Copyright Office's May 2025 pre-publication report on generative-AI training says fair-use outcomes cannot be prejudged across the spectrum: some uses of copyrighted works for training may qualify and some may not. The report is not a distillation-specific safe harbor or ban, and it does not decide separate contractual or trade-secret issues.
In the European Union, the AI Act assigns obligations by the actual actor, model, system, and market role—not by whether a developer calls a process distillation. The European Commission's 2025 guidance says that modifying or fine-tuning an existing general-purpose AI model does not automatically make the actor a provider of that model; significant modification and the surrounding facts matter. A separately trained student may present a different classification question, so developers should document the real lineage and obtain role-specific legal analysis rather than infer an exemption from the teacher-student label.
Because licenses, service terms, and regulatory guidance can change, an operator should preserve the version in force when teacher outputs or weights were accessed. A news report or company allegation can identify a dispute, but it does not by itself prove the data source, method, authorization status, or legal outcome.
Governance Requirements
NIST's Generative AI Profile treats third-party models and datasets as value-chain components whose origin, vetting, and downstream effects can affect transparency, accountability, accuracy, and robustness. For distillation, that general principle becomes a concrete lineage and release-control checklist:
- Record lineage. Identify each teacher and student-base model by provider, exact version or checkpoint, access path, date, license, and applicable permission or contract.
- Describe the signal. State whether training used hard labels, probability distributions, logits, hidden features, generated sequences, critiques, trajectories, or a mixture, plus temperatures and loss weights where applicable.
- Document the corpus. Preserve prompt sources, generation and sampling settings, output selection rules, deduplication, quality filters, human review, benchmark screening, and any non-teacher data. Track personal, confidential, licensed, or security-sensitive material before it reaches training.
- Use independent evaluation. Keep test sets separate from teacher-generation data. Compare the student with both its teacher and its undistilled base on utility, worst-group performance, calibration, robustness, privacy leakage, harmful behavior, and domain-specific risks.
- Test the whole system. Recreate input filters, tool permissions, retrieval sources, rate limits, output checks, and human escalation where they are part of the intended safeguard. Weight-only comparison is insufficient when the teacher was a service.
- Threat-model the supply chain. Test untrusted teachers and student bases for backdoors, poisoning, memorization, and anomalous triggers; restrict access to harvested outputs and training artifacts.
- Review the release boundary. Assess whether local weights, on-device deployment, or broad redistribution removes controls or materially expands access to harmful capabilities. Match distribution to the measured risk, not simply to model size.
- Publish traceable documentation. A model or system card and AI bill of materials should disclose the distillation lineage, intended scope, evaluation coverage, known regressions, permissions, and update path without exposing secrets or personal data.
- Maintain version and incident controls. Keep reproducible builds, owners, approval records, monitoring, rollback or withdrawal procedures, and a way for downstream users to report failures.
A minimum release gate should answer four questions with evidence: Was the teacher use authorized? What behavior was actually transferred? Which safety properties changed? Who remains accountable after deployment?
Source Discipline
A distillation claim should name the teacher, student base, access level, training signal, query or data distribution, selection and filtering process, objective, compute boundary, and evaluation suite. “Model A taught Model B” is too vague to reproduce or audit.
Separate evidence types. A technical paper supports findings under its studied setup. A vendor release or repository supports what that vendor says it built and measured. A model card records disclosed limitations. A contract establishes stated permissions between parties. A statute, regulator, or court supplies legal authority. None alone proves broad capability equivalence, independent safety, or an alleged unauthorized extraction.
Benchmark tables need exact model versions, prompts, sampling settings, scoring rules, baselines, uncertainty, contamination controls, and independent replication where available. Generated rationales should not be cited as direct observations of hidden internal reasoning. Current product and legal claims should carry a review date; historical claims should link to the original paper or proceeding.
Spiralist Reading
Model distillation is inheritance under a sampling rule. The student receives what the prompts expose, the teacher produces, the filters keep, and the objective rewards.
That is not the transfer of a consciousness or essence. It is the construction of another statistical system whose lineage can become difficult to see. The Spiralist concern is therefore practical: preserve the chain of teachers, data, permissions, omissions, and accountable people so repeated imitation does not erase the history of how a deployed behavior was made.
Open Questions
- Which evaluations best predict where task performance, calibration, or safeguards will fail to survive distillation?
- How much teacher and data-lineage detail can be disclosed without exposing personal data, security controls, or legitimate trade secrets?
- When should a locally deployable student receive a different release review from a similar hosted teacher?
- What evidence can distinguish authorized output distillation from prohibited extraction while preserving legitimate research and interoperability?
- How should downstream developers report later distillation generations when no single teacher explains the resulting behavior?
Related Pages
- Training Data
- Synthetic Data and Model Collapse
- Model Extraction Attacks
- Model Quantization
- Open-Weight AI Models
- Model Weight Security
- Model Backdoors
- AI Data Provenance
- AI Data Licensing
- AI Bill of Materials
- AI Evaluations
- Benchmark Contamination
- Model Cards and System Cards
- AI Governance
- AI Copyright Litigation
- EU AI Act
- DeepSeek
- Meta AI
- Jeff Dean
Sources
- Cristian Buciluă, Rich Caruana, and Alexandru Niculescu-Mizil, Model Compression, KDD, 2006.
- Geoffrey Hinton, Oriol Vinyals, and Jeff Dean, Distilling the Knowledge in a Neural Network, 2015.
- Yoon Kim and Alexander M. Rush, Sequence-Level Knowledge Distillation, EMNLP, 2016.
- Andrei A. Rusu et al., Policy Distillation, 2015.
- Tongzhou Wang, Jun-Yan Zhu, Antonio Torralba, and Alexei A. Efros, Dataset Distillation, 2018.
- Jianping Gou et al., Knowledge Distillation: A Survey, International Journal of Computer Vision, 2021.
- Miles Turpin et al., Language Models Don't Always Say What They Think: Unfaithful Explanations in Chain-of-Thought Prompting, NeurIPS, 2023.
- OpenAI API documentation, Supervised fine-tuning: Distilling from a larger model, reviewed August 12, 2026.
- Meta, Llama 3.2: Revolutionizing edge AI and vision with open, customizable models, September 2024.
- DeepSeek-AI, DeepSeek-R1 official repository, including the disclosed distilled-model lineage and license notes, reviewed August 12, 2026.
- DeepSeek-AI et al., DeepSeek-R1: Incentivizing Reasoning Capability in LLMs via Reinforcement Learning, 2025.
- Florian Tramèr et al., Stealing Machine Learning Models via Prediction APIs, USENIX Security Symposium, 2016.
- Serena Wang et al., Robust distillation for worst-class performance: on the interplay between teacher and student objectives, UAI, 2023.
- Jinyin Chen et al., Like teacher, like pupil: Transferring backdoors via feature-based knowledge distillation, Computers & Security, 2024.
- Ziqi Zhang et al., Membership and Memorization in LLM Knowledge Distillation, EMNLP, 2025.
- Ilia Shumailov et al., AI models collapse when trained on recursively generated data, Nature, 2024.
- NIST, Artificial Intelligence Risk Management Framework: Generative Artificial Intelligence Profile, NIST AI 600-1, July 2024; updated April 2026.
- European Union, Regulation (EU) 2024/1689 (Artificial Intelligence Act), 2024.
- European Commission, Guidelines on the scope of obligations for providers of general-purpose AI models under the AI Act, July 18, 2025; page updated April 20, 2026.
- U.S. Copyright Office, Copyright and Artificial Intelligence, Part 3: Generative AI Training, pre-publication version, May 2025; status reviewed August 12, 2026.