Where Does Time Go?
- Resolution: more pixels take longer
- Samples: more rays per pixel take longer
- Many lights, glass and reflective surfaces
- High polygon counts and large textures
- Heavy effects such as depth of field and motion blur
Speed Tips
| Tip | Why it helps |
|---|---|
| Render a region | Test just the area you changed |
| Lower resolution while testing | Fewer pixels |
| Use instances and proxies | Saves memory for repeated objects like trees |
| Reduce unneeded lights | Fewer light calculations |
| Reduce texture sizes | A 4K map is not needed for a small prop |
| Denoise | Fewer samples for a clean result |
| GPU rendering (where supported) | Often much faster on a good graphics card |
Batch Render
Use Rendering > Batch Render to queue several camera views or scene states. Each job can have its own camera, size and file name, and they run one after another.
Animation Render Estimate
frames: 250 | total render time: 750 minutes = 12.5 hours | with 5 machines: 2.5 hours (ideal)
A 10-second shot at 25 fps has 250 frames. At 3 minutes per frame it takes 12.5 hours on one machine, and about 2.5 hours on five machines in the ideal case. Always render a few test frames to know your number before you start.
Common Problems
| Problem | Try |
|---|---|
| Noise | Raise samples or use the denoiser |
| Black render | Check lights, exposure and that the camera is active |
| Missing textures | Check the file paths in Asset Tracking |
| Out of memory | Reduce texture sizes, use proxies, close other programs |
| Fireflies (bright dots) | Clamp sample values or reduce very bright small lights |
Practice
- Time a test frame and estimate a 300-frame job
- Render a region only
- Replace 50 copies with instances
- Use Batch Render for three camera angles
Conclusion
Time is saved by testing small, reducing waste and using instances and denoising. Estimate before you start long jobs.

