3D rendering glossary
Build time: what it means in programming and 3D rendering
Build time is the time a system spends “setting up” something before running it. In programming, it is the code compilation time. In 3D rendering, it is the scene preparation stage: loading geometry, building acceleration structures, calculating light caches and, in real-time engines, building lighting before generating the image.
Build time in general: software development
In software development, build time (build time or compilation time) is the interval between the compile command and the generation of the executable or final package. During this period, the compiler checks syntax, resolves dependencies, optimises the code and generates the artefacts. Tools such as Maven, Gradle, Webpack or Vite automate this process.
The term is also contrasted with runtime (execution time). Something “defined at build time” is fixed at compilation; something “defined at runtime” is only resolved when the program runs. The same logic applies to rendering: some work is done before the image calculation and some during it.
In practice: Render Fabrik is a 3D architectural rendering studio working with clients in Brazil and Europe, with a quote within 24 hours.
What is build time in 3D rendering
When you press the render button, the engine does not start drawing pixels immediately. First it prepares the scene. This preparation is the build time, which some programs show as “preparing scene”, “building BVH”, “parsing scene” or “building light cache”. The most common tasks are:
- Scene reading: loading models, proxies, textures and materials into memory.
- Acceleration structure (BVH): organising millions of polygons into a hierarchy that enables ray tracing to quickly find what each ray hits.
- Displacement and subdivision: generating the extra geometry for reliefs and smoothed surfaces.
- Lighting pre-calculations: irradiance map, light cache or other global illumination caches, when the chosen method uses them.
- Shader compilation: in GPU and real-time engines, materials are converted into programs that the graphics card runs.
Build time in real-time engines
In engines such as Unreal Engine and Unity, build time has an even more concrete meaning. The “Build Lighting” command calculates static lighting and stores the result in lightmaps, textures that hold ready-made light and shadow. After that, the scene runs in real time without recalculating it. Shader compilation, generation of levels of detail (LODs) and packaging the project for distribution, for example in an interactive tour, are also part of the build.
With dynamic lighting systems such as Lumen in Unreal Engine 5, much of this pre-calculation is no longer required, reducing build time in exchange for more processing during execution.
Build time, render time and total time: the difference
| Stage | What happens | What it depends on |
|---|---|---|
| Build time | Scene preparation before the first pixel | Amount of geometry, textures, displacement, light caches |
| Render time | The actual image calculation | Resolution, number of samples, complexity of lighting and materials |
| Post-production | Colour adjustments, compositing and corrections | Number of render passes and level of finish |
In a still image, build time is usually a small part of the total. In an animation, it can have a greater impact, because it repeats for each frame when the scene changes. That is why optimising the preparation makes a difference in 3D videos with hundreds or thousands of frames.
How to reduce build time: best practices
- Use proxies: heavy trees, cars and furniture come in as proxies, loaded on demand.
- Instance repeated objects: a hundred identical chairs should be instances of a single model, not a hundred independent copies.
- Limit displacement: apply real relief only where the camera sees it up close; at a distance, a normal map does the job.
- Optimise textures: resolutions compatible with camera distance and suitable formats reduce memory load.
- Reuse caches: in animations with a moving camera and static scene, calculate the light cache once and reuse it.
- Clean the scene: delete hidden objects, forgotten layers and unused materials.
A common mistake is trying to speed up rendering only by lowering image quality, when the bottleneck is in the preparation: poorly organised scenes can spend more time building the structure than calculating the lighting.
Build time in a visualisation studio's workflow
In architectural projects, scenes bring together the building, surroundings, vegetation, people and vehicles. Organising these elements well keeps build time under control and frees up time for what matters: lighting, materials and framing. This applies both to exterior 3D images with lots of vegetation and to real-time experiences such as the interactive virtual model, where the build defines the smoothness of navigation. Other technical terms are in the glossary.
Frequently asked questions
Are build time and render time the same thing?
No. Build time is the scene preparation before the calculation; render time is the actual image calculation. Many programs show both separately in the log or progress window.
Why does my render get stuck at “preparing scene”?
Usually due to excessive geometry, displacement across large areas, very heavy textures or poorly configured proxies. Reviewing these points usually solves it.
What is “Build Lighting” in Unreal Engine?
It is the command that pre-calculates the static lighting of the scene and stores it in lightmaps. After the build, the scene runs in real time with lighting and shadows already resolved.
Does a more powerful graphics card reduce build time?
It helps in part, mainly in shader compilation and BVH construction in GPU engines. But file reading, memory and scene organisation also matter a lot.