What an Architect’s portfolio website needs (and what to leave out)

Architects spend years shaping spaces with careful hierarchy, proportion, and restraint, yet their websites often fall short of that standard. Either a cluttered grid of thumbnails or a template whose design competes with the work. A portfolio site has one job: let the buildings lead.

Start with structure. Visitors should reach a project within two clicks and understand what they’re looking at within seconds. A clean index with a strong lead image, project name, location, and type is usually enough. Resist filters and effects that exist for their own sake.

Case studies are where a portfolio earns trust. Rather than a gallery of finished photographs, show how the project was approached: the brief, the site, the key decisions, and the outcome. Plans, sections, and sketches alongside photography reveal thinking, which is what clients and peers actually hire. Keep the copy short and specific.

Then keep the design quiet. Generous space, a restrained palette, and one or two typefaces let the work speak. Motion should be subtle and purposeful, and images should load quickly and hold up on large screens.

What to include

• A clear project index with consistent image ratios and naming.

• Case studies with process: brief, site, concept, and outcome.

• Drawings and diagrams alongside photography.

• A short studio statement and team page with real names.

• An easy way to enquire, with clear contact details.

What to leave out

• Autoplay video and heavy transitions.

• Every project you’ve ever completed. Curate instead.

• Long, jargon-heavy copy.

• Competing colours, badges, and clutter.

In conclusion: Let the work lead

Great architecture is often defined by what has been taken away, and the same is true of its website. When structure is clear, case studies show real thinking, and the design steps back, the portfolio does what it was built to do: make the right clients want to build with you.