Generative 3D platform
How to use
Meshy.
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.
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 covers the whole path in one place: official access, a first session that produces something reviewable, the checks that make output trustworthy, and the permissions worth limiting before you connect real work.
AI should make the work easier to inspect. If the workflow removes the source, the owner, or the review step, redesign the workflow.
Access & setup
Find, install, and sign in to Meshy
Get into the official Meshy experience with the right account and a setup you understand.
- 01
Start at https://www.meshy.ai/ and confirm the domain before entering account or payment information.
- 02
Availability: Meshy is available through a browser-based web application, plugins, and asynchronous developer APIs for 3D generation and processing tasks.
- 03
A Meshy account and plan with the needed privacy, commercial, attribution, and API rights; authorized prompts or reference art; 3D review software; polygon, topology, UV, texture, rig, and engine acceptance criteria.
- 04
Sign in with the account you intend to keep using, then review plan, data, notification, and permission settings.
- 05
Run one low-risk test task before connecting sensitive files, repositories, or workspace data.
- Use official download pages.
- Review permissions during setup.
- Keep installers and applications updated.
First session
Your first useful Meshy session
Learn the interaction loop using a small task with a clear outcome.
- 01
Define the asset purpose, silhouette, dimensions, style, polygon budget, topology, UVs, textures, rig, animation, formats, engine, platform, license, and approval criteria.
- 02
Use an authorized non-sensitive prompt or concept image and create a geometry preview before spending credits on refinement or downstream processing.
- 03
Inspect silhouette, scale, watertightness, normals, topology, intersections, UVs, texture seams, materials, likeness, and accidental protected design elements in a 3D editor.
- 04
Retopologize and correct the asset, validate rigging and animation where needed, test the actual engine and performance target, and archive source, task IDs, plan license, edits, and attribution.
- State the outcome before the background.
- Provide the real source material.
- Review the result before expanding the task.
Quality control
Check the quality of Meshy output
Turn a promising generation into an asset you can legally and safely ship.
- 01
Restate the brief, the deliverable format, and where the asset will appear before judging any output.
- 02
Inspect at full resolution: generated media hides its errors at thumbnail size.
- 03
Check the details these systems reliably get wrong — hands, text, logos, reflections, symmetry, and edge artefacts.
- 04
Confirm the licence and commercial-use terms for your plan, and check the output does not reproduce a recognisable style, mark, or likeness you have no right to use.
- 05
Review for accessibility and delivery: alt text, contrast, colour profile, file size, and the exact export format.
- Inspect at full resolution before approving anything.
- Confirm commercial-use rights before an asset reaches a client.
- Keep the prompt and settings with the asset so it can be reproduced.
Privacy & permissions
Use Meshy safely
Use the platform without surrendering rights, likenesses, or client material you do not control.
- 01
Confirm you hold the rights to every reference image, voice, or clip before uploading it.
- 02
Check whether your plan trains on submitted content, and opt out before uploading client work.
- 03
Never upload a real person's likeness or voice without their explicit, documented consent.
- 04
Review the output for marks, styles, or likenesses you have no licence to reproduce.
- 05
Label synthetic media where your client, platform, or jurisdiction requires disclosure.
- 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.
- Follow your organisation's approved-use policy.
- Never treat fluent output as authorization to act.
Core workflows
Step-by-step ways to use Meshy for the work it does best.
Each workflow below has its own outcome, steps and review checkpoints.
Use preview, refine, and artist cleanup as distinct gates so a compelling render does not conceal unusable geometry.
↓ 02 WorkflowRun a governed Meshy 3D API pipelineAutomate asynchronous 3D jobs with plan-aware rights, secure references, cost limits, asset retention, and technical validation.
↓Workflow 01
Turn a concept into a game-ready Meshy asset
Use preview, refine, and artist cleanup as distinct gates so a compelling render does not conceal unusable geometry.
Outcome: Deliver a licensed 3D asset that meets measured topology, texture, scale, rig, and runtime requirements.
- 01
Define silhouette, dimensions, style, polygon and material budget, topology, UVs, textures, rig, animations, formats, engine, platform, license, and acceptance tests.
- 02
Submit an authorized prompt or clean multi-view concept, create geometry previews first, and select on silhouette and proportion before texture refinement.
- 03
Download and inspect scale, normals, watertightness, intersections, topology, UVs, texture seams, materials, likeness, and protected design similarity in a 3D editor.
- 04
Retopologize, unwrap, bake, correct textures, set pivots and collisions, rig and weight where needed, and preserve the generated source as a separate derivative.
- 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.
What good use looks like
- Approve geometry before texturing.
- Treat generation as a draft mesh.
- Test the final asset in-engine.
Workflow 02
Run a governed Meshy 3D API pipeline
Automate asynchronous 3D jobs with plan-aware rights, secure references, cost limits, asset retention, and technical validation.
Outcome: Process authorized 3D requests without losing outputs, leaking references, overspending credits, or accepting broken files.
- 01
Review current API version, plan rights, attribution, privacy, training use, output retention, formats, credit costs, rate limits, and prohibited content.
- 02
Keep tokens server-side, authenticate owners, validate image and prompt rights, reject sensitive personal data, strip metadata, and isolate source and output storage.
- 03
Create idempotent preview tasks, poll with backoff and timeout, refine only approved geometry, cap retries and spend, and download expiring assets immediately.
- 04
Parse and validate file type, geometry, bounds, scale, normals, materials, textures, polygon count, UVs, rig, animations, malware, and visual similarity before acceptance.
- 05
Test cancellation, partial failure, duplicate callbacks, provider outage, credit reconciliation, deletion, key rotation, license records, manual-review routing, and rollback.
What good use looks like
- Download API outputs before expiry.
- Refine only approved previews.
- Validate geometry programmatically and visually.
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 guide.