3D Rendering

A named set of images at an agreed resolution, from agreed camera positions, with an agreed number of review rounds. That last part is what most quotes leave vague and most disputes come from. A typical architectural package mixes exterior views, interior views, an aerial or context shot, and a dusk or night version of the hero image. Around them sit the extras a project may need: 360 degree panoramas, walkthrough animations, floor plan renderings, and material or option comparisons. What is not included unless it is stated is unlimited revision. Get the view list, the resolution, the delivery format, and the number of rounds onto one page before work starts. That single page prevents the argument that otherwise arrives the week the images are due. It is the first thing worth asking any provider for.

Speed against control. Real-time engines such as Enscape, Lumion, D5 and Twinmotion render in seconds from inside your model. Options can be tested live in a meeting, and a change costs almost nothing. Offline engines such as V-Ray and Corona compute each image over minutes or hours. In exchange they give you control over light, material and detail that a real-time engine only approximates. The practical rule is what the image has to survive. A design review, an internal option study, or a fast client check runs beautifully in real time. A hero image usually earns the offline render. That is the one printed at size, put on a competition board, or used in marketing for two years. Most firms use both on the same project, which is why the specialist we place works in both.

The model, the direction, and the constraints. On the model side: the Revit, SketchUp, Rhino or ArchiCAD file, plus the site context if the surroundings matter. On direction: the camera positions you want and reference images of a look you like. Then the material and finish selections, and the mood, meaning time of day, season and weather. On constraints: the resolution, the format, the deadline, and where the image will be used. Reference images do more than any written brief, because rendering style is a visual language and describing it in words rarely lands. If the model is not ready, say so early rather than hoping it resolves in time. Rendering an unresolved design produces images that get discarded when the design settles. That is the most common way a rendering budget is quietly wasted.

By reviewing in the right order, and by agreeing the number of rounds up front. The order matters more than the count. First review the camera and the composition on a gray clay render, before any material or lighting work exists. Then review materials and lighting on a draft quality image. Only then produce the final at full resolution. A firm that approves a camera angle at the end has paid for every intermediate image twice. Two rounds is a normal structure when the reviews happen in that order. Because the professional works your hours, a clay review can be a fifteen minute screen share rather than a next-day email. Collecting the client's comments into one consolidated list, instead of forwarding them as they arrive, is the other half of it.

Your firm owns them. Images produced for your projects are yours, in the working files as well as the final format, and they stay in your environment. You can use them in a client presentation, on your website, in a competition entry, or in a submission to a planning authority. None of that needs our permission. Two things are worth checking separately, and neither is about us. First, whether your own client agreement lets you publish images of their project. Second, the copyright in the underlying building, since the U.S. Copyright Office protects architectural works as their own category. Purchased assets inside an image, such as licensed entourage or HDRI libraries, carry the license terms they came with. Ask which assets an image contains before it goes out, because those terms travel with the asset rather than with the render.