Before buying a scanner
Phone or dedicated 3D scanner?
Try the phone you own on a representative object. Check the exported file in the application you will use. If it preserves the feature and passes your acceptance check, you may already have the capture setup you need.
How will your phone capture the object?
Common routes, shown schematically. Apps may combine photographs and depth.
A phone can contribute photographs, depth data or the controls for a separate scanner. Find out which method your app uses, where it creates the model and what you can export. Those answers make the comparison useful.
Photos from your phone
Photogrammetry reconstructs a model from overlapping photographs. The phone supplies the images; reconstruction may happen on the phone, a computer or a service, depending on the app.
Start with a rigid object that keeps its shape while you capture it. Surface patterns give the software features to match between views. Plain, reflective, transparent and very thin objects need particular care. Apple's photograph capture guidance describes these limits for its Object Capture workflow.
Use consistent, diffuse lighting and cover the sides your next task needs. Check whether the app lets you retain the original images, reconstruct again and export a model in a format your application accepts.
Depth on your phone
A depth-capable phone can record distance information as part of a capture. Some apps also combine photographs and depth. Apple's Object Capture walkthrough shows that combination, including a way to handle some low-texture objects.
A phone's LiDAR label does not tell you which small feature the exported model will preserve. Apple's scene reconstruction example builds an estimated mesh of the surrounding environment; its plane-detection option can flatten surfaces. Treat the final geometry as something to inspect for your task.
Match the exact phone, app version and operating system. For example, Apple's current Object Capture sample has specific hardware and OS requirements. They apply to that sample, rather than to every app that can use phone photographs.
Phone with a dedicated scanner
In this setup, the external scanner captures the object while the phone participates in the workflow. Confirm whether the phone controls capture, processes the data or displays a session running elsewhere.
The wireless scanner guide gives named scanner and phone paths, including cases that require a compatible bridge. Include that hardware and every finishing device in the comparison. Confirm capture and export with the scanner, phone and any bridge in the setup.
Match the file to your next task
Choose the deliverable before comparing the appearance of previews.
| Your next task | What to ask for | What to check |
|---|---|---|
| Show an object in a visual scene | A mesh with its materials, or a supported visual representation | Appearance and coverage in the intended viewer |
| Print a physical part | A mesh your slicer can read | Scale, openings, thin features and the actual layer preview |
| Rebuild a mechanical part | A usable reference mesh and a separate reconstruction path | The critical feature, reference dimensions and the intended CAD edit |
| Accept a dimensional result | A defined measurement and acceptance process | The reference, measurement conditions and evidence required by the job |
Apps can offer a textured mesh, a point cloud or a Gaussian splat. A capture may also include more than one output. Polycam's capture and export documentation distinguishes splat artifacts from mesh data and requires mesh data for its mesh export formats. Ask for the actual file your next tool needs, including any separately generated mesh.
A mesh opens a path to CAD reconstruction. It does not supply a native parameter tree by itself. Use the CAD handoff checks when the job requires an editable solid or a named parameter change.
Run the same-object file check
- Name the feature. Choose the edge, recess, hole or silhouette that matters. Write down how you will decide whether the result is usable.
- Keep a reference. Record a span you can check independently, along with the intended units. Retain source images or the capture project where the app supports it.
- Finish the capture. Reconstruct and export using the devices and app features you will actually have. Confirm export access and any required processing before committing to a paid plan.
- Inspect the geometry. Open the export in the software you will use. View it without the color texture, inspect the feature and look for holes or doubled surfaces. A convincing color image can leave a geometry problem unnoticed.
- Check the next operation. Compare the reference span, inspect the slicer's layers or perform the intended CAD edit. Check scale and the small feature separately.
The accuracy guide helps choose a check for the question you need to answer. The scan repair guide routes a visible file problem to its next useful check.
Compare a dedicated scanner on the same object
If the phone export does not pass, identify what failed before choosing another device. Missing coverage, surface reconstruction, a lost feature and an incompatible file require different responses.
Give the scanner vendor the same object, critical feature and receiving-file task. Request the original capture and the exported result, then repeat your check in the same application. Record the mode, preparation and devices used. If a demonstration changes the surface, decide whether that preparation is allowed for your own object; the surface guide explains the questions to ask.
Price the complete working route: scanner, any bridge or computer, software features, processing and export. The scanner catalog and selector help compare dedicated capture setups once you know what needs to improve.
Where to go next
- The phone file passes your task: keep that workflow and its settings for the job. You can postpone a hardware purchase while you learn its limits on other objects.
- The model looks useful but fails a fit or measurement check: keep its role clear. It may still serve as a visual asset while the mechanical task needs a different capture or reconstruction route.
- A specific feature is missing: bring that feature and the failed export to a same-object scanner trial.
- You need to finish without a computer: check capture, processing and export as separate stages.
Sources for the capture methods
The linked Apple capture, scene reconstruction and sample documentation, its WWDC23 demonstration, and Polycam's public export documentation were read on October 20, 2026. They explain particular software workflows. Device support and export access should be confirmed in the app you choose.