Free tool
Will your IFC file open on a phone?
Check in seconds whether a heavy IFC model will perform well on a mobile device. Free, no install required — a readiness gauge for your field team.
Enter your file details and click "Check readiness" to see the result.
How to use the IFC mobile readiness check
- Step 1
Enter the file size
Type the IFC file size in megabytes. Don't know it? Check the file properties on your computer.
- Step 2
Pick the geometry detail level
Choose Low, Medium, or High based on how complex the model geometry is — MEP models with pipes and connections are High.
- Step 3
Select your device tier
Pick Entry-level, Mid-range, or High-end. This determines what the calculator considers acceptable performance.
- Step 4
Read the verdict
Get an instant readiness score and practical tips — green means smooth, amber means workable, red means split for comfort.
How the calculation works
The raw IFC file size is only a proxy — what really stresses a device is geometry complexity combined with memory limits. That's why we apply a detail multiplier to get the effective complexity.
Low detail (×0.7) is for simple slabs and walls. Medium (×1.0) for standard architectural models. High (×1.5) for MEP models with pipes, bolts, fittings, and dense connections.
Each device tier has two thresholds. Below the green threshold the file should open smoothly. Between green and amber it may need patience. Above amber, it will open but navigation may be slow — we recommend splitting the model.
Entry-level — 80 / 150 MB effective
Budget phones with 2–4 GB RAM. Files up to 80 effective MB open smoothly; up to 150 MB are workable.
Mid-range — 150 / 300 MB effective
Typical work phones with 4–6 GB RAM. Most construction IFC files fall into this range and perform well.
High-end — 300 / 500 MB effective
Flagship phones or tablets with 8+ GB RAM. Even large federated models are often within the green zone.
Worked example: 220 MB MEP model on a mid-range phone
A 220 MB MEP IFC with High detail (×1.5 multiplier) = 330 MB effective complexity. For a mid-range device, the amber ceiling is 300 MB. 330 > 300 → Red verdict. Readiness score: ~40/100. Tips: compress to IFCZIP (could shrink to 22–44 MB) or split by discipline.
Frequently asked questions
Why does my IFC file weigh so much?
IFC files store geometry as explicit triangles or extruded shapes, plus property sets, relationships, and classifications. MEP models are especially heavy because every pipe fitting, bolt, and connection adds geometry. A single federated hospital model can easily exceed 2 GB.
How do I reduce the IFC file size?
Compress it to IFCZIP (.ifczip) — this typically reduces size by 80–90%. Also consider exporting by floor or discipline instead of one monolithic federated file. Remove unnecessary property sets and classification references before export.
Can I open IFC without Revit?
Yes — IFC is an open standard. You don't need Revit or any BIM authoring tool. PinMy opens IFC files directly in a browser on desktop and mobile, no install required. Other free viewers include BIMcollab ZOOM and the IFC.js-based online viewers.
What device can handle a large IFC?
For files over 300 MB effective complexity, we recommend a high-end phone or tablet with at least 8 GB RAM. PinMy's mobile viewer is optimized for heavy models and performs better than generic web viewers on the same hardware.
Does IFC version affect performance?
Not directly. IFC4.3 files can be larger because they include more entity types, but it's the geometry count that determines performance — not the schema version. That's why this calculator focuses on file size and detail, not the IFC version.
From IFC file → PinMy
Knowing whether your IFC will open is step one. On site, you need to navigate the model, find the exact spot, and leave a pin with a photo, voice note, or video. PinMy does all of that on mobile — no CAD, no BIM license, no sync. Just open and annotate.
Related
This is an indicative estimate; actual performance depends on the specific model structure and device conditions. Always test with your own hardware.