VitruAI + SketchUp
VitruAI for SketchUp reads groups, components, layers, and tags in SketchUp Pro 2023+ and pushes clean design intent into Revit or ArchiCAD documentation without breaking classification. It installs as a Ruby API extension focused on execution work, not rendering, and is available now as a Labs engagement with a productised release on the Roadmap.
- SketchUp model audit across group/component structure, layer/tag discipline, and geometry validity against the documentation team’s import standards.
- Clean hand-off to Revit or ArchiCAD with group/component classification preserved, naming aligned to BIM templates, and triangulated geometry simplified for stable imports.
- Available now as a Labs engagement under MSA + Appendix, with the first deployed rule packs feeding into the productised Roadmap release.
Install, requirements, and what runs through the integration.
-
SketchUp Pro 2023+ on Windows and macOS
VitruAI for SketchUp ships as a Ruby extension that runs inside SketchUp Pro 2023+ on both Windows and macOS, using the desktop Ruby API for model access. SketchUp Free (web) is not supported because it does not expose the extension API required for group and component inspection. Firms running mixed environments can pair this with VitruAI + Revit for downstream documentation and with VitruAI + Rhino/Grasshopper where Rhino massing also feeds the same projects.
-
Available now as a Labs engagement
VitruAI scopes a SketchUp audit and clean hand-off rule pack against the firm’s existing modeling standards, tag conventions, and Revit or ArchiCAD import rules. The Labs engagement runs on one or two live projects, then folds the calibrated rule set into the Roadmap release. This matches how the Interop Agent for Rhino and SketchUp already handles Rhino-to-Revit transfers, so multi-tool studios see consistent behavior across platforms.
-
Outbound HTTPS only
The SketchUp extension communicates over outbound HTTPS only, with a single FQDN and a documented IP range for firewall configuration. No inbound ports open on firm networks, and no direct connections from external services into SketchUp desktops. Security reviews can reuse the same patterns already approved for VitruAI + Revit and VitruAI + Rhino/Grasshopper, including proxy routing and certificate pinning where required.
-
Strategic non-pursuit: visualisation
VitruAI does not enter the SketchUp-to-render pipeline market; tools like Veras, D5, Lookx, or Midjourney remain the preferred stack for visualisation. The SketchUp integration focuses on execution-stage work: model audit, naming and tag discipline, and clean transfer into Revit or ArchiCAD documentation. For firms already using the Interop Agent for Rhino and SketchUp, this keeps VitruAI’s role clearly in design-intent transfer and model quality, not imagery generation.
SketchUp integration — common questions
-
Does VitruAI generate renders from SketchUp?
No, VitruAI does not generate stills or animations from SketchUp models; visualisation is outside the product scope. The SketchUp integration is built for execution workflows such as model audit, geometry clean-up, and hand-off to Revit or ArchiCAD documentation. Firms typically keep their existing Veras, D5, or Midjourney stack for imagery and use VitruAI for model discipline and transfer.
-
When does the productised release ship?
The SketchUp integration is available now as a Labs engagement under MSA + Appendix, with productisation on the Roadmap. Ship-by dates depend on the scope agreed with the first partner firms and how their SketchUp standards align with existing VitruAI rule libraries. Each Labs deployment feeds directly into the packaged release, similar to how VitruAI + Revit matured from early partner work.
-
How does the SketchUp-to-Revit hand-off work?
The hand-off follows the patterns defined in the SketchUp-to-Revit clean import workflow, preserving group and component classification while simplifying triangulated geometry for stable imports. The rule pack checks for loose geometry, stray edges, and tag drift that would otherwise create Generic Models or imports that break view filters in Revit. Where firms also use Rhino, the VitruAI + Rhino/Grasshopper path and the Interop Agent for Rhino and SketchUp keep naming and category mapping consistent across tools.
-
Will this work for our LayOut documentation?
LayOut integration is on the Roadmap and is available as a Labs engagement for firms whose documentation sets are LayOut-led. The focus is on keeping model audit and naming rules in SketchUp aligned with LayOut viewports, tags, and page templates so the same discipline carries through. Early Labs work will inform how LayOut support sits alongside VitruAI + Revit for firms that split documentation between the two tools.