Calling all IFC Importer users… to let you know you’re about to become IFC Importer hard core fans (hopefully)!
We have re-written the IFC Importer from scratch so it’s ready for a bunch of improvements!
With the help of @Christopher_Diggins, the Next-Gen IFC Importer is faster than ever and can allow us to scale to larger files.
Large files previously behaved unreliably with our old web based IFC Importer. No more of that.
We’re R E A D Y to deploy these changes to app.speckle.systems where new IFC uploads will use the new .NET based Importer logic.
Wanna see it in action?
Check out these models imported with the Next-Gen Importer:
The Next-Gen IFC Importer is more scalable, and faster when importing large files. Chef’s kiss.
Correct scaling of IFC files - all length Units will be scaled to Meters.
Imported Speckle models will have the data structured the same as our Next-Gen (current) connectors - i.e. using Collections and DataObjects.
This makes it work with all other Next-Gen Design Coordination workflows as well as Automations and Businesses Intelligence workflows. (explore use cases at speckle.systems)
Good to know:
For the next 4 weeks only the files ending in .legacyimporter.ifc will still trigger the old IFC Importer logic. After that we’re saying bye to the old Importer logic. We’re always here to support you along the way!
New features like CRS, IFC Space geometry, IFC Annotations are still a TBD.
The new IFC Importer is converting Property Sets, and basic spatial element properties only.
Support for super duper large files is not there yet, we are still keeping the same 100MB limit on the files uploaded.
We may explore options to offer even higher limits in a paid plan once we’re confident that the experience is worth it for you!
So keep the feedback coming—that’s how we keep the ball rolling.
It really depends on how you’ve configured your self hosted server. From the screenshot it doesn’t look like you have file imports enabled. It’s a separate service.
Good catch, those links were accidently private . I’ve updated them now.
The update is now on app.speckle.systems
You might be seeing an old import that got stuck. This shouldn’t happen again with the new uploads. Please let me know if you do see new uploads get stuck.
@Sonderwoods side effect of your gmail stealth mode on the forum here is that we didn’t make 2+2=4.
The deployment to other speckle-hosted servers is usually in short order of time after live on the main server. Let me check with the server team and I’ll let you know directly as soon as I know
I’ve checked the server and the new IFC parser is deployed.
A 413 status code is caused because the upload is larger than allowed by the ingress or loadbalancer. I’ll take a look at the configuration in case it is set too low.
Support for super duper large files is not there yet, we are still keeping the same 100MB limit on the files uploaded.
Why the 100MB limit is still in place
While we’ve rebuilt the IFC Importer from scratch (with huge thanks to @Christopher_Diggins), and it’s performing significantly better, this isn’t the final form just yet.
We treat this release as a step forward, not a final solution.
That’s why we’re keeping the 100MB upload limit in place for now:
It’s about setting expectations.
We know this importer is already more scalable and stable than the previous one, but we’re still learning where it breaks, where it shines, and what edge cases remain. Keeping the limit helps ensure users don’t hit rough edges we haven’t ironed out yet.
There are still technical and UX considerations.
Larger files affect import speed and server memory, timeout limits, and downstream processes like automations and commit viewing. We need confidence across the whole pipeline before scaling up.
We’re still collecting feedback and performance data.
Real-world IFC models behave in wonderfully chaotic ways. Your uploads and feedback are helping us shape the roadmap for further improvements, including better chunking, ingestion, and lifting the file size cap.
We already know from some of you that not everything is being captured.
Our goal is that you can trust your IFC data in Speckle—so if you spot anything missing or misrepresented, shout! The worker bees are still spinning their web… (editor: spiderbees?)
So in short: You’re using the new importer already—no config needed. The 100MB limit is still active, intentionally. We’re not done yet—but we’re on the right track. Please keep the feedback coming—it’s what keeps us moving.
We’re always here to support you along the way!
. I’ve updated them now.
), and it’s performing significantly better, this isn’t the final form just yet.
You’re using the new importer already—no config needed.
The 100MB limit is still active, intentionally.
We’re not done yet—but we’re on the right track.
Please keep the feedback coming—it’s what keeps us moving.