3D
Remeshing and retopology
Three stages in your browser turn a generated mesh into quads that keep their textures, which almost nothing else does.
Remeshing here runs in three stages, locally, and **it re-projects your UVs and textures onto the new topology**. A remesh that keeps the surfacing is rare, and it is the difference between a usable step and one that costs you the texture work. ## Why generated meshes need this A mesh from an image or a prompt is a good likeness with bad topology. The triangles are dense and irregular, and AI output reliably carries non-manifold shells, hidden internal geometry and self-intersections. That is the specific reason naive remeshers explode on it rather than merely doing a poor job. That is what the first stage exists for. ## The three stages 1. **Manifold repair**, by rebuilding the surface from a voxel signed-distance field. This is the same class of preprocessing that ZRemesher-style tools run, and it is what makes the rest possible 2. **Isotropic remeshing**, which evens out the triangle distribution 3. **Quad extraction**, field-aligned, which produces the quads The quads are real quads, carried through the GLB, so they arrive in Cinema 4D or Blender as quads rather than as triangulated geometry. ## What it costs Nothing in credits, and roughly **30 to 60 seconds on a 50,000-triangle mesh**. Denser input takes longer. All of it happens on your machine, which is why it is free and why it keeps working during a provider outage. :::note[A real GPU helps and is not required] The pipeline is WebAssembly running locally. It loves a proper GPU and it completes on a thin laptop, more slowly. Nothing about it degrades in quality on slower hardware, only in speed. ::: ## The alternatives on the card Local remeshing is not the only route, and the others are provider calls that cost credits. | Option | When to reach for it | |---|---| | **remesh.js** | The default. Free, keeps textures, real quads | | **hunyuan-smart-topo** | When you want a model's opinion about edge flow | | **tripo-remesher** | The provider-side counterpart, useful as a second opinion | | **ultrashape** | Reshaping rather than retopologising | Try the local one first. It costs nothing to find out whether it was enough. ## Where it sits in a pipeline The usual order, and each step is worth doing in it: 1. Generate the mesh from an image or a prompt 2. **Remesh** it, so the topology is workable 3. Retexture or upscale the textures if the surfacing needs it 4. Export, with quads intact, into your modelling package Skipping step two and exporting straight from a generator is the most common way to end up with an asset nobody downstream can work with. :::caution[Remesh before import, not after, for heavy scans] A multi-million-triangle scan will load onto the board and make it heavier for everyone sharing it. Reducing it first is kinder, and the tool is free either way. :::Remeshing here runs in three stages, locally, and it re-projects your UVs and textures onto the new topology. A remesh that keeps the surfacing is rare, and it is the difference between a usable step and one that costs you the texture work.
Why generated meshes need this
Section titled “Why generated meshes need this”A mesh from an image or a prompt is a good likeness with bad topology. The triangles are dense and irregular, and AI output reliably carries non-manifold shells, hidden internal geometry and self-intersections. That is the specific reason naive remeshers explode on it rather than merely doing a poor job.
That is what the first stage exists for.
The three stages
Section titled “The three stages”- Manifold repair, by rebuilding the surface from a voxel signed-distance field. This is the same class of preprocessing that ZRemesher-style tools run, and it is what makes the rest possible
- Isotropic remeshing, which evens out the triangle distribution
- Quad extraction, field-aligned, which produces the quads
The quads are real quads, carried through the GLB, so they arrive in Cinema 4D or Blender as quads rather than as triangulated geometry.
What it costs
Section titled “What it costs”Nothing in credits, and roughly 30 to 60 seconds on a 50,000-triangle mesh. Denser input takes longer.
All of it happens on your machine, which is why it is free and why it keeps working during a provider outage.
The alternatives on the card
Section titled “The alternatives on the card”Local remeshing is not the only route, and the others are provider calls that cost credits.
| Option | When to reach for it |
|---|---|
| remesh.js | The default. Free, keeps textures, real quads |
| hunyuan-smart-topo | When you want a model’s opinion about edge flow |
| tripo-remesher | The provider-side counterpart, useful as a second opinion |
| ultrashape | Reshaping rather than retopologising |
Try the local one first. It costs nothing to find out whether it was enough.
Where it sits in a pipeline
Section titled “Where it sits in a pipeline”The usual order, and each step is worth doing in it:
- Generate the mesh from an image or a prompt
- Remesh it, so the topology is workable
- Retexture or upscale the textures if the surfacing needs it
- Export, with quads intact, into your modelling package
Skipping step two and exporting straight from a generator is the most common way to end up with an asset nobody downstream can work with.