Drag an .ifc and see it in 3D right away: IFC2x3, IFC4 and IFC4x3, several federated models at once, measuring, section planes and real UTM coordinates. Nothing to install and no upload to any server.
Open my IFC — free I also need to edit it
Load structure, services, buildings and terrain together: they align by their real coordinates, not by eye. You can focus one model, switch it off or isolate it.
Honours IfcMapConversion and the IfcSite placement: what you read is the project coordinate, not an invented local one.
Distances, polylines, angles, areas, coordinates and edges, snapping to real vertices and edges, with axis or face-perpendicular locking.
Several simultaneous cuts, aligned to a face with one click, to look inside the model the way you would in Navisworks.
View cube, parallel or perspective projection, orbit and zoom-to-cursor, and iPad gestures: one finger selects, two zoom, three orbit.
Every element with its Psets and properties in a filterable table, and export to CSV/Excel, DXF or BCF.
The short answer is that megabytes are misleading: what loads memory is the geometry inside, not the file size. A 500 MB alignment model with triangulated surfaces moves better than an 80 MB model full of curved pipework, rebar or bolts.
Since there is no server — the file is processed on your device — the ceiling is the browser: a tab has a bit over 2 GB of JavaScript memory. Above 480 MB Geoma switches to read-only with streaming, because the JavaScript engine cannot create strings larger than about 512 MB and editing works on the IFC text.
| Test | Figure |
|---|---|
| File | IFC2x3 alignment model exported from Istram · 567 MB |
| Content | 1,797,290 triangles · 5.4 M points · 72 elements |
| Machine | MacBook with Apple M1 and 8 GB of RAM |
| Open (read-only) | 11 s |
| Build and show the 3D | 14 s more |
| Memory in use | ~850 MB out of ~2,100 MB available |
Note the detail that explains everything: that file has 72 elements and nearly 1.8 million triangles. The megabytes were in the mesh, not in the data model.
A viewer lets you inspect. An editor changes the content of the file and hands you back a new IFC. If you got here because a model has its properties wrong, extra elements or sits in the wrong place, what you need is the IFC editor: batch editing, deletion, merging and georeferencing.
Viewing, measuring and sectioning is free and account-free. Editing and exporting belong to the paid plans. See plans.
Because the IFC lands in your inbox at seven on a Friday and has to be looked at on whatever laptop is around, with no install rights and sometimes from the site itself. And because the file never leaves your device: it is processed locally with WebAssembly, something you cannot take for granted with viewers that upload the model to their cloud to display it.