Automatic retopology depends heavily on the structure of its input mesh. A preflight check helps you distinguish errors worth fixing from intentional model construction—and gives you a baseline for evaluating the result. It also prevents the common mistake of treating a successful processing job as proof that the output is ready to ship.
This guide starts with the 3DLabTools Model Analyzer and ends with a cautious experiment in Auto Retopology Alpha. Analyzer accepts GLB and FBX up to 100 MB (100,000,000 bytes). Its detailed topology pass has separate triangle and transfer-size budgets; a skipped check is not evidence of zero defects. Auto Retopology accepts GLB, embedded glTF and FBX, with its own geometry admission checks.
1. Keep an untouched source copy
Export a separate test asset and store the editable project in your normal source-control or asset folder. Retopology can change face order, vertex positions, surface detail, UV coordinates and downstream assumptions. Do not process the only surviving version of a character, environment or client delivery asset.
Capture reference views from the front, side, top and a few critical close-ups. Note the intended dimensions and which features must remain intact.
2. Inspect geometry totals and scene structure
Open the Model Analyzer with a supported asset. Review triangle and vertex counts together with mesh count and hierarchy. A single large object and a scene containing hundreds of disconnected mechanical parts pose different problems even if their total polygon counts match.
A complicated asset may contain multiple legitimate shells: separate bolts, handles, wheels, panels or other components. Do not indiscriminately weld those parts together or fill every visible opening. First determine what is intentional.
Checkpoint: You know whether the model is a simple static shell, a multi-part environment/prop, or an animated/skinned character. The latter needs extra caution and is not an automatic static-retopology candidate.
3. Interpret topology warnings in context
Review the measured topology indicators: connected components, tiny components, boundary edges, non-manifold edges, exact degenerate faces, near-zero-area faces and inconsistent winding where available. Duplicate-face and unreferenced-vertex repair are separate cleanup concerns; this Analyzer view does not promise those measurements. Treat findings as prompts for inspection—not as automatic proof that the file is broken.
An open architectural doorway may be intentional. A non-manifold intersection inside a scanned solid can be accidental. A multipart asset is not inherently defective. Decide what must be corrected in the source application and what should remain separate.
For more on what Analyzer metrics mean, consult How to Analyze a 3D Model Before Using It on the Web.
4. Identify what must survive the rebuild
Write down the critical requirements of the target asset:
- Silhouette: Which outer edges or thin features cannot drift?
- Mechanical separations: Which individual parts must remain distinct?
- UV/material appearance: Must existing texture placement survive, or is a re-UV/rebake workflow acceptable?
- Rigging: Is skinning or deformation required? If yes, use a deformation-aware workflow and plan separate acceptance tests.
- Output budget: What mesh density does the actual downstream use need?
This list is your acceptance standard. It prevents you from accepting an attractive wireframe that silently broke the surface detail or asset workflow.
5. Run only a supported, reversible test
If the current Auto Retopology Alpha supports the selected static mesh, try a copy within its published constraints. Read the preflight recommendation and use the recommended target when available. Small or thin shells may be kept unchanged; a run can therefore contain both processed and preserved geometry. Do not expect identical results on a clean statue and a complicated, overlapping multipart vehicle.
The Alpha label matters: processing may fail, stall or produce topology unsuitable for production. The output is a neutral rebuilt mesh: original textures and material assignments are not transferred, and rigging, morph targets and animations are not preserved. A textured or rigged import is not a preservation promise. A failed result should lead to a clearer diagnosis or a different authoring approach, not a promise of guaranteed repair.
6. Compare before and after
Inspect the source and output using comparable camera views. Check silhouette, thin areas, holes, panel boundaries, new edge distribution and, where relevant, texture/UV continuity. Reanalyze the output when a supported export is available. Use the actual downstream editor, engine or viewer to test the result.
Do not use a lower triangle count as the sole acceptance gate. If the mesh was intended for animation, verify deformations in extreme poses using a rigging-aware pipeline rather than assuming a static topology preview proves success.
Illustrative diagnostic walkthrough
Consider a prop made from a thick body and thin separate panels. A multi-component count alone does not justify welding the panels into the body. Read the shell recommendation: a thin panel or a very small shell can be preserved rather than remeshed. If detailed topology was skipped for a large input, keep the result marked unmeasured and inspect the asset in an authoring tool. This example explains decisions; it does not report benchmark measurements.
A simple pass/fail checklist
A candidate may be worth keeping if it preserves the expected silhouette, intentional separate parts, required visual details and downstream compatibility. Reject or revisit it if it merges unrelated geometry, destroys thin features, changes essential openings, or cannot support the next pipeline step.
Next step: Analyze your mesh and only then try Auto Retopology Alpha on a separate copy. If the actual issue is browser rendering cost, follow the web optimization checklist instead.
Verification note: checked against V1 Analyzer metrics and experimental Retopology preflight/export limitations on October 20, 2026.
Explore product documentation or open the 3D Model Analyzer.