What to actually look for in a web designer's portfolio
Telling a template reskin apart from original work
The portfolio grid is loaded on your screen, thumbnail after thumbnail, all of it looking clean and finished. Some entries are original builds. Others are a popular theme with the client's logo dropped in and a couple of colors swapped. Both can look polished in a screenshot. Only one shows you what a designer can actually build from a blank file.
One way to check: search a distinctive layout element or an unusual section from a portfolio piece. If it turns up on a theme marketplace, you're looking at a customization, not a custom build from scratch.
That's not automatically a problem. Customized templates are a legitimate, faster path for plenty of projects. What matters is that you know which one you're being shown, rather than assuming every entry in the grid was built the same way.
A quick reverse image search on a hero photo can turn up the same stock image on other sites entirely unrelated to the one in front of you. That's not a red flag by itself. Everyone uses stock photography somewhere. It's a way to gauge how much of the page is custom work and how much is dressing.
Ask directly if you're not sure. "Was this built from scratch, or customized from a theme?" is a fair question, and a designer who's proud of either answer will just tell you.
Checking whether the sites shown are still live and working
Click through, not just the homepage. A few inner pages, a contact form if there is one, the mobile view on your own phone. A portfolio entry that's broken, redirects somewhere unrelated, or simply no longer loads tells you something worth knowing.
Either the relationship ended badly, the site didn't hold up over time, or it was quietly retired and left sitting in the portfolio anyway. Live and working is a low bar, and that's exactly why it's worth checking before you assume otherwise.
A portfolio that hasn't been maintained tells you how closely this business tends to its own presentation of its own work. If nobody bothered to remove a dead link from their own showcase, that's worth remembering once your own project is finished and sitting somewhere similar.
Date stamps help too, if the portfolio shows them. A page full of work from several years back, with nothing recent added, raises a fair question about how active the business actually is right now, versus how active it was when the grid was first built.
Asking who on the team actually did the samples shown
A portfolio represents a business, not necessarily one specific person. At an agency, ask directly who worked on a piece you liked, and whether that person would actually be on your project.
The answer sometimes exposes a mismatch. The standout piece was built by someone no longer there, or by a senior designer who won't come near a smaller budget project like yours. Neither answer is disqualifying on its own, but both are worth knowing before you sign anything based on that one piece.
Whose work you're actually looking at in an agency portfolio is a real difference between hiring a freelancer and hiring an agency, and it's worth understanding before you assume the portfolio tells you who you'll actually be working with day to day.
Whether the portfolio actually matches your kind of business
A gorgeous restaurant site doesn't tell you much about whether someone can build a service business with a working booking flow, or a shop that needs inventory shown clearly at a glance. Look for portfolio pieces closest to your own situation: similar size, similar function, similar audience.
A designer with no experience anywhere near your kind of business isn't automatically the wrong choice. It does mean you're paying partly for a learning curve on their side.
It's worth going in aware of that trade instead of discovering it midway through the project, once changes start taking longer than either of you expected them to. Ask a direct question to close the gap faster: "Have you built anything for a business like mine before?" A specific example beats a general reassurance every time.
Spotting a portfolio padded with stock photography and mockups
Some portfolios show real, live client sites you can visit today. Others show polished mockups: device frames, staged photography, a design that may never have shipped as pictured, or shipped once and got pulled down quietly later. Both can look identical sitting side by side in a thumbnail grid.
Ask plainly: "Is this a live site I can visit, or a concept piece?" A designer with real work behind them answers without hesitation. One who gets vague about which pieces are real and which are speculative has told you something about how to read the rest of the pitch too.
A portfolio review is one piece of a larger process, not the whole thing on its own. The broader vetting process this fits into covers what to check beyond the portfolio, and judging whether the work shown actually matches your trade goes further than a portfolio glance on its own ever can.
The full picture of all four builder options is worth revisiting too, since a template service's own gallery deserves the same close look as a designer's, and the same questions apply whether or not a person built it by hand.
None of this is about catching someone in a lie. Most portfolios are honest, built by people proud of the work sitting in them. A close look just makes sure the one in front of you is the kind you're hoping it is, before it becomes the reason you hired someone.
More from the blog
- Will a professionally built website actually get you more customers
- When a booking system is worth adding to your site
- What has to be on your website before a stranger will choose you
- What to ask before a monthly retainer adds a new tool to your site
- Where your website's contact form submissions actually go