> For the complete documentation index, see [llms.txt](https://docs.flora.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.flora.ai/nodes/3d-node/3d-to-3d.md). # 3D to 3D Remesh, retexture, or segment an existing 3D asset 3D to 3D takes a model you already have on the canvas—generated, imported, or saved in Assets—and produces a new 3D asset from it. Use it to clean up topology for a game engine, swap in a new material, or split a model into parts. ## How It Works 1. Start with a 3D Node that holds the source model. 2. Add a second 3D Node and drag a connection from the source node's output handle to its input. 3. The new node switches to **3D to 3D** mode and the model picker shows only models that accept a 3D asset. 4. Pick a model, add any prompt or reference image it asks for, and click **Run**. The source node is untouched—each 3D-to-3D run produces a separate asset you can compare, export, or feed further down the chain. ## What You Can Do * **Remesh** — change topology (triangles or quads) and polygon density with **Meshy 5 Remesh** or **Tripo Remesh**, which also bakes the existing textures onto the new mesh * **Retexture** — apply a new surface guided by a text prompt or a reference image with **Meshy 5 Retexture** or **Trellis 2 Retexture** * **Segment** — split a model into semantic parts with **Tripo Segment** ## Models Visit [3D Models](/models/3d-models.md) for the full list of 3D-to-3D models. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://docs.flora.ai/nodes/3d-node/3d-to-3d.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.