
3D rendering is the process of turning a 3D model into a finished two-dimensional image: software simulates how light behaves inside a digital scene and computes the photograph a camera would have taken if the scene were real. It is the stage that makes CGI look like photography, and it is how buildings, products and film shots get pictured before they physically exist. A single architectural render takes minutes to hours of computation; buying one takes about a week and starts around 700 pounds.
Think of a 3D model as a stage set: geometry for the walls and objects, materials that tell each surface how to behave, lights placed like a photographer would place them, and a camera. Rendering is pressing the shutter. The engine (V-Ray, Corona and Cycles are the common ones) traces how light bounces around the scene, through glass, off brushed metal, into soft shadow, and resolves it into pixels. The better the simulation and the artist driving it, the harder the result is to distinguish from a photograph.
Rendering is one stage of the wider craft (modelling and texturing come before, grading after), but in everyday use "a 3D rendering" means the finished image, and buying "3D rendering" means buying that whole pipeline; the neighbouring term is covered in our guide to what CGI is.
Five stages, whoever does it. The scene is modelled from drawings, scans or reference. Materials and textures are applied: real product finishes, actual paint references, believable wear. Lighting is set, which is where most of the realism is won or lost. The render is computed, on a workstation for small jobs and a render farm for production work; ours runs six nodes and a queue, because a 4K photoreal frame is real computation. Finally post-production grades the image the way photography is finished.
The client-visible rhythm matters more than the software: cameras are agreed on a plan, a grey clay render locks composition while changes are still cheap, and only then do materials and lighting go on. Studios that skip the clay stage bill you for the consequences later.
You send drawings (DWG, RVT, SKP or even a clean PDF set), a finishes schedule, and reference images for the mood. You get back a camera plan, then a clay render for sign-off, then the final images, usually inside one to three weeks depending on the set size. Two things separate good experiences from bad ones: whether revision rounds are scoped in the quote rather than discovered in the invoice, and whether the studio asks what decision each image has to win. A render for a planning committee, a tender and an Instagram campaign are three different briefs that happen to share a model.
Architecture and property are the biggest commercial users: unbuilt schemes need images to win planning, tenders and off-plan buyers, which is our own field and the subject of our architectural visualization service. Product and e-commerce rendering replaces photography for configurable or unreleased goods. Film and television render everything from set extensions to whole characters, and games render in real time. The pipelines differ in scale, not in kind: the five stages above are the same everywhere.
Modelling builds the geometry; rendering photographs it. A model with no render is a wireframe nobody can sell with; a render is the deliverable. Commercially, "3D rendering services" almost always include the modelling.
Computation is minutes to hours per frame. The project is days to weeks: about a week for a single architectural view, two to three weeks for a full set, driven mostly by decision and revision speed.
Architectural stills start around 700 pounds per view at our studio, with market prices from a few hundred dollars for template work to several thousand for luxury scenes. Complexity of the scene and of the lighting is what moves the number.
Professionals render on farms; a capable single workstation wants a modern NVIDIA GPU with at least 16 GB of VRAM for GPU engines, or a high-core-count CPU for engines like Corona. Our GPU guide for 3D rendering covers the 2026 choices.