An architecture firm does not need to choose between a website and a PDF portfolio.
They are strongest at different moments.
A PDF is excellent when someone already knows you and asks, “Can you send me your portfolio?” A website matters earlier and later: when a referral searches your name, when a developer compares firms, when a homeowner wants to verify that the practice is legitimate, or when someone wants to see whether you have solved a project like theirs before making contact.
The useful question is therefore not “website or PDF?” It is:
What information does a prospective client need before they are ready to enquire, and which format should carry it?
For many architecture practices, the sensible answer is an owned website for discovery and trust, plus a focused PDF for situations where a portable curated document is genuinely useful.
A PDF waits to be requested; a website can be discovered
A PDF portfolio is a delivery format. Someone normally needs the file, a link to it, or an introduction before they see it.
That can be perfectly adequate for a referral-led practice.
But consider what often happens after a referral:
recommendation → Google the architect or firm → inspect projects → verify credibility → understand fit → contact
If the website is weak or absent, the prospect has to fill those gaps elsewhere.
The American Institute of Architects’ current global-practice guidance specifically recommends maintaining an up-to-date portfolio on a firm’s website as part of outreach, while also recognizing social media as a separate channel for reaching wider audiences. See the AIA Global Practice Primer.
That does not make PDFs obsolete. It simply means the website has a job a PDF cannot fully perform.
Do not build an image gallery and call it a portfolio strategy
Architecture is visual, so it is easy to overcorrect and make the website almost entirely photography and renders.
Beautiful work matters. But a prospective client is not reviewing the site like an awards jury.
They may be asking:
- Have you handled my type of project?
- What scale of work do you take on?
- Do you work in my location?
- Was this a concept, an unbuilt render or a completed project?
- What exactly did your practice do?
- Can you navigate planning, consultants and construction?
- Who will I actually work with?
- How do I start a conversation?
A useful project page therefore needs more than a slideshow.
For each selected project, consider showing the project type, location, status, scope, your role, important constraints and enough process to explain the thinking behind the final images.
Even AIA’s guidance for architecture portfolios warns against showing only attractive renders; hiring managers want to understand the thought process and range behind the work. The audience is different, but the principle transfers well: proof becomes stronger when the viewer understands what the images actually demonstrate. AIA discusses portfolio review here.
Your website should help a client verify you
Professional services websites carry a trust burden that an Instagram grid or image-heavy PDF may not.
For a Nigerian architecture practice, this is especially practical. The Architects Registration Council of Nigeria maintains a public verification facility for architects and firms and says it is responsible for registering architects in Nigeria. ARCON’s current site includes its verification tools.
If the firm is properly registered, make that status easy to verify rather than burying credentials inside a long About page.
The same principle applies internationally. In the UK, the Architects Registration Board explicitly encourages registered architects to display evidence of registered status on websites so potential clients can verify that they are dealing with a regulated professional. ARB explains this guidance here.
Trust should be inspectable, not merely claimed.
What belongs on the website versus the PDF?
| Need | Website | PDF portfolio |
|---|---|---|
| Be found from search or a referral | Strong | Weak |
| Verify practice identity and credentials | Strong | Useful, but less independently verifiable |
| Browse several relevant projects | Strong | Strong when curated |
| Send a tailored selection to one prospect | Possible | Excellent |
| Update a project once for future visitors | Excellent | Requires redistributing the file |
| Work offline or attach to a procurement process | Limited | Excellent |
| Create a clear enquiry journey | Excellent | Possible, but secondary |
The formats are complementary.
A useful rule is: the website explains the practice; the PDF packages a selection for a specific conversation.
Build project pages around fit, not vanity
A common architecture-site mistake is sorting everything only by year.
That may make sense internally, but prospects often think in other dimensions:
- residential
- hospitality
- commercial
- institutional
- interiors
- renovation
- masterplanning
- project scale
- location
- completed versus concept
You do not need filters for all of these. You need an information structure that helps the right client quickly recognize, “They have done work relevant to my problem.”
This is where web design becomes business analysis rather than decoration.
If the firm wants more hospitality work, a strong hospitality project should explain the hospitality problem solved. If the goal is high-end residential, do not make the prospect hunt through twenty unrelated concepts before finding a completed residence.
The enquiry path deserves as much attention as the portfolio
A portfolio can impress someone and still lose the enquiry.
After a prospect decides the work looks credible, the website should answer:
- What kinds of projects do you take?
- Where do you work?
- What happens after I contact you?
- What information should I send?
- Who receives the enquiry?
A generic form asking only name, email and “message” often throws away useful context.
For an architecture practice, a short enquiry form might ask for project type, location, approximate stage and a free-text description. Do not turn it into a twenty-question tender document. Capture enough to route the conversation responsibly.
Then test the operational side: submission, notification, acknowledgement and follow-up.
A polished portfolio is not doing its job if enquiries disappear into an inbox nobody checks.
When a PDF-only setup is still enough
Do not build a website merely because every business is told it needs one.
A PDF-only approach can still be rational when:
- virtually all work arrives through trusted introductions;
- the practice intentionally takes very few projects;
- prospects already know the firm’s credentials and capabilities;
- there is no realistic need for search acquisition;
- the team can reliably send an appropriate portfolio when requested.
But watch the behaviour around the PDF.
If people repeatedly ask for your website, search your name before meetings, struggle to verify the firm, request different project examples, or ask basic questions the portfolio does not answer, those are signs that the website has a real job to do.
When to stop patching an old architecture website
If you already have a site, do not assume the answer is a redesign.
First diagnose whether the problem is:
- outdated projects;
- poor mobile presentation;
- slow oversized images;
- unclear service positioning;
- weak project context;
- difficult content updates;
- broken enquiry forms;
- missing analytics;
- or a structure that no longer matches the work the firm wants.
Some of those are repair jobs. Others justify a rebuild.
Use my guide to the signs a business website actually needs a redesign before changing the whole system.
If the site receives visitors but not enquiries, the broader traffic-without-sales diagnostic is also useful: find the broken decision step before changing the visual style.
A practical architecture-firm setup
For a small or mid-sized practice, I would usually start with less than teams expect:
Homepage — what you design, where you work, selected proof and a clear next step.
Projects — curated work organized so prospects can judge fit.
Project detail pages — context, role, status and images rather than images alone.
Practice/About — people, approach and verifiable professional credibility.
Services or sectors — only where they clarify what the practice actually takes on.
Contact/enquiry — a low-friction route into a real follow-up process.
Then make project publishing easy enough that the team can keep the site current without calling a developer for every photograph.
That last point matters. An architecture website that cannot absorb new completed work will slowly become a historical archive of the firm you used to be.
The decision
Keep the PDF.
Use it when someone needs a portable, tailored portfolio.
But do not force it to handle discovery, professional verification, project exploration, search visibility and enquiry conversion at the same time.
Your website should answer the questions that happen before someone asks for the PDF and after the images have convinced them to talk.
If you run an architecture or design practice and want the project structure, mobile portfolio and enquiry journey treated as one system, see my web design service or contact me.
