IFC, RVT, NWD Repair Center

One-stop tool that bundles GUID repair, coordinate fix, orphan purge, and broken-xref cleanup. Toggle individual actions on / off, or preview first to see what would change before touching the file.

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.

Fix the common structural faults in an IFC model in one pass: conflicting or missing GlobalIds, coordinates too far from the origin, orphaned geometry, and dead references to external files. Toggle the individual repairs, or preview first to see exactly what would change before anything touches the file.

Most broken IFCs are broken in one of a handful of specific ways, and each has a known fix. What made them annoying was that the fixes lived in separate tools, so repairing a model meant four runs, four downloads and remembering the order. This is one run with everything on by default.

When to reach for it: Before sharing a model. Bundles four common repairs into one pass: fix missing/duplicate GUIDs, anchor coordinates near the origin, purge orphan geometry, clean broken external references.

What you get: An IFC file with every selected repair applied. Dry-run mode reports what each action would change without mutating the file.

Example: Run a full repair pass before sharing an IFC with a partner: dedupe GUIDs, anchor coordinates, drop orphans, clean broken xrefs in one go.

What it repairs

Identifier conflicts — duplicate and missing GlobalIds regenerated. This is the repair that matters most, because duplicates silently corrupt clash results, BCF references and revision comparisons rather than producing an error anyone sees.
Coordinates — a model authored at survey coordinates far from the origin brought back to a workable position, which removes the viewer jitter and the float-precision loss that come with large coordinate values.
Orphaned geometry — representations that no element references, purged. Dead weight that inflates the file and slows every parse.
Broken external references — dead pointers to files that only ever existed on the authoring machine, removed, so the model stops asking your recipient for files they don't have.

Preview before you commit

Preview runs every enabled repair and reports what it WOULD change without writing anything: how many identifiers would be regenerated, what the coordinate shift would be, how many orphans and references would go. On a model you didn't author, that's the right first move — a repair is a change to someone else's data, and knowing its scope before applying it is the difference between fixing a model and explaining later what you did to it.

Everything is on by default so a first run does something sensible, and each repair can be turned off independently when you only want one. The most common reason to deselect is identifier regeneration, since it has consequences beyond the file.

The one repair to think about first

Regenerating GlobalIds fixes duplicates, and it also means every element gets a new identity. Anything keyed to the old identifiers stops resolving: BCF issues raised against this model, clash results referencing its elements, a revision comparison against a previous version, an asset register built from its GUIDs. On a model with no coordination history that costs nothing; on one mid-project it can invalidate work several people have done.

So run the Schema & Identity Check first to see whether you actually have duplicates, and if you do, decide deliberately. Run the IFC Health Check to see the full picture before repairing — this tool fixes what it fixes, and the health check tells you whether that covers your model's actual problems. The original upload is never modified: the run writes a new file, and in a workspace your source stays as its own version.

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.

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 repair an IFC file

Upload your model (IFC, RVT or NWD)
Pick which fixes to run (GUIDs, origin, orphans, xrefs — all on by default)
Optionally preview first to see what would change
Click Run to apply the fixes
Download the repaired 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 do I fix duplicate GlobalIds in an IFC file?

Run the Repair Center with identifier repair enabled — duplicates and missing GlobalIds are regenerated. Preview first to see how many would change, and read the caveat below about what regenerating them affects.

What does regenerating GlobalIds break?

Anything keyed to the old identifiers: BCF issues raised against this model, clash results referencing its elements, revision comparisons against a previous version, an asset register built from its GUIDs. On a fresh model that costs nothing; mid-project it can invalidate other people's work. Check whether you actually have duplicates first with the Schema & Identity Check.

Can I see what it would change before running it?

Yes. Preview runs every enabled repair and reports what it would do — identifiers regenerated, the coordinate shift, orphans and references removed — without writing anything. On a model you didn't author, that's the right first move.

Can I run only one of the repairs?

Yes — each is an independent toggle. They're all on by default so a first run does something sensible, but you can enable just the coordinate fix, or everything except identifier regeneration, which is the most common combination.

Will it modify my original file?

No. The run writes a new file, and in a workspace your uploaded model stays available as its own version, so you can always go back to it.

Which IFC versions are supported?

IFC2x3 and IFC4 — the two schema versions exported by essentially every AEC authoring application. IFC4x3, the infrastructure schema, works too: it opens in the viewer, and validation, health reports, property-set editing and georeferencing all run on it. Tools that need geometry processing, such as clash detection and 3D export, aren't verified on IFC4x3 yet.

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 IFC Repair Center free?

Yes. IFC Repair Center 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 IFC, RVT, NWD Repair Center?

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.