
The short answer
Choose images for the information they add. Prepare a source, permission record, meaningful caption and appropriate text alternative for each useful visual. Check the actual exported files instead of assuming a format or a large original will suit every placement.
An image should help the visitor understand the work, the decision or the process being described. A screenshot can show a real interface. A diagram can explain a connection that a photograph cannot. A graph can show a measured comparison when the underlying data is available. Choose the visual after identifying that purpose.
Prepare an image record alongside the copy
For each proposed asset, record its source, approved use, subject and intended placement. Keep a client screenshot attached to the correct project and delivery role. Remove private records from any proposed example before sharing it for approval.
Label constructed interfaces and illustrative scenarios clearly. They can explain an idea without pretending to be a delivered project. A stock photograph should not imply that the people shown are WebBuild staff or a named client's team.
Use captions to explain the evidence
A caption can identify what the reader is looking at and why it matters. It can also preserve a limitation, such as a screenshot demonstrating an interface without proving an increase in enquiries. Keep that distinction close to the visual.
For technical processes, use labels that match the documented implementation. A daily scheduled data import should not become a live-sync animation or a real-time claim. The property listing integration guide shows how attribution and update timing affect the explanation.
Give meaningful images an appropriate text alternative
W3C distinguishes informative, decorative, functional and complex images. The appropriate alternative depends on the image's purpose in that context. A graph or detailed process diagram may need a nearby explanation as well as a short alternative.
Avoid copying the same long description into every image field. Keep decorative material from adding unnecessary reading, and ensure the text around a complex visual preserves the information someone needs if they cannot see it.
Compare the actual exports
The measured graph below compares the PNG and WebP exports of one featured illustration prepared for this review batch. Both have the same pixel dimensions. File sizes come from the supplied files; the chart is not a claim about client website performance or a universal compression ratio.
Use this as a practical review method. Inspect both versions at the size used on the page. Check fine text, logos and hard edges. A smaller file that damages important information may need different settings, another format or a simpler composition.
Review checkpoints
- Purpose
- What does this visual explain?
- Permission
- Source and approved use
- Description
- Caption and appropriate text alternative
- Export
- Dimensions, format and observed quality
Measured local files · 7 November 2026
Compare two exports of the same illustration.
File size · KiB
Both bars start at zero and use the same 0–50 KiB scale.
Inspect the measurements and source files
| Format | Bytes | KiB |
|---|---|---|
| PNG | 41,711 | 40.73340 |
| WEBP | 26,604 | 25.98047 |
Review the crop where the image appears
A featured image, a narrow related-reading card and an in-body illustration can use the same source differently. Check that an important label or project detail survives the actual crop. A desktop approval alone will not reveal every problem in a phone layout.
For in-body diagrams, keep text readable and connections understandable at the displayed size. If a wide diagram becomes unreadable, provide a layout suited to the smaller width and retain a textual explanation.
Make the handover usable
Keep original assets, approved exports and permission notes together. Give the editor a rule for choosing future images and a route for checking uncertain material. The managed CMS guide covers the wider editing and handover responsibilities.
For a website redesign, share the images you already have and the facts they can demonstrate. The brief can then identify where a real screenshot, a clear diagram or new commissioned photography would add useful information.
Tell us about your project
Start with your details. We’ll discuss the right next step.
Questions covered in this guide
Can a mockup be presented as delivered client work?
No. Label illustrative material clearly and keep actual project attribution accurate.
Will every WebP file be smaller than a PNG?
No. Compare the actual exports, their visual quality and their intended use. The measured example in this article describes only the supplied files.
Sources and project context
- W3C accessibility guidance Checked 7 November 2026
- Yukt Law Offices: redesign and continuing website care Web Build Solutions project record
Turn the question into a clear next step.
Tell us about your current setup, the people using it and what needs to improve.
