Open an IFC File: Link It, Open It, or Just View It

If the IFC opened as a model of its own, you reached for the wrong command.

Someone sent you an IFC, you hit Open, and Revit handed back a brand new project with none of your work in it. Below is the route you actually wanted, and then the route for whichever program you happen to run.

Revit treats opening and linking as two different jobs. They sound interchangeable. They are not.

• Open turns the IFC into a fresh Revit model built on the default template. From that moment it is your model, and yours to maintain.
• Link keeps the other party's model theirs. Revit wraps it in an intermediate file and references that from your project.

Autodesk puts the warning at the very top of its own page about opening: to use the IFC as reference information for an existing model, use the Link IFC tool. One sentence, easy to scroll past, and that scroll costs people a working day.

I put it bluntly to new starters. Open a file that becomes yours. Link a file that stays somebody else's. On a live project it is nearly always the second one.

Linking an IFC in Revit takes five steps and leaves three files behind.

1. Open your own Revit model first. You link into a project, not into an empty window.
2. Click the Insert tab, then the Link panel, then Link IFC.
3. Find the file in the Open IFC File dialog and select it.
4. Set Positioning. Autodesk recommends Auto - Origin to Origin in most cases. If your project runs on shared coordinates, choose Auto - By Shared Coordinates instead.
5. Click Open and let it grind.

Now look in the folder next to the IFC. Revit has written three new files:

<ifc_file>.ifc.RVT
<ifc_file>.ifc.log.html
<ifc_file>.ifc.sharedparameters.txt

The first is an intermediate Revit model, and that is what your project links to. Not the IFC itself. Move it, rename it or delete it and the link breaks. The second is the file almost nobody opens: drop .ifc.log.html into a browser and you get a readable account of what came through and what did not. Half the questions people send us are already answered in there.

One more detail, straight from the Autodesk instructions for linking an IFC file, checked on 8 August 2026: from Revit 2024.1 onwards Link IFC uses a new link processor by default. It delivers better geometric fidelity and more stability, and it can be slower. If a link takes an age to load, that is the trade you are paying, and the legacy framework can be switched back on through Revit.ini.

Navisworks Freedom will not open an IFC, whatever you try.

This deserves its own heading because it is a popular search and the answer is flatly no. Navisworks Freedom is the free viewer for the NWD and DWF formats. It has no IFC reader. There is no add-on, no hidden setting, no file association trick that changes that.

To open or append an IFC in Navisworks you need Navisworks Manage or Navisworks Simulate. If Freedom is all you have, ask whoever sent the IFC to publish an NWD for you. It costs them a minute and gives you one self contained file you can open, measure and mark up.

The word Freedom in that product name refers to the price. It was never a promise about formats.

Open an IFC only when the model becomes yours to maintain.

There are honest reasons to open one. The consultant has moved on, the native file no longer exists, and the IFC is all that survived the handover. Then this is the route:

1. Click the File tab, then Open, then IFC.
2. Pick your file in the Open IFC File dialog. Under Files of type you can choose ifc, ifcXML or ifcZIP.
3. Clear Auto-Join Elements if you want control. Left selected, which is the default, Revit joins walls to other walls and to columns automatically. Clearing it can also speed the import up.
4. Leave Correct lines that are slightly off axis selected, unless you are importing a site plan. It straightens lines that sit less than 0.1 degree off axis.
5. Click Open.

Revit now builds a new model on the default template. If no default template has been set for IFC, it takes the first template listed under File Locations in Revit Options, which is how a warehouse ends up inside a residential template with the wrong units.

Spend two minutes in Import IFC Options first, reachable through File tab, Open, IFC Options. That is where you choose the template and map IFC classes onto Revit categories. Skipping it is what creates the afternoon of cleanup afterwards.

An IFC import gives you shape and data, never behaviour.

The import worked, the geometry is on screen, and nothing behaves. That is not a fault. It is the format doing exactly what it was designed to do.

• The parametrics are gone. A wall from an IFC is not a Revit wall with a type you edit. You cannot change its thickness by typing a number.
• The families are gone. What the other office drew as a window family arrives as an object shaped like a window.
• The relationships are gone. A window is no longer hosted in a wall. It sits in the right place, and that is the whole of it.
• The appearance is thin. Colours often survive. Render materials rarely do.

Autodesk has a name for this, imported geometry, and notes that its quality depends on the file type, on the export settings of the originating application and on your own import settings. Three places it can go wrong, and only one of them sits on your side of the fence.

No button turns imported geometry back into a fully editable native model. Tools exist that reassign imported objects to Revit categories, which helps with schedules and visibility, but the original structure was discarded at export and does not come back. If you genuinely have to keep modelling, ask for the native file. That request is awkward once and saves weeks.

If the model lands cleanly but collaboration falls over instead, you are in different territory, and the usual messages are covered in the write-up on the Revit central model error. And if you catch yourself rebuilding imported objects by hand, it is worth learning how to create a Revit family properly rather than tracing over a mesh.

Plain AutoCAD cannot read IFC, but the Architecture toolset can.

Forums argue about this and both sides are half right. Standard AutoCAD has no IFC reader. The AutoCAD Architecture toolset does, and it is included with an AutoCAD subscription. You only have to install it and launch it separately.

1. Start the AutoCAD Architecture toolset, not the plain AutoCAD shortcut.
2. From the application menu choose Open, then IFC (Industry Foundation Classes), or type IFCIMPORT at the command line.
3. In the Import IFC File and Create Drawings dialog, click Browse for IFC file to import and select your file.
4. Decide between a project and a set of standalone drawings, change the template if you need to, then click Create.

The toolset is IFC certified for importing and exporting version 2x3, and since the 2019 toolsets it reads IFC4 schemas as well. An infrastructure model exported as IFC 4.3 can still defeat it, and that is a schema gap rather than a broken installation.

Inventor gained IFC reading in the 2025 releases, and it asks a sensible question up front: Reference Model or Convert Model. A Reference Model stays linked to the source IFC and cannot be edited. A Convert Model is a one time import with no link back to anything. If you are dropping a machine into a building somebody else designed, Reference Model is the right answer almost every time.

SketchUp, SolidWorks and Rhino each read IFC on their own terms.

In SketchUp Pro the path is File, then Import, then set the file format to IFC Files (*.ifc, *.ifc.ZIP). In the Options dialog, Preserve Drawing Origin is selected by default and you want to leave it that way if the model has to line up with anything else. SketchUp reads IFC2x3 and IFC4 and turns every IFC class into its own tag, so hiding an entire trade after import is one click.

What arrives is groups and components, not building objects. That is why SketchUp is a pleasure for massing and a poor tool for quantities. Anyone coming from a CAD background will recognise the same pattern described in the guide to importing DWG into SketchUp.

SolidWorks treats IFC the way a mechanical package would. Simple building shapes such as walls, roofs, beams and columns convert into genuine solid and surface bodies you can reference and mate to. Anything faceted, so people, trees and furniture, arrives as mesh. There is no editable feature tree waiting for you, just accurate context to design against.

Rhino has no IFC reader of its own. IFC arrives through a plug-in, most often VisualARQ, which reads and writes IFC 2x3 and IFC 4. Worth knowing before you buy Rhino for building work, because the licence you need turns out to be two licences.

Which IFC version you were sent matters more than which viewer you choose.

IFC is not one format. It is a family of schemas maintained by buildingSMART, and the distance between the oldest one still in daily use and the newest official release is nearly twenty years.

Those dates and statuses come from the buildingSMART schema specifications page, checked on 8 August 2026. If your software refuses a 4.3 file, nothing on your machine is wrong.

The working summary: most building projects still exchange IFC 2x3, most current tools handle IFC4, and 4.3 turns up on roads, rail and bridges. Ask which one you are receiving before the first delivery rather than after it.

If you only need to look at the model, a browser is enough.

Plenty of people searching for how to open an IFC have no intention of modelling anything. They want to see what the engineer meant, once, today, and then get on with their job.

• Autodesk Viewer runs in the browser and lists IFC among its supported file types. Drag the file in and look. Nothing to install, no account juggling.
• Trimble Connect has a free personal tier and shows IFC in the browser with properties per object, which makes it the better choice when several people need to look at the same file and talk about it.
• Desktop viewers such as BIM Vision or Solibri Anywhere are noticeably faster once a model gets large, and they stay usable on a poor connection.

Web viewers share one habit worth remembering: they upload your file to somebody else's server. On a project covered by a confidentiality agreement, settle that question before you drag anything into a browser window. A desktop viewer keeps the model on your own machine, which is sometimes the only argument that matters.

When looking turns into coordinating and modelling, the tool itself starts to matter and a Revit licence becomes the thing the rest of the workflow rests on. For viewing alone it is far more than you need.

Still not working? Open the log file before you change any settings.

• Nothing is visible, yet the import reported success. Zoom to fit first, then check your view range. A linked IFC often sits outside the cut plane of whichever plan you happen to have open.
• The model landed miles from the origin. Autodesk states that an IFC with many or large negative Cartesian values may not place geometry where you expect. That gets fixed by the exporter, not by a move command.
• Half the services are missing. Read the log. If an element is not mentioned in there, it never arrived, and the export settings at the other end are what need changing.
• It takes forever. Large IFC files are heavy and the newer link processor adds time. Half an hour on a full building model is normal rather than broken.

If none of that gets you there, email us with the program, the version number and the first lines of the log file. Those three details usually settle it in a single reply.

A closing observation that has nothing to do with software. The best predictor of a painless IFC handover is the file name. Teams that send model_final_v3_REVISED.ifc are the same teams that cannot tell you three weeks later which revision you are looking at, and no viewer on earth fixes that. Ask for a date in the file name. It sounds petty right up until the second delivery arrives.