How to create an architecture portfolio for college

Do architecture programs require a portfolio?

Many do, and some don't. Some programs ask for a portfolio of creative work, some for a response to a prompt, and some review applications without one. Check each program's page and the application instructions, as explained in do colleges require a portfolio? The wider picture is in college application portfolios.

You usually don't need architecture experience

Many programs state that applicants aren't expected to have studied architecture before. If so, they're usually looking for evidence of visual thinking, curiosity, and the ability to make things, which can come from many kinds of work. Always confirm in the program's own guidelines.

What you can include

• Drawings: from observation, of spaces and objects, or imagined.
• Sketches and sketchbook pages that show how you explore ideas.
• Models, from cardboard to wood, photographed from several angles.
• Design projects, such as a small structure, a furniture piece, or a redesign of a room.
• Other creative work: sculpture, woodworking, painting, photography, graphic design, or digital work.
• Process, including early sketches, attempts that didn't work, and revisions.

The question to ask of each piece is not "is this architecture?" but "does this show how I think and make?"

Projects you can make without architecture experience

Most of these need nothing more than paper, cardboard, a ruler, and a camera. They're ideas, not requirements, and a program's own prompt comes first:

• A measured drawing of a room you know, as a plan and one or two elevations.
• A study of a real building or space near you, in sketches, noting how light, movement, and materials work.
• A cardboard or foam model of a small shelter for a specific person, use, and place.
• A redesign of one space, such as a corner of your school or a room at home, with before and after drawings.
• A photo-and-sketch record of one street, showing how people use it.
• A piece of furniture or an object built at scale, with the drawings you made first.

Choosing projects

• Choose a small number of projects you can explain well, rather than many you can't.
• Favor work where your own decisions are visible.
• Include a variety of scales and media if you have them, within your program's piece limit.
• Say what's yours in any team project.

Present a project clearly

A repeatable structure helps reviewers compare projects:

1. A short statement of the idea or problem.
2. Drawings or sketches showing how you developed it.
3. Photographs of models, shot against a plain background in good light.
4. A final view: drawing, model, or render.
5. Scale, materials, and your role.

Explain the idea in a few lines

Short, specific captions help a reviewer follow your thinking. For each project, try to answer a few of these:

• Who is it for, and what will they do there?
• How do people move through it?
• Where does light come in, and what does it do?
• What is it made of, and why?
• What did you change after your first version?

Photographing models

• Use a plain, uncluttered background, and use the same one for every model.
• Light from a window, with soft light from one side, and avoid mixed bulbs.
• Shoot an overall view, a view from a lower angle, and a detail.
• Put something in the frame for scale, such as a small figure or your hand.
• Keep the camera steady and level, and avoid wide-angle distortion by stepping back and zooming slightly.

Layout and drawings

• Use landscape pages and generous margins for drawings.
• Keep line weights readable at the size they'll be viewed.
• Photograph hand drawings flat and square, and clean up shadows.
• Keep text short and consistent in position and size.
• Number pages and keep the same project structure throughout.

Common mistakes

• Showing only polished renderings with no process.
• Photos of models with cluttered backgrounds or bad light.
• Copying an existing building or a design from a website instead of making your own.
• Too much text, or text too small to read.
• Ignoring the program's piece count or format.
• Leaving out the thinking behind a design.

PDF or website?

Architecture portfolios are often laid out as pages, so a PDF is common, and many programs ask for one or for uploads. A website can sit alongside, holding the same projects in a repeatable structure, and a downloadable PDF too. See PDF vs website portfolio, our architecture portfolio websites, and what to include in a college portfolio. Some scholarships also review creative work; scholarship portfolios explains how those differ. If your interests cross several fields, see portfolio websites for young creatives and student portfolio examples.

Portlio designs and builds custom portfolio websites for architecture applicants. A website complements each program's required submission; it doesn't replace it, and nobody can promise it will change an admissions or scholarship decision. If you'd like help presenting your work, you can get started or ask for a portfolio review first.

Frequently asked questions

Do I need to know CAD or 3D modeling?

Usually not for undergraduate applications. Many programs say applicants aren't expected to have software skills yet. Hand drawings, sketches, and physical models are widely accepted, but check each program's own guidance.

Can I include work that isn't architecture?

Often yes. Programs commonly welcome drawing, sculpture, woodworking, photography, and graphic design, because they show how you see and make. Where it's allowed, choose pieces that show your thinking.

Should I include renderings?

Only if they show something about your ideas. A polished render without drawings or process says little about how you think, and a program may value sketches and models more.

How many projects should I show?

Use the program's number. If you choose, a few projects you can explain well is a stronger selection than many you can't.