The outcome

Deliver a licensed 3D asset that meets measured topology, texture, scale, rig, and runtime requirements.

Meshy is a Generative 3D platform and API for text-to-3D, image-to-3D, texturing, remeshing, rigging, and animation. Rapidly prototyping 3D props and characters, converting concept images into meshes, generating textures, and preparing draft assets for games, visualization, AR, or further artist refinement. This guide narrows that broad capability into one repeatable outcome, with checkpoints that keep the source material and your judgment in the loop.

Before you begin

Set the boundary before the tool starts.

Choose one real task, identify who will use the result, and decide what evidence or test will make the result acceptable. Gather only the source material needed for that task. If the work contains confidential, personal, regulated, or client-owned information, confirm that the platform and account are approved before sharing it.

Troiana principle

AI should make the work easier to inspect. If the workflow removes the source, the owner, or the review step, redesign the workflow.

Step by step

A workflow you can repeat.

  1. 01

    Define silhouette, dimensions, style, polygon and material budget, topology, UVs, textures, rig, animations, formats, engine, platform, license, and acceptance tests.

  2. 02

    Submit an authorized prompt or clean multi-view concept, create geometry previews first, and select on silhouette and proportion before texture refinement.

  3. 03

    Download and inspect scale, normals, watertightness, intersections, topology, UVs, texture seams, materials, likeness, and protected design similarity in a 3D editor.

  4. 04

    Retopologize, unwrap, bake, correct textures, set pivots and collisions, rig and weight where needed, and preserve the generated source as a separate derivative.

  5. 05

    Import into the target engine, test animation, lighting, LODs, memory, draw calls, physics, and hardware performance, then archive task IDs, plan license, edits, and attribution.

Working standard

What good use looks like.

  • Approve geometry before texturing.
  • Treat generation as a draft mesh.
  • Test the final asset in-engine.

A plausible render can hide broken topology, non-manifold geometry, poor UVs, unusable rigs, excessive polygons, or copied design language. Current Meshy rights and data handling vary materially by plan: free outputs require CC BY attribution, non-enterprise content may be used for model improvement, and API outputs have stated retention. Never upload sensitive personal data, confirm current commercial and training terms, preserve task assets promptly, and require artist and engine QA.

Official references

Check the current product documentation.

Features, plan limits, availability, and data controls change. These official pages are the starting points used for this collection.