Portfolio Website for Architects: Project Pages, Drawings, and Photo Rights

A portfolio website for architects works when each project reads in a set order: what the building is, why it looks the way it does, how it was drawn, and who made it. That applies to a firm's archive and to an individual architect looking for a job, with different rules on whose work you can show. Below is the structure we'd use for project pages, how to handle drawings and photography, the rights questions most people skip, and how to keep image-heavy pages fast.

Two kinds of architecture portfolio website

The firm portfolio and the personal portfolio look alike but answer different questions. A firm's portfolio is there to win commissions, so it speaks to clients. An individual's portfolio is there to win a job or a promotion, so it speaks to principals and hiring managers.

That changes what goes on the page:

• Firm portfolio. Finished buildings, the client's problem, the outcome, and a path to an inquiry.
• Individual portfolio. The person's role on each project, the skills it shows (detailing, modeling, code research, client meetings), and how to reach them.

Most of this page is about the firm version. The section on job-seekers covers the extra rules for personal sites.

A project page structure that holds up

Use the same sequence on every project page, so visitors learn to read your archive. Here's the order we'd start with:

1. Lead image. The one photo that explains the building best, not necessarily the most dramatic.
2. Fact line. Building type, town, size, status (completed, under construction, unbuilt), and year.
3. Short story. Two or three paragraphs: the site, the brief, the main design move, and what changed because of it.
4. Drawings. A plan, a section, or a site plan placed next to the text that refers to it.
5. Photo sequence. Arranged the way someone would walk through the building: approach, entry, main spaces, details.
6. Process material. A sketch, a model photo, or a construction image if it helps the story.
7. Credits. Your team, the builder, consultants, and the photographer.
8. Next step. A related project and a link to the inquiry form.

Keep unbuilt work honest. Label renderings as renderings and competition entries as entries, so no one mistakes a proposal for a finished building.

Drawings: what to show and how to prepare them

Drawings are what separate an architect's portfolio from a photographer's, so show at least one on every project. Clients get a sense of how you think, and other architects see the quality of your documents.

Construction sets don't work on screen as they are. Prepare a presentation version instead:

• Remove dimensions, keynotes, and title blocks unless they're the point.
• Add a north arrow and a graphic scale bar, because a written scale is meaningless once the image is resized.
• Use a heavier line weight than in print. Fine lines disappear on a phone.
• Crop to the part of the plan the text talks about.

For private homes, ask the owners before publishing floor plans. A plan with the street visible tells a stranger exactly where the bedrooms are. Many firms show plans for houses only with the location kept to the town.

Photography and the rights you actually hold

Paying a photographer to shoot your project usually doesn't make you the copyright owner. The U.S. Copyright Office explains that copyright belongs to the author of the work or the author's heirs or assignees, and ordinarily the author is the person who created it.

The "work made for hire" exception is narrower than many people assume. It covers work prepared by an employee within the scope of employment, or commissioned work in nine listed categories with a signed written agreement. A freelance architectural photographer is usually not your employee, and a building shoot rarely fits those categories. What you normally get is a license.

Read the license before you build the site. Questions to settle with the photographer:

• Can you use the images on your website, social accounts, and printed materials?
• Can you give them to the builder, the interior designer, or the client, and on what terms?
• Can you submit them to awards and publications?
• Is there a time limit?
• How does the photographer want to be credited?

Credit the photographer by name on every project page. It's courteous, it's often required by the license, and it helps readers find the person behind the images. If you want that information attached to the files too, Google supports image license metadata, through structured data or IPTC fields embedded in the photo, covering the creator, credit line, and copyright notice.

Your own site photos, taken by staff during construction, are different. Work an employee creates within the scope of the job is a work made for hire, so the firm generally owns those photos. They're fine for process images, even if they're not polished enough to lead the page.

Portfolios for individual architects and job-seekers

A personal architecture portfolio website has to be clear about who did what. The AIA's ethics code says members shall accurately state the scope and nature of their responsibilities for work they claim, and shall recognize the contributions of employers and colleagues.

The same code has a rule that catches people changing jobs: members leaving a firm shall not take designs, drawings, data, reports, notes, or other materials relating to the firm's work without the permission of their employer. Even if you're not an AIA member, your employment agreement may say something similar.

In practice:

• Ask your current or former firm in writing which projects and drawings you may show.
• Name the firm on each project and state your role: "project architect, design development through construction administration," not "designed by."
• Use the firm's published photos only with permission, and credit the photographer.
• Mix in work that's clearly yours: school projects, competitions, personal drawings, built work from your own practice.

Until you're licensed, don't call yourself an architect on the site. Use the title your state board allows, such as designer.

A personal portfolio can be short. Five or six well-explained projects, a résumé page, and a contact link will do more than twenty thumbnails. Some firms still ask for a PDF with applications, so keep one that mirrors the site.

Image files: size, format, and alt text

An architecture portfolio lives or dies on images, and images are what make it slow. Google's own image guidance notes that images are often the largest contributor to overall page size and suggests checking pages with PageSpeed Insights.

Practical rules for a portfolio site:

1. Export for the screen, not for print. A photo straight from the photographer can be tens of megabytes. Resize to the largest width the layout actually shows.
2. Use modern formats. Google Search supports JPEG, PNG, WebP, and AVIF, among others. Test a WebP or AVIF export against your JPEG and keep whichever is lighter at the same visual quality.
3. Serve smaller versions to phones. Responsive images (the srcset attribute or the picture element) do this, and Google recommends always keeping a fallback URL in the src attribute.
4. Watch the first image. On most project pages it's the largest element, and web.dev suggests keeping Largest Contentful Paint at 2.5 seconds or less.
5. Save drawings as PNG or SVG if they're mostly lines, since JPEG compression blurs thin lines.

Alt text should say what the image shows in plain words. For photos: "Living room with clerestory windows and a board-formed concrete fireplace." For drawings, describe what the drawing communicates: "Ground floor plan showing the kitchen opening onto a covered terrace." Skip alt text stuffed with phrases like "best architect portfolio."

How this differs from a design studio portfolio

If you've read our page on an interior design portfolio website, much of the logic carries over, but the evidence is different. Interior portfolios rely on styling, materials, and before-and-after. Architecture portfolios need drawings, a building's relationship to its site, and a clear account of scope, because a building involves more consultants and approvals than a room.

To see how the portfolio fits into the rest of a firm site, our look at patterns behind strong architecture firm websites covers the options.

How we build architecture portfolios

Our clients are design and landscape businesses, architecture firms among them. For a portfolio-heavy site, the work starts with a written questionnaire about each project you want to show: the brief, your scope, the credits, and which drawings and photos you're allowed to use. We write the project text from your answers, and you correct the technical details before anything goes live.

You get the structure, the copy, a custom design, development, mobile layouts, basic SEO, and launch in one build. The price begins at $1,000 and rises with page count and with features like a filtered archive. You'll see scope, timing, payments, and revision rounds in a written proposal first. For the full service picture, see our page on website design for architects.