How to Build a Photographer Website Without Code 2026

A photographer website without code starts with one description: what you shoot, who hires you, and what happens when someone wants to book. Zugo builds the site from that text, boots it in a sandbox to check it opens, and publishes it to a live address. A simple build takes about a minute.

The images are the hard part, and they are yours. What the builder removes is the week spent choosing a theme, fighting a gallery plugin, and configuring hosting before a single photograph is online.

What does a photographer's site have to do?

One thing: get a specific client to enquire. Not to impress other photographers, not to show everything you have ever shot. A wedding client and a commercial art director want opposite things from the same page, and trying to serve both produces a site that serves neither.

So the first decision is not visual, it is editorial. Pick the work you want more of and lead with it. If you shoot weddings on weekends and products midweek, that is two audiences and arguably two sites, or at minimum two clearly separated sections with different calls to action.

The second decision is quantity. Twenty photographs chosen ruthlessly outperform two hundred. Clients do not browse an archive, they scan until something matches what they need and then look for the price. Everything that is not your best work is actively costing you enquiries.

What should the prompt say?

Name the genre, the audience, the gallery structure, and the action. A vague prompt gives you a generic creative page. A specific one gives you something close enough to edit rather than argue with.

Build a website for a [wedding / portrait / product] photographer
in [city].
Sections:
1. Hero: one full-width image, my name, one line on my style,
   button "Check my availability".
2. Portfolio: [N] galleries by type, each opening a grid.
3. About: my photo, how I work on a shoot day, what clients say
   about the experience.
4. Pricing: packages with what is included and delivery times.
5. FAQ: turnaround, travel, deposits, usage rights, weather backup.
6. Enquiry form: date, location, type of shoot, contact.
Layout: images large, text small and quiet.
Palette: neutral, so photographs carry the colour.

The last two lines matter for a photographer more than any other trade. A busy palette and heavy typography fight your images. Ask for restraint explicitly, because a default design will always add more than a photographer wants.

If a blank prompt feels harder than editing, Zugo ships 25 templates and a portfolio template is a reasonable starting point. The portfolio site guide goes deeper into structure for creative work.

Should you publish prices?

The oldest argument in the trade, and the site makes it concrete. Three approaches, each with a real cost.

For anything with a repeatable package, publishing "from" prices is usually the highest-value change you can make to a photography site. It removes the enquiries you would have lost anyway at the price question, which is the expensive part of your week.

Commercial and editorial work is the honest exception, since usage rights change the number more than the shooting day does. In that case the page should explain how you quote, which is itself reassuring, rather than staying silent.

How do you take deposits and payments?

Photography has an unusual payment shape: a deposit to hold a date, a balance before or after delivery, and sometimes an album order months later. Match the site to that reality rather than to a generic cart.

The deposit is the piece worth building first, because an unpaid date is not a booking. Payments in an AI-built app covers connecting Stripe, test mode, and what happens after the first live charge.

What does it cost in credits and time?

Zugo bills per action, so the project is priceable before you start. A photographer site with a hero, galleries, pricing, and a form is a normal build. It becomes a multi-page platform when you add client logins and private galleries.

Free gives 5 credits, enough to look around, and a build costs 6, so a working site starts on Pro at $25 a month with 200 credits. Business is $99 a month. Hosting for the published site is included, which removes a recurring bill photographers often forget to budget.

A simple build takes about a minute and a multi-page platform takes several minutes. Realistically the site is not what takes your week: selecting and exporting the images is, and that work exists no matter which tool you use.

How do you keep the site fast with big images?

This is the failure that actually kills photography sites. Full-resolution exports on a landing page produce a beautiful gallery that nobody waits for, and mobile visitors leave before the hero finishes loading.

The fix is at the source. Export web copies at roughly 2000 pixels on the long edge, quality around 80, and check the file weight before uploading. A photograph that looks identical at 400 kilobytes instead of 8 megabytes is the single largest speed gain available to you.

Then test on a phone using mobile data rather than your studio wifi. If the hero image has not appeared by the time you would normally lose patience, cut the number of images on that screen. A fast site with fifteen photographs beats a slow one with sixty.

How do you publish on your own domain?

Publishing is one action and the site goes live at yourname.zugo.run. For a photographer the domain is part of the brand, so connect your own quickly. The custom domain guide covers the DNS records to add.

Add Google Analytics at the same time and watch one number: how many people who open a gallery go on to the enquiry form. That ratio tells you whether the work or the ask is failing, and each is fixed differently.

If you later outgrow the builder, GitHub export gives you the real repository. The project is yours, so a developer can take over the code rather than starting again, which is worth knowing before you invest a year of image updates into it.

Where does an AI builder stop for photography?

Three limits, stated plainly.

Client proofing and delivery are a different product. Private galleries where a client selects favourites, approves retouching, and downloads finals are a real application with accounts behind it. Zugo can build accounts with Supabase through repeated edits, but a dedicated proofing service is better at this today.

Print fulfilment is not built in. Selling a framed print means a lab, sizes, and shipping. The site can take the payment. It does not order the print.

The photographs and the licensing text are yours. The builder writes structure and copy. It does not shoot, retouch, or know what your usage terms should say.

Inside those limits you get a quiet, fast, well-structured portfolio that asks for the booking, built in an evening and edited in a sentence. Describe the work you want more of at zugo.dev and see the first build.