In this guide
Create a visual mesh derivative from the engineering source, then review the features that matter at the intended viewing distance. Keep the CAD source unchanged and identify the export settings. The goal is not the smallest file at any cost, or the highest triangle count available; it is a usable visual representation with a traceable source.
Product curves, holes, small fasteners and thin edges expose different export problems. Review those features deliberately instead of judging only the main silhouette from one camera.
Separate authoring source from visual derivative
The CAD model carries the engineering representation and its own history. A tessellated export approximates surfaces with polygonal geometry. Preserve source revision, units, component identity and material mapping alongside the derivative.
Autodesk’s Tessellate documentation describes surface deviation, normal deviation, maximum edge length and other refinement controls.1 Record the values and application version used; a preset name alone may not explain a cross-application difference.
| Feature | Inspect visually | Possible export issue |
|---|---|---|
| Broad curved housing | Silhouette and reflected shape | Insufficient surface refinement |
| Circular opening | Roundness and edge continuity | Coarse local tessellation |
| Small repeated fasteners | Readability at target distance | Excess detail or missing identity |
| Thin trim | Presence and shading | Geometry omission or poor normals |
Choose representative stress views
Export a candidate and inspect a complete product view, a curved silhouette and the most important small feature. Use the same camera and lighting when comparing candidates. Changing presentation between exports hides the effect of the tessellation change.
Keep file size, triangle count and observed visual differences together. A larger file is only justified by detail the receiving task needs. Conversely, a very small file that loses a key control opening is a failed derivative even if it loads quickly.
Check component and material mapping
Confirm which source components are separate nodes and which were merged. A visually correct export can still be unsuitable for product configuration if it collapses alternatives into one inseparable mesh. Check the material slots needed for finish choices and verify textures stay associated with the right regions.
The Khronos glTF overview describes the format’s runtime-delivery purpose.2 Confirm supported features in the receiving tool rather than treating a file extension as proof that every CAD or renderer feature survived.
Compare a small set of candidates
Choose a coarse, working and finer export around the features of interest. The labels describe your trial, not standard quality levels. Record actual settings and observations. Pick the least expensive candidate that meets the agreed visual task, then retain the comparison evidence.
Use the tessellation review sheet. Add actual measurements and file statistics after export; the sheet contains no prefilled pass results. For engineering handoff, continue using the CAD-versus-concept guide and supplier drawing package.
Rendora’s option library accepts supported self-contained GLB masters for material/component configurations and image outputs. Export the GLB through a tested conversion workflow; this entry is not a native CAD tessellation service.
Export questions
Is a render-ready GLB suitable for manufacturing?
Use the source and requirements agreed with the manufacturer. A visual derivative is not automatically an engineering source.
Should I preserve every screw thread?
Preserve what the viewing or configuration task needs. Keep omitted manufacturing detail in the engineering source rather than silently changing its authority.
References
- Autodesk, Tessellate, checked October 26, 2026.
- Khronos Group, glTF, checked October 26, 2026.
About this guide
Rendora publishes practical guides for teams working with configurable 3D assets and traceable production handoffs. Updated October 26, 2026.