What Actually Goes in an Architecture Portfolio (An Instructor’s Guide)

I’ve reviewed a lot of student portfolios. The gap between the good ones and the rest almost never comes down to talent — it comes down to editing. Strong students put in everything they’ve ever made, and the work drowns.

Here’s what actually belongs in an architecture portfolio, what to leave out, and the format details that quietly get people rejected before anyone looks at the design.

Your portfolio is a design project, not an archive

This is the reframe that fixes most portfolios. You are not documenting everything you’ve done. You are designing an object whose job is to make someone want to meet you.

That changes every decision. Sequence matters. Pacing matters. White space matters. A reviewer looking at a hundred applications will give you somewhere between ninety seconds and three minutes on a first pass — and they are looking for a reason to keep reading, or a reason to stop. Every page either earns its place or costs you.

The practical test: if a page doesn’t change the reviewer’s opinion of you, cut it.

How many pages should an architecture portfolio be?

Shorter than you think. Rough targets:

• Job applications: 30–35 pages. Firms are busy. A tight portfolio reads as confidence.
• Graduate school: 40–45 pages. You have more to prove — research capability as well as design.
• A focused short portfolio: 20–25 pages. In a competitive market this often outperforms a longer one.

Surveys of student and professional portfolios consistently land in the 31–40 page range as the most common band. That’s a reasonable default if you’re unsure.

Project count matters more than page count. Four to six projects, shown properly, beats twelve shown thinly. Some schools state this outright — RIT’s portfolio requirements ask applicants to limit portfolios to five to ten projects across roughly twenty pages, explicitly noting they care about quality rather than quantity.

The format details that get people rejected

This is the boring part that costs real applicants real places. File size limits vary enormously between schools, and they are hard limits. A few current examples:

• Yale (M.Arch): a single PDF, not to exceed 40MB
• Princeton (M.Arch): 25MB digital limit, plus a bound physical copy no larger than 8.5 × 11 inches
• CCNY Spitzer: under 10MB, images compressed to 150 DPI, no page or project minimum at all
• University of Washington (undergrad): 30MB, with a page cap in the region of 24 letter-size or 12 tabloid pages

The spread there is four to one. Build at print quality, then export a compressed version per application. Do not build one 90MB file and hope.

These figures move between admissions cycles, so treat them as illustrations of how much the requirements vary rather than as current numbers — always check the page for the year you’re applying.

Other format basics worth getting right:

• PDF, always. One file. Not a folder, not a link, unless they ask for one.
• Design for screen. Almost every portfolio is now reviewed on a monitor. Landscape usually reads better than portrait.
• Name the file properly. Lastname_Firstname_Portfolio.pdf. Some schools specify an exact convention — follow it exactly.
• Read the specific requirements. Every year students lose places to a rule they didn’t read. This is the cheapest possible thing to get right.

What actually goes in

1. Process work — more than you’re comfortable with

The single most common weakness I see: students show only the polished final render. Reviewers already know you can follow a tutorial. What they can’t tell from a beauty shot is how you think.

Show the sketches. Show the iterations you rejected. Show the study models, including the ugly ones. A page that reads “here are six massing options and here’s why I killed five of them” is worth more than another render.

2. Hand drawing

Students assume this is old-fashioned. It isn’t. Some programs require it as a minimum — RIT’s M.Arch portfolio requirements state that portfolios must include examples of hand drawing at a minimum, whatever else they contain.

Hand work signals that you can think spatially without software doing it for you. Include sketchbook pages, life drawing, diagrams, anything drawn. It doesn’t need to be beautiful. It needs to be evidence.

3. A clear statement of your role

For every group project and every internship project, say plainly what you did. “I developed the facade system and produced the sections” is credible. Ambiguity reads as inflation, and reviewers assume the worst when it’s unclear.

Short written summaries per project are standard, and several schools explicitly ask for them.

4. Non-architecture work — yes, really

This surprises people. M.Arch programs are often open to applicants from any undergraduate background, and admissions staff say so directly. CCNY’s Spitzer School tells applicants they’re happy to consider portfolios containing no architecture or landscape design work at all.

Photography, furniture, ceramics, printmaking, textiles, code, film — if it demonstrates visual thinking and craft, it can earn its place. Don’t pad with it, but don’t hide it either.

5. Drawings, not just images

Plans, sections, elevations, details, axonometrics. This is the actual language of the discipline. A portfolio of atmospheric renders with no orthographic drawings reads as visualization work, not architecture.

Include at least one detail drawing somewhere. It’s a small thing that signals you understand buildings get built.

The anatomy of a good spread

Most students design pages. Design spreads — the two facing pages a reviewer sees at once. A spread that works usually has:

• One dominant image. Not four equal ones. Hierarchy is the whole game.
• Supporting drawings at a smaller scale that explain the dominant image.
• Roughly forty words of text. Enough to frame the project, not enough to be an essay.
• Real white space. Not the gaps left over after you placed things — space you chose.
• A consistent grid running through the whole document.

Set two type sizes and one typeface, and hold them for the entire portfolio. Typographic discipline reads as design maturity faster than almost anything else on the page.

What to cut

• Software logo grids. Nobody has ever been admitted because they put the Rhino icon on a page. List software as text on your CV.
• First-year exercises, unless the drawing is genuinely exceptional. The nine-square problem does not distinguish you.
• Every view you rendered. Pick the best one. Then delete another.
• Long project descriptions. If it needs three paragraphs to explain, the drawings aren’t working.
• Decorative graphic flourishes. Gradients, drop shadows, and diagonal text boxes age badly and distract from the work.
• Your weakest project. A portfolio is judged closer to its worst piece than its average.

A realistic build order

If you’re starting from a folder of chaos:

1. Gather everything into one place, including sketches and phone photos of models. You will be missing things — this is why you photograph work as you go.
2. Choose four to six projects. Range matters: different scales, different media, at least one that shows technical resolution.
3. Set the grid and type before you place a single image.
4. Lay out the strongest project first to establish the visual system, then apply it to the rest.
5. Order the projects strongest first, second-strongest last, weaker ones buried in the middle.
6. Print it. Even for a digital submission. Errors you cannot see on screen are obvious on paper.
7. Get it reviewed by someone who will be unkind about it, and leave time to act on what they say.

A note on the software side: portfolio layout in InDesign with high-resolution renders placed is one of the heaviest things you’ll do all degree, and it always lands during the worst week of term. If your machine struggles with it, that’s usually memory rather than processor — see how much RAM you actually need, or our laptop guide if you’re still choosing hardware.

Frequently asked questions

How many projects should be in an architecture portfolio?

Four to six shown properly is the sweet spot for most students. Some programs cap it — RIT asks for five to ten. More projects almost always means less depth, and depth is what’s being assessed.

Can I apply to an M.Arch without an architecture background?

Yes. Many M.Arch programs are designed for applicants from any undergraduate major, and some state explicitly that a portfolio need not contain architectural design work. Show creative and visual thinking in whatever medium you have.

Should my portfolio be landscape or portrait?

Landscape suits screen viewing and most architectural drawings, which is why it’s the common default. Portrait works if your content genuinely favours it. Either is fine — consistency matters more than the choice.

Do I need a physical printed portfolio?

For most applications, no — digital PDF is standard. But some schools still require a bound copy alongside the digital file, and a printed book carries real weight in an interview. Check each application individually.

How do I reduce my portfolio file size?

Export from InDesign with images downsampled to 150 DPI and use a compressed PDF preset. Keep the print-quality master file separately. Build once, export per application — the limits differ a lot.

When should I start building my portfolio?

Now, in the sense that you should be photographing and archiving work continuously. The actual layout takes a few focused weeks. Students who start from scratch a fortnight before a deadline produce portfolios that look exactly like that.

The short version

Fewer projects, more process, real hand drawing, a grid you hold to, and file specs that match what was actually asked for. Portfolios don’t fail because the work is bad. They fail because the work is buried.

Portfolio template pack — coming soon

We’re building a set of InDesign portfolio templates with the grid and type systems already set up, so you can spend your time on the work instead of the layout. Join the list and we’ll send it the moment it’s ready.