Repeat a setup with Quick Render
Quick Render is the shortest path from a prepared model and approved template to a repeatable set of outputs. It creates the required project work and renders the views already saved in the template, without asking you to direct each product in Studio first.
Use Quick Render when
- the template has already produced an accepted result
- each model is prepared and ready for the saved setup
- the saved angles or clips are the outputs you need
- consistency matters more than custom art direction for this run
Use Studio when the product needs a different composition, finish, light placement, camera, prop arrangement, or motion treatment.
Before you start
Confirm that:
- every selected model has finished processing
- model scale and material regions are prepared
- the template uses the intended version
- the template contains the required image angles or video clips
- one representative product has already been reviewed in that setup
Run the setup
- Open Quick Render.
- Choose one or more ready models.
- Select the approved template.
- Review the included views and supported output settings.
- Start the render.
Glossi creates the production work for each selected model and processes the template’s included captures. Follow progress in the flow or return to the render library.
Read the result
Each selected product can produce several images or clips. A completed request is still subject to visual review. Check product scale, framing, material mapping, contact shadows, and any product-specific exception the shared template could not anticipate.
If one capture fails, inspect the render job before restarting the entire request. Supported recovery paths preserve completed captures and allow failed work to be retried.
Quick Render, Studio, or Automations?
| Lane | Best fit | Human decision |
|---|---|---|
| Studio | A new or custom visual setup | Direct the scene and save the views. |
| Quick Render | A known batch using an approved setup | Choose models and a template. |
| Automations | An ongoing workflow triggered by a folder or event | Design and monitor the production rules. |
| API | A product or system that should control Glossi | Implement the production contract. |
Prove reuse with a second product
The first accepted render proves that the setup works. Apply the same template to a second prepared product and review the output. That second useful result is the clearest test that the scene has become a production asset rather than a one-off project.