An architecture portfolio is a curated document that shows how you think through a building, not a complete archive of everything you have drawn. For a studio job or graduate admission, three to five projects presented in depth beat a dozen shown as thumbnails: each project should carry a concept, the drawings that prove it (plan, section, and at least one detail), and the renders or models that show it built. Lead with your single strongest project, keep a consistent grid and type system across every spread, and publish it as both a downloadable PDF and a website you control so a reviewer can open it on any device without a login.
What it is for
A portfolio is an argument, not an archive
The most common mistake in an architecture portfolio is treating it as a complete record. Five years of studio work, every competition entry, every rendering you ever finished, all bound together in the hope that volume reads as ability. It does the opposite. A reviewer who opens forty pages of undifferentiated work learns only that you cannot tell your strong projects from your weak ones, and that judgment is the exact skill the portfolio is supposed to demonstrate.
Reframe it as an argument. The claim is that you can conceive a building, resolve it in drawing, and communicate it clearly. Every project you include is evidence for that claim, and every project you leave out is evidence too, because restraint is legible. A portfolio of four projects that each earn their place tells a hiring architect more than a portfolio of twelve that do not.
Who is reading changes the argument slightly. A firm hiring for a job wants to see that you can produce usable drawings and work inside constraints, so professional and technical work carries weight. A graduate committee is buying potential and a point of view, so conceptual range and the quality of your questions matter more than construction detail. Licensure documentation is different again: it is a record of demonstrated experience against a competency framework, kept for a board rather than styled for a reader. Know which of the three you are building before you choose a single page.
What to show
The drawings and media that carry a project
A project is not shown until a reader can understand the building from the page. That takes a specific set of representations, each doing a job the others cannot.
Concept
The idea, in one image
Open each project with the single diagram, sketch, or line that states the concept. If a reader cannot grasp what the project is arguing in the first few seconds, the drawings that follow have nothing to hang on.
Plan
Plans that read as space
A clean plan at a legible scale with a consistent line hierarchy is the backbone of any project. Poche the walls, show the furniture only where it clarifies use, and never crop a plan so tightly that a reader loses the parti.
Section
Sections that show how it stands
The section is where architecture students most often go quiet, and where reviewers look hardest. A good section proves you understand structure, light, and the vertical experience of moving through the building.
Detail
At least one detail resolved
One well-drawn wall section or junction tells a firm you can carry an idea down to how it is built. You do not need a full construction set; you need proof that the concept survives contact with material.
Render
Renders that serve the idea
Use renders and collages to show atmosphere and material, not to hide thin thinking. One considered image that reinforces the concept beats five high-gloss views that all say the same thing.
Model
Physical and digital models
Photographs of a well-lit physical model, or clean axonometric views of a digital one, communicate massing and assembly faster than any plan. Shoot models against a neutral ground so the object, not the desk, is the subject.
How to build it
From a folder of studio work to a finished document
The work already exists. The portfolio is the act of selecting, sequencing, and setting it so a stranger reads it the way you intend.
Select ruthlessly, then cut once more.
Lay out every project and rank them honestly. Keep three to five for a job or admission portfolio, and make sure the set shows range: a large project and a small one, a conceptual piece and a resolved one. When in doubt, drop it.
Sequence for a first and last impression.
Put your strongest project first, because most reviewers spend the most attention on the opening spreads and skim from there. Close with a memorable one. Keep the middle from sagging by alternating scale and mood rather than stacking similar work.
Set a grid and stick to it.
Choose one layout grid, one or two typefaces, and a fixed set of line weights, then hold them across every page. Consistency is what makes a portfolio read as designed rather than assembled, and a reader registers it before they read a caption.
Caption for a reader who was not in the crit.
Each project needs a short line naming the brief, the site, the year, and your role, especially where the work was collaborative or professional. A reviewer must never have to guess which parts of a team project were yours.
Export a PDF, then build the website.
Produce the PDF first, because that is what firms and programs request and what stays fixed on the page. Then publish the same work as a website so it can be found, opened without a download, and updated without re-sending a file.
Working conventions
The numbers reviewers quietly expect
None of these are rules, and a strong portfolio can break any of them. They are the conventions most firms and programs assume, so departing from one should be a decision, not an accident.
The academic and professional mix
Balancing studio work against built work
Early in a career the portfolio is nearly all academic, and that is correct. Studio projects are where you had the freedom to take a position, and a committee or a design-led firm wants to see that position more than they want to see redlines. Show the conceptual reach of the studio work, and do not apologize for the fact that none of it was built. Unbuilt is the native state of a student portfolio.
Once you have office experience, the balance shifts, and it shifts in a way you have to manage carefully. Professional work is often collaborative, incremental, and owned by the firm, so you cannot simply lift a set of construction documents and call them yours. Show the parts you genuinely drove, credit the team, and check what your employer permits you to publish. A single professional project where you can honestly say what you did is worth more than a folder of work you can only gesture at.
The strongest mid-career portfolios hold both in tension: one or two professional projects that prove you can build, alongside academic or personal work that proves you still have a point of view. If the professional work has flattened your voice, competition entries and self-initiated studies are the place to show it is still there. A reviewer is hiring the person, and the person is more visible in the work nobody paid for.
Where it lives
Pair the PDF with a site you actually own
The PDF and the website are not competitors; they do different jobs. The PDF is the artifact a firm attaches to your application and a committee downloads to review offline, and its fixed page is exactly right for a designed spread. Keep it lean enough to email and to clear the file-size caps that many application portals impose, and make sure the type stays legible when it is read on a laptop rather than printed at A3.
The website is the version that keeps working after the application closes. It is what a search for your name returns, what you can hand to someone with a single link, and what you update the week you finish a new project without re-exporting and re-sending anything. Hosting it on a domain you control, rather than a social profile whose layout and reach belong to a platform, is what makes it durably yours.
Folio builds exactly this pairing from one set of work: an architecture portfolio website and a resume that stays in sync. Being straight about the free plan: it puts you on portfolio.wrxstack.com/yourname rather than a custom domain, it shows a small Made with Folio badge, and the full theme gallery sits on the paid tier. What is not gated is the resume export, which downloads as PDF and DOCX at no cost and with no watermark. Whatever you build it with, publish the PDF for the people who ask for a file, and keep the site for everyone who will simply search your name.
Frequently asked questions
How many projects should an architecture portfolio have?
For a studio job or a graduate application, three to five projects shown in depth is the reliable range. A reviewer is judging your ability to select as much as your ability to design, so a tight set that each project earns reads as stronger than a large one padded with weaker work. Show range within the set: mix scales, and mix conceptual with resolved work.
What should each project in an architecture portfolio include?
Open with the concept in a single image, then prove it with drawings: at minimum a plan, a section, and one resolved detail at a legible scale and consistent line weight. Add renders, collages, or model photographs to show material and atmosphere. Finish with a short caption naming the brief, site, year, and your specific role, especially on collaborative or professional work.
Should an architecture portfolio be a PDF or a website?
Build both, because they do different jobs. Firms and admissions portals ask for a PDF, and its fixed page suits a designed spread, so keep one lean enough to email and to clear file-size caps. A website is the version that gets found in a search for your name, opens without a download, and updates without re-sending a file. The two are complements, not alternatives.
How do I make an architecture portfolio for grad school?
A graduate committee is buying potential and a point of view, so lead with conceptual range and the quality of your questions rather than construction detail. Most application portfolios run roughly fifteen to twenty-five spreads, open with your strongest project, and hold one grid and type system throughout. Check each program for page limits, file-size caps, and required formats before you export.
Can I put professional office work in my portfolio?
Yes, but carefully. Professional projects are usually collaborative and owned by the firm, so show only the parts you genuinely drove, credit the team, and confirm what your employer permits you to publish. One professional project where you can honestly state what you did is worth more than a set of documents you can only gesture at. Pair it with academic or personal work that shows your own voice.