Image Optimization vs Alt Text: What AI Agents Actually Read on Your Page

The Decision #

Half the web's bytes are images Source 2, but the agents now hitting your pages — Claude, ChatGPT, agentic shoppers, coding assistants — consume tokens, not pixels Source 9. The choice between optimizing image bytes and optimizing image text is no longer about accessibility versus performance; it's about who your traffic actually is.

The Table #

| Dimension | A: Byte-level optimization (`next/image` , WebP/AVIF, CDN s) |
B: Text-level optimization (alt text, captions, structured metadata) |
|---|---|---|

| Latency | Cuts LCP — next/image auto-serves WebP, lazy-loads, sets width/height to prevent CLS | Zero render impact; agents read HTML, not pixels | | Memory | sharp on glibc Linux can balloon without tuning |

alt

next start

; cloud s (Cloudinary, Imgix, Akamai) for static export [Source 7](#source-7)[Source 17](#source-17)`ai_image_alt_text`

module) [Source 5](#source-5)`dangerouslyAllowSVG`

is blocked [Source 4](#source-4); v16 caps`qualities`

to `[75]`

by default [Source 18](#source-18)[Source 10](#source-10); 8.5% end in`.jpg`

/.png

filenames Source 5I'd pick B as the default in 2026, and bolt A on top. Agents are the fastest-growing consumer of your HTML Source 11, and they cannot see your AVIF.

The Mechanism #

Why A (byte-level) wins when humans on bad networks dominate. The next/image

component serves device-correct WebP, prevents layout shift via intrinsic width/height, and lazy-loads off-screen images natively Source 3. On a flaky link, this matters: Kornel's observation that mobile bandwidth arrives in "laggy bursts rather than slowly" Source 20 means a 155 kB hero is a real LCP hit. Byte savings compound — Lara Hogan's point that images are "arguably the easiest big win" for page load time Source 2 still holds, and the v16 default of minimumCacheTTL: 14400

(4 hours, up from 60 s) reflects that revalidation cost was real money Source 18. Why B (text-level) wins when AI agents are reading your site. LLMs are next-token predictors over text Source 15. Even multimodal models tokenize images through a vision encoder + projector into the same latent space as text Source 1Source 1 — and IBM's own teams admit "text-ify everything" loses visual context Source 12, which is why hybrid multimodal RAG keeps text captions as the retrieval index even when the LLM can see the image Source 12. Translation: when an agent or RAG pipeline crawls your page, the alt

attribute is the image as far as retrieval is concerned. Docling's whole pitch for AI ingestion is converting unstructured assets into "clean, structured text that large language models can actually use" Source 13Source 14. The Web Almanac is blunt that ~50% of images ship with empty or sub-10-character alt text Source 10 — that's a silent retrieval failure on every agent-driven query. Pick B as the default.

The Migration Path #

If you optimized for bytes and now need agents to actually understand your pages: Audit alt coverage. Grep your codebase for<Image

and<img

and flag any whosealt

is empty, missing, or ends in.jpg

/.png

— the 8.5% filename-as-alt anti-patternSource 5.Replace filename alts with descriptive text. Target 20–30 characters, the band the Almanac flags as balancing brevity and signalSource 5. For decorative-only images,alt=""

is correct — don't pad.Co-locate machine-readable context. Addopengraph-image.tsx

per route for agent crawlers that follow OG metadataSource 16Source 19, and emit afigcaption near content images so RAG chunking captures the caption with the surrounding paragraphSource 13.Keep byte optimization, tighten its config. Stay onnext/image

withremotePatterns

locked downSource 6. If you're on Next 16, explicitly setqualities andimageSizes

if you need more than the new[75] default or the dropped16w

sizeSource 18.For SVG, use it. SVG carries semantic structure agents can parseSource 10, unlike raster — but if you serve user-uploaded SVG throughnext/image , you must setdangerouslyAllowSVG

with a strict CSP andcontentDispositionType: 'attachment'

Source 4.For RAG-targeted content, consider Docling. Convert PDFs/decks to structured Markdown so thetext representationof every embedded image survives ingestionSource 14.

CEMENT Brick #

If you ship a page tuned only for byte-level image optimization in 2026, then your fastest-growing class of visitors — AI agents and RAG crawlers — will retrieve a blank where your image was, because every LLM-backed reader still resolves images through their textual representation (alt, caption, surrounding chunk) before any vision encoder is consulted Source 1Source 12Source 12, and a missing or filename-shaped alt collapses to zero signal in the embedding space Source 5.

Sources #

What Are Vision Language Models? How AI Sees & Understands ImagesOptimizing Images | Designing for PerformanceImage OptimizationImage Legacy- Engineering Docs ImageHow to create a static export of your Next.js applicationHow to self-host your Next.js application- Engineering Docs

• Engineering Docs AI agents in 2025: Why agentic commerce isn't ready for Black Friday yetWhat is Multimodal RAG? Unlocking LLMs with Vector DatabasesUnlock Better RAG & AI Agents with DoclingWhat Is Docling? Transforming Unstructured Data for RAG and AIAI vs Human Thinking: How Large Language Models Really WorkMetadata and OG imagesimagesHow to upgrade to version 16opengraph-image and twitter-imageThe present and potential future of progressive image rendering