Teams running many generations at once need a clear strategy for queuing, concurrency, and organization. This guide covers best practices for bulk generation workflows with Meshy.

Batching makes sense when you have a large, predictable set of assets to generate—for example, a full set of game props or a product catalog—rather than one-off exploratory generations.

Your plan determines how many tasks can run concurrently. Plan your batch size and submission rate around your concurrency limit to avoid hitting rate limits mid-run.

Use a consistent naming or tagging convention for batch jobs so you can track which assets belong to which run, especially when working across a team.

For large batches, webhooks are more efficient than polling every task individually—your system gets notified as each task completes instead of repeatedly checking status.

Generated assets are retained for a limited time. Download or archive outputs from large batch runs promptly rather than relying on Meshy to store them indefinitely.

Shared workspaces let teams collaborate on the same organization's credits and assets. Review member roles and permissions so batch jobs are run by the right people with the right access.

Teams with high-volume, ongoing batch needs should evaluate Studio or Enterprise plans, which offer higher concurrency and dedicated support for large-scale workflows.

Plan your submission rate around your account's concurrency limit, and see the related rate limits article for specific error handling guidance.

Webhooks are generally more efficient for large batches since they avoid repeatedly polling every task.

Studio or Enterprise plans are designed for higher concurrency and larger team workflows—see the related article on the Studio plan for details.