Reduce the size of a Revit IFC before presenting it

To reduce the size of a Revit IFC, export the content you need for the meeting and compare it with the full file. First identify the problem: loading, moving around, or displaying part of the project. There is no guaranteed reduction percentage or file size that works equally well on every device. The right presentation copy keeps what you need to explain.

The viewer interface is in Spanish. Spanish control names are followed by their English meaning in this guide.

Editorial review: October 20, 2026 · DRB Studio.

1. Separate file size from the problem you are seeing

   Note when the difficulty occurs. If the file takes a long time to open, record whether loading eventually finishes. If it opens but the camera feels sluggish, describe the view and the content on screen. If an element is missing, start with the troubleshooting guide: exporting fewer elements could make that problem worse.

   Keep the original IFC and record its size from your file manager. Note the computer, browser and design revision you are testing. File size is useful, but it does not tell you on its own how much geometry must be drawn or how a device will respond.

   Set a specific task for comparing versions: open the whole scheme, move to the entrance, then look inside. Repeat it after each adjustment. Changing the file, computer and display quality together makes it difficult to identify what helped. Keep a baseline before experimenting.

2. Create an export view with a clear scope

   Create a view for the presentation and decide what it should include. To explain a house, you may need the envelope and the furniture that shows how spaces work; for an entrance, you may also need part of the wider scheme. Write down that scope before hiding elements.

   Revit offers “Export only elements visible in view” in its IFC settings. Visibility comes with conditions: framing or cropping the image does not automatically exclude everything outside it. Check Autodesk’s Revit 2026 IFC options (source review: October 20, 2026). Inspect the exported file rather than assuming it matches the screenshot exactly.

   Hide components that do not contribute to the explanation in that view, while preserving your working model. Check linked files and design alternatives to avoid overlapping versions. Keep the elements the client needs to understand circulation and adjoining spaces.

3. Start by testing detailed objects

   Decorative furniture, planting and repeated objects are useful candidates for a lighter copy. Do not assume they are always the cause: inspect your actual project. A simple building may contain a highly detailed imported object; another model may need all its geometry for the review.

   Make a version that hides just one family of objects that is unnecessary for the meeting. Export it under a different name and repeat your comparison task. If the experience does not improve, restore those objects and test another possibility. This gives you evidence for each decision.

   Avoid removing supports, doors or stairs just to shrink the file. Smooth navigation through an incomplete building can confuse the client. Where an object matters for its presence rather than its detail, consider a simplified representation in a clearly identified working copy.

4. Save settings you can use again

   Once you have a useful scope, record the export settings. Revit lets you create or duplicate named IFC setups and save them with the project. Changes to the in-session setup do not persist between sessions. See Autodesk’s IFC export setup documentation (source review: October 20, 2026). A name such as “Entrance presentation” explains the purpose better than a list of numbered experiments.

   Keep the IFC version unchanged while investigating which content makes the file difficult to use. Changing the format and selection together obscures the cause. If you later compare another exchange setup, treat it as a separate test and check the geometry again.

   Decide which data you need during the meeting. If you will select elements to discuss their properties, confirm that those properties remain available. Do not remove information without checking its purpose. The presentation file has a defined scope; the full model remains the reference for other work.

5. Compare the improvement and what you left out

   Record each IFC’s size and its behavior during the same task. You can time loading, provided you note the equipment and conditions. Distinguish an initial load from subsequent openings. This guide gives no measured reduction because no new Revit export was tested to measure one.

   Compare the content from similar viewpoints as well. Check the facade, entrance and an interior area. Select a representative element and inspect the properties you need. Confirm a known dimension. If a smaller version lost something essential, revisit the step that excluded it.

   Be specific in your notes: what you removed, what remains and what still needs checking. Record loading times or specific improvements in navigation. That record helps you repeat the preparation after a design revision and prevents a partial copy from being mistaken for the complete project.

6. Rehearse on the meeting device

   Open the chosen IFC on the device you will use and save your views. In the standard 3D view, left-drag orbits, right-drag pans, scrolling zooms toward the cursor as in SketchUp, and middle-mouse dragging looks around from your current position. Rehearse the client’s route and check that you can return to the overall view.

   A gallery demo may use a lightweight version with different information from the full IFC. A demo running well on a phone does not guarantee your export will perform the same way. Test the actual file before promising a walkthrough or sharing the project remotely.

   Keep the RVT, full IFC and presentation copy. “Mis proyectos” (My projects) stores files in your browser; project cloud storage is currently disabled. If you send a .drb package, confirm the revision and test it on the receiving device. Name it clearly so a selection is not mistaken for complete project documentation.