Should a 13-Year-Old Have a Public Portfolio? A Balanced Take

Your kid has built something, or is about to, and the question comes up: should they put it online where anyone can see it? On one side, a public portfolio is one of the most powerful things a young person can have, real proof of what they can do. On the other, putting a thirteen year old's work and name on the open internet raises genuine concerns about privacy, safety, and permanence. Both instincts are right. This is how to hold them together.

The short version: a portfolio is worth having, the risks are real but manageable, and there is a sensible middle path that gives your kid the upside without the exposure you are worried about. You do not have to pick between hiding everything and broadcasting everything.

Why a real portfolio is genuinely valuable

A portfolio is proof, and proof is rare. Most kids reach the end of high school with a list of activities and grades, which is a set of claims about what they did. A kid with a portfolio has something different: evidence. A live thing they made, that works, that anyone can look at and judge for themselves. In a world where claims are cheap and increasingly easy to fabricate, demonstrable proof of real work is becoming the most credible thing a young person can offer.

This matters for the obvious destinations, college and eventually work, but it matters for something deeper too. A kid who can point to real things they made carries themselves differently. The portfolio is not just for admissions officers. It is a record your kid can look at and think, I made that, it is real, it exists. That is worth a great deal at an age when most kids are being told what they will be able to do someday rather than shown what they can do now.

A resume is a list of claims. A portfolio is a set of proofs. As claims get cheaper and easier to fake, proof gets more valuable, and a kid who has it stands out without having to say a word.

The real risks, named honestly

The concerns are legitimate, and they are worth being precise about, because precision is what lets you address them rather than just worry.

• Privacy. A public page can leak more than the work: full name, location, school, age, photos, contact details. The work is the point. The personal details usually are not, and they are what create exposure.
• Permanence. Things on the open internet are hard to fully remove and can resurface years later. A kid's taste and judgment change fast. Something they were proud of at thirteen they may wince at later.
• Unwanted contact. A public presence with a way to reach your kid directly opens a channel to strangers. That channel is the risk, more than the visibility of the work itself.

Notice that none of these is "the work is visible." They are all about personal information, permanence, and direct access. That is the key, because it points straight at the middle path.

The middle path: show the work, protect the kid

You can have almost all of the upside and very little of the risk by separating the work from the person. The principle is simple: make the thing your kid built fully visible, and keep the identifying details under control.

• Show the work, not the dossier. The project, what it does, how it was built, can all be public. The full name, exact location, school, and birthday do not need to be. A first name and a general region is plenty.
• Route contact through the parent. Any way to reach your kid should go through an address you control, not a direct line to them. This single move closes the riskiest door.
• Own the address. A portfolio at a domain you and your kid control is far safer and more lasting than work scattered across platforms with their own defaults and data practices. You decide what is shown.
• Review before publishing. Make it a family habit that anything going public gets a quick look from a parent first. Not to censor, but to catch the detail your kid did not think about.

How to talk about it with your kid

Frame it as a privilege with a structure, not a fight. "Your work is good enough to show people, and that is genuinely valuable. We are going to put it where the right people can see it. To do that safely, here is what we keep private and how anyone who wants to reach you goes through me." Most kids accept this readily, because they want the work seen and do not particularly want their birthday and address on the internet. The boundaries feel reasonable when they are tied to a real benefit.

The free Parent Field Guide below covers the step before the portfolio, helping your kid build something genuinely worth showing. It is useful on its own, with nothing to buy.

The honest bottom line

Yes, a thirteen year old can and often should have a portfolio, because real proof of real work is one of the most valuable things they can carry. The risks, privacy, permanence, and unwanted contact, are real but they are all about personal information and access, not about the work being visible. So show the work and protect the kid: control the identifying details, route contact through you, own the address, and review before publishing. Make the choice deliberately as a family, and a portfolio becomes a clear win rather than a worry.