Recipes
Pro 3.0 workflow: the default target-aware production path is Asset Compiler followed by Ship Gate. This page documents an advanced or manual Pro tool that remains available alongside the compiler.
Recipes are Pro’s repeatability layer: a saved configuration that defines how you process an asset or a batch of assets.
Why recipes exist
- Consistency across a team
- Repeatable exports for engine pipelines
- Batch processing without manual UI fiddling
How to think about recipes
- Recipes should encode standards, not personal preference
- Keep them asset-class specific (hero prop vs clutter vs environment kit)
- Name them like pipeline steps, not vibes