Freelancer Portfolio Websites: Getting One Online, Not Just Designing It

Every article about freelance portfolio websites shows you twenty beautiful examples and stops. The examples are the easy part — the hard part is deciding what goes on yours, getting it to a domain clients can type, and knowing what it will cost you every month.

The galleries are genuinely useful for taste, and useless for execution. This is the execution half: what a portfolio needs to actually win work, the four routes to putting one online with the trade-offs stated plainly, and the running costs nobody mentions until the first invoice.

What clients actually look at
Four ways to put it online
The images are the whole performance problem
What it costs, honestly
Things worth doing once, at the start
How this fits the rest of the stack
FAQ

What clients actually look at

The uncomfortable finding from anyone who has watched clients browse portfolios: they do not read. They scan three or four pieces of work, form an impression in seconds, and then look for two things — whether you have done something like their problem before, and how to contact you.

That has direct consequences for what belongs on the site.

Fewer pieces, better chosen. Six strong projects beat twenty mixed ones. A weak piece does not add to the average; it drags it down, because the reader assumes it is representative.
Lead with the work, not with you. The About page matters, and it is not the front door. The front door is the strongest thing you have made.
Say what the problem was. Two sentences of context in front of each piece — what the client needed, what you did — separates a portfolio from a gallery. This is the single most common omission.
Make contact unmissable. An email address in the header, in the footer, and on its own page. Not a form that may or may not be wired up. An address they can copy.
Show the category you want more of. You get hired for what you show. If you want different work, show different work, even if you had to make it up as a self-directed piece.

The thing that consistently loses work is not an unfashionable design. It is a portfolio where the visitor cannot tell what you do, or cannot find how to reach you within one screen of scrolling.

Four ways to put it online

In rough order of effort, with the real trade-off rather than the marketing one.

A portfolio platform. Sign up, upload, done in an afternoon. Fastest route, and your work lives inside someone else’s product on someone else’s URL structure. Fine as a first version; a poor place for an archive you want in ten years.
A site builder. More design control, your own domain, a monthly fee that continues indefinitely. Good middle ground for people who do not want to touch code, with the caveat that the site is not portable — you cannot take the pages elsewhere.
A static site. Written as files or generated from Markdown, built once, served as HTML. Cheapest to run, fastest to load, and the most portable — the content is text files you own. Requires being comfortable with a build step, or a Git-backed editor sitting on top.
A CMS you host. WordPress or similar. Most flexible, most maintenance. Worth it if you need to publish frequently or run a blog alongside; overkill for twelve project pages that change twice a year.

For most freelancers the honest answer is a static site on your own domain. A portfolio is content that changes rarely and is read often, which is precisely the case static hosting is designed for — and it is the option that costs the least while performing the best.

Whichever you pick, register the domain yourself, in your own account, with your own card. That is the one decision that is expensive to reverse.

The images are the whole performance problem

A portfolio is an image-delivery problem wearing a website costume. The HTML weighs nothing; the work does.

A photograph or a design mockup exported at full resolution is commonly 3 to 10 megabytes. A project page with eight of them is a page that takes ten seconds to arrive on the phone your prospective client is holding on a train. They will not wait, and you will never know they were there.

Three fixes, in order of how much they help:

Resize to the width you actually display. A 4000px image in a 1200px container downloaded three times more data than the screen could use. Export a few widths and let srcset choose.
Use a modern format. AVIF or WebP with a JPEG fallback is routinely a third to a half the size at the same perceived quality.
Lazy-load below the fold — and not the hero. Add loading="lazy" to gallery images, and deliberately leave it off the first image, which is what the reader is waiting for.

Also put explicit width and height on every image. Without them the page jumps around as each one arrives, which looks careless in a way that is hard to unsee on a page whose entire job is to demonstrate care.

What it costs, honestly

The numbers people are usually surprised by, in both directions.

The domain is a fixed annual cost, typically the price of a couple of coffees. Buy it for a year, set auto-renew, and forget it. This is not where money goes.
Hosting a static portfolio is close to free until you get traffic, because you are serving files rather than running a server. There is no process sitting idle waiting for visitors.
Bandwidth is the line that moves. A portfolio is quiet for months, then a piece gets shared somewhere with an audience and a month of transfer happens in an afternoon. Check what is included and what the rate is afterwards, before that happens rather than after.
A site builder’s subscription continues whether anyone visits or not, and is usually the largest recurring line for a portfolio that gets modest traffic.
Email on your domain is a separate small cost and worth it. An address at your own domain reads as a business; a free consumer address on a proposal reads as a hobby.

The trap is optimising the wrong line. People agonise over saving a few pounds on the domain and then pay a builder subscription forever for a site that could have been static files.

Things worth doing once, at the start

A short list that costs an hour and saves a lot of irritation later.

Own the domain and the DNS. In your account. If a developer or agency registers it for you, get it transferred before you need it in a hurry.
Pick one canonical hostname — with or without www — and permanently redirect the other, so you are not accidentally running two copies of your site.
Get the certificate automated. An expired certificate shows a full-page browser warning, and it will expire on the week you are pitching.
Put the source somewhere safe. A repository, even a private one. Portfolios get lost when a laptop dies or a platform closes.
Write the case-study text before designing the layout. Design around real content and it fits. Design first and you will be padding to fill boxes.
Check it on a phone, on mobile data. Not on your desktop over wifi. That is where most people will actually see it.

And set a calendar reminder to update it every six months. The single most common portfolio problem is not the design or the hosting — it is that the newest piece on it is three years old.

How this fits the rest of the stack

A portfolio’s running cost is mostly bandwidth, and bandwidth is the line that moves suddenly rather than gradually. The RunxBuild hosting calculator puts it beside the build and anything dynamic you need, so the month a piece gets shared is a number you already know. RunxBuild builds static sites straight from a repository — which is where the image resizing and format conversion belong — with 120GB of bandwidth included, and the custom domain and its certificate handled as part of the deploy rather than as a separate thing to remember.

Useful related references:

FAQ

What should a freelance portfolio website include?

Six to eight strong pieces rather than everything you have made, two sentences of context in front of each explaining the problem and what you did, an unmissable contact email, and work in the category you want more of. Clients scan rather than read, so the strongest piece belongs on the front page.

Do I need my own domain for a portfolio?

Yes, and it is the one decision that is expensive to reverse. Register it in your own account with your own payment method. A portfolio on a platform subdomain means your URL, your search rankings and your archive belong to that platform rather than to you.

What is the cheapest way to host a portfolio site?

A static site built from files and served as HTML. There is no server process running between visits, so the cost is close to zero until traffic arrives. The line that actually moves is bandwidth, because portfolios are image-heavy and get shared in bursts.

Why is my portfolio site slow?

Almost always the images. A page with eight full-resolution exports can be tens of megabytes. Resize to the width you actually display, serve AVIF or WebP with a JPEG fallback, lazy-load everything below the fold but not the hero image, and set explicit width and height so the layout does not jump.

Should I use a portfolio platform or build my own site?

A platform is the right first version — it gets work online in an afternoon. Move to your own domain and your own files when the portfolio starts winning work, because that is the point at which the URL, the rankings and the archive become worth owning.