Export 3D files
Some configurations need to leave the browser. An architect specifying benches for a public space, a dealer preparing a proposal, an in-house team dropping the configured product into a rendering - each of them needs the file itself, not a screenshot of it. The Planner Studio exports any saved configuration as a 3D file: GLB and USDZ for web viewers and AR, OBJ and Collada (.dae) for design and rendering tools. The export carries the exact configuration your customer built - the modules they selected, the materials, the dimensions - rather than a generic product model that then has to be corrected by hand. For specifier-facing ranges there is also a CAD drawing. We export the arranged configuration as a DXF plan in millimetres, with each module placed as a reusable block, so an architect can drop it straight into their project. AutoCAD and every major CAD package open DXF natively. That combination is often what moves a specification forward in contract and project work. The specifier configures the product themselves, takes the dimensions, the bill of materials and the drawing, and never has to call your sales team to get them. Exports are available directly in the configurator interface, and the same configuration data is available through our API when the output needs to reach a system rather than a person.
What we do not export
We are precise about this, because a vague answer costs both sides time later. We do not write native DWG or Revit (RVT) files, and we do not generate machine files for production. If your specifiers have asked for DWG, it is worth testing a DXF against their workflow first - most CAD tools read it directly, and in practice that closes the gap more often than not. Where manufacturing output is the real goal, the structured configuration data is the part that matters: the bill of materials, the dimensions and every option the customer chose. That data can be pushed to a CAD automation tool on your side, which regenerates the assembly and the drawings from it. Tell us where your drawings need to end up and we will confirm the fit before you commit.
Frequently Asked Questions
Common questions about file export, CAD workflows and what the configurator hands over. Missing something? Reach out and we will add it.
Which file formats can the configurator export?
GLB and USDZ for web and AR viewing, OBJ and Collada (.dae) for design and rendering tools, and - for specifier-facing ranges - a DXF plan in millimetres with each module placed as a reusable block. Alongside the files, the platform produces a PDF summary and a bill of materials, and exposes the full configuration through the API.
Can you export DWG or Revit (RVT) files?
No. We export DXF, not native DWG or RVT, and we would rather say so early than discover it at the end of a project. AutoCAD and every major CAD package open DXF directly, so it is worth testing an export against your specifiers' workflow before treating DWG as a hard requirement.
Can you export a format that is not listed here?
Ask us. We extend the platform as real customer needs come up, and adding an export format is usually a scoped piece of work rather than a rebuild. Tell us which format you need and what has to survive the export - geometry, materials, dimensions or structured data - and we will tell you whether we can support it and what it would take.
Does the exported file match the exact configuration?
Yes. The export is generated from the saved configuration, so the modules, materials, finishes and dimensions in the file are the ones the customer chose. There is no separate master model to keep in sync.
Can exports be automated instead of downloaded by hand?
Yes. The configuration - including options, pricing and the bill of materials - is available through our API, so it can be pulled into an ERP, a quoting tool or a CAD automation setup without anyone downloading a file manually.
Who typically uses file export?
Architects and specifiers who need the product inside their own drawing, dealers building a proposal, and internal marketing or visualisation teams who want the configured product in a render. In contract and project sales it is often the specifier, not the buyer, who decides whether the output fits their workflow.