STL / OBJ
Mesh reference
Use captured shape as a reference. Check units, scale and coverage. It has no native feature history.
Check a meshPractical scanning guide
Choose the CAD edit you need before you process the scan. Mesh reference, editable solid and native parameters need different checks.
STL / OBJ
Use captured shape as a reference. Check units, scale and coverage. It has no native feature history.
Check a meshSTEP / B-rep solid
Reconstruct surfaces or solids, then prove the requested direct edit in your CAD app.
Check a solid editNative CAD project
Build the agreed sketches, constraints and parameters. Reopen the file and prove a parameter change rebuilds it.
Check a parameter changeKeep the original at every handoff. A reconstruction route may need separate software; the final check belongs in the application that will receive the file.
Keep an untouched capture. Record the mode, surface preparation and known dimension before exporting; verify the units against that dimension after import.
Check overlap, doubled surfaces and drift. Record whether best-fit or defined datums establish the coordinate system before reading deviations.
Remove fixtures and noise in a copy. Separate a missing captured surface from a real opening, and check critical features after smoothing or decimation.
Choose the route for the intended edit. Planes, cylinders, sections and fitted surfaces are modeling decisions; changing the extension does not recover original design history.
Check geometry against the job, then open the actual exported file. Prove the agreed reference task, direct edit or named parameter rebuild and retain any failures.
Practice files teach a stated software check. They do not establish scanner accuracy, physical fit or universal application compatibility. Nothing is uploaded by these stage controls.

Retain raw data, declared units and alignment. Test the reference operation the designer needs.
Check the surface or solid and the agreed direct edit. Missing original history does not mean the body is uneditable.
Change a named parameter and rebuild its dependent features in your CAD app.
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.
| Deliverable | Practical file check | Do not assume |
|---|---|---|
| Point cloud or mesh reference | Opens at the agreed scale and alignment with required areas captured; supports the designer's reference task | That it is a watertight solid or a parameter-driven CAD design |
| Imported CAD surface or solid, commonly a B-rep (faces, edges and vertices) via STEP or IGES | Imports as the intended body type, passes geometry checks and supports the agreed direct edit in your CAD app | That missing history makes it uneditable, or that import recovers the original sketches, constraints and feature sequence |
| Native parametric CAD | Contains the agreed named parameters, sketches and feature dependencies; a parameter change rebuilds the intended geometry | That a native file extension alone proves useful history, or that every dent should become a design feature |
B-rep describes geometry through faces, edges and vertices. An imported solid may support direct edits such as moving a face even without the original design history. A native project can also contain only a history-free body. Ask for the edit you need, not just a file extension.
Start a mesh-reference shortlist, plan a direct edit to a CAD solid, or plan a native parametric model. The selector shows this starting choice and lets you change it before you enter your actual object and conditions.
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. The source list identifies the supporting software documentation.
Already have a mesh with holes, double surfaces or the wrong scale? Choose the symptom and its next check before starting CAD reconstruction.
Import the three practice boxes in millimeters. The open-top box has the same outer dimensions as the complete box, while the mis-scaled box is 25.4 times too large. Check both units and missing geometry.
Practice file, not a scan.
Download all ten checked files (ZIP) | Checked Blender STL export | Checked Blender OBJ geometry | Blender reproduction code | Original baseline | Original open top | Original coordinate scale fault | Six results CSV | Actual version, settings and hashes | Commands, limits and CC0
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.
Align the two practice passes using the matching landmarks, then check the separate control span. A small alignment residual does not prove that every dimension of the combined part is correct.
Practice file, not a scan.
Pass A coordinates | Transformed pass B | Registered combined coordinates | Wrong alignment coordinates | Six named point pairs | All rotation/translation matrices | Result table CSV | Reproduction script | Instructions and CC0 license
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 distributes mismatch across the part, while a datum-based alignment uses the reference surfaces and axes you have chosen. State which one you used before reading a deviation map, and do not switch alignments quietly to make a critical area look better.
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.

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.
| 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 feature in Fusion's timeline is not the original designer's feature history. Autodesk separately documents direct editing of imported models and the creation of new history after import; neither restores all original design intent.
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.
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. A screenshot from the reconstruction software is not a substitute.

Compare a mesh, a STEP solid and a native CAD project. Ask for the exact edit you need: opening a solid does not restore its original sketches or parameters.
Practice file, not a scan.
Original solid STEP | Direct-edit STEP | Rebuilt STEP | Native construction source (Python) | original STL | direct-edit STL | rebuilt STL | Instructions and CC0 license | Geometry results CSV | Detailed results and file information | Second STEP import check (JavaScript)
Open the supplied STEP files in FreeCAD and check their scale, solid geometry and the edit you need. A successful import is only the first step in a usable CAD handoff.
Practice file, not a scan.
FreeCAD 5 mm hole STEP | FreeCAD 7 mm hole STEP | FreeCAD reproduction script | Commands, original inputs and CC0 license | Five checked operations CSV | Actual application versions, results and file hashes
Change the hole parameter from 5 mm to 7 mm in the supplied native project, then rebuild it. Check that the dependent feature changes too; moving a surface is a different task.
Practice file, not a scan.
Download all nine checked files (ZIP) | Native FreeCAD project: 5 mm hole | Native FreeCAD project: 7 mm hole | 5 mm STEP geometry | 7 mm STEP geometry | Reproduction code | All ten operation results | Actual versions and checked hashes | Commands, scope and CC0 license
These two projects have matching geometry but different editable histories. Compare changing the named parameter with editing the geometry-only version.
Practice file, not a scan.
Download paired native files and results (ZIP, 24 KB) | Project with named parameter | Geometry-only native project | Direct-edit STEP result | Eight results | Software versions and file details | Reproduction code | Commands, datum, limits and CC0 license
| Required result | Task to perform in your CAD app | Record |
|---|---|---|
| Mesh reference | Import with declared units, check a known dimension and use the agreed section, alignment or reference operation | Application/version, import setting, reference dimension and any unusable area |
| Directly editable B-rep | Import as the agreed surface or solid, inspect validity and perform one specified direct edit, such as a face offset or hole change | Body type, exact edit and before/after dimensions; no claim of recovered original history |
| Native parametric history | Open the native project, change one named parameter and rebuild the dependent features | Parameter name/value, dependencies affected and rebuild warnings or failures |
Keep these outcomes separate in the demo record. A successful STEP import checks a different result from a native-history rebuild. Test the direct edit separately, even if a parameter rebuild fails. Judge the file against the actual part, software edition and requested modification.
Choose the symptom, compare the known files and keep the raw copy. All four pairs are synthetic examples made by us, not physical scans. After is not automatically better.


Drag or use the arrow keys. Home shows after; End shows before.
The outer 100 x 40 x 20 mm bounds match in both files. We know the intended top only because we created this practice box. A real opening or uncaptured area needs separate evidence before filling.
A closed mesh does not establish captured coverage, physical accuracy or freedom from every topology fault.
Open either exact file in the checker below. Choose units there before interpreting dimensions.


Drag or use the arrow keys. Home shows after; End shows before.
Both main views share a coordinate-to-pixel scale; the after image also contains an inset at 5x display zoom. The X-extent bar changes in the known 25.4 ratio. This correction uses our stated author intent; it does not discover a real scanner unit error.
Record the declared units and a known dimension. Correct bounds alone do not establish complete geometry.
Open either exact file in the checker below. Choose units there before interpreting dimensions.


Drag or use the arrow keys. Home shows after; End shows before.
The rendered outside shape can look identical. Orange marks the actual repeated triangle as a diagnostic overlay, including if it lies behind the visible surface. Removing it changes 13 triangles to 12; these exact-coordinate edge checks are for this fixture.
The overlay is not a photograph or a general non-manifold detector. Passing this example does not certify arbitrary STL topology.
Open either exact file in the checker below. Choose units there before interpreting dimensions.


Drag or use the arrow keys. Home shows after; End shows before.
After means later in the exercise, not better. The existing copy applies two simultaneous neighbor-averaging steps with weight 0.5 and no volume constraint. Shared display scale makes the changed dimensions and corner shape visible.
The smoothing is deliberately excessive so you can see the damage. This practice box is not a scanner benchmark.
Open either exact file in the checker below. Choose units there before interpreting dimensions.
Load the synthetic example or choose your own ASCII/binary STL, up to 15 MiB and 200,000 triangles. Your file stays in this browser tab. STL units must be chosen explicitly. This viewer calculates bounds and displays geometry; it does not repair or certify a file.
Drag to rotate. With the preview focused: arrow keys turn, + / - zoom, R resets the view. Use the controls above to set units.
Choose a file or load the synthetic example.
Compare the Smithsonian scan with a copy whose coordinates are multiplied by 25.4. The source gives no independently confirmed physical units or dimensions; use a reference measurement before relying on this file for dimensional work.
Attributed scan and a coordinate-scaled copy; see the source and license in the instructions.
Original STL (7.5 MB) | Coordinate-scaled STL (7.5 MB) | Coordinate check results (CSV) | Instructions and license | Reproduce the check (Node.js script) | Full file report (JSON)
Use the downloadable exercise to practice two checks that do not require a scanner: import scale and missing geometry. The baseline is a closed box measuring 100 x 40 x 20 mm. One copy has its top removed. Another has every coordinate multiplied by 25.4. Both faults are intentional.
The supplied checker compares shared edges and coordinate bounds. Open the files in your own CAD app to test its import and editing behavior. Download the standalone file checker with the three STLs and run it as described in the exercise instructions. Autodesk's Insert Mesh instructions explain where to select import units in Fusion. Check the equivalent setting in the program that imports your file.
Use one row per delivered revision, and attach the files rather than relying on memory of the settings.
| 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 pass/fail evidence |
| Delivery | Mesh-reference check, B-rep direct-edit check or native parameter/rebuild check, according to the agreed deliverable | A different level of editability was delivered, or the receiving system cannot perform the agreed task |
| Revision | Part number, revision, date and approver from your team | Versions cannot be told apart |
Most problems point to a specific fix. If all spans share a factor of ten, check import units and the export/transform history against a known reference first. A common factor alone does not identify its cause. Distorted raw geometry or poor coverage needs a capture or alignment check; changing units cannot repair it. 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.
| File type | What it can carry in this workflow | Check on the delivered file |
|---|---|---|
| STL | Triangulated surface coordinates | Declared import units, bounds, intended holes and closedness where required; color is not established by an STL filename |
| OBJ with companion assets | Surface mesh and potentially materials/textures | Package includes referenced files; geometry scale and texture both import |
| PLY | Points or mesh with properties supported by the exporter | Confirm which attributes are present and retained by the program that opens the file |
| STEP | Neutral CAD geometry, commonly surfaces or solids | Intended body type, units, validity and the agreed direct edit; native feature history is not inferred |
| Native CAD project | Application-specific bodies and possibly parameters/history | Open in the agreed version, find the named parameter and rebuild the intended dependency |
Format capability is not proof of this scanner's export or of an installed software edition. Keep the delivered file, not a screenshot. Measure the same control dimension after each conversion. Declaring inches for coordinates intended as millimeters changes their interpreted scale; repairing topology cannot correct an unexplained unit choice.
The STL mesh, colored PLY point cloud and textured OBJ can have the same outer dimensions while containing different data. Check that your program receives faces, point colors or texture files as required.
Practice file, not a scan.
Download the practice pack (ZIP) | Six import results (CSV) | Repeat the file checks | STL | Complete OBJ | MTL | Original checker PNG | Absent-MTL case | Absent-PNG case | Absent-PNG material | Mesh PLY | Point-only PLY | Actual version, settings and source hashes | Blender reproduction code
Preserve the full mesh before reduction. Trial the actual triangle count, feature size and receiving operation on the computer being quoted. Avoid promising a universal maximum triangle count or processing time. Reduction, face grouping and conversion may change different features.
Autodesk's Convert Mesh documentation , checked October 17, 2026, distinguishes faceted and prismatic conversion and an Organic method provided through the Fusion Design Extension. Confirm the installed edition and available operation. A converted body still needs the requested edit and geometry check.
Capture software, mesh editing, reconstruction and inspection can be separate products. Write the exact product, edition, version, license term and output operation in the quote.
| Path | Task to complete | Cost or compatibility question |
|---|---|---|
| Manufacturer capture software to mesh | Registration, preserved raw data and the exact mesh export | Included license, supported capture/processing computer and project access |
| Mesh editor | Remove a fixture, preserve a real bore and inspect boundary edges | Local/cloud handling, available tools and what the operation changes |
| CAD reconstruction software | Extract reference geometry, construct intended solids and compare them with the retained mesh | Exact edition, renewal terms, neutral export and your CAD app/version |
| Inspection software | Define datums, evaluate named features and produce the agreed report | Appropriate reference, uncertainty, license and documented decision rule |
Our catalog's mesh formats and software notes are documentary starting points. No file format alone establishes a successful transfer. In particular, geometry export, texture export and native history need different checks.
Use the requirements for your exact model and software release. Check capture and desktop processing separately before choosing a computer.
Scroll horizontally to read every requirement and source.
| Exact model | Capture and computer stages | OS, GPU, RAM and connection guidance | Manufacturer sources and checks |
|---|---|---|---|
| EINSTAR 2 | Choose mode and desktop/mobile host | EXStar Hub 2.0: Windows 10/11 64-bit, minimum 13th Gen i7 or Ryzen 7 5800, 32 GB RAM and RTX 2060; recommended i9/Ryzen 9 7900X, 64 GB and RTX 3060. Mac: Tahoe 26.2+, named Apple silicon, 16 GB minimum / 24 GB recommended. EXStar Mobile: Android 15+, Snapdragon 8 Gen 2+, 8 GB minimum;Snapdragon 8 Elite (Gen 4) or later/12 GB recommended. Apple app availability is still pending. | EINSTAR 2 product page (new tab) EXStar Mobile: phone requirements and downloads (new tab) EXStar Hub: computer requirements and downloads (new tab) EXStar Hub 2.0 release notes (new tab) Capture last checked Requirements last checked |
| EINSTAR VEGA | On-device capture; check desktop processing/export | Capture runs on device. StarVision desktop processing: Windows 10/11 or macOS 11 or later on Apple silicon; manufacturer recommends Intel i7 and 32 GB RAM for PC processing. | EINSTAR VEGA product page (new tab) Capture last checked Requirements last checked |
| CR-Scan Raptor | Choose mode and desktop/mobile host | Creality's performance guide recommends macOS 14 or later, Apple M2 or later and at least 32 GB RAM. The older Raptor manual lists macOS 11.7.7+, M1/M2/M3 and 16 GB; confirm the exact software and project size. For Windows, that older manual lists Windows 10/11, i7 7th Gen, NVIDIA 6 GB VRAM and 16 GB RAM. A compatible optional Scan Bridge adds a separate phone capture, processing and sharing route. | Original Raptor user manual (PDF, new tab) Manufacturer instructions CrealityScan mobile app guide (new tab) CrealityScan 4.3.2 release notes (new tab) Capture last checked Requirements last checked |
| MIRACO Plus | On-device capture; check desktop processing/export | Capture and PMK coordinate calculation can run onboard. The manual documents external USB-storage sharing of model files and coordinate data. Further computer editing and the documented PMK computer point-cloud export path have separate requirements, including Revo Scan 5.4.12+. This is not a blanket PC requirement for every PMK calculation or output. | All in one 3d scanner miracoplus product page (new tab) MIRACO Plus user manual (new tab) MIRACO Plus user manual (new tab) Capture last checked Requirements last checked |
| POP 4 | Choose mode and desktop/mobile host | Multi-line laser capture requires a computer; full-field and VCSEL may capture on a compatible phone. PC minimum Windows i7 13th Gen or Ryzen 7 5800, RTX 3060 8 GB, 16 GB RAM; Mac M1 Pro/Max/Ultra 16 GB. Android mobile requirements: Android 11 or later, 12 GB RAM or more, 128 GB storage or more; manufacturer CPU baseline Snapdragon 8 Gen1, Dimensity 9000, Kirin 9000S equivalent performance or better. Revo Scan for iOS supports POP 4; the download center lists version 6.0.4.0 and the App Store requires iOS 15 or later. Check the phone CPU, RAM and storage requirements separately. POP 4 multi-line laser capture needs a computer; RevoMirror casts its screen to a phone. | Pop4 wireless hybrid 3d scanner product page (new tab) POP 4 user manual (new tab) Revopoint software downloads (new tab) Capture last checked Requirements last checked |
| Peel 3 | Computer capture, processing and export | Current manufacturer guidance: Windows 11; minimum i7 6 cores 2.3 GHz AVX2, 16 GB RAM, NVIDIA 6 GB VRAM, 200 GB free SSD. Recommended i7 8 cores 2.5 GHz, 32 GB RAM, RTX 3070 8 GB, 512 GB SSD; USB 3.0. | Peel 3 product page (new tab) Manufacturer instructions Capture last checked Requirements last checked |
Record the current workstation, exact OS release and architecture, GPU and memory, RAM, available ports and power arrangement. Trial capture and the largest intended reconstruction separately. Request a complete workstation/software quote if either stage needs another machine.
For a wireless setup, compare computer, phone and standalone paths before choosing where each stage will run.
Choose what runs the capture app: a connected computer, a compatible phone, or the scanner itself. Wi-Fi may still connect to a desktop or only mirror a screen; it does not by itself establish direct phone capture. Check capture, meshing/sharing and CAD editing as separate stages.
| Capture setup | What to confirm | What it does not establish |
|---|---|---|
| Laptop or desktop | Exact mode, OS, GPU/RAM, ports and capture software | That a wireless connection runs the capture app on a phone |
| Phone with a dedicated scanner | Named mobile mode, compatible phone/app and any model-specific bridge | That the phone camera supplied the scan, or that every desktop mode works on mobile |
| Capture on the scanner itself | Which processing and export steps run on that device | That meshing, CAD reconstruction and the final edit need no other computer |
In the selector, Phone, no laptop and No computer at all describe the capture setup. Answer the separate processing-computer question too. Include any additional phone, bridge, computer and software in the full-kit budget.
Creality's mobile-app guide and Revopoint's POP 4 mode table , checked October 17, 2026, document model- and mode-specific paths. Confirm the exact app, firmware and delivered accessories.
Record OS and processor architecture, GPU and dedicated memory where specified, RAM, required ports, disk space and the exact capture/reconstruction releases. Check both the manufacturer's minimum and recommended specification without treating a recommendation as a processing-speed measurement. Test the actual dataset size, export and editing operation.
The catalog filters retain unknown compatibility. MetroX-family Apple versus x86_64 statements need an exact build confirmation; if macOS is not listed, ask the manufacturer whether the exact application and scanner support it. Do not order a workstation solely from a brand-wide description.
EINSTAR 2 and Rockit support Android capture, meshing and local OBJ/PLY/STL export in EXStar Mobile. POP 4 has released iOS support for its mobile modes; laser capture still runs on a computer with RevoMirror for the phone display. For S1, official descriptions conflict on direct phone capture. Compare the named phone setups before choosing one.
A coin, miniature, small fastener and machined housing ask different questions. For decoration, retained texture and visible shape may decide the job. For fit, the bore, edge, thread or mating face must survive capture, meshing and the receiving operation.
| Object | Name the detail before the demo | Avoid this shortcut |
|---|---|---|
| Coin or miniature | Relief, edge, underside and intended print scale | A textured image as proof of geometric relief |
| Fastener or fitting | Thread/seat geometry and independently measured functional dimensions | Deriving a working thread from headline point spacing |
| Small housing | Bore, thin wall, recess and mounting interfaces | Treating the manufacturer's minimum object cube as the minimum usable feature |
Inspect unedited geometry of the named detail. A turntable can improve a controlled workflow but cannot expose every occluded surface. For simple mechanical geometry, independent dimensions and manual CAD may be more suitable than reconstructing every surface.
Phone photogrammetry and phone depth capture are different inputs. Evaluate them by the output and part, not by a single claim about phone accuracy. A phone can also run the app for a separate 3D scanner. In that setup the dedicated scanner supplies the capture data. Keep this distinct from using the phone camera or depth sensor; see the three capture setups.
Apple's Object Capture guidance , checked October 5, 2026, describes photogrammetry from overlapping photographs. It advises choosing stable objects and avoiding reflective, transparent, very thin or featureless surfaces. It also distinguishes images with depth information from images that may need scale adjustment.
In a 2024 laboratory study , Kersten, Sönksen and Przybilla used several phones, three test objects, image reconstruction in Metashape and an ATOS 5 reference. That is evidence for the studied photo workflows under those conditions; it is not a universal phone-LiDAR result or a test of the scanners in our catalog.
| Needed result | Low-commitment route to trial | Pass/fail check |
|---|---|---|
| Appearance or visual reference | Controlled photographs of a stable textured object | Geometry coverage, texture package and independently checked scale |
| Accessible simple mechanical geometry | Independent dimensions plus CAD modeling | Functional dimensions and the intended edit |
| Detailed part mesh | Phone/photo trial and a dedicated-scanner demo on the same part | Named detail in raw geometry, scale and the required task in the target program |
| Dimensional inspection | A suitable measurement process or specialist service | Reference quality, uncertainty and the agreed pass/fail rule |
Use the practice files to learn the file and unit checks. Keep the original images or captures, software release and a control dimension when running your own trial.
Use a stable part and enough visibility of its reference features or targets. A smooth symmetrical object can remain ambiguous while rotating. A movable fixture or shifted marker arrangement can change the reference between passes.
Test a complete rotation, underside repositioning, interrupted tracking and recovery. Record which data were discarded and which transform joined the passes. Keep a full-resolution copy before removing fixtures. The accessory must be compatible with the exact scanner/software mode and able to hold the actual part without deflection; an included turntable is not an accuracy guarantee.
Choose an exercise or a blank worksheet for your next task. Instructions, source credits and licenses are included with the files.
Practice models and attributed scans are labeled separately. Your files stay on your device.
Find a missing top even when the three outer dimensions still match.
Read instructions (1.3 KiB)3D Scanner Match original synthetic geometry, code or blank planning template. CC0 1.0. Author-defined millimeters where geometric; choose units on STL import.
Compare the attributed original scan file with an intentional coordinate-scale derivative.
Read instructions (1.7 KiB)Smithsonian original scan file and attributed coordinate derivative. CC0 1.0. Coordinate units; physical size unverified.
Original Smithsonian file and license
Check imported units and missing faces in Blender.
Download ZIP (8.4 KiB)3D Scanner Match original synthetic geometry, code or blank planning template. CC0 1.0. Author-defined millimeters where geometric; choose units on STL import.
Keep mesh faces, point colors and OBJ companion assets distinct, even when bounds match.
Download ZIP (10.4 KiB)3D Scanner Match original synthetic geometry, code or blank planning template. CC0 1.0. Author-defined millimeters where geometric; choose units on STL import.
Use given point pairs to inspect rigid alignment and a separate control span.
Read instructions (1.9 KiB)3D Scanner Match original synthetic geometry, code or blank planning template. CC0 1.0. Author-defined millimeters where geometric; choose units on STL import.
Compare intentional holes, scale faults, duplicate faces and aggressive smoothing.
Read instructions (891 B)3D Scanner Match original synthetic geometry, code or blank planning template. CC0 1.0. Author-defined millimeters where geometric; choose units on STL import.
Inspect nominal pin/hole clearance and computed CAD intersection, without a physical-fit claim.
Read instructions (933 B)3D Scanner Match original synthetic geometry, code or blank planning template. CC0 1.0. Author-defined millimeters where geometric; choose units on STL import.
Separate a mesh, a STEP body, a direct edit and a native rebuild.
Read instructions (2.0 KiB)3D Scanner Match original synthetic geometry, code or blank planning template. CC0 1.0. Author-defined millimeters where geometric; choose units on STL import.
Check the supplied STEP files in FreeCAD before you agree on a CAD handoff.
Read instructions (2.1 KiB)3D Scanner Match original synthetic geometry, code or blank planning template. CC0 1.0. Author-defined millimeters where geometric; choose units on STL import.
Reopen a native project, change the named hole parameter and rebuild its dependent feature.
Download ZIP (32.9 KiB)3D Scanner Match original synthetic geometry, code or blank planning template. CC0 1.0. Author-defined millimeters where geometric; choose units on STL import.
Compare matching geometry with and without the original requested parameter dependencies.
Download ZIP (23.7 KiB)3D Scanner Match original synthetic geometry, code or blank planning template. CC0 1.0. Author-defined millimeters where geometric; choose units on STL import.
Try the example calculations, or use the blank worksheet for your own reference and repeated measurements.
Read instructions (1.0 KiB)3D Scanner Match original synthetic geometry, code or blank planning template. CC0 1.0. Author-defined millimeters where geometric; choose units on STL import.
Record a part test, file check or scanning-service brief for your own part.
Read instructions (553 B)3D Scanner Match original synthetic geometry, code or blank planning template. CC0 1.0. Record and declare your own units.
Record preparation permission, coverage and the evidence to request for a difficult surface.
Read instructions (2.4 KiB)3D Scanner Match original synthetic geometry, code or blank planning template. CC0 1.0. Record and declare your own units.
Prepare a vendor demo with the actual part, permitted coating and targets, capture mode, reference, raw files, processing settings and the final operation in your target program. Prepare a service request with access, logistics, confidentiality, deadline, requested outputs and revision and pass/fail rules.
The download library includes practice geometry and blank demo or service briefs. Choose the kit for your next check, and keep private drawings and personal information out of public examples.
Autodesk import and mesh-conversion instructions were checked November 6, 2026; imported-history and edition references were checked October 17. Confirm the available commands in your installed Fusion version and license.
Use the checklist to agree on the delivered file and the edit it must support.