When a manufacturer starts a 3D product display project, the engineering files already exist: SolidWorks assemblies, STEP files sitting on the designers hard drive. These files cannot go straight onto a web page, and a preparation stage sits between the CAD data and the browser. Do this stage well and the modeling budget shrinks, because the shape and dimensions are already correct.

Why CAD files cannot enter the browser

CAD stores exact mathematical surfaces, built for manufacturing; a browser can only draw triangles. Convert an assembly directly and the usual symptoms appear: file sizes in the tens or hundreds of megabytes; the model lying flat because CAD uses Z up while web engines use Y up; millimeter units that make the product microscopic; hundreds of separate parts where every bolt is its own mesh; colors that came from random CAD swatches and mean nothing as materials. None of this means the manufacturer did anything wrong. Manufacturing data and realtime rendering simply want opposite things.

The good news: starting from CAD costs less than modeling from photos. The shape is locked, so the comparison and correction work disappears, and studios commonly quote thirty to fifty percent below photo based modeling. Cleaning up a large assembly still takes extra days, which is the exception.

From CAD Files to a Web Ready GLB: Preparing Product Data for 3D Display(pic1)

Five steps from engineering file to web asset

Step one, have engineering export a STEP file with the outer shell only. Internal mechanisms, tolerances and machining notes stay behind; this saves weight and protects confidential design.

Step two, tessellate and clean up. Delete internal parts nobody will ever see, weld bolts into parent bodies, merge hundreds of parts into a dozen meshes, and fix orientation and scale once at import.

Step three, reduce the polygon count. Spend density on silhouette edges and on the spots a buyer zooms into, such as hinges, seams and control panels; flat surfaces deserve almost nothing, a tabletop works with two triangles. Tens of thousands to around one hundred thousand triangles is plenty for a product page. If the converted file still ships heavy, work through the five ways to lighten a web 3D model.

Step four, rebuild materials. Replace CAD colors with real PBR materials for plastic, metal and glass, and size textures to on screen coverage; a 4K map on a part occupying a fifth of the screen is pure waste.

Step five, compress and export GLB. Draco handles geometry, KTX2 handles textures, and a 90 megabyte input regularly comes out at two or three. For AR on iPhones, export a USDZ from the same source file rather than maintaining two separate outputs.

What to prepare before handover

Tidy the parts list so names follow one convention; decide which structures need an exploded view, because parts that must separate keep their individual meshes and cannot be merged for the sake of file size; prepare a color board plus reference photos. The overall pipeline matches the full workflow from modeling to launch, which also covers the part level structure that exploded views demand.

This preparation looks tedious, yet it carries the largest cost swing inside any 3D product display project. Clean files let the studio spend its hours on visual quality; a tangled file makes every line of the quote more expensive. Where the project scope and budget should sit, the 3D configurator service page explains in more detail.

Related Q&A

Why is a directly converted CAD model so huge?

Two reasons: exact surfaces explode into millions of triangles when tessellated, and the assembly carries internal parts no visitor will ever see. Removing hidden parts and reducing polygons by silhouette need brings the file down to a fraction of the original size.

Does polygon reduction ruin the details?

No, provided density stays on silhouettes and key details. Surface detail such as brushed metal grain or stitching returns through normal maps baked from the high resolution model; the detail lives in the texture, not in the triangle count.

How do we avoid leaking secrets when sending CAD files?

Sign an NDA that requires the source files to be deleted or returned after the project. Export the outer shell only, keeping internal mechanisms and process parameters inside the company. Marketing display never needs the internals, and this is standard industry practice.