An architecture portfolio website is a public collection of your work published under your own domain. It replaces the PDF for discovery, referrals and cold outreach, while the PDF stays the format hiring managers actually read during shortlisting. Most architects need both, kept in sync and built around a small number of well-documented projects.
The confusion starts at the wrong question. People pick a site builder before deciding what the site is for. A studio principal chasing clients, a graduate applying for a first job and a visualization freelancer all need different sites.
When a Website Replaces Your PDF, and When It Does Not
Hiring at architecture practices still runs on files. A recruiter downloads applications, opens them side by side, and skims. A link that needs a browser, a login, or thirty seconds of loading loses to the attachment already in the inbox.
A site wins when someone found you rather than the other way around: search results, an Instagram bio, a business card, a competition credit, a colleague passing your name along. In those moments there is no email thread to attach anything to.
The split is easier to hold if each format has one job. The PDF is the application document, sized and ordered for a specific role, as covered in the comparison of A3 and A4 portfolio formats. The site is the permanent public record, and it can hold more projects, process work and contact detail than any application PDF should.
⚠️ Common Mistake to Avoid
Uploading your portfolio PDF to a page and calling that a website. The file is usually 20 to 80 MB, it will not load on a phone, and its text is invisible to both search engines and screen readers. Put the PDF behind a download link on a real HTML page, and keep the project content as text and images.
Choosing a Platform for an Online Architecture Portfolio
Four routes cover almost every case. The right one depends on how much maintenance you want, and whether the address needs to be yours.
Hosted site builders such as Squarespace, Wix, Cargo and Format give you a working site in a weekend and connect a custom domain. You pay monthly and accept their templates. For most students and early-career architects that is the correct trade.
Behance and Instagram are distribution, not a portfolio site. They put work in front of people who were not looking for you, but you control neither the layout nor the address. Treat them as feeders pointing at your own domain.
A static site built with Astro, Eleventy or Hugo and hosted on Netlify or GitHub Pages is fast, cheap and fully yours, though it expects a text editor and a build step. WordPress sits between the two, with more plugins and more upkeep.
Platform Comparison at a Glance
The table sets the four routes against the decisions that matter for a portfolio site.
| Route | Setup Effort | Own Domain | Best For | Watch For |
|---|---|---|---|---|
| Hosted site builder | A weekend | Yes, on paid plans | Students, graduates, small studios | Heavy templates slow image-led pages |
| Behance or Instagram | An afternoon | No | Reach and visualization work | You rent the audience and the layout |
| Static site generator | A week, plus a learning curve | Yes | Anyone comfortable with code | Every edit runs through a build |
| WordPress | A few days | Yes | Studios publishing regularly | Updates and security are your job |
Site Architecture: The Five Pages That Do the Work
Portfolio sites fail more often from structure than from styling. Five page types carry the whole thing.
The home page answers who you are and what you do, above the fold, in one line of text and three to six project thumbnails. No splash animation, no full-screen video that loads before anything appears.
Each project page gets its own URL. This is the unit that gets linked, shared and indexed, so a single scrolling page holding every project at once throws away most of the site's value.
The about page carries a real photograph, your education, licensure status and the software you use. The contact page needs an email address you check and little else. A CV page holds the current PDF plus the same information as HTML text, the version search engines and screen readers can read. The guidance on writing an architecture resume and on matching a CV to your portfolio applies to the web version too.
💡 Pro Tip
Publish six well-documented projects rather than fourteen thin ones. Reviewers open two or three project pages at most, and a weak entry in the grid does more damage than a missing one. Keep the extras in a folder and swap them in when an application calls for them.
What Belongs on a Project Page?
A project page should let a reader understand the work without you in the room, in a fixed order repeated across every project.
Open with one strong image and a short factual block: name, type, location, year, your role, team, and whether the project was academic, competition or built. Crediting that role honestly matters, because a reviewer who spots an office project presented as solo work stops trusting the page.
Then run the drawings in the order the design was made: site and context, plans, sections, the detail or model that carries the idea, renders last. Around 200 words of text is enough, written as a problem and a response rather than a caption for what the images already show. The editing discipline in the twelve pages every strong portfolio needs transfers straight to a web layout.
Images, Load Time and Mobile Layout
Architecture sites are the heaviest kind of personal site on the web, because the content is renders. One 8 MB JPEG exported straight from V-Ray stalls a page on a phone before anyone sees a pixel of it.
Google's web.dev guidance on Largest Contentful Paint sets 2.5 seconds as the threshold for a good score, and the largest image on screen is almost always what decides it. Export at the size you display, usually 1600 to 2000 pixels on the long edge, serve WebP or AVIF, and lazy-load everything below the fold. Never the hero image, which is the most common way portfolio sites lose those 2.5 seconds.
📐 Technical Note
WCAG 2.2, published by the W3C in 2023, asks for a contrast ratio of at least 4.5:1 between normal body text and its background. Thin grey type over a render, a habit borrowed from print layouts, routinely lands near 2:1 and fails.
Most first views happen on a phone, where a landscape drawing at 390 pixels wide is unreadable. Give wide drawings a full-bleed treatment with a tap to enlarge, stack two-column layouts into one, and set body text at 16 pixels or larger. Test on a real device, not a resized desktop window.
Accessibility and Search Basics
These two overlap, because both depend on text describing images that machines cannot see.
Alt text is the clearest case. The W3C's alt text decision tree covers when an image needs a description, when a short one is enough, and when the attribute should stay empty. Google's image SEO documentation asks the same from the other side: descriptive filenames and alt text that describes the image accurately instead of stuffing keywords into it.
Three more things carry most of the search value. Each project page needs its own title tag naming the project and its type. URLs should be readable words separated by hyphens, which is what Google's URL structure guidance recommends, so /projects/riverside-library beats /p?id=7. And every page needs real HTML text, since a project told entirely in image files gives search engines nothing to index.
Confidential Work, Domains and Professional Email
Office work usually cannot go public. A password-protected page, available on every platform above, is the normal answer: publish it, lock it, and give the password in your application email. Where a contract forbids even that, describe your contribution in drawings you produced yourself. Never publish work covered by an NDA, because the people most likely to notice it are hiring in your city.
💡 Pro Tip
Buy the domain before you build the site, and buy your own name if it is free. Email on the same address then costs a few dollars a month and makes every application read differently from one sent by a numbered free account. Keep the renewal on auto-pay, since a lapsed domain takes every link shared with it.
Mistakes That Cost You Interviews
The same failures repeat across hundreds of sites, and almost all are fixable in an afternoon.
- An intro animation or splash screen between the visitor and the work
- Renders at full export resolution, turning every page into a ten-second wait
- All projects on one endless scroll, with no individual URL to share
- No email address anywhere, or a contact form that silently fails
- Process work, sketches and models left out, so the site shows results without thinking
- A site last updated three years ago, still describing you as a student
Several repeat the problems in common portfolio layout mistakes, which is unsurprising, since a bad grid on paper stays a bad grid on screen. The portfolio templates in our store give you a page order you can adapt for both the PDF and the site.
Frequently Asked Questions
Do I Still Need a PDF Portfolio if I Have a Website?
Yes. Most practices ask for an attachment with a size limit, often 10 MB, and a link does not answer that request. Build the PDF for applications, the site for everything else.
How Many Projects Should Go on the Site?
Five to eight for a graduate, up to twelve for an experienced architect. Reviewers rarely open more than three project pages, so depth beats breadth. Anything you would hesitate to discuss in an interview does not belong there.
Is Behance Enough on Its Own?
Enough to be seen, not enough to read as a studio or a working freelancer. A profile page cannot hold a CV, a contact route and password-protected work the way your own domain can.
What Should the Domain Name Be?
Your own name, if it is free, because it stays accurate after your job title, city and studio all change. Avoid padding an unavailable name with words like portfolio or arch, since a different extension on your real name reads better.
How Often Should I Update It?
Twice a year, plus a pass whenever you finish a significant project or change roles. Set a calendar reminder, because the most common state for a portfolio site is not broken, it is out of date.
Where to Go From Here
Your next step: before comparing a single template, write out the page list you plan to publish, project by project, with the URL each one will live at. If that list does not hold five projects you can talk through confidently, the work to do is on the portfolio, not the website.
Comments (0)
Back to Architecture and Design Blog