Build your photography website around your work and your next enquiry
You can start a photography website by pasting the prompt below into an AI builder: a portfolio of your real work, your services and packages, and a shoot enquiry form. Replace the brackets, add your photos, then check the copy and test the form before sharing it. The first version gives potential clients somewhere to see your style and tell you what they need.
Start with the work you want to book: weddings, portraits, products, events or another specialty you actually offer. You can add photo selection, client access and payments later. If you already use a gallery service for delivery, link to it while you evaluate whether a custom workflow meets your needs.
Step 1 — Pick your platform
- Base44 — start here for a portfolio connected to an enquiry database and owner dashboard.
- Lovable — consider it for a visually tailored portfolio with a managed backend for enquiries.
- v0 by Vercel — consider it if you want a Next.js workflow and more hands-on control over the site and connected services.
Use the cards below to choose. These are starting points, not a claim that any builder produces a tested photography business system from one prompt. Not sure? Take the 60-second quiz →
Our Top 3 Picks
All three let you start building for free. Pick one, copy the prompt below and see your own first version.
Base44
· FreeStart with a portfolio, enquiry database and owner dashboard. Add client galleries only after testing file access and delivery.
Lovable
· FreeBuild a visually tailored portfolio with a managed backend for enquiries. Review image presentation and test every connected workflow.
v0 by Vercel
· FreeA Next.js path for photographers who want more hands-on control over layouts and connected services. Plan for setup and provider usage.
Step 2 — Copy the master prompt
Replace every [BRACKET] with your own details before pasting.
Build a mobile-first website for my photography business. Style: image-led, clear and personal. Help visitors understand my work and send a useful shoot enquiry. MY DETAILS - Business name: [NAME] - Specialty and clients: [ONLY THE PHOTOGRAPHY SERVICES AND AUDIENCES I SERVE] - Country, service area and travel: [COUNTRY / CITY / ACTUAL TRAVEL AREA] - Website language and currency: [LANGUAGE / CURRENCY] - Visual style: [DESCRIBE MY PHOTOGRAPHY AND PREFERRED COLOURS] - Portfolio: [MY APPROVED PHOTOS, CATEGORIES AND FACTUAL CAPTIONS; OR PLACEHOLDERS] - Packages: [REAL NAMES, COVERAGE, DELIVERABLES, DELIVERY TIMES AND PRICES; OR ASK FOR A QUOTE] - Background: [FACTUAL BIO, EXPERIENCE AND CREDENTIALS; OMIT ANYTHING NOT SUPPLIED] - Contact and social links: [EMAIL / OPTIONAL PHONE / LINKS] - Existing client gallery: [SERVICE LOGIN URL, OR NONE; NEVER A PRIVATE CLIENT'S SHARE LINK] - Response time and policies: [MY ACTUAL RESPONSE WINDOW AND REVIEWED TERMS; OR OMIT] PAGES Home: name, specialty, area, selected work and a clear "Enquire about a shoot" button. Use "Ask about your date" for event work; do not claim a date is available. Portfolio: show only my selected specialties. Use a responsive grid, sensible image crops, and a lightbox with keyboard controls, visible close button and mobile navigation. Avoid autoplay and heavy effects. Services and packages: use only supplied inclusions, delivery times, prices and currency. Distinguish a starting price from a fixed package. Use "Ask for a quote" when needed. About: write from my supplied facts without inventing a personal history. Contact: add the enquiry form, contact links and FAQ based on my supplied information. ENQUIRIES Ask for name, email, shoot type, preferred date or flexible timing, and city/venue if relevant. Make phone, budget and a short brief optional. Adapt labels to my specialty: do not ask product clients about a wedding. Do not collect identity documents, payment details or photo uploads here. Save enquiries in an owner-only dashboard and notify my supplied address using a supported, configured email service. Visitors must not read or list submissions. Use server-side validation and spam protection. Show success only after saving; handle notification failure without losing or duplicating the enquiry. State that this is a request, not a confirmed booking. Promise a response time only if I supplied it. REAL WORK AND PUBLICATION Use neutral image placeholders until I upload my own work. Never invent shoots, clients, awards, testimonials or portfolio images. Publish testimonials only when I supply genuine wording and permission; otherwise hide the section. Improvements to my real photos may refine lighting, crop, colour or background without inventing work or misleading clients about what I photographed. Make public portfolio selection deliberate. Do not automatically publish private client files. Use only images I have rights and any necessary publication permissions for. Keep private gallery links out of public pages. HANDOFF Let me edit images, captions, packages and service copy without rebuilding pages. Use responsive web images; keep delivery originals separate. Add accurate page titles, headings and alt text from the supplied images and facts. Support RTL if I choose Hebrew. Prepare privacy/terms drafts from my actual tools and country for review, never invent verified legal compliance. List missing settings and test mobile enquiries, owner access, notification delivery and gallery navigation. Clearly report anything you cannot test.
Step 3 — Refine with follow-up prompts
Paste these one at a time, in any order. Each takes seconds.
Build the business behind the website
Build a Portfolio Site
Extend your portfolio with project stories using your real shoots and locations.
Build a Client Portal
Build client access and photo selection, with file permissions and downloads tested before delivery.
Build a Booking & Appointments App
Add availability and deposits once your booking rules and payment flow are tested.
Build a CRM & Lead Tracker
Track shoot enquiries, quotes and follow-ups in one place.
How much does a photography website cost in 2026?
Your cost depends on what you build: a public portfolio and enquiry form, or a larger system that also delivers client files and takes payments. Budget for the builder, domain, email delivery and any gallery, storage, download traffic or payment services. Build credits and running costs are not the same thing.
Compare the complete workflow with your actual current bill. A specialist gallery may be free or inexpensive at your volume; a custom build is not automatically cheaper. Check storage capacity, original-file downloads, print ordering, support and migration effort before replacing it. Keep a service that already does these jobs well while testing any replacement.
Start free — try your photography website with your own work
Use your chosen builder's available free allowance to try the prompt with a small set of approved portfolio images. You may need more credits to finish. Free publishing options exist, but custom domains, connected features and increased usage can require payment. Check the current plan for the workflow you want.
First test a real enquiry from your phone. Then decide whether the site is useful enough to extend with galleries or payments.
Two honest warnings
- Public portfolios and private delivery are different jobs. Optimize the public portfolio for viewing. Keep client originals and private details behind tested access controls. A login screen alone does not protect a public image URL. Use the gallery follow-ups as a staged build, with separate backups and checks for access, downloads and expiry.
- Show work you can substantiate and publish. Use your own real photos and genuine testimonials. AI-assisted improvements to your real images are welcome when they remain faithful to your work. Do not invent shoots or portfolio pieces. Check both your rights to the image and any necessary permission to publish recognizable clients, particularly children; a booking is not automatically permission for marketing.
Set your country, language, currency and service area before building. Permission and privacy requirements depend on location and use; a translated page is not a legal review. For example, France's CNIL guidance distinguishes agreeing to be photographed from online publication, and Spain's AEPD explains that recognizable images are personal data. Use the country guides as a starting point and get qualified advice for unclear uses.
FAQ
See what you can build with Base44.
Start on the free plan, paste your prompt and explore your first version.
Start free with Base44Not sure? Take our 60-second quiz →