Federated Model Merging is a technique that mathematically combines the weights of multiple models fine-tuned independently on siloed datasets into a single, unified model. Unlike federated averaging, which aggregates gradients during training, model merging operates post-hoc by interpolating parameters in weight space, typically using methods like spherical linear interpolation (SLERP) or task arithmetic. This completely bypasses the need to share raw patient data or synchronize training runs across institutions.
Glossary
Federated Model Merging

What is Federated Model Merging?
A post-training technique that combines the weights of independently fine-tuned models from separate institutions into a single, more robust model without requiring access to the original private training data.
The core mechanism relies on the linear mode connectivity hypothesis, which posits that independently fine-tuned models reside in a shared loss basin. By computing a weighted average or resolving sign conflicts through techniques like TIES-Merging, a merged model can inherit the specialized clinical knowledge from each source institution. This approach is particularly valuable for combining models fine-tuned via federated LoRA or federated PEFT, where only low-rank adapter weights need to be merged, drastically reducing computational overhead while preserving the privacy guarantees of the original decentralized training paradigm.
Key Characteristics of Federated Model Merging
Federated Model Merging is a post-training technique that combines the weights of independently fine-tuned models from disparate institutions into a single, more robust model without requiring access to the original sensitive training data. This approach leverages linear mode connectivity to bypass traditional gradient-based aggregation.
Data-Free Knowledge Amalgamation
Unlike standard federated averaging, model merging operates entirely in the weight space after local training is complete. Institutions fine-tune a shared foundation model on their private clinical data and share only the final delta weights or full model checkpoints. The central server then mathematically interpolates these weights using techniques like spherical linear interpolation (SLERP) or task arithmetic. This completely eliminates the need to transmit gradients or align data distributions during the aggregation phase, providing a strict privacy guarantee by decoupling the act of sharing from the act of training.
Linear Mode Connectivity and Loss Basin Analysis
The success of weight merging relies on the empirical phenomenon of linear mode connectivity, which posits that independently fine-tuned models often reside in the same low-loss basin. Key merging strategies include:
- Spherical Linear Interpolation (SLERP): Blends two models by traversing the geodesic on the hypersphere of weights, preserving magnitude and angular velocity.
- Task Arithmetic: Adds the task-specific 'delta' vectors (fine-tuned weights minus pre-trained weights) to the base model, often scaled by a coefficient.
- TIES-Merging: Resolves interference between delta vectors by trimming low-magnitude changes, resolving sign conflicts, and merging only the aligned components.
Mitigating Interference and Negative Transfer
A primary technical challenge is parameter interference, where the weight updates from different institutions conflict, causing the merged model to perform worse than the individual local models. Advanced merging algorithms actively resolve these conflicts:
- Sign Consensus: Algorithms like TIES-Merging discard weight changes where institutions disagree on the direction (sign) of the update.
- Magnitude Pruning: Low-magnitude weight deltas, which often represent noise rather than generalizable knowledge, are dropped before merging.
- Drop-and-Rescale: Redundant parameter changes are dropped, and the remaining values are rescaled to compensate, preserving the overall signal strength from the collective fine-tuning process.
Computational and Communication Efficiency
Model merging drastically reduces the infrastructure burden compared to iterative federated training. The process requires only a single round of communication after local training is fully complete. There is no need for the complex server orchestration, synchronous gradient aggregation, or straggler mitigation required by standard Federated Averaging. This makes it highly suitable for cross-silo healthcare networks with limited bandwidth or strict firewall policies. Institutions can train at their own pace, and the global model is generated instantly upon receipt of the final checkpoints, enabling a 'train-then-merge' workflow.
Robustness Through Model Soups
A practical application of model merging is the creation of 'Model Soups' . Instead of selecting a single best-performing checkpoint, a server averages the weights of multiple fine-tuned models from different hyperparameter configurations or data subsets. This simple uniform averaging has been shown to improve out-of-distribution generalization and robustness without any additional training. In a federated context, this translates to averaging the final weights from diverse institutional fine-tuning runs, resulting in a global model that is often more resilient to distribution shift than any single institutional model.
Federated Merging vs. Federated Averaging
While both techniques create a global model, their mechanisms differ fundamentally:
- Federated Averaging (FedAvg): Operates during training. It aggregates gradients or model updates iteratively over multiple communication rounds. Requires synchronized training and exposes intermediate model states.
- Federated Model Merging: Operates post-training. It interpolates final model weights in a single step. Training is fully asynchronous and decoupled from the aggregation server. This distinction makes merging a powerful tool for combining models that were never intended to be part of a synchronous federated learning run, such as models fine-tuned on different clinical tasks or modalities.
Federated Model Merging vs. Federated Averaging
A technical comparison of weight-space integration via merging versus parameter-space aggregation via averaging for combining independently trained models across healthcare institutions.
| Feature | Federated Model Merging | Federated Averaging (FedAvg) |
|---|---|---|
Core Mechanism | Post-hoc weight interpolation in parameter space using techniques like spherical linear interpolation (SLERP) or task arithmetic | Iterative weighted averaging of local stochastic gradient descent updates during training rounds |
Training Synchronization | Asynchronous; models are fine-tuned independently and merged afterward | Synchronous; all clients must compute updates within the same communication round |
Communication Overhead | Single-shot exchange of final model weights per institution | Multiple rounds of gradient or parameter transmission proportional to convergence time |
Access to Raw Data During Combination | ||
Handles Non-IID Clinical Distributions | Moderate; relies on linear mode connectivity and weight interpolation heuristics | Strong; mathematically proven convergence under heterogeneous data with sufficient tuning |
Computational Cost at Aggregation | Low; simple vector arithmetic and normalization operations | Higher; requires weighted summation and global model redistribution each round |
Catastrophic Forgetting Risk | Low; preserves specialized local knowledge through interpolation coefficients | Moderate; global model may overwrite site-specific features without personalization |
Primary Use Case in Healthcare | Combining domain-specialized foundation models fine-tuned on different clinical tasks or modalities | Training a single global diagnostic model from scratch across multiple hospital data silos |
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.
Frequently Asked Questions
Clear, technical answers to the most common questions about combining independently fine-tuned models across decentralized healthcare networks without accessing raw patient data.
Federated Model Merging is a post-training technique that combines the weights of multiple models independently fine-tuned on separate institutional datasets into a single, unified model without requiring access to the original training data. The process operates on the principle of weight interpolation in the parameter space. After each hospital fine-tunes a shared base model on its local clinical data, the resulting task-specific weights are transmitted to a central server. An aggregation algorithm—such as linear interpolation, spherical linear interpolation (SLERP), or task arithmetic—mathematically fuses these weight vectors into a new model that exhibits the combined capabilities of all individual contributors. Crucially, this differs from standard federated averaging because the merging occurs after training is complete, not during iterative gradient exchange. The merged model often demonstrates emergent generalization, performing well on tasks it was never explicitly trained on, making it a powerful tool for creating robust multi-institutional diagnostic models without data centralization.
Related Terms
Explore the key techniques and architectural patterns that enable or complement the process of combining independently fine-tuned model weights across decentralized healthcare networks without accessing raw patient data.
Weight Interpolation (LERP/SLERP)
The core mathematical operation in model merging. Linear Interpolation (LERP) computes a weighted average of corresponding parameters from two models. Spherical Linear Interpolation (SLERP) blends weights along a hypersphere, preserving the model's weight norm and often resulting in more stable, higher-quality merges. In a federated context, these operations are performed centrally on aggregated model updates, never on raw data.
Task Vector Arithmetic
A methodology where a model's fine-tuned knowledge is isolated as a task vector—the element-wise difference between the fine-tuned weights and the original pre-trained weights. These vectors can be added, subtracted, or negated to compose model capabilities. Federated task vector merging allows institutions to contribute specific clinical competencies (e.g., radiology report generation) that are arithmetically combined into a single multi-task model.
Federated Averaging (FedAvg) vs. Merging
While both combine model updates, they operate at different stages. FedAvg aggregates gradients or weight updates during training over multiple communication rounds to converge on a single global model. Model merging is a post-hoc technique that combines fully-trained, independently-fine-tuned models in a single operation without iterative communication. Merging is ideal when institutions have already specialized their models locally.
TIES-Merging
Trim, Elect Sign, and Merge. A technique designed to resolve interference between task vectors from different models. It first trims low-magnitude parameter changes to reduce noise, then elects the dominant sign for each parameter across all models to resolve directional conflicts, and finally performs a disjoint merge using only the agreed-upon parameters. This is critical in federated settings where institutions fine-tune on heterogeneous clinical data.
DARE (Drop And REscale)
A pre-processing step before merging that randomly drops a high percentage (e.g., 90-99%) of delta parameters from each task vector and rescales the remaining ones to compensate. This sparsification reduces redundancy and interference between models, often leading to superior merged performance. In federated healthcare, DARE allows merging models from many institutions without catastrophic forgetting.
Federated Model Soups
A simple yet effective merging approach where multiple independently fine-tuned models are averaged uniformly or with validation-set-optimized weights. Unlike complex merging algorithms, model soups require no additional training or hyperparameter tuning. In a federated context, each hospital contributes a fully-trained model, and a central server greedily soups them together, selecting combinations that maximize performance on a held-out validation set.

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