Three routes, one portfolio, and a decision most people end up making twice: once when they build the site, and again eighteen months later when the work has moved on and the site has not. Templates, custom builds and no-code tools will all get your name online. What separates them is what they ask of you afterwards — and that is worth thinking about before you pay for anything.
Pin this down first, because the answer decides the rest. Four questions, answered honestly, will point you towards one option:
A photographer selling limited prints and a motion designer pitching to studios want very different things, even though both call the result a portfolio. Write your answers down. Vague intentions are how people end up paying for a rebuild after nine months.
A template is a finished design you pour your work into. Buy a theme, install it on a content management system, swap the sample images for yours, publish. You can realistically be live in a weekend.
The appeal is cost and predictability. You pay once, or a modest annual fee, and the platform handles security updates, hosting and the fiddly parts. That matters when you would rather spend Saturday drawing than debugging.
The layout follows the theme's grid, and your work has to fit it. If you want a long-scrolling case study with video, process shots and pull quotes woven through, you will spend a lot of time fighting the structure. Themes also accumulate plugins, and every plugin you add is another thing to update and another chance of a slow page.
Rule of thumb: if your work fits neatly into a grid of thumbnails, a template will serve you well. If it does not, you will feel the edges within a month.
A custom build means the design and the code are made for you. It is the right answer when the site itself is part of the pitch — a developer or designer showing craft, or anyone whose work does not fit an existing shape. Done well, a custom site can be leaner and faster than anything off the shelf, because nothing is loaded that you did not ask for.
You pay for that in two currencies: money upfront and time later. Someone has to maintain the code, renew the hosting, watch for security updates and check accessibility. A custom site that nobody maintains becomes a site you cannot update without ringing the person who built it.
If you commission one, agree two things in writing before work starts: who owns the code, and how you will edit your own content. Without answers to those, you are renting your own portfolio.
Visual editors such as Webflow, Framer, Squarespace and Cargo sit between the two. You drag and style elements directly, and the platform hosts the result. There is more layout freedom than a fixed theme, far less maintenance than a hand-built site, and no code to debug when something breaks.
The trade-off is that you are renting. Your site lives on their servers, and export options vary widely — some platforms let you take your code elsewhere, others do not. Read the terms before you commit, particularly around what happens if you stop paying or want to move. Content you have written and images you have uploaded should always be something you can download in full.
Portfolio search visibility is less technical than people assume. Templates and no-code platforms already handle the basics — sitemaps, page titles, sensible URLs. A custom build can be sharper still, but only if someone bothers. The difference is usually made by the content you write and the weight of your images.
All three routes can do this. A slow, well-organised template will outperform a fast, empty custom site.
Where your server sits matters more than the badge on the plan. Hosting in the UK keeps response times low for British visitors and keeps personal data in the UK, which simplifies matters if you collect enquiries through a contact form under UK data protection rules.
Before you commit, check that the domain includes a .co.uk if that suits your clients, that SSL is included rather than charged extra, that backups run automatically, and that support answers during your working hours. If you collect personal data or sign client contracts, take proper advice from a qualified professional rather than relying on a hosting provider's summary.
Give yourself one hour. Register the domain in your own name first — that is the one thing all three routes share. Then pick the option you can realistically maintain for two years, not the one that looks best in a demo. A template if you need to be online quickly and your work suits a grid. A no-code tool if you will update monthly and want layout freedom without touching code. A custom build if the site is part of the pitch and you have the budget and the patience for upkeep.
Whichever you choose, build one case study properly before you build the whole site. It will tell you more about the platform than any comparison can. Then diarise a review in twelve months — you can always move later, as long as you own the domain and can export your content.
Photo: jamesmarkosborne / Pixabay
