PROJECT BLUEPRINT · Photographers
How to build a photography website with AI
A photography website should help a potential client recognise your style and take the next step. Start with a tightly edited portfolio and a useful enquiry flow. A complicated gallery system is less valuable than a fast page that shows the right work.
A suggested project plan and original prompt—not a report of a completed Emergent test.
We may earn a commission if you purchase through our links.
What the first version needs
Turn a visitor who likes your photographs into a qualified enquiry.
- A homepage with one strong photograph and a clear description of your speciality.
- Two or three focused galleries, such as weddings, portraits, or commercial work.
- An about page with your location, approach, and working area.
- An enquiry form asking for project type, date, location, and contact details.
Choose work for the client you want
Select a small group of photographs that demonstrate the kind of assignment you want next. A wedding client needs to see a complete story, while a product client may care about lighting consistency and detail. Avoid mixing every genre into a single unlabelled gallery. Ask the builder for separate categories only when each category has enough strong work to stand on its own.
Prepare the photographs before building
Keep original files separately and prepare smaller web versions. Provide captions or short descriptions when they help explain a project. Alternative text should describe meaningful visual information; decorative images do not need keyword-heavy descriptions. Give the builder your own images and ask it to preserve their proportions instead of stretching them to fill arbitrary boxes.
Make the enquiry useful
Ask only for information you will use to respond. A form that asks for a date and location helps you assess availability, but visitors should not need to write an entire brief before making contact. Show a confirmation message after successful submission and provide a fallback contact method. A visual success message alone is not evidence that the message reached you.
A worked brief: a portrait photographer taking local enquiries
Imagine a fictional portrait photographer, Mira, who offers individual and small-team sessions in one city. Her existing social profile mixes paid work, travel photographs, and experiments. The website has a narrower job: show the portrait style, explain the session, and collect enough information to suggest a date. This example is an editorial exercise, not an Emergent customer story.
Mira starts with twelve approved portraits, a short biography, the session options she actually sells, and a reply address. She does not start by uploading an entire photo archive. The first homepage needs one representative portrait, a sentence identifying the service and location, selected work, a description of the session, and an enquiry action. A visitor should understand whether this is corporate photography, family photography, or fashion before reaching a gallery.
A useful draft headline is “Natural portraits for independent professionals in [city].” Under it, explain the format using confirmed facts: where sessions happen, whether guidance is included, and how enquiries are answered. Replace those brackets before publishing. Do not claim a turnaround time or number of delivered images until the photographer has approved it.
Organise the gallery around buying decisions
A gallery label should help a potential customer find relevant evidence. “Studio portraits” and “Team photographs” tell visitors more than “Collection one” and “Moments.” Put the strongest relevant work early, but include enough variation to demonstrate consistency. Ten variations of one flattering image are less informative than a smaller selection showing different people and lighting conditions.
| Visitor question | Content that answers it | What to avoid |
|---|---|---|
| Can you photograph someone like me? | A representative range of approved subjects | A gallery unrelated to the service |
| What will a session feel like? | A short process and preparation explanation | Vague claims about magical experiences |
| What am I buying? | Confirmed package inclusions or a clear quote process | Invented packages or prices |
| How do I ask about a date? | An enquiry form that carries the session type | A gallery with no next action |
Keep gallery navigation usable without a mouse. If images open in a lightbox, the visitor needs a labelled close control, keyboard movement, and a way back to the same place in the page. Do not make essential captions appear only on hover, because a phone has no equivalent persistent hover state.
Prepare images without sacrificing their purpose
Work from copies and keep the originals separately. Export images close to the largest size the page actually displays, then inspect the result on a high-density phone and a normal laptop. A practical starting experiment is a roughly 1,600-pixel-wide hero and smaller gallery versions, but the correct dimensions depend on the design. Compare file size and visible detail instead of applying one compression setting blindly.
Record a focal point for photographs that may be cropped. A face near the edge of a landscape image can disappear in a tall mobile hero. Ask the builder to use an uncropped image or a separately approved mobile crop when necessary. Reserve image space while files load so the text below does not jump around. Load the first important photograph promptly and let images farther down the page load later.
Write alternative text for meaningful photographs in their context. “Founder portrait beside a studio window” is more useful than a string of location keywords. If a caption already gives the project context, the alternative text can focus on the visual information. Decorative texture should not become a long spoken interruption for someone using assistive technology.
Build the enquiry as a small conversation
The enquiry form should collect name, email, session type, preferred timing, and a brief message. If the business covers multiple locations, ask where the session is needed. A date field should allow flexibility: someone planning a team session may know the month without knowing an exact day. Explain what happens after submission using a promise the photographer can maintain.
Test the complete chain with an address you control. Submit a message, inspect the inbox, reply to it, and confirm the response reaches the test sender. Then test missing fields, a long name, and an interrupted connection. If a failed submission clears the visitor’s message, ask the builder to preserve the text and show a retry action.
Review the photography enquiry flow. Keep the gallery unchanged. Require a name, reply email, session type, and message; make the exact date optional. Explain validation next to each field. Preserve entered text after errors. Show success only after the configured service accepts the submission. Give me steps to test delivery and replies.
Decide whether the first version is ready
Ask someone unfamiliar with the business to complete three tasks: identify the photography speciality, find a relevant gallery, and ask about a session. Watch without explaining the navigation. If they open a decorative menu before finding the work, simplify the route. If they ask what a package includes, add that missing explanation near the enquiry action.
For the first month, record enquiries by session type and note the questions people repeat. Those questions are a better content backlog than adding more animation. Add a dedicated service page when the service has enough distinct information and photographs to deserve one. Keep a monthly reminder to check contact delivery and update availability statements; a beautiful portfolio loses value quickly when its enquiry path fails.
Your starting prompt
Use this as an editable brief. Replace the brackets with your own details and review the result before connecting real services.
Create a responsive photography portfolio for [name], a [speciality] photographer serving [location]. Use my supplied images. Include a homepage, galleries for [categories], an about page, and an enquiry form collecting name, email, project type, date, and location. Keep the photographs prominent and preserve image aspect ratios. Ask which email service to connect. Use clearly labelled placeholders for missing images or testimonials. Start with the homepage and one gallery.
A useful follow-up request
The images feel cramped on mobile. Show one image per row on small screens, preserve its proportions, and keep captions beneath each image. Leave the desktop layout unchanged.
Check the result before launch
- Open a gallery on a phone using a slow connection.
- Check image crops, captions, and keyboard navigation.
- Submit a real enquiry and confirm it arrives at the intended inbox.
- Remove placeholder names, photographs, and testimonials.
Plan the cost and scope
Image volume and repeated gallery redesigns can increase the work involved. Budget separately for a domain and any form or email service. Do not assume the free credit allowance will cover a finished portfolio.
Read our pricing guide and credit-planning guide before setting a budget.
Ready for a first draft?
Choose a builder, start with the essentials, and check the result one step at a time.