
Ready for a better website?
Serious about growing your business online?
Give each important image a specific purpose before selecting it.
Keep original files and supply context about the subject, project and intended use.
Plan wide and narrow crops together instead of leaving mobile to the end.
Separate genuine evidence of your work from decorative or conceptual imagery.
Review the finished page for clarity, image quality, loading and appropriate alternative text.
A folder of attractive photos is not yet a useful website image library. The designer still needs to know what each picture shows, which claim it supports and whether it will survive the crop required by the page. Without that context, a redesign can reach its final stages with the wrong images in its most important places.
Prepare website photography around the decisions your visitors need to make. Show the work, people and details that help someone understand your offer. Then organise the files so the design team can use them accurately, consistently and without avoidable delays.
Start With the Questions Your Images Must Answer
Begin with the page rather than the camera. What does a potential client need to understand here? A contractor's service page might need to show the type of work undertaken, the quality of a detail and the people responsible. A consultancy might need a clear portrait, a real working environment or a simple explanation of its process.
Write one short purpose beside each planned image. Examples include showing the scale of a completed installation, introducing the person who leads consultations or explaining the sequence of an engagement. If the purpose is merely to fill a large rectangle, consider whether that rectangle belongs in the design.
The image and nearby copy should tell the same story. A paragraph about careful restoration needs different evidence from a paragraph about rapid installation. Selecting the most dramatic photograph without checking that relationship can leave the visitor with a misleading impression of the service.
Use your service-page copy as a starting point. Mark the statements that would benefit from visual support, then ask what you can actually show. This often reveals a more useful shot list than a general request for fresh branding photos.
Keep expectations proportionate. An image can explain a detail or establish who is involved. It cannot independently prove every claim about reliability, expertise or commercial outcomes. Where the claim needs a caption, process explanation or other evidence, provide that alongside the picture.
Audit the Library Before Commissioning More Photography
Gather the best available originals in one place before deciding what is missing. Include completed work, details, team portraits, premises and process images. Keep a separate area for assets that need clarification, rather than mixing them with files ready for publication.
Make a small inventory. Record a recognisable filename, subject, date where relevant, source, proposed page and any restrictions or unresolved questions. This is an operational record, not a substitute for checking the permissions applicable to a particular asset. Do not tell the designer that everything is cleared if that has not been established.
Review each image at a useful size. Look for missed focus, heavy compression, distracting backgrounds and edits that make surfaces or colours hard to judge. A thumbnail can hide faults that become obvious when the image fills half a desktop screen.
Choose a shortlist rather than handing over several hundred near-identical files. Retain the full archive, but make the preferred options easy to find. If three photographs show the same room, explain which view best communicates the layout and which close-up shows the relevant workmanship.
A gap should describe missing information. Need more images is vague. Need a clear view of the finished entrance and a portrait of the consultation lead gives the next person something to produce. That distinction helps keep a new shoot focused on what the website actually needs.
Build a Shot List Around Page Roles
A useful shot list connects the page, the subject and the composition. It also explains what must remain visible when the photograph is cropped. Share rough layouts or reference frames with the photographer when available, clearly labelling them as direction rather than a finished design.
The following planning table is a suggested working method, not a universal photography specification.
Page role | Useful subject | Composition question |
|---|---|---|
Homepage introduction | A representative service, place or real team | Can the main subject remain clear beside the opening message? |
Service explanation | A relevant task or specific detail | Does the image explain this service rather than a different offer? |
Project story | Overall result plus meaningful close-ups | Can the sequence show context before detail? |
Team introduction | The person a client will actually meet | Will the portrait still read well in a narrow crop? |
Process section | An authentic stage of the work | Can a caption explain what happens at this stage? |
For a hypothetical cabinetry business, a completed kitchen photograph might introduce the project. A close-up of internal storage could explain a feature. A consultation image could show how decisions are made. Three versions of the same wide room view would not serve those three purposes equally well.
Capture variations where the layout genuinely needs them. A wide scene with quiet space on one side may suit a desktop hero. A more concentrated composition may be better for a phone. Ask for these alternatives during the shoot rather than expecting every image to work in every frame afterward.
Do not turn the shot list into a requirement to photograph every possible page independently. One strong asset may have several appropriate uses. The aim is enough meaningful variety to explain the business, not a large collection for its own sake.
Keep Real Evidence Distinct From Illustration
When a photograph appears in a project story, visitors may reasonably read it as evidence of that project. Check that the caption, context and presentation support that interpretation. Do not use an unrelated stock interior to imply a completed installation, or a generated team portrait to suggest a real employee.
Conceptual imagery can still be useful. A diagram can explain a process that is difficult to photograph. An illustration can make an abstract service easier to understand. The distinction is what the image claims to represent, not simply which tool produced it.
Label a concept where the surrounding context could otherwise make it look like actual work. Keep approved originals separate from mockups, reference material and experimental artwork in the handoff folder. Clear separation helps prevent an attractive placeholder from accidentally becoming permanent evidence.
For project photography, ask the person responsible for the work to verify the description. Which parts were delivered by the business? What was supplied by others? What can be said publicly? Our project-page guide explains how to turn accurate project information into a useful story.
Editing should preserve the information the visitor is meant to assess. Removing a temporary distraction is a different decision from changing the appearance of the delivered work. When an alteration changes the substance of the claim, reconsider the image or explain its status rather than relying on the viewer to guess.
Plan Crops Before Approving the Final Selection

The uncropped photograph is only one version of the image a visitor will see. Cards, wide sections and phone layouts may all reveal different portions of it. Review proposed images inside those frames before considering the selection finished.
Identify the focal point. It could be a person's face, a particular joinery detail or the relationship between two parts of a room. Ask whether that information remains visible at each relevant size. A crop that keeps the centre of the file is not necessarily a crop that keeps its meaning.
Also consider text placement. A visually quiet area can make a headline easier to place, but the designer should not have to cover a crucial part of the subject to achieve it. If no crop works, change the layout, choose another image or supply a separate composition.
For a hypothetical team portrait, a wide crop might include everyone while a narrow one removes two people at the edges. That is a content problem, not just a styling detail. A different arrangement or an alternative photograph may be more appropriate than shrinking the entire image until faces become unreadable.
Approve crops in context with the actual heading and surrounding content. A photograph that looks excellent in an isolated gallery may feel repetitive next to another nearly identical scene. The whole page needs a sequence of information, not a collection of individually attractive selections.
Hand Over Originals With Useful Context
Supply the highest-quality originals available and let the production workflow create delivery versions. Repeatedly saving a compressed export or forwarding a small messaging-app copy can remove detail before the designer has even chosen the final crop.
Use a simple folder structure that distinguishes originals, selected assets and approved exports. Give files recognisable names and keep the inventory beside them. Avoid a system where the only clue to the preferred image is that it was sent most recently in a chat.
Include the proposed page, what the image shows, the relevant project facts and any caption wording already confirmed. Add a named contact for questions. If a file is still awaiting approval, label that status clearly and explain what remains unresolved.
A practical handoff record might read: finished storage detail; project A; proposed use on the cabinetry service page; wide and square crops available; description confirmed by the project lead. This is a fictional example of the information to provide, not a client result.
Add the asset plan to the website redesign brief. Agree who supplies missing material and when it is needed. That prevents image production from becoming an invisible dependency that delays a page everyone assumed was ready to build.
Write Alternative Text for the Image's Actual Purpose
Alternative text is contextual. The same file can play a different role on two pages, so copying a generic description everywhere may miss what a visitor needs to understand.
The W3C alternative-text decision tree distinguishes informative, decorative and functional uses. A meaningful photograph generally needs a concise description that conveys its contribution. Pure decoration may need an empty alternative. An image that provides the only explanation of a link or button needs text communicating that action or destination. Complex information may need a fuller explanation elsewhere on the page.
Review the decision with the surrounding content visible. Do not force a long description into an image that repeats information already stated clearly nearby. Equally, do not hide meaningful project evidence from someone who cannot see the photograph.
Google's image SEO guidance recommends descriptive filenames, relevant placement and useful contextual alternative text. It cautions against filling that text with keywords. Treat the field as communication first, not a place to repeat a city name and service phrase.
For example, a fictional storage-detail image might be described as pull-out drawers inside a narrow kitchen cabinet. That is more useful than a string of phrases about the best local contractor. The description should reflect the image you actually selected, including any important change caused by the final crop.
Check Delivery Quality on the Finished Website
Original files and public delivery files have different jobs. Keep the original for future crops and revisions; verify that the published site serves an appropriately optimised version. A smaller file is not automatically better if the relevant detail becomes indistinct.
Ask the developer to check the actual rendered image rather than relying on the upload interface. Does it remain clear at the size used? Does it load reliably? Does the page shift around it? Is a phone receiving an unnecessarily large version?
The web.dev image-performance guidance explains why reserving image space can prevent movement during loading and why delaying an important image near the top of the page can hurt its appearance time. Images further down the page may be loaded later. Those decisions should follow the layout and measured behaviour, rather than applying one loading rule to every picture.
Check the main pages on a phone and a desktop with the actual published assets. Review the crop, surrounding text, loading behaviour and the next action. If a new export makes the page heavier, investigate the cause rather than assuming that a format change alone solves it.
Record the approved filenames and crops in the handover. Future editors should know which source to reuse and what to test when replacing it. The website handover checklist can help turn that one-time decision into a maintainable process.
Next steps
Choose one important service page and list the three visual questions it needs to answer. Match each question to an available original, note the crop it must support and record anything still missing. That short exercise gives a designer or photographer a much clearer starting point than an unstructured folder.
If the image plan is part of a broader redesign, explore our website design service. We can help connect the content, imagery and page structure so each element has a useful role.



