Inspect the scan before using cleanup commands
View the scan with and without its texture. Texture detail can hide rough geometry or make an incomplete surface appear continuous. Rotate underneath the object and inspect areas that the camera or scanner could not see. A plausible color patch does not prove that the underlying wall is present.
Check scale against a known dimension when measurement matters. Keep the original scan with its texture images, material files, and capture notes. Save geometry-only exports as separate files so you can return to the textured source if a cleanup step goes wrong.
| Observed feature | Possible interpretation | Action before reduction |
|---|---|---|
| Floating island | Background fragment or a real separate part | Inspect each component before deleting it |
| Open border | Occlusion, cut edge, or intentional opening | Decide whether the opening should exist |
| Rippled surface | Capture noise or real fine detail | Compare photographs or the physical object |
| Overlapping shells | Merged captures or separate surfaces | Check alignment and intended connectivity |
| Fine texture on a coarse shape | Appearance detail without geometric relief | Keep textures; remeshing cannot recover the missing relief |
Clean a working copy in Blender
Duplicate the imported scan, then work through the defects one at a time. Select the area you mean to change before running a cleanup command. Check the result immediately so you can undo a merge or fill that affects the wrong surface.
Separate background and fragments
In Edit Mode, inspect linked components and select only confirmed unwanted geometry. Delete Loose helps with unconnected elements, but it is not a universal remove-floating-islands button: a detached shell with many connected faces can remain.
Merge only unintended duplicates
Use Mesh > Clean Up > Merge by Distance with a small distance relative to the object. Inspect seams, thin walls, and adjacent surfaces afterward. A large threshold can join two surfaces that should stay separate.
Repair known missing surface
Inspect each border before using Fill Holes or a more deliberate fill. A vase mouth or socket is not a defect. A large occluded region requires a shape decision; automatically filling it invents geometry rather than recovering a measurement.
Check orientation and density
Inspect normals and shading, then compare a conservative simplified copy with the source. Use remeshing only when rebuilding the surface is actually useful; do not add it automatically to every scan-cleanup sequence.
Example: keep the handle, remove the table
Suppose you scan an ornament with a ring-shaped handle. The mesh includes a patch of table, but the scanner never saw the underside. Delete the table patch, preserve the opening through the handle, and inspect the underside separately. Filling that unseen area creates an estimated shape; it does not recover the missing scan data.
After isolating the ornament, compare the handle thickness and opening in the original and simplified versions. If the opening closes or the loop becomes disconnected, undo the reduction. For a textured display asset, compare the rendered surface as well as the wireframe; damaged UVs may take longer to fix than the reduction saved.
Keep textured scans in a tool that preserves their materials
The browser tool reads OBJ, STL, ASCII PLY, and OFF below 25 MB and returns a geometry-only OBJ. Scan textures, vertex colors, material assignments, and UV layouts are not retained. Use it on a separate copy if you only need to experiment with geometry. Point clouds need surface reconstruction in another application before they can be remeshed here.
Watch for new open borders after reduction. The browser's face-limiting step can create gaps, including on an input that was originally closed. The troubleshooting guide includes a downloadable synthetic sphere that reproduces this failure.
Decide what a finished scan means for your task
For a viewer or static scene, check silhouette, shading, and texture appearance from the intended viewing distances. For a print, also check closed surface requirements, wall thickness, and the sliced layers. For measurement work, compare against calibrated reference data; an attractive remesh is not a substitute for that validation.
Save the working mesh separately and record the important operations and thresholds. Keep the source until the downstream application has loaded the new file successfully. That makes it possible to change a cleanup decision without repeating the entire capture or losing the original texture reference.
Common questions
Will remeshing remove scan noise automatically?
It can suppress some geometric detail, including noise, but it can also erase real features. Compare with reference photographs or the original object and keep a copy before smoothing or rebuilding the surface.
How do I choose a Merge by Distance threshold?
Start with a distance small relative to the object and inspect the selected area after merging. Increase it only if unwanted duplicate vertices remain. Undo the change if a seam closes or nearby surfaces join; the same numeric threshold will behave differently on scans at different scales.
Can I retain the scan texture in this browser tool?
No. Its OBJ export contains geometry only. Keep the textured source for texture transfer or baking in another application.
Should every hole in a scan be filled?
No. Keep intentional openings such as handles and sockets. Fill missing scan regions only when you can accept an estimated shape in place of the uncaptured surface.
References
Based on the documentation below, checked October 22, 2026. Blender controls may differ by version.