ModelRefs / Adapter (PEFT) — AI Glossary
Adapter (PEFT) — AI Glossary
Small trainable modules inserted between transformer layers, enabling parameter-efficient fine-tuning with <1% of full model parameters.
Overview
Adapters (Houlsby et al. 2019) insert bottleneck MLP layers in each transformer block. Only adapter weights are updated; the base model is frozen. LoRA generalizes this to low-rank weight-matrix updates. Adapters allow multiple task specializations to share a single frozen base model, swapping adapter weights per task at inference time.
Reference details
| Topic | training |
|---|---|
| Also known as | PEFT adapter, bottleneck adapter |
| Last reviewed | 2026-06-24 |
Related terms
How it works
- A bottleneck module is inserted into each transformer block: a down-projection to a small dimension, a nonlinearity, and an up-projection back to the model width.
- Only those modules are trained and the base weights stay frozen, so the gradient and optimiser footprint is proportional to the inserted parameters rather than the model.
- The up-projection is initialised near zero and the module is wrapped in a residual connection, which makes the untrained adapter an approximate identity and training start from the base model's behaviour.
- Because the module sits in series within the block, it adds computation to every forward pass — which is the structural difference from a low-rank update that can be folded into the existing weights.
- That series placement is also what cannot be merged away: an adapter's latency cost is permanent while a merged low-rank update's is zero.
- In exchange, several adapters can be held beside one resident base model and selected per request, so switching behaviour is loading a few megabytes rather than a second model.
Example: One base model, many behaviours
Keep one frozen base in memory and load a small adapter per task — support tone, code review, summarisation. Swapping tasks means swapping a few megabytes rather than loading a new multi-gigabyte model. That is the operational argument for adapters, independent of training cost.
Commonly confused with
Adapters and LoRA are related but not identical. Classic adapters insert new bottleneck layers into each block; LoRA adds low-rank updates to existing weight matrices and can be merged back into the base at inference. LoRA is the more common form today, and adapter is often used loosely to mean both.
When to use it
Reach for it when:
- Several task variants must share one base model in memory
- Adapters need independent versioning and rollback
- Full fine-tuning is not affordable
Reach for something else when:
- The change is broad and general rather than task-specific
- You have not tried prompting or retrieval first
- There is no evaluation to catch a quietly worse adapter
Primary source
Continue your research
Use these connected ModelRefs sections to compare alternatives, inspect implementation paths, and review the evidence and governance boundaries relevant to Adapter (PEFT) — AI Glossary.
Frequently asked questions
What is Adapter (PEFT)?
Small trainable modules inserted between transformer layers, enabling parameter-efficient fine-tuning with <1% of full model parameters.
Is Adapter (PEFT) the same as PEFT adapter?
Yes — PEFT adapter, bottleneck adapter are common aliases for Adapter (PEFT).
What concepts are related to Adapter (PEFT)?
Closely related concepts include lora, prefix tuning, sft.