Merge IFC, RVT, NWD Files

Combine multiple IFC, Revit or Navisworks files into a single federated IFC model.

Besides IFC, this tool takes Revit (.rvt) and Navisworks (.nwd) files, with no Revit or Navisworks licence. Drop one in and it is converted to IFC first, then the tool runs on that IFC; your original file is not changed.

Merge IFC files online — combine up to 10 IFC files into a single federated model in your browser. The typical job is discipline federation: the architecture, structure, MEP, and facade teams each export their own IFC, and you need one coordinated file for review, clash detection, or delivery.

There's no desktop coordination software to install and no per-seat licence: upload the primary file, add the others, run, and download one merged IFC that opens in any buildingSMART-compatible tool.

When to reach for it: When you need to combine separate discipline models (architecture + structure + MEP) into a single federated file for review or coordination.

What you get: A single IFC file containing all elements from every input file combined into one model.

Example: Merge architecture + structure + MEP models into a federated file.

Why merge IFC files into one model?

Discipline models are authored apart but reviewed, checked, and delivered together. At some point almost every openBIM workflow needs the separate exports combined into a single file. One merge job takes a primary IFC plus up to nine additional files, so a full ARC + STR + MEP + FAC federation fits in a single run:

One coordination model — clash detection and clearance checks need every discipline in the same file to find pipe-through-beam conflicts.
One deliverable — many handover and review workflows expect a single federated IFC rather than a folder of per-discipline exports.
One share link — a merged model can be shared as a single read-only browser viewer link for stakeholders who don't run BIM software.
One pipeline input — downstream steps (validate, optimise, export) run once on the federation instead of once per discipline file.

What survives the merge

Properties, property sets, classifications, and type definitions from every source file are carried into the merged IFC. Duplicate GlobalIds across files are de-duplicated so downstream tools don't choke on the federation.

Coordinates are preserved exactly as each discipline authored them. If the source files share a common project origin they line up automatically; if disciplines modelled against different origins, the merged model will reflect that offset — the merge never silently re-bases anyone's geometry. When alignment is off, fix the origin in the offending source (the Repair Center's coordinate fix handles the common far-from-origin case) and re-run the merge.

Pre-clean each source during the merge

Each additional file can be cleaned in place before it's combined: keep only physical elements (drop spaces, grids, annotations), delete specific IFC classes, strip materials, or strip property sets — configured per source file, all in one run. A federation of consultant models can each get a different cleanup without a separate pre-processing pass.

For recurring federations, save the whole thing as a pipeline: merge the four discipline files, run clash detection on the result, and re-run the recipe on every revision.

Do you need a merged file — or a live federation?

Merging produces one physical IFC file — the right shape for delivery, archiving, clash runs, and any tool that expects a single input. But if the goal is just to look at several discipline models together, BIMCamel's workspace can also federate models in the viewer without writing a combined file: registered accounts can view up to 5 member models together, Pro and Team up to 10, each keeping its own identity and revision history.

A useful rule of thumb: federate for day-to-day review, merge when something downstream — a deliverable, a clash report, a share link, a pipeline — needs one file.

Using it on Revit and Navisworks files

When you open a .rvt or a .nwd file here, BIMCamel converts it to IFC on the server and brings you back to this tool with the converted model loaded. Element ids, levels and properties come across under their Revit and Navisworks names, so pick properties as they appear in your model. Your .rvt or .nwd itself is never edited: a tool that changes the model gives you an IFC back.

On Revit and Navisworks files: A file in another IFC version or length unit is converted to match the first file before it is merged, and the job log says what was converted.

Revit files can be up to 25 MB without an account, 100 MB with a free one and 200 MB on a paid plan. Navisworks files can be up to 25 MB without an account, 100 MB with a free one and 200 MB on a paid plan, and they open in the browser viewer at the same sizes. Revit projects saved in Revit 2021 to 2027 are supported.

How to merge IFC files online

Upload your primary IFC file
Add additional IFC files to merge using the file picker
Click Run to combine all files
Download the merged IFC file

Under the hood

BIMCamel parses IFC files in the browser using the open-source web-ifc engine and renders models with @thatopen/components + three.js. Heavy operations (clean / optimise / validate / convert) run on disposable server-side workers using the same web-ifc stack plus our own .NET pipeline; results stream back to your browser as soon as they're ready. Uploads sit on our servers only as long as your tier's retention window allows and are never used to train AI.

Frequently asked questions

How many IFC files can I merge at once?

Up to 10 IFC files in a single merge job. For project-scale federation (architecture + structure + MEP + facade) that's typically all you need; heavier assemblies can be chained through a saved pipeline.

Does merging preserve properties and classifications?

Yes. Properties, property sets, classifications, and type definitions from every source file are carried into the merged IFC. Duplicate GlobalIds across files are de-duplicated so downstream tools don't choke.

Can I merge IFC files from different disciplines?

That's exactly the use case. A typical federation combines ARC, STR, MEP, and FAC exports from each discipline's authoring tool into one coordinated file for review, clash detection, or delivery.

Will coordinates line up automatically?

Only if the source files share a common project origin or use IfcGeographicElement for georeferencing. BIMCamel preserves each file's coordinate system — if disciplines modelled against different origins, the merged model will reflect that offset.

Can I clean the source files as part of the merge?

Yes. Each additional file can be pre-cleaned before it's merged: keep only physical elements, delete specific IFC classes, strip materials, or strip property sets — per source, in one run.

What should I check after merging?

Open the result in the viewer and eyeball the disciplines' alignment first. Then run Clash Detection for cross-discipline conflicts and a Model Health Check before sharing — both accept the merged file directly, no re-upload needed.

Can I automate a recurring federation?

Yes — save the merge (with its per-source pre-cleans and any downstream steps) as a pipeline and re-run it on every revision. Pro accounts can get an email when the job finishes; Team accounts can notify teammates and clients, up to 15 recipients per job.

What's the maximum IFC file size?

Up to 25 MB as a guest, 100 MB with a free account, 500 MB on Pro, and 1 GB on Team. The caps are on upload size only — every tool itself is available on every tier.

What happens to my file after processing?

Your file is uploaded over HTTPS and processed on our servers. Guest uploads are stream-only — the working files are deleted as soon as your download finishes. Free accounts keep results for 7 days; Pro and Team keep saved models until you delete them. Files are never shared with third parties or used to train AI.

Is Merge IFC, RVT, NWD Files free?

Yes. Merge IFC, RVT, NWD Files is free to use — guests get 3 runs a day with 25 MB uploads, and a free account raises that to 10 runs a day with 100 MB uploads. No trial clock, no watermarks.

Can I use a Revit or Navisworks file with Merge IFC, RVT, NWD Files?

Yes. Open a .rvt or .nwd file and it is converted to IFC first; the tool then runs on that IFC and your original file is not changed. On Revit and Navisworks files: A file in another IFC version or length unit is converted to match the first file before it is merged, and the job log says what was converted.