Content Writing
How to Select and Optimize Images for Blog Posts
Choose images that explain something, size them for the layout, use modern formats, write useful alt text and keep the featured image out of lazy loading.
Choose blog images that do a job (explain a process, show an example, present data or show the real thing) rather than decorate. Then resize each one to the width your layout actually displays, compress it and save it as WebP or AVIF where your site supports them, give it a descriptive file name and alt text that says what it shows, and never lazy-load the image at the top of the post.
The rest of this guide puts numbers on each step, with a worked sizing example, a format table and an alt-text decision rule you can apply in seconds.
Start With the Job Test
Before adding any image, finish this sentence: "This image helps the reader by...". If the answer is "breaking up the text", a subheading or a list usually does that better and loads instantly. Images that pass the test:
- Screenshots: of the actual setting, report or screen you are describing. The most useful image type in how-to posts.
- Diagrams and process flows: anything with more than three steps or relationships. Words struggle with structure; a simple diagram does not.
- Charts: when you cite numbers that compare or change over time.
- Real photographs: of your team, premises, products or finished work. They carry information a stock photo cannot.
- Annotated examples: a before-and-after, a marked-up document, a sample template.
Stock photos of people pointing at laptops rarely pass. They add page weight and tell the reader nothing; worse, readers recognise them. There is some evidence that useful visuals pay off: in Orbit Media's 2026 blogger survey, bloggers who used two to three visuals per post were the group most likely to report strong results. That is a correlation from self-reported data, not proof, but it points towards a few purposeful images rather than none or a dozen.
Size Images for Where They Will Actually Appear
The single biggest image mistake on blogs is uploading a 4,000-pixel photo straight from a phone or a stock site into a column that displays it at 800 pixels. The browser downloads every one of those pixels and throws most away.
A worked example. Suppose your blog's content column is 800 px wide:
- Display width: 800 px.
- Export width: 1,600 px, so it stays sharp on high-density ("retina") screens. Going beyond twice the display width rarely adds visible quality.
- Format: WebP or AVIF at a quality setting around 75–80, then look at it at full size before accepting.
- Check the file size: as a working rule, aim for well under 200 KB for an in-content photo and much less for screenshots and diagrams. If a photo is still over 300 KB, lower the quality or crop.
Better still, let the site serve different sizes to different screens. Most modern CMSs generate these automatically using the srcset attribute, which Google's image SEO guidance describes as a way of "specifying different versions of the same image, specifically for different screen sizes". Check yours does; on WordPress it is built in.
Choose the Right Format
| Format | Use it for | Notes |
|---|---|---|
| WebP | Most photos and screenshots | Usually smaller than JPEG at similar quality; supports transparency. |
| AVIF | Photos, where your CMS and CDN support it | Often smaller again than WebP; slower to encode. |
| JPEG | Photos, as a fallback | Universal, but larger at the same quality. |
| PNG | Screenshots with fine text, images needing exact pixels | Lossless and often heavy; convert to WebP if you can. |
| SVG | Logos, icons, simple diagrams | Vector, so sharp at any size and usually tiny. |
| GIF | Avoid | Use a short video or animated WebP for motion instead. |
All of these are formats Google Search supports; its documentation lists "BMP, GIF, JPEG, PNG, WebP, SVG, and AVIF" and asks that the file extension matches the file type.
Do Not Lazy-Load the Top Image
Lazy loading (telling the browser to fetch an image only when it is about to scroll into view) is excellent for images further down a long post. It is harmful for the featured image at the top, which is very often the largest thing on screen when the page loads.
That matters because Largest Contentful Paint, one of Google's Core Web Vitals, measures how long that largest element takes to appear. Google's web.dev guidance sets the target at 2.5 seconds or less. According to the HTTP Archive's 2024 Web Almanac, the element responsible for LCP involved an image on 68% of mobile pages, and nearly one in ten of the LCP images it found were lazy-loaded, delaying the very thing the metric times.
Rule of thumb: the first image a reader sees should load eagerly (and can carry fetchpriority="high"); everything below the fold can be lazy-loaded. If your theme or plugin lazy-loads every image by default, check how it treats the featured image.
Write Alt Text in Ten Seconds
Alt text exists so that people using screen readers, and anyone whose images fail to load, get the information the image carries. Search engines read it too, but that is a side benefit, not the purpose. The same Web Almanac chapter found 45% of images had no alt text at all, so getting this right is an easy edge.
Use this decision rule, simplified from the W3C's alt decision tree:
-
Is the image purely decorative, or is everything it shows already said in the text next to it? Use an empty alt attribute (
alt="") so screen readers skip it. Do not leave the attribute out. - Does it contain text, such as a screenshot of a heading or a quote card? The alt text repeats that text.
- Does it show a chart or data? State the takeaway ("Bar chart: organic visits doubled between January and June") and give the full figures in the body or a table.
- Otherwise: describe what it shows, in one sentence, specifically.
Google's own examples make the point well: alt="puppy" is better than nothing, but alt="Dalmatian puppy playing fetch" is best. For a blog that might mean "Search Console performance report filtered to one blog post" rather than "SEO".
Do not stuff keywords into alt text. Google's image guidance explicitly says to avoid filling alt attributes with keywords. It makes the page worse for the people alt text is for, and it does not help rankings.
File Names, Captions and Placement
-
File names: short and descriptive. Google gives the example that
my-new-black-kitten.jpgis better thanIMG00023.JPG. Rename before uploading; most CMSs keep the original name in the URL. - Placement: put each image beside the text it illustrates. Google's guidance asks for images to be placed near relevant text, and readers expect it too.
- Captions: use them when the image needs context, a date or a source credit. A caption that states the point of a chart saves the reader working it out.
- Charts and screenshots: check they are legible on a phone. If the labels are unreadable at mobile width, crop tighter or redraw.
Licensing: Keep a Record
Every image needs a clear right to use it. Your own photos and screenshots are simplest. For stock and free-image libraries, read the licence for each site (terms differ on commercial use, attribution and editing) and keep a note of the source page and licence with each image. Never use an image just because it appears in image search results; that is how businesses receive invoices from rights holders years later.
A Pre-Publish Image Checklist
- Every image passes the job test.
- Exported at no more than twice its display width; file size checked.
- WebP or AVIF where supported; SVG for diagrams and logos.
- Featured image not lazy-loaded; lower images lazy-loaded.
- Alt text written using the decision rule; empty alt on decorative images.
- Descriptive file names; images next to the text they illustrate.
- Licence source recorded.
- Charts and screenshots checked on a phone.
Images are one part of on-page optimisation; the rest is covered in how to optimise blog posts for SEO, and if a diagram is doing the explaining, making technical content easy to understand has advice on when one helps. Add this checklist to your final editing pass so it happens every time. And if you would like a specialist to check images, headings and metadata across existing posts, that is part of our on-page SEO service.
Questions
Questions about this article
Still unsure about something? Talk to a specialist — no script, no sales pitch.
Export each image at its display width, or up to twice that width for sharpness on high-density screens. If your content column is 800 pixels wide, an export of around 1,600 pixels is plenty. Anything larger adds download weight without visible benefit. Let your CMS generate smaller versions for phones using responsive image markup.
Usually, yes. WebP files are generally smaller than JPEGs at similar visual quality, which speeds up pages, and all major modern browsers support the format. AVIF can be smaller still but takes longer to encode and needs support from your CMS or CDN. Keep JPEG as a fallback only if your platform requires it.
It helps search engines understand what an image shows, which can help it appear in image search, but its main job is accessibility for people using screen readers. Write a specific, accurate description of the image. Google advises against filling alt attributes with keywords, and doing so makes the text less useful to the people who rely on it.
As many as do a job and no more. A how-to post may need a screenshot for each step, while an opinion piece may need only one. Orbit Media's 2026 blogger survey found bloggers using two to three visuals per post were most likely to report strong results, but that is a correlation, not a rule.
Lazy-load images that appear below the first screen, because it saves bandwidth and speeds up the initial load. Do not lazy-load the featured image or anything visible as soon as the page opens, because it delays the Largest Contentful Paint measurement that Google uses as part of its Core Web Vitals.