Key takeaway
Keep website images sharp and fast by separating lossless source archives from web-ready derivatives: serve WebP/AVIF with fallbacks, multi-width srcset, preserved aspect ratios, content-hashed cache filenames, and functional bilingual alt text across all six image categories.

Website image delivery tends to fail at one of two extremes: either teams upload a 12 MB camera original that stalls mobile browsers, or someone saves a chat-compressed screenshot and exports a transparent product cutout as a JPEG, leaving an ugly white rectangle on a blue card and unreadable labels.
Keeping images both crisp and fast does not come from nudging export sliders right before launch. It requires splitting source archiving from web derivative delivery: store lossless masters in your archive, and ship only modern-format, multi-width, aspect-preserved, content-hashed derivatives with disciplined alt text to live pages.
Two-Stage Pipeline: Separate Source Archiving from Web Derivatives
- Retain the master
- Create suitable dimensions
- Load for the placement
- Check alternatives and clarity
Visuals degrade over time when storing a master asset and exporting for the web overwrite the same file. Once a banner is saved at 600 px wide, future layouts cannot recover the detail.
- Stage 1: Source Archiving (Never Linked Live). Keep camera RAWs, lossless transparent master PNGs, layered design files, and editable SVG sources in a read-only archive. For team-wide folder governance and licensing ledgers, see our guide on building an enterprise media asset library. At web handoff, masters simply need full resolution and readable names (
product-flowmeter-master.png, neverIMG_1043). - Stage 2: Web Delivery Derivatives (Built for Transport). Generate public assets through build scripts, tools like
sharpor ImageMagick, or an automated image service. As shown on web.dev's Serve responsive images guide, sending desktop-sized images to mobile phones wastes 2–4x more data than needed; when a page's Largest Contentful Paint (LCP) element is an image, proper sizing reduces resource load duration and eases bandwidth contention.
Enforce three rules at the delivery layer:
- Modern Formats with Fallbacks: Per Google Image SEO best practices, Google Search supports BMP, GIF, JPEG, PNG, WebP, SVG, and AVIF inside HTML
<img>elements (including<picture>fallbacks), with file extensions matching actual formats. Serve WebP or AVIF first via<picture>or server negotiation while retaining a fallback<img>src. - Multi-Width
srcsetandsizes: Following web.dev's baseline, export 3–5 width variants per large photo or visual (for example,480w,800w,1200w, and1600win a hypothetical template), pairingwdescriptors insrcsetwith CSS units likepx,vw, orcalc(...)insizes(percentages like25%are invalid insizes). - Reserved Aspect Ratios and Hashed Caching: Declare intrinsic dimensions or fixed aspect boxes to prevent layout shifts. Append content hashes to derivatives (
product-flowmeter-800w-c387d6ef.webp) for safe long-term caching, while keeping one stable URL for shared sitewide icons so browsers and crawlers reuse the cached file.
Delivery Specifications Across Six Website Image Categories
Different image slots solve different communication tasks and cannot share one export preset:
1. Logos and Vector Icons
Export geometric marks and navigation icons as cleaned SVGs with trimmed artboards and collapsed paths for sharp rendering at any pixel density, reusing one URL sitewide. Generate transparent PNGs only where legacy slots such as favicons require bitmaps.
2. Transparent Concept Graphics and Product Cutouts
Graphics floating over blue cards or gradients must never be saved as JPEG, which strips transparency into a solid box. Export alpha WebP or AVIF (with PNG fallback), check edges against both light and dark surfaces, and keep inner padding so drop shadows never clip flat at the canvas edge.
3. 16:9 Covers and Social Share Previews
Article covers start in 16:9, yet grids and link previews frequently crop toward 1.91:1, 4:3, or 1:1 squares. Keep primary subjects inside a centered safe crop zone. Per Google's image SEO guidance, pick a high-resolution, page-representative og:image and structured-data image, avoiding generic site logos, text-heavy overlays, or extreme aspect ratios—and do not lazy-load your primary hero image.
4. In-Article UI Screenshots and Diagrams
Never force software captures or diagrams into cropped 16:9 banners or blurry JPEGs. Preserve native aspect ratios, export lossless or high-fidelity WebP/PNG (or SVG for crisp flowcharts), add click-to-zoom for dense UI views, and mirror key metrics or steps in readable HTML prose or tables.
5. Product and On-Site Photography
Archive full-resolution photos and export lossy high-quality WebP or AVIF across 3–5 widths for srcset, stripping unnecessary camera metadata before upload. When wide shots shrink into illegible mobile thumbnails, use <picture> media queries for art direction (as web.dev outlines) to deliver a focused mobile crop.
6. Background Textures and Decorative Visuals
Prefer lightweight CSS gradients or subtle vector patterns that preserve foreground text contrast. Since Google does not index CSS background-image assets, never hide meaningful product visuals in CSS backgrounds—while pure decoration fits cleanly in CSS or as an <img> with alt="".
Corporate Website Image Delivery Specification Table
Category | Source Archive | Web Format & Alpha | Ratio & Responsive Rules | Loading & Caching | |
|---|---|---|---|---|---|
Logos & Vector Icons | Editable SVG master | SVG first (small transparent PNG only if needed) | Trimmed artboard, consistent padding | Single shared URL; avoid bloated inline SVGs | Brand name for logo; |
Transparent Cutouts & Graphics | Transparent PNG or layered source | Alpha WebP / AVIF (PNG fallback); no JPEG | Export for max slot density; shadow padding | Content-hashed long cache; hero non-lazy | Brief contextual description of object |
16:9 Covers & Previews | 16:9 lossless master | WebP / AVIF + JPEG/PNG fallback | Focal subject inside centered 4:3–1:1 safe zone | Card | One sentence linking cover scene to topic |
Screenshots & Diagrams | Full-res UI capture or vector | Lossless/high-fidelity WebP or PNG; SVG charts | Preserve native aspect ratio; click-to-zoom | Below-fold loading; data mirrored in HTML | Brief summary + adjacent HTML data text |
Product & On-Site Photos | RAW or high-res master | WebP / AVIF + JPEG fallback (strip EXIF bloat) | 3–5 width variants ( | Never send desktop sizes to mobile; Lighthouse audit | Concrete model/scene; zero keyword stuffing |
Backgrounds & Decoration | Vector pattern or texture | CSS gradient preferred; compact WebP | Small byte footprint; verify text contrast | Never put meaningful visuals in CSS backgrounds | Explicit |
Writing Disciplined alt Text by Image Function
- Primary above-the-fold image
- Discover and load early
- Images later in the article
- Load when needed
Set priority from the actual first-screen element and page purpose; do not preload every image.
Following the W3C WAI alt Decision Tree and Google Image SEO best practices, write alt text by image function rather than stuffing terms:
- Informative Photos & Graphics: State what the visual shows in context concisely (e.g., in a hypothetical page:
alt="Stainless-steel electromagnetic flowmeter with flanged end connections"), never stuffing keywords (alt="flowmeter industrial flowmeter china price"). - Complex Charts & Diagrams: Keep
altshort to name the graphic and place full figures, labels, or steps in adjacent HTML text or tables. - Functional Link/Button Icons: Without visible label text, describe the action or destination (
alt="Download PDF datasheet"), not the icon's appearance. - Text in Images & Inline SVGs: Use web fonts and HTML for copy; where non-decorative image text has no HTML equivalent, copy it into
alt. Pair meaningful inline<svg>elements with<title>andaria-labelledby. - Decorative or Redundant Images: Set an explicit
alt=""instead of omittingalt(omitting it causes screen readers to read raw filenames). - Bilingual Separation: Write Chinese
alton/zh/...and natural Englishalton/en/..., exporting separate localized files when screenshots display UI text.
How This Site Separates Image Masters from Delivery Files
For this batch of articles, design masters stay in the project and the site delivers separately compressed WebP covers. The main file is 1400 × 788 pixels; the CMS also maintains sharing and administration thumbnail sizes. Needing a cover on a page does not mean sending the design master unchanged to the browser.
Both languages share the image, with separate alternative text describing its relationship to the article. Compare the themes in the article list. This illustrates the separate responsibilities of masters, delivery files and localized text; an image format alone guarantees neither load speed nor rankings.
Website Image Ingestion & Delivery Checklist
Copy this checklist into design handoffs or CMS workflows before publishing (pair it with our Website Project Preparation Checklist during early asset collection):
[Website Image Delivery Checklist — Example Slug: product-flowmeter-cutout]
1. Source Archive & Naming
- [ ] Lossless original, transparent master, or SVG saved in internal archive (never linked live)
- [ ] Short, descriptive, lowercase hyphenated filename matching actual format; localized screenshots exported separately for `/zh` and `/en`
2. Format, Transparency & Crop Zones
- [ ] Logos/icons cleaned SVGs; transparent graphics exported as alpha WebP/AVIF (PNG fallback, no JPEG) with clean light/dark edges
- [ ] 16:9 covers and social previews center focal subjects inside the safe zone without logos or dense text
- [ ] In-article screenshots and diagrams keep native aspect ratios uncropped, stay crisp, and support click-to-zoom if dense
3. Responsive Widths, Loading & Caching
- [ ] Photos and large visuals include 3–5 `srcset` widths with non-percentage `sizes`, fixed aspect containers, and non-lazy hero LCP loading
- [ ] Shared icons reuse one URL; long immutable cache headers apply only to content-hashed derivatives
4. Alt Text & Audit
- [ ] Every `<img>` carries an `alt` attribute (concise informative text without stuffing, or `alt=""` for decoration); chart figures live in HTML text/tables
- [ ] Desktop and mobile rendering verified in devtools and Lighthouse's "Properly size images" auditSeparating source archiving from web derivative exports stops teams from degrading visuals across edits or stalling mobile visitors. When planning a bilingual redesign or media workflow, explore our Corporate Website & Standalone Site Services or bring your current image inventory to a consultation.