Makey Updates

A practical guide to better images in blog posts

Best practices for using images in blog posts are less about decoration and more about helping readers understand, trust and act. A relevant featured image can establish the subject, a diagram can simplify a technical idea, and an original screenshot can prove that a tutorial works. Used with purpose, visual content adds clarity without pulling attention away from the words.

Images also shape how a post feels on every device. Australian readers often arrive through search on a phone, sometimes while commuting across Sydney or Melbourne, so sharp graphics and sensible file sizes matter. The aim is a consistent visual story that remains clear, quick and accessible when the connection is unreliable and the screen is small.

Choose the right image for each job

Start with the job the image must do, then choose a format that preserves it. Photography benefits from efficient compression, diagrams need legible text, and interface captures need crisp edges. These starting points keep production simple while preventing a decorative file from slowing the whole article.

Image role Recommended export Useful starting size Main benefit
Hero or featured banner WebP with JPEG fallback 1600 × 900 px Strong desktop crop with broad compatibility
Article photograph WebP or compressed JPEG 1200–1600 px wide Small file while retaining natural detail
Tutorial screenshot PNG or lossless WebP Up to 1200 px wide Crisp labels and interface elements
Infographic or chart WebP or PNG 1200 × 1500 px Vertical space for mobile reading
Logo or simple icon SVG with PNG fallback 512 × 512 px Scalability and clean edges

Keep the highest-quality source file, but do not upload it directly. Produce variants for the places the image will appear, and check that crops still make sense. A 16:9 hero can work on a desktop, while a taller crop may be needed for a mobile card; one master asset cannot cover every placement without compromise.

Plan for Australian readers and local moments

Australian seasonality should shape your visual calendar. December and January are summer here, so a travel feature set in June should show a winter scene rather than snowy streets copied from a northern-hemisphere campaign. Local events also create useful visual opportunities: Melbourne Fashion Week may suit a style guide, while a Sydney Harbour Festival preview can support a city guide, provided the images are original or properly licensed.

Localise the words inside and around the image too. Use Australian English such as “colour”, “favourite” and “organisation” in captions and alt text. For commercial posts aimed at the Australian market, show prices in AUD and use day-month-year dates when confusion is possible. These details make the visual message feel native rather than translated or imported.

Compress and resize for real-world connections

Large media files are a common cause of slow pages. Compress photographs before export, strip unnecessary metadata, and serve modern formats such as WebP or AVIF with a suitable fallback. Use the quality setting that keeps edges and colours clean; repeated recompression can make screenshots look fuzzy. Check the largest file on the post before publishing, because it often sets the experience for readers on mobile data.

Responsive images reduce that burden further. Add width and height attributes to prevent layout shifts, provide alternate sizes with srcset, and let the browser select an appropriate file. Lazy-load images below the first screen, but avoid lazy-loading a featured image that should appear immediately. A content delivery network can also serve cached assets from suitable locations, helping regional Australian readers whose fixed-line connections may be shared by an entire household.

Add descriptions that make images useful

Alternative text should describe the information conveyed by an image, not repeat a keyword list. For example, alt text reading “Orange tram passing Flinders Street Station in Melbourne” helps a screen-reader user understand the scene. Keep it concise, use Australian English, and mention the subject when it adds meaning. If an image is purely decorative, use an empty alt attribute so assistive technology can skip it.

Captions belong when they add context, such as a source, date or instruction. Do not hide essential instructions inside an image, because embedded text cannot reflow or be read reliably by everyone. Maintain strong contrast between labels and backgrounds, avoid conveying meaning through colour alone, and test the final page with a keyboard and at 200% zoom. These practices align with WCAG 2.2 AA guidance.

Protect rights and maintain visual consistency

Record the source and licence for every visual asset. Unsplash, Pexels, Canva and similar platforms may offer suitable licences, but the exact terms still need checking, and visible credits may be required. Creative Commons images also have conditions around attribution, modification and commercial use. For original photographs, retain the licence or model release. Screenshots can raise separate copyright or trade-mark questions, so use only what the tutorial or commentary requires.

A small asset library prevents inconsistent images from reaching the blog. Name files descriptively, organise originals separately from exports, and save the caption, alt text, licence and target dimensions with each asset. A Canva template can give a small business a recognisable colour palette and reliable logo placement, but a single master design is safer than rebuilding every social post from scratch. Clear rules also make seasonal updates faster.

Publish images for search and social discovery

Images become easier to discover when the surrounding signals are complete. Use a descriptive file name, relevant alt text, nearby keyword-rich copy and an internal link with a natural anchor. Add images to an image sitemap, reference the canonical page, and check that the original file is indexed instead of a low-resolution copy. Structured data can identify photographs, but the markup should describe visible content accurately.

Social sharing needs separate preparation. Export a correctly cropped Open Graph image, confirm the page title and description, and preview the result for LinkedIn and other channels where your audience spends time. When images support a broader publishing system, the approach in this visual content strategy can help connect assets to a defined content purpose. Reuse the strongest image without changing its meaning in a way that breaks the context.

A practical checklist for stronger visual content

Use a short, repeatable sequence before each post goes live. It catches speed, access and rights issues while changes are still inexpensive.

Start with one existing article today: check its largest image, alt text, crop and mobile rendering, then publish the corrected version. Record the page-speed result and apply the same checklist to the next post, creating a visual workflow that improves with every publication.