The guides to starting a photography business cover the business name, the LLC, the camera and the pricing, and then say build a portfolio as though that were one line. It is not one line — it is the storefront, and it is the part of the business with the most unusual technical requirements.
Everything else on the startup checklist is ordinary small-business admin. The portfolio is different, because a photography site is an image-delivery problem and images behave differently from every other kind of web content. Here is what that actually means for the business.
Table of contents
- The bits every guide covers, briefly
- Why a photography site is technically unusual
- The three changes that fix it
- Client galleries are a separate problem
- The costs to put in the plan
- How this fits the rest of the stack
- FAQ
The bits every guide covers, briefly
Worth acknowledging so we can move past them, because the standard advice is genuinely good.
- Keep the name simple, usually your own. Photographers are remembered by name, and a legal name is one thing nobody else can trademark out from under you.
- Register properly and get liability insurance before shooting a paid job, particularly weddings, where the cost of a failure is somebody’s day.
- Buy less gear than you think. Second-hand bodies and one good lens beat a new kit spread thin. The camera is rarely the constraint on early work.
- Build the portfolio by shooting free work deliberately — friends, local businesses, styled products — chosen to look like the paid work you want.
- Price on total time, including editing and admin, not on shoot hours. This is the most common early mistake and the hardest to correct upward later.
The one thing to add to that list: check the domain is available while you are choosing the name. It costs almost nothing to register and it is far easier than discovering after the business cards are printed that the matching domain is gone.
Why a photography site is technically unusual
Most small-business websites are text with a few images. A photography portfolio is the inverse, and the arithmetic is stark.
A file straight out of a modern camera is commonly 5 to 15 megabytes. A gallery page showing twenty of them, uploaded as exported, is somewhere between 100MB and 300MB. On a phone on mobile data that page takes tens of seconds, or never finishes because the visitor left.
The same twenty images, resized to the widths actually displayed and encoded as a modern format, land somewhere around 2 to 5 megabytes for the whole page. That is not a tweak — it is two orders of magnitude, and it is the difference between a portfolio that feels professional and one that feels broken.
This matters commercially rather than technically. A prospective client looking at three photographers on their phone will form an impression of competence partly from whether your work appeared. A slow gallery reads as amateur even when the photographs are the best of the three.
The three changes that fix it
- Resize to display width. A 6000px original shown in a 1200px container downloaded five times more data than the screen could use. Export a handful of widths and let the browser pick with
srcset. - Encode as AVIF or WebP, with a JPEG fallback via
<picture>. Typically half the bytes of a comparable JPEG at the same perceived quality. - Lazy-load below the fold, never the hero. Gallery images get
loading="lazy"; the first image the visitor is waiting for does not.
Also set explicit width and height on every image so the page does not shift as photographs arrive. On a site whose whole purpose is demonstrating visual care, a layout that jumps is a poor first impression.
The practical way to do all of this without touching it per-upload is a build step: point the site generator at your originals and let it produce the variants automatically at publish time. That is one setup task rather than a discipline you have to maintain for every shoot.
Client galleries are a separate problem
Delivering finished work to clients is a different requirement from the public portfolio, and conflating them causes trouble.
- Full resolution, not web-optimised. Clients want the originals. That is a large download, repeatedly, and it is where photography bandwidth bills actually come from.
- Access control. A wedding gallery should not be public or guessable. A password or an unguessable link, and files that cannot be enumerated by walking a directory.
- A retention policy. Galleries accumulate forever otherwise. Decide how long you keep them and tell clients, or storage grows without limit.
- Backups that are not the delivery mechanism. The gallery is for the client; your archive is a separate thing, ideally in two places.
Plenty of photographers use a dedicated client-gallery service for this and keep the public portfolio separate. That is a reasonable split — the requirements genuinely differ, and paying for delivery infrastructure while hosting the portfolio cheaply is usually better than forcing one system to do both.
The costs to put in the plan
Against the gear and insurance lines you are already budgeting, the web presence is small — with one line that can move.
- Domain — small, annual, and the only thing you must own outright from day one.
- Portfolio hosting — for a static site serving optimised images, one of the smaller monthly figures in the business.
- Bandwidth — the one that moves. A portfolio is quiet for months and then a shoot gets shared, and a month of transfer happens in a weekend. Know the included allowance and the overage rate before that happens.
- Client delivery — either a subscription to a gallery service or storage plus bandwidth on your own setup.
- Archive storage — your originals, in two places. This grows every single shoot and is the line that quietly compounds over years.
- Business email on your domain, per mailbox, small.
The one that surprises people is archive storage, because it never goes down. Every wedding adds tens of gigabytes that you cannot delete. Budget for it growing rather than for its current size.
How this fits the rest of the stack
Photography is one of the few small businesses where bandwidth genuinely is a line item, and it moves in bursts rather than gradually. The RunxBuild hosting calculator shows transfer beside the build and the storage so a shared shoot is a number you priced in advance. A static build is the right shape for the public portfolio — RunxBuild builds one from a repository, which is where the resize-and-encode step belongs, with 120GB of bandwidth included before metering at $0.10/GB and the domain and certificate handled at deploy.
Useful related references:
- Photography Hosting: What Image-Heavy Sites Actually Need
- Small Business Automation: Start With the Task You Do Every Tuesday
- AWS Business Support Pricing: 10% of Your Bill for a One-Hour SLA
- Services on RunxBuild
FAQ
What do I need to start a photography business?
The standard list — a simple name, proper registration, liability insurance before any paid job, less gear than you think, and pricing based on total time including editing. Add one thing the guides omit: check the domain is available while you are still choosing the name, before anything gets printed.
Why is my photography website so slow?
The images, essentially always. Camera exports are 5 to 15MB each, so a twenty-image gallery uploaded as-is can be 100MB or more. Resize to displayed width, encode as AVIF or WebP with a JPEG fallback, and lazy-load below the fold. That typically cuts the page by more than 90%.
How much bandwidth does a photography portfolio use?
Unpredictably, and in bursts. It stays quiet for months, then a shoot gets shared and a month of transfer happens in a weekend. Optimised images make this manageable; the thing to check in advance is the included allowance and the rate charged beyond it.
Should client galleries be on the same site as my portfolio?
Usually not. They have different requirements — clients need full-resolution downloads with access control and a retention policy, while the portfolio needs small optimised files served publicly. Many photographers use a dedicated gallery service for delivery and host the portfolio separately.
What is the hidden cost in a photography business?
Archive storage. Every shoot adds tens of gigabytes of originals you cannot delete, in two places if you are being sensible. Unlike most costs it never goes down, so budget for it growing rather than for what it is today.