Choosing Website Images: A Client Review Checklist for Relevance, Cropping and Credits

Website images should contribute to the page rather than simply fill available rectangles. A useful image can explain a product, establish a setting or make a service feel more concrete. An unrelated photograph can make the layout attractive while leaving the message no clearer.

Treat image selection as a design decision with its own review process. Ask what each image should communicate, whether the proposed asset does that job and how it behaves in the actual layout. Keep source information with the final choice so publication does not depend on someone finding the original download later.

Decide the role before searching

Write a short description of what the image needs to accomplish. “Show the scale of the product in a room” is more useful than “find something modern.” “Introduce the people providing the service” calls for different material from a generic illustration of collaboration.

The role also determines what not to use. A stock meeting photo may illustrate a discussion, but it should not be presented as a photograph of the client's team. A conceptual image can support an abstract service, provided the surrounding copy does not imply a specific customer or result.

Compare meaning before color coordination

Matching the brand palette is useful, but relevance comes first. Ask the client what a visitor would infer from the photograph without reading the caption. If the image suggests a different audience, setting or product category, a matching background color will not resolve that mismatch.

Review a small, purposeful selection rather than sending a large folder with no context. Explain the role of each candidate and the tradeoff it introduces. One image may communicate the product more clearly while another leaves more space for the heading.

Judge the crop inside the design

An image that works at its original proportions may lose its meaning in a wide banner or a small card. Place it in the actual container and check the focal point. Avoid approving an asset from a stock-site thumbnail without seeing the intended crop.

Repeat the check for the narrow layout. A side-by-side desktop hero may become a stacked mobile section with a different aspect ratio. Document whether the same crop works or whether the implementation needs a different focal position. Do not assume the developer can recover a subject that the supplied file cuts off.

Check text placed over images

Review every proposed text overlay using the actual image, not a flat placeholder background. A readable heading on one crop may become unclear when the subject or bright areas move. The design should explain how readability is maintained rather than rely on a fortunate composition.

Also consider whether the text belongs in the image at all. Text rendered as part of a photograph or export cannot behave like ordinary page text. For the working website, keep meaningful copy available in the appropriate page structure instead of treating a visual mockup as the implementation.

Keep licensing and credits with the asset

Save the source page, creator name and the license information associated with the download. A credit line is useful context, but it is not a substitute for permission to use an asset. Follow the source terms and any additional restrictions relevant to the intended use.

For Pexels assets, review the current Pexels License rather than assuming every use is unrestricted. Do not imply that a photographed person endorses the business. When a photograph is illustrative, a clear caption can prevent it from being mistaken for a real project or team photo.

Approve the asset, not just the placeholder

Create a short asset record: page, section, source filename, source link, creator, intended crop, alt-text purpose and approval status. Distinguish approved final images from temporary candidates. This makes the handoff more reliable and prevents placeholder photography from reaching the live site unnoticed.

Use descriptive alternative text where the image conveys information, and decide how decorative imagery should be handled in the implementation. The correct treatment depends on the image's role, not on a desire to repeat keywords in every attribute.

Review the page as a sequence

After choosing individual images, scroll through the whole page. Repeated compositions can make different sections feel interchangeable. Look for useful variation in subject and scale while keeping the overall direction coherent. Do not add more images solely to increase the count.

Share the final composition through Swelik and collect feedback against the actual layout. The website content checklist helps organize supporting copy and assets before the final review. Keep the full-resolution originals for the production workflow.

Create an image brief for each important section

Before collecting candidates, write the section's message, the image's role, the intended proportions and any practical restrictions. A homepage hero may need space beside the subject for copy, while a service card may need a recognizable detail at a much smaller size. These are different requirements even when the overall visual direction is the same.

Include what the image must not imply. If the business does not have a photographed office, an illustrative workplace image should not be labeled as its premises. If the page describes a process, a generic handshake may not explain anything useful. The brief helps the client judge relevance rather than simply choosing the most attractive picture in a search result.

Compare candidates in the actual layout

Place two or three suitable options into the same section using the intended crop. Keep the text and surrounding layout consistent so the client can judge the image choice itself. Showing raw downloads with different proportions can make the comparison harder because the reviewer has to imagine how each will be used.

Discuss the tradeoffs explicitly. One photograph may communicate the context clearly but leave little space for an overlay. Another may be easy to crop but feel too generic. A third may require a different arrangement. The decision becomes more useful when the client understands the consequences rather than voting without context.

Build variation without losing coherence

A page can become repetitive when every section uses the same wide office photograph. Vary the image's role: a setting, a close detail, a process moment or a concrete example. The variation should follow the story rather than introduce unrelated subjects simply to make the page look busy.

Review the images together at the end. Check whether the lighting, visual density and subject matter feel compatible with the design. Perfectly matching colors are not essential, but abrupt changes can make the page feel assembled from unrelated sources. Use the overall direction to guide selection without applying identical crops to every asset.

Plan for portrait and landscape source material

A portrait image can be useful in an editorial layout but may perform poorly in a very wide banner. Consider its natural proportions before designing a container around it. Cropping away most of the useful subject is rarely a good solution to a mismatch between the asset and the intended space.

Where the same image appears on several layouts, document the important focal point. If a separate mobile crop is needed, supply or specify it clearly. Preserve the original file so the production team can generate appropriate derivatives without repeatedly working from an already compressed copy.

Use captions to prevent misleading context

A caption can explain whether a photograph is an illustrative stock image, a real customer project or a supplied team photo. This is especially useful where the surrounding story could otherwise imply that the people or location belong to the business. Avoid captions that make unsupported claims about the subject.

For credited stock assets, keep the photographer's name and source link readable but visually secondary. The credit should not compete with the main article text, and it should remain connected to the correct image. If several photographs are used, a single ambiguous credit at the bottom may make the attribution difficult to follow.

Prepare a publication-ready asset record

For each final image, record the source URL, creator, download date, license reference, final filename and the page sections where it appears. Include any edits or crops relevant to later maintenance. Keep this record with the project assets rather than relying on browser history or a message containing a temporary download link.

A small spreadsheet or document is enough for many projects. The important part is that someone can later identify the asset and its permitted use. If an image must be replaced, the team should know where it is used and which design requirement the replacement needs to satisfy.

Review alternative text as content

Describe the information the image contributes in its specific context. Do not turn alternative text into a list of search keywords or repeat a caption unnecessarily. If the image is purely decorative, the implementation needs an appropriate treatment rather than an invented description that adds noise.

Ask the content owner to review meaningful descriptions alongside the visible copy. A product image may need a different description from a generic illustrative photograph, even if both occupy the same dimensions. The right text follows the purpose of the image, not the design template alone.

Check the exported preview before approval

Open the actual file or preview that the client will receive. Confirm that the selected images are present, correctly cropped and not replaced by broken external references. If a design includes externally hosted assets, understand the limitations of the preview format and use a self-contained export where appropriate.

Keep the full-resolution originals for production, while using sensible review files. A lightweight preview is useful only if it still communicates the image decision clearly. If the client needs to inspect product detail, provide an appropriate source reference rather than asking them to infer quality from a small thumbnail.

Finish with an asset acceptance summary

Identify the final choices, any remaining placeholders, who supplies missing files and which credits must appear. Separate approval of the composition from approval of the actual asset. That distinction prevents a temporary stock image from becoming permanent simply because everyone liked the page layout.

Frequently asked questions

Does adding a photographer credit make any image usable?

No. Confirm that you have the necessary permission or license. Attribution and permission are separate issues.

Should every section have a stock photo?

No. Use photography where it adds meaning. A diagram, product screenshot or well-structured text block may explain the section more effectively.