You have a hard drive full of work and a browser full of bookmarked templates. Nine months later the site still says "coming soon". It happens to a lot of photographers, and the stall is rarely about design taste. It is about the decision underneath it: template or custom build?

Both can look beautiful. Both can rank. The differences show up in cost, control, maintenance and how much of your own time you hand over. Here is how to think it through without getting stuck.

Cost: the price tag is only part of it

A template shifts money into time. You pay a modest fee, either a monthly subscription or a one-off theme licence, and then you spend evenings dragging galleries around and rewriting placeholder text. A custom build flips that: a larger upfront invoice, fewer hours of your own.

The true cost of either route usually includes:

• Licence or subscription fees, and whether they are monthly or one-off
• Hosting and a custom domain, plus business email if you want it to match
• Your time to build, populate and proofread
• Ongoing updates, backups and the occasional emergency
• The cost of switching later, which is rarely zero

That last point deserves attention. If you leave a platform in three years, can you take your content and your URLs with you? Ask before you sign up, not after. A theme that exports cleanly is worth more than one that saves you a few pounds a year.

If you commission a build, get the scope in writing: how many page templates, how many revision rounds, who handles hosting and what happens when you want a change six months later. Any agreement involving money or ongoing services is worth reading properly, and if the sums are significant, take proper advice before signing.

Control: what you can change and what you cannot

Where templates win

They handle the boring parts. Responsive layouts, mobile menus, contact forms, image compression — configured for you, often without you noticing. If your work presents well in a standard grid, a good template will do the job and let you get back to shooting. For a portrait photographer with a handful of galleries and a contact page, there is little to gain from a custom build.

Where templates start to bite

Templates have opinions. They decide the aspect ratios, the spacing, the way captions sit, the maximum number of images in a row. If you shoot panoramic landscapes, square medium-format film or long vertical editorial frames, you will fight the crop. You will also hit walls on the unusual jobs: an interactive map of wedding venues, a print shop with size and framing options, a password-protected client area with download limits.

Custom builds exist for exactly these cases. You get the layout you imagined, but you also own every decision, including the ones you would rather not make.

SEO: the platform matters less than the fundamentals

Search performance comes mostly from things you control on any platform:

• Unique, descriptive page titles and headings
• Real words on the page: what you shoot, where, and for whom
• Well-compressed images with sensible file names and alt text
• Fast loading, especially on a phone
• Links from other sites, which no template can give you

Where custom builds pull ahead is in the details. You can add structured data, control URL structures, create location or service pages without a workaround, and edit the head of the document. On a rigid template you may be stuck with URLs like /portfolio/item-847 and a blog that lives on a subdomain.

That said, plenty of photographers rank well on hosted platforms. If your plan is to publish useful pages about the weddings you shoot in Somerset and get listed by the venues you work with, a template will carry you a long way.

Maintenance, hosting and year three

With a hosted template, someone else handles updates, security patches and backups. You trade that convenience for dependence: pricing can change, features can be retired, and your site lives on someone else's terms.

A custom site, particularly on WordPress or another CMS, puts you in charge — which means you are responsible. Plugins need updating, software versions move on, backups need testing. A neglected build becomes a liability rather than an asset. If you would rather not think about any of it, factor a maintenance arrangement into the quote.

A sensible middle ground exists: custom design on a managed platform, or a template platform with a custom domain and a theme you have stripped back to its bones.

Speed and how your images actually load

Your visitor is probably on a phone, often on patchy mobile data, tapping through from a social profile. Image handling decides whether they stay. Export at a sensible long edge rather than uploading 6000-pixel files, convert to modern formats where you can, and avoid a homepage slideshow of thirty full-width images. Test the site on a real phone, on mobile data, not just on your desktop.

Hosted platforms handle much of this automatically, which is a genuine advantage. On a custom build, image optimisation is a task rather than a default — someone has to configure it and keep it working.

How to decide, practically

Give yourself a week and work in this order.

1. Write down what the site must do: show work, take enquiries, sell prints, host client galleries, publish a blog. Rank those jobs.
2. Shortlist two templates and get one quote for a custom build, so you are comparing real numbers.
3. Build the template version first if you can, and fill it with twenty images from your last shoot rather than placeholders.
4. Look at it on your phone. If it shows your work the way you want, stop looking and ship it.
5. If you have hit three genuine walls — cropping, checkout, client delivery — a custom build has earned its cost.

Either route fails for the same reason: it never goes live, or it goes live with twelve images and was last updated two years ago. Choose the option you will actually finish, then treat the site as a living thing — new work in, old work out, and a page of writing every couple of months. That habit will beat any amount of clever design.

Photo: alonbluem / Pixabay