If you work with Revit and NVIDIA Omniverse, you have probably run into the same question that trips up most BIM and visualization teams today: what is the best Revit to USD workflow right now, given that native USD export still is not built into Revit? The honest answer is that there is no single perfect path yet — only a set of transitional strategies, each with its own trade-offs. Understanding where Datasmith fits, why NVIDIA is moving away from dedicated connectors, and which intermediate formats actually hold up in practice can save you weeks of trial and error.
Where Datasmith Fits in the NVIDIA Ecosystem Today
Datasmith has an interesting history. It originated at Motiva before Epic Games acquired the technology, and for years it was primarily associated with Unreal Engine pipelines. That origin story matters less now than its current function: within the NVIDIA Omniverse ecosystem, Datasmith has effectively become a core data-handling layer, even though it did not start out as an NVIDIA tool.
You can see this most clearly in tools like the Omniverse CAD Converter and various Omniverse Connectors. The Revit connector, for instance, relies on Datasmith behind the scenes to package geometry, materials, and metadata before converting everything into USD. It is not exposed as a standalone Kit extension, so most users never interact with it directly — but it is doing real work under the hood every time data moves from Revit into Create or View.
Why NVIDIA Is Moving Away from Connectors
NVIDIA’s own developers have been fairly consistent in their public messaging: the long-term direction is native USD support built directly into every major DCC (digital content creation) application, rather than a patchwork of third-party connectors. That is the strategic endpoint the industry is heading toward, and it makes sense — native support removes an entire layer of conversion overhead, sync issues, and version dependencies.
The catch is timing. Until Revit 2025 and later versions ship with a genuine, built-in “Export to USD” feature, teams are stuck in a transitional phase. Any predictions beyond that point are, realistically, speculation — without official confirmation from Autodesk or NVIDIA, it is fortune-telling rather than planning.
Practical Workflows for Revit Users Right Now
In practice, the right approach depends heavily on which version of Revit your team is running.
For teams on Revit 2023–2024: The NGC-based Omniverse Connector remains the most dependable option for achieving live sync with Create or View. It is not glamorous, but it is stable, and stability matters more than novelty when you are working against project deadlines.
For teams on Revit 2025 and newer: Since the connector path is less reliable here, most workflows now rely on intermediate formats:
- IFC → Blender or Rhino → USD — This path tends to preserve geometry and structural relationships well, making it a strong choice for BIM-heavy projects where topology matters more than material fidelity.
- FBX — Fast and convenient, but lossy when it comes to materials, so it is best treated as a quick preview solution rather than a production pipeline.
- CAD Converter — Promising and actively evolving, though not yet mature enough to be considered a universal solution.
One workflow worth highlighting is the IFC-to-Omniverse pipeline via Blender, using a BIM-oriented workflow. In hands-on testing, this approach is far from flawless, but it preserves topology and building levels surprisingly well — well enough that it may become something close to a de facto standard for teams handling complex BIM datasets until native USD export arrives.
The Bigger Shift: From Connectors to USD-First Pipelines
The underlying trend here is bigger than any single tool. The industry is moving from a connector-based mindset — where each application needs a dedicated bridge to Omniverse — toward a USD-first pipeline approach, where USD itself becomes the common language between applications. Workflows built around Revit, Blender, Rhino, and Omniverse will need to adapt accordingly as this shift continues.
Tools like Datasmith are likely to remain relevant during this transition, quietly doing conversion work behind the scenes even as the ecosystem moves toward more direct, native interoperability.
Final Thoughts
For now, the most reliable strategy is to match your workflow to your Revit version: lean on the NGC connector if you are on Revit 2023–2024, and experiment with IFC-based pipelines through Blender or Rhino if you are on Revit 2025 or later. Keep an eye on official announcements from Autodesk and NVIDIA rather than community speculation, since native USD export — when it arrives — will likely reshape these workflows significantly.
If you have tested the IFC-to-Omniverse pipeline yourself, particularly around material fidelity and overall stability, sharing that experience is genuinely useful to the wider community navigating this same transition.