Workflow · Workflow

The render deck: how to sequence, size and caption images so a client actually approves them

A strong set of renders can still lose a presentation if the deck is built wrong. Image order, one idea per page, caption discipline, and the file formats that survive the client's boardroom.

By ArchVizDaily··10 min read
Overhead view of an architectural presentation being assembled on a studio table: printed sheets showing a house render, a floor plan and a material palette, a laptop with a render deck, and swatches of oak, concrete and linenWORKFLOW
AI-generated illustration of a presentation set in assembly. The deck, the prints and the material palette are one argument told in three formats, and the image order is doing as much work as the images.Illustration: ArchVizDaily · AI-generated

The deck is an argument, not a gallery

Studios spend weeks on the renders and an afternoon on the deck, and then wonder why the client fixated on the wrong thing. The deck is not a container for the images. It is the argument the images are making, in order, and a client who sees a strong set in a weak sequence will approve the wrong version, ask for the wrong changes, or stall entirely. Sequencing is a design decision, and it deserves the same care as the lighting.

The other reason the deck matters is that you are rarely in the room when it does its work. The architect forwards it, the developer's board reviews it without you, the planning officer opens it on a laptop in a corridor. A deck that only works with a narrator is a deck that fails most of the time it is used.

Sequence: context, arrival, interior, detail

The sequence that works for almost every residential and commercial scheme is the sequence a person would experience the building: context first, then arrival, then the key interior, then the details. Context answers where is it. Arrival answers what is it. The hero interior answers what does it feel like. Details answer is it any good. Every question gets one answer, in that order, because that is the order an unconvinced viewer asks them.

The mistake to avoid is opening with the best image. The hero dusk shot is a payoff, and a payoff spent on page one is a payoff wasted, because the viewer has no context to weigh it against. Put the strongest image where the argument peaks, usually the hero interior or the money exterior after the context has been established, and let the opening pages do the quieter work of orientation.

One idea per page

One idea per page is the rule that separates professional decks from image dumps. A page with three renders asks the viewer to compare them, and comparison invites critique of the images rather than consideration of the design. A page with one render asks the viewer to look at the building. If two images genuinely belong together, a clay view and its finished twin, a day and dusk pair, put them together deliberately and caption the comparison, because a deliberate pair reads as a study and an accidental pair reads as indecision.

White space is not wasted space. A render bled to every edge of every page reads as a brochure, and brochures get flicked through. A render given a margin and a caption gets read. The pages that clients remember are almost always the quietest ones.

Captions that answer the real question

A caption should answer the question the viewer is actually asking at that point in the deck, which is almost never what software was used. View from the garden at dusk, showing the kitchen extension's relationship to the existing house is a caption. Exterior render v4 final is a filename. The first one sells the design; the second one reminds the client how many versions there have been, which is never a thought you want to plant.

Keep captions short, factual and free of adjectives. The image supplies the emotion; the caption supplies the orientation. If a page needs more than two lines of text to make sense, the page is doing two jobs and should be split. And never caption a render with a promise the design has not yet earned, because the caption is the part of the deck a client will quote back at you.

Sizing, crops and the boardroom test

Size images for the worst screen they will meet, which is a laptop at the far end of a boardroom table or a projector with the lights on. That means checking every page at arm's length and at thumbnail: if the subject of the image is not legible at four centimetres wide, the crop is wrong. Dusk exteriors and dark interiors fail this test most often, because their drama lives in tones that a bright boardroom flattens, so give those images a larger page area and a simpler composition than you would for print.

Crops should be decided per page, not inherited from the master render. A 16:9 hero that fills a landscape page is right; the same image squeezed into a portrait slot with a caption band is a compromise that helps nobody. Render wide enough masters that every page's crop is a choice, and keep the verticals honest in every crop, because a cropped image with converging verticals looks like a mistake even when the master was correct.

Formats that survive the client

Deliver the deck as a PDF, always, and treat every other format as a supplement. A PDF survives forwarding, opens on any device, and preserves your page order, which is the whole point. Send full-resolution stills separately as a zipped folder with sane filenames, project, view, date, because the client will lift images out of the deck for their own documents and you want the lifted version to be the good one.

Two technical habits save more embarrassment than any other. First, export the PDF in sRGB and check it on a cheap screen, because a deck graded on a wide-gamut monitor can shift noticeably on a boardroom laptop. Second, keep the file under the email limit your client actually has, which usually means a compressed viewing copy and a link to the full set, rather than one forty-megabyte attachment that bounces.

The pre-send checklist

Before the deck goes out, run the same checklist every time. Page order follows the experience of the building. One idea per page. Every caption answers a real question. Every image legible at thumbnail. Filenames sane. PDF in sRGB, under the size limit, with full-resolution stills linked. And the final page is a single calm image with contact details, not a thank-you slide, because the last image in the deck is the one that stays on the screen while the room talks.

None of this is glamorous, and all of it is visible in the outcome. Clients rarely know why one studio's work feels easier to approve than another's, but the difference is usually here, in the ten percent of the job that happens after the render button. The images make them want the building. The deck is what lets them say yes.

Continue reading

Technical references

FAQ

Common questions

What order should renders go in a client presentation?
Follow the experience of the building: context first, then arrival, then the key interior, then details. Save the strongest image for where the argument peaks rather than opening with it.
How many renders should go on one page?
One idea per page. Multiple images on a page invite comparison and critique of the images rather than consideration of the design, unless the pairing is deliberate and captioned as a study.
What format should I send a render deck in?
A PDF in sRGB, kept under the client's email limit, with full-resolution stills delivered separately under sane filenames. The PDF preserves your page order, which is the argument the deck is making.
How do I write captions for architectural renders?
Answer the question the viewer is asking at that point in the deck, in one or two factual lines. Name the viewpoint and what the image shows about the design, and never use a filename or a version number as a caption.