Model merging is the arithmetic combination of the parameter sets—typically the task vectors or adapter modules—from multiple fine-tuned models into a single, unified model. This technique, central to parameter-efficient transfer learning, allows a base model to inherit capabilities from several specialized adaptations without the cost of training a massive multi-task model from scratch. The core operation is often a weighted linear interpolation of model weights or adapter parameters.
Glossary
Model Merging

What is Model Merging?
Model merging is a parameter-efficient technique for creating multi-capability models by combining the learned adaptations from multiple fine-tuned models.
The primary goal is to achieve multi-task generalization or improve overall robustness by blending complementary skills. Common methods include task arithmetic, where fine-tuning deltas are added, and merging specialized LoRA or Adapter modules. This approach is highly efficient, as it operates on the small, learned adaptations rather than the full model, enabling rapid prototyping of models with blended expertise for enterprise applications.
Key Model Merging Techniques
Model merging combines the learned adaptations from multiple fine-tuned models into a single, more capable network. These arithmetic and compositional techniques enable multi-task proficiency without the cost of training a model from scratch.
Task Arithmetic
Task arithmetic is a foundational merging technique where the weight differences (task vectors) between fine-tuned models and their shared base model are combined through simple addition and scaling. This method treats model adaptation as a linear operation in weight space.
- Core Operation: A merged model is created as:
W_merged = W_base + Σ(α_i * (W_task_i - W_base)), whereα_iis a scaling coefficient. - Use Case: Efficiently blending competencies from multiple single-task models (e.g., translation, summarization, coding) into a single multi-task model.
- Key Insight: Demonstrates that fine-tuning often moves weights along low-dimensional, roughly linear subspaces, making simple vector arithmetic surprisingly effective.
Model Souping
Model souping involves averaging the weights of multiple models fine-tuned from the same pre-trained checkpoint, often with different hyperparameters or data orders. This technique improves generalization and robustness.
- Process: Simple or weighted arithmetic mean of the parameter sets from multiple fine-tuned checkpoints.
- Benefit: Acts as an implicit ensemble, smoothing loss landscapes and often outperforming the best individual model without extra inference cost.
- Practical Note: Commonly used in competition settings and production to stabilize model performance by merging top-performing checkpoints from a training run.
TIES-Merging
TIES-Merging (TrIm, Elect Sign, and Merge) is an advanced method that addresses interference from conflicting parameter signs when merging multiple task vectors. It is a three-step process for creating a cleaner, more effective merged model.
- TrIm: For each parameter, only retain the top-k% most significant values across all task vectors, trimming away small, potentially noisy updates.
- Elect Sign: Resolve sign conflicts by electing the dominant sign (positive or negative) for each parameter across the trimmed vectors.
- Merge: Average the task vectors after applying the trim and sign consensus filters.
- Result: Significantly outperforms simple task arithmetic when merging many diverse models by reducing negative interference.
DARE & TIES
DARE (Drop And REscale) is a complementary technique often used before TIES-Merging. It randomly drops a large proportion (e.g., 90%) of the values in task vectors to zero and rescales the remaining values to preserve the original vector's norm.
- Purpose: DARE sparsifies task vectors, dramatically reducing redundancy and interference between them. The subsequent merge (like TIES) operates on these sparsified vectors.
- Key Finding: Most parameters in a task vector are redundant; dropping them randomly does not harm, and can even improve, merging performance.
- Workflow: A typical pipeline is DARE (to sparsify) → TIES-Merging (to trim, elect sign, and merge) for robust multi-model fusion.
Adapter Fusion & Composition
This technique merges at the module level rather than the weight level. It combines multiple Adapter or LoRA modules, each trained for a different task, into a single model's architecture.
- AdapterFusion: A two-stage method. First, train multiple independent adapters. Second, add a new fusion layer that learns to combine the outputs of all adapters using an attention mechanism, allowing the model to dynamically leverage different skills.
- Adapter Composition: Directly interpolating or averaging the parameters of multiple adapters to create a unified adapter, or using a router (like in Mixture-of-Adaptors) to select which adapter to use per input.
- Advantage: Enables modular, interpretable merging where specific capabilities are tied to distinct, manipulable components.
Gradient-Based Merging
Gradient-based merging formulates model fusion as an optimization problem. Instead of direct weight arithmetic, it seeks a merged model that minimizes the combined loss on data from all source tasks, using gradient information.
- Process: The merged model's weights are initialized (e.g., from the base model). Gradients are computed from each source model's task loss, and an update step is taken to find a consensus point in weight space that satisfies all tasks.
- Methods: Includes techniques like Fisher Merging, which weights parameter updates by their importance (using the Fisher Information Matrix) to preserve crucial features from each model.
- Use Case: Provides a more principled, performance-driven alternative to arithmetic methods, especially when task conflicts are significant.
How Model Merging Works
Model merging is a technique for creating a single, multi-capable model by arithmetically combining the learned parameters from multiple fine-tuned models.
Model merging is the arithmetic combination of the parameter deltas—the learned changes from fine-tuning—from multiple specialized models into a unified set of weights. This is typically performed on models that share an identical pre-trained base architecture. The core operation is often a simple linear interpolation, such as averaging the weights or task vectors of the source models. This process aims to blend distinct capabilities, like coding and reasoning, into a single model without additional joint training, thereby improving generalization and multi-task performance.
The technique relies on the geometric observation that fine-tuned models often reside in a low-dimensional, task-specific subspace within the broader parameter space. Methods like task arithmetic perform operations on these task vectors to add or subtract competencies. More advanced approaches, such as TIES-Merging, resolve sign conflicts and trim redundant parameters to create a cleaner, more effective merged model. This makes merging a powerful, compute-efficient alternative to multi-task training for building versatile foundation models.
Primary Use Cases for Model Merging
Model merging is not a single technique but a family of methods with distinct objectives. These cards outline its core applications in modern machine learning workflows.
Multi-Task Model Creation
This is the most direct application of model merging. By arithmetically combining task vectors—the weight differences between fine-tuned models and their shared base—a single model can acquire competencies from multiple domains. For example, merging a model fine-tuned for code generation with one fine-tuned for summarization can yield a unified model capable of both tasks. Techniques like task arithmetic and linear mode connectivity underpin this approach, enabling the creation of generalist models from specialist components without multi-task training data.
Improving Generalization & Robustness
Merging multiple models fine-tuned on different subsets or variations of data for the same task can lead to a more robust and generalized final model. This acts as an ensemble method at the parameter level. By averaging the weights of models exposed to diverse data distributions (e.g., different linguistic styles, image corruptions, or sensor noise), the merged model inherits a broader, more stable representation. This reduces overfitting to idiosyncrasies in any single training run and can improve performance on out-of-distribution examples.
Efficient Continual Learning
Model merging provides a pathway for continual learning where a model sequentially learns new tasks without catastrophic forgetting of previous ones. Instead of retraining on all past data, a separate adapter or LoRA module is trained for each new task. These task-specific modules can then be stored and dynamically merged or composed at inference time. Frameworks like AdapterFusion or Mixture-of-Adaptors (MoA) learn to combine these modules, allowing a single model to maintain expertise across a growing library of tasks with minimal parameter overhead.
Knowledge Consolidation from Multiple Sources
In enterprise settings, separate teams may fine-tune a base model on proprietary, domain-specific datasets (e.g., legal documents, medical literature, internal codebases). Model merging allows for the secure consolidation of this decentralized knowledge into a unified corporate model. By merging only the delta parameters (like LoRA matrices) from each specialized model, organizations can create a powerful, multi-domain assistant without ever centralizing the raw, sensitive training data, aligning with privacy-preserving machine learning principles.
Model Specialization & Personalization
The inverse of multi-task creation, this use case involves starting with a large, general-purpose merged model and extracting or refining a component for a specific user or sub-domain. Techniques can involve subtracting a general task vector to reduce unwanted behaviors or merging a global model with a lightly personalized adapter. This is critical for on-device adaptation, where a base model on a smartphone can be quickly personalized by merging a tiny, user-specific delta, enabling efficient hyper-personalization without full retraining.
Architecture Exploration & Model Souping
Merging is used as a tool for neural architecture exploration and performance boosting. Model souping involves averaging the weights of multiple checkpoints from the same training run (taken at different epochs or with different hyperparameters). This simple merge often yields a model with superior performance and stability compared to any single checkpoint. More advanced methods explore merging models with different PEFT configurations (e.g., different LoRA ranks) or from different initializations to discover more optimal regions in the weight space.
Model Merging vs. Alternative Multi-Task Approaches
A technical comparison of methods for achieving multi-task capabilities from a single base model, focusing on architectural, computational, and performance trade-offs.
| Feature / Metric | Model Merging (Task Arithmetic) | Multi-Task Fine-Tuning (MTL) | Mixture-of-Experts (MoE) | Adapter Composition (e.g., AdapterFusion) |
|---|---|---|---|---|
Core Mechanism | Arithmetic combination of fine-tuned weight deltas (task vectors) | Joint training on multiple tasks with a shared backbone | Conditional routing through specialized expert sub-networks | Learned combination of pre-trained, task-specific adapter modules |
Parameter Efficiency | ||||
Requires Joint Multi-Task Data | ||||
Preserves Isolated Task Performance | ||||
Additive Task Capacity | ||||
Primary Compute Cost | Inference-only merging; cost in prior fine-tuning | High (full model training on mixed dataset) | High (maintains large total parameter count) | Moderate (train adapters, then fusion layer) |
Catastrophic Forgetting Risk | None (tasks trained in isolation) | Low (managed via gradient balancing) | Low (experts are specialized) | Low (adapters are frozen) |
Typical Performance on Blended Tasks | 0.5-2% lower than single-task | On par with single-task | 0.1-1% lower than single-task | 1-3% lower than single-task |
Inference Latency Overhead | < 1% | 0% | 30-50% (due to routing logic) | 5-15% (per-adapter forward pass) |
Ease of Adding New Tasks | High (merge new task vector) | Low (requires retraining on all data) | Moderate (add/retrain new expert) | High (train new adapter, update fusion) |
Frequently Asked Questions
Model merging is a core technique in parameter-efficient fine-tuning (PEFT) for creating multi-capability models. This FAQ addresses how it works, its benefits, and its relationship to other PEFT methods.
Model merging is the technique of arithmetically combining the learned parameter changes from multiple fine-tuned models into a single, unified model. It operates on the principle that the knowledge required for a new task can be represented as a directional change, or task vector, from the original pre-trained weights. The most common method is task arithmetic, where the task vectors (fine-tuned weights minus base weights) from different models are simply added to the base model: M_merged = M_base + α*(M_task1 - M_base) + β*(M_task2 - M_base). The scaling factors (α, β) control the influence of each task. This process creates a model that exhibits a blended capability of the source tasks without requiring joint training on all tasks simultaneously.
Enabling Efficiency, Speed & Accuracy
Intelligent Analysis, Decision & Execution
We build AI systems for teams that need search across company data, workflow automation across tools, or AI features inside products and internal software.
Talk to Us
Search across company data
Give teams answers from docs, tickets, runbooks, and product data with sources and permissions.
Useful when people spend too long searching or get different answers from different systems.

Automate internal workflows
Use AI to route work, draft outputs, trigger actions, and keep approvals and logs in place.
Useful when repetitive work moves across multiple tools and teams.

Add AI to products and internal tools
Build assistants, guided actions, or decision support into the software your team or customers already use.
Useful when AI needs to be part of the product, not a separate tool.
Related Terms
Model merging intersects with several key concepts in parameter-efficient adaptation, multi-task learning, and model compression. The following terms define the core techniques and frameworks that enable or are enhanced by merging.
Task Vectors
A task vector is the arithmetic difference between the weights of a model fine-tuned on a specific task and its original pre-trained weights. This vector represents the directional change needed for task adaptation.
- Core to Merging: Model merging techniques like task arithmetic perform linear operations (addition, scaling) on these vectors to combine competencies.
- Example: Adding the task vector for 'translation' and the task vector for 'summarization' to a base model can yield a single model capable of both tasks.
Task Arithmetic
Task arithmetic is a specific model merging technique where task vectors are combined through simple linear operations—such as addition, negation, or scaling—to create a multi-task model or improve generalization.
- Mechanism: If
W_baseis the base model andW_taskis a fine-tuned model, the task vector isτ = W_task - W_base. Merging involves calculatingW_merged = W_base + Σ(α_i * τ_i)whereα_iare scaling coefficients. - Use Case: Enables model soup creation and multi-task inference from a single checkpoint without additional parameters.
Delta Tuning
Delta tuning is the general paradigm of adapting a pre-trained model by learning and applying a small set of parameter changes (the 'delta'), rather than updating all weights. Model merging is a natural extension of this concept.
- Relationship to Merging: Techniques like LoRA, Adapters, and Prefix Tuning all produce a parameter delta. Merging involves combining these deltas (e.g., averaging LoRA matrices) into a unified model.
- Benefit: Provides a modular framework where task-specific deltas can be stored, shared, and arithmetically composed.
Model Soup
Model soup refers to the technique of averaging the weights of multiple models fine-tuned from the same pre-trained checkpoint (often with different hyperparameters or data orders) to create a single, more robust model.
- Simple Merging: A foundational form of weight-space merging that improves generalization and out-of-distribution performance.
- Process: Involves a uniform average or a greedy soup where checkpoints are sequentially added if they improve validation performance.
- Result: Often outperforms the best individual fine-tuned model with zero additional inference cost.
AdapterFusion
AdapterFusion is a two-stage, parameter-efficient method for multi-task learning. It first trains isolated, task-specific adapters, then learns a secondary composition layer to dynamically combine them.
- Composition vs. Merging: Unlike weight arithmetic merging, AdapterFusion performs activation-level merging via an attention mechanism over adapter outputs at inference time.
- Advantage: Allows knowledge transfer between tasks without catastrophic interference, as the base model and original adapters remain frozen.
Mixture of Experts (MoE)
A Mixture of Experts (MoE) model uses a gating network to route each input token to a small subset of specialized 'expert' sub-networks. This is architecturally related to modular adaptation and merging.
- Sparse Activation: Only a few experts are active per token, making the model massively parameter-efficient during inference.
- Connection to Merging: Techniques like Mixture-of-Adaptors (MoA) apply this routing concept to PEFT modules. Model merging can be seen as creating a 'dense' combined expert from multiple specialized ones.

About the author
Prasad Kumkar
CEO & MD, Inference Systems
Prasad Kumkar is the CEO & MD of Inference Systems and writes about AI systems architecture, LLM infrastructure, model serving, evaluation, and production deployment. Over 5+ years, he has worked across computer vision models, L5 autonomous vehicle systems, and LLM research, with a focus on taking complex AI ideas into real-world engineering systems.
His work and writing cover AI systems, large language models, AI agents, multimodal systems, autonomous systems, inference optimization, RAG, evaluation, and production AI engineering.
Partnered with leading AI, data, and software stack.
How We Work
Custom AI workflows for your Business
One-fit-all AI don't work for modern businesses. At Inferensys, we aim to understand your business & custom requirements; which we use to define most efficient agentic workflows, the data, and the tools for your business.
01
Review the use case
We understand the task, the users, and where AI can actually help.
Read more02
Pick the right approach
We define what needs search, automation, or product integration.
Read more03
Build the first useful version
We implement the part that proves the value first.
Read more04
Improve from there
We add the checks and visibility needed to keep it useful.
Read moreThe first call is a practical review of your use case and the right next step.
Talk to Us