Manage IFC, RVT, NWD Storeys
View and reassign IFC elements to different building storeys/levels.
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.
Move IFC elements between building storeys. Upload the model, choose what to move — everything on one level, the elements you've picked in the 3D viewer, or everything with no storey at all — pick the destination, and download the model with the assignments corrected.
Storey assignment is the axis nearly every coordination workflow runs on. Drawings are issued per level, quantities are broken down per level, clash reviews are walked level by level, and models are split per level for hand-off. An element on the wrong floor — or on no floor — is wrong in all of them at once, while looking completely correct in a 3D view.
When to reach for it: When elements are assigned to the wrong building storey/level — a common issue with exported IFC models.
What you get: An IFC file with elements moved to the correct building storey.
Example: Move 50 elements from 'Level 0' to 'Ground Floor'.
Three ways to choose what moves
- Everything on a storey — move a whole level's contents to another level. The fix when a merge landed a discipline one storey out, or when two levels need consolidating.
- The elements selected in the viewer — click them in 3D and they're picked up automatically. The fastest route when the problem is a specific handful of objects rather than a pattern.
- Everything unassigned — target the elements with NO storey at all and give them one. This is the mode that pairs with the Spatial Structure Check, which finds exactly those elements: they render fine and are invisible to every per-level workflow, and this is how you bring them back in.
The modes are separate on purpose
They used to be one dropdown, in which an "Unassigned" option quietly meant something structurally different from the storey names beside it, and picking elements in the viewer changed the behaviour invisibly. People reported that repeatedly, and they were right: choosing WHAT you're doing and choosing WHERE it goes are two decisions, and collapsing them into one control makes the second one lie about the first.
Saved setups keep a mode and its storey choice together under a name, so the same correction can be re-applied to the next revision without reconstructing it — useful when a consultant's export is reliably one level out every time.
Assignment only, and what to run alongside
Only storey assignment changes. Geometry is not moved: an element reassigned from level 3 to level 4 stays exactly where it is in space, and now reports as belonging to level 4. That is almost always what you want, because the usual defect is a correctly-placed element with the wrong containment. If the geometry itself needs moving, that's Transform IFC Model.
Run the Level Consistency Check first when levels look wrong at all — it finds storeys with no elevation, storeys sharing an elevation, and empty leftover template levels, and reassigning elements between duplicated storeys just moves the confusion around. Fix the levels, then fix the assignments.
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 files: "Unassigned" also lists duct and pipe connection points and wall openings, which belong to their host element rather than a storey.
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 move IFC elements between storeys
- Upload your model (IFC, RVT or NWD)
- Select the source storey and target storey
- Click Run to reassign elements
- Download the updated 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 move IFC elements to a different floor?
Choose what to move — a whole storey's contents, the elements you've selected in the 3D viewer, or everything currently unassigned — pick the target storey, and run. Only the assignment changes; the geometry stays where it is.
Can I assign elements that have no storey?
Yes — that's a dedicated mode. It pairs with the Spatial Structure Check, which finds the elements outside the hierarchy: they render normally but are invisible to every per-level schedule, filter and split, and this is how you bring them back in.
Does reassigning a storey move the element in space?
No. The element stays exactly where it is and now reports as belonging to the new storey. That's usually the fix you want, since the common defect is a correctly-placed element with the wrong containment. Use Transform IFC Model if the geometry itself needs moving.
My levels themselves look wrong — fix those first?
Yes. Run the Level Consistency Check — it finds storeys with no elevation, storeys sharing an elevation, and empty template levels. Reassigning elements between duplicated storeys just moves the confusion around; fix the levels, then the assignments.
Can I save a reassignment for the next revision?
Yes — saved setups keep the mode and the storey choice together under a name, so a consultant's export that arrives one level out every time can be corrected the same way each revision without rebuilding the settings.
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 Manage IFC Storeys free?
Yes. Manage IFC Storeys 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 Manage IFC, RVT, NWD Storeys?
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 files: "Unassigned" also lists duct and pipe connection points and wall openings, which belong to their host element rather than a storey.