Practical scanning guide
Scan-to-CAD Workflow
A six-step scan-to-CAD workflow: keep raw data, fix scale and alignment, clean without hiding gaps, rebuild features and test the file in the receiving CAD.
Define the deliverable before processing
If you are designing a cover around an existing object, a scaled reference mesh may be enough. If you are manufacturing a revised bracket, list the dimensions and features that must stay editable. Only ask for a fully parametric model if someone will actually change those parameters.
Scroll horizontally to compare all columns.
| Deliverable | Useful acceptance check | Do not assume |
|---|---|---|
| Point cloud or mesh | Opens at the right scale with the required areas captured | That it is a watertight solid or a CAD design |
| Surface or solid exchange file (STEP, IGES) | Imports cleanly into the receiving CAD system | That it contains the original feature history |
| Native editable CAD | The agreed features change and the model rebuilds | That every dent and scan imperfection should become a feature |
Start with what the next person needs to edit. A mesh, a CAD solid and a feature-based model are three different deliverables. Agree on one before scanning, and keep enough evidence at each step to catch a scale or modeling error before it reaches the end.
This page covers the process after you have a scanner. For choosing the scanner and reconstruction software, see 3D scanners for reverse engineering. Software behavior below comes from vendor documentation checked on September 26, 2026.
On this page
1. Keep the raw capture and fix the scale
Save the original project and raw scan before any cleanup. Note the scanner, mode, calibration, surface preparation and software version. Keep one known dimension you can check after every export. A plausible-looking object in the viewport does not prove the units are right.
Mark which surfaces were captured and which could not be reached. If the part was sprayed, record it with the scan. The dark and shiny surface guide helps separate a capture problem from a reconstruction problem.
2. Register views and choose an alignment
Where scans overlap, check for doubled surfaces, seams and drift. Set the coordinate system from features that matter for the job, such as a mounting face and a bore axis, and write down why.
A best-fit alignment spreads the error across the whole part, while a datum-based alignment puts it where the datums allow. State which one you used before reading a deviation map, and do not switch alignments quietly to make a critical area look better.
3. Clean the mesh without hiding missing data
Remove fixtures and stray noise in a working copy. Look at every hole before filling it: a missing face may need another scan, while a real bore should stay open. Keep a log of smoothing, decimation and rebuilt areas.
Check critical features after reducing the mesh. If the smaller file loses the edge or radius the CAD user needs, it is not a successful handoff. Keep the full-resolution version for comparison.
4. Choose a reconstruction route
Machined parts usually rebuild well from planes, cylinders, sections and constrained sketches. Freeform areas need fitted surfaces, and many parts need both. The goal is the intended design, not a copy of wear, dents or scan noise.
Scroll horizontally to compare all columns.
| Route | Question to answer | Check before continuing |
|---|---|---|
| Mesh as a reference | Can the designer model the needed features around it? | Scale, visibility and coordinate system |
| Dedicated reverse-engineering software | Can the quoted edition extract and rebuild your features? | Fit controls, deviation checks and export options |
| Mesh conversion inside CAD | Does conversion give usable geometry for this shape? | Face count, solid or surface result and how it edits |
| Manual feature modeling | Which dimensions describe the design rather than the worn part? | Constraints, nominal values and rebuild behavior |
SHINING 3D's EXModel tutorials show primitive extraction, reference geometry and mesh sections, and QUICKSURFACE documents reconstruction from mesh data. That shows what the software can do, not that it will rebuild every part automatically.
Autodesk documents three ways Fusion converts a mesh: faceted, where each mesh triangle becomes a face; prismatic, which infers faces from groups of triangles; and organic, which needs an extension. A conversion step in Fusion's timeline creates new geometry from the mesh. It does not recover the original designer's feature history.
5. Check the geometry against the job
Compare the rebuilt model with the retained scan, using a documented alignment and color scale. Measure named critical dimensions separately where the job requires it. A color map summarizes differences; it cannot tell you whether a deliberately nominal feature is right or whether the scan itself can be trusted.
Keep three questions apart. Did the scanner capture the area? Did reconstruction change it appropriately? Does the result meet the design requirement? The accuracy guide covers the first question.
6. Test the file in the receiving system
Export the agreed format and open it in the actual application and version that will use it. Check scale, coordinate system, missing faces and geometry validity. If editability is required, change the agreed dimension and rebuild there. A screenshot from the reconstruction software is not a substitute.
CAD handoff record
Use one row per delivered revision, and attach the files rather than relying on memory of the settings.
Scroll horizontally to compare all columns.
| Handoff item | Evidence to keep | Send the job back if |
|---|---|---|
| Source | Raw scan, software version and setup notes | Only the smoothed final mesh exists |
| Reference | Units, orientation, datums and the known dimension | Scale or alignment is unexplained |
| Mesh edits | Processed mesh and a log of filling, smoothing and decimation | Filled-in geometry cannot be told apart from captured data |
| Design decisions | Nominal dimensions, tolerances and assumed features | Wear was copied or removed without an agreed reason |
| Validation | Critical checks, comparison settings and open areas | A color map is the only acceptance evidence |
| Delivery | Native project where required, exchange file and import check | The receiving system cannot use the file |
| Revision | Part number, revision, date and approver from your team | Versions cannot be told apart |
Most problems point to a specific fix. A model ten times too large or small needs a units check, not a rescan. Thousands of tiny triangular faces in a CAD file mean the conversion route needs another look. A model that will not rebuild needs its features and constraints repaired. Go back to scanning only when the needed geometry was never captured well enough.
Sources and limits
- Autodesk: convert a mesh to a solid or surface body
- Autodesk: access organic mesh conversion
- SHINING 3D EXModel tutorials
- QUICKSURFACE: scan data to editable CAD
- How we research
The handoff record is a working checklist, not a report of a reconstruction we carried out.