Max-Image-Preview: Large: What It Means and How to Add It

max-image-preview:large is a robots directive that gives search engines permission to use a larger image preview for a page. In Google, large allows a preview up to the width of the viewport, but it does not guarantee that Google will show a preview, select a particular image, or use the largest rendering.

What does max-image-preview:large mean?

The directive sets the maximum image-preview size a search engine may use for the page. Google supports three values:

Value	What it allows	Typical use
`none`	No image preview	When previews must be suppressed
`standard`	A default-size image preview	When normal previews are acceptable
`large`	A larger preview, up to the viewport width	When publishers want to permit prominent previews

If you omit the rule, Google may apply its default image-preview behavior. The setting can affect Google Search, Google Images, Discover, Assistant, and other search-result formats listed in Google’s documentation. A separate, more specific permission, such as qualifying structured data or a licensing agreement, can allow uses that are not interrupted by this setting. See Google’s robots meta-tag documentation.

How to add max-image-preview:large

Option 1: HTML robots meta tag

Place this element in the <head> of the HTML document:

<meta name="robots" content="max-image-preview:large">

The crawler must be able to fetch the page and read its <head>. A blocked page, inaccessible response, or implementation that is only added after crawler processing cannot reliably communicate the directive.

Combine it with other robots controls

Separate directives can share one content attribute, separated by commas:

<meta name="robots" content="max-snippet:20, max-image-preview:large">

Keep each directive valid and avoid conflicting tags. If multiple robots meta tags or headers exist, audit the final response so your intended policy is clear.

Option 2: X-Robots-Tag HTTP response header

You can send the equivalent policy in the HTTP response:

X-Robots-Tag: max-image-preview:large

Example Apache configuration:

<IfModule mod_headers.c>
  Header set X-Robots-Tag "max-image-preview:large"
</IfModule>

Example Nginx configuration:

location / {
    add_header X-Robots-Tag "max-image-preview:large" always;
}

Use the header when you need one policy across server-rendered pages or non-HTML responses. Confirm that your CDN, reverse proxy, and application do not remove or overwrite it.

Option 3: WordPress

WordPress includes wp_robots_max_image_preview_large(), introduced in WordPress 5.7.0, which adds the directive when the site is public. A theme or plugin can register it with the robots filter if a custom setup has disabled the default behavior:

add_filter('wp_robots', function ($robots) {
    return wp_robots_max_image_preview_large($robots);
});

Check the generated page source and the HTTP response after changing SEO plugins or privacy settings. A private, discouraged, or noindex site may intentionally omit the rule.

Does it make Google show a large image?

No. It is permission for a maximum size, not a command to display a large image. Google’s wording says a larger preview “may be shown.” Search systems still decide whether to show an image, which image to select, and how it is rendered.

For the directive to help, make the page and image crawlable, return successful responses, avoid accidental blocks in robots.txt or authentication, and provide an image that is relevant to the page. The directive cannot override a page that crawlers cannot access.

Does Bing support max-image-preview?

Bing documents support for the robots meta tag and X-Robots-Tag. Its description of large permits a standard or large optimized image. Implement the directive in the HTML tag or response header, then verify the actual response reaching Bingbot. See Bing’s robots directives documentation.

Implementation checklist

Choose large only if large previews are acceptable for your content.
Add either the HTML meta tag or the X-Robots-Tag header.
Use valid comma-separated syntax when combining directives.
Ensure crawlers can fetch the page and read the directive.
Check canonical, redirect, CDN, and cache responses for consistency.
Confirm that important images are publicly reachable and relevant.
Inspect the rendered source and response headers after deployment.

Common errors and fixes

Symptom	Likely cause	Fix
No directive appears in source	Template, SEO plugin, or privacy mode removed it	Inspect the final HTML and enable or add the directive at the active template layer.
Header is missing	CDN or proxy strips response headers	Check the origin and public response separately; configure the last proxy to preserve `X-Robots-Tag`.
Large preview does not appear	The directive only sets a maximum; search presentation is discretionary	Verify crawlability and image relevance, then allow time for recrawling.
Conflicting robots rules	Multiple tags or headers contain different values	Remove duplicates and keep one intentional policy for the page.
Works on HTML but not generated routes	Some responses use a different server or cache rule	Test representative URLs, redirects, and cached variants.
WordPress helper has no effect	Site is not public or another filter changes the robots array	Review visibility settings and inspect the final `robots` meta output.

Performance, reliability, and cost considerations

The directive itself adds negligible response size and no client-side work. The operational concern is consistency: a cached HTML document and its origin response should expose the same policy. Test after deploys, theme changes, SEO-plugin updates, and CDN rule changes.

There is no charge from Google or Bing for adding this directive. Image delivery, crawling, and any screenshot or rendering service you use are separate concerns. If you generate previews for QA or documentation, capture only the pages and states you need, cache stable URLs, and retry transient timeouts with a bounded backoff.

Or skip the browser setup

If you need a rendered image of a page that contains this directive, ScreenshotNeo returns a screenshot or PDF with one GET request. Before capture it accepts cookie or consent banners and removes more than 60 known consent platforms, newsletter popups, and chat widgets; each step can be turned off. Bot checks, blank pages, timeouts, failed loads, and cache hits are not billed, and the response identifies the result with X-Page-Verdict and X-Billed headers. An MCP server provides take_screenshot, get_page_info, and capture_pdf tools for Claude, Cursor, and other MCP clients.

See the ScreenshotNeo API documentation for all options.

curl -G "https://api.screenshotneo.com/v1/shot" -d access_key=YOUR_API_KEY --data-urlencode url=https://stripe.com -o shot.webp

import requests
r = requests.get("https://api.screenshotneo.com/v1/shot", params={"access_key": "YOUR_API_KEY", "url": "https://stripe.com"}, timeout=90)
open("shot.webp", "wb").write(r.content)

const q = new URLSearchParams({ access_key: 'YOUR_API_KEY', url: 'https://stripe.com' });
const res = await fetch(`https://api.screenshotneo.com/v1/shot?${q}`);

Features include full-page and element captures, dark mode, device presets, retina scale, custom CSS and JavaScript, waits, request blocking, custom headers and cookies, timezone and geolocation, transparent backgrounds, resizing, caching with a chosen TTL, signed links, asynchronous jobs, bulk capture, usage reporting, and PDF output. Every feature is included on every plan. The free plan includes 1,000 shots per month with no card; paid plans start at $5 for 3,000 shots.

Create a free ScreenshotNeo account and get 1,000 screenshots a month with no card.

FAQ

Should every page use `large`?

Use it when your publishing policy permits larger previews. It is optional, and standard or none may be better for restricted content.

Can I use both the meta tag and the header?

Yes, but keep them consistent. Duplicate or conflicting policies make audits harder.

Does the directive choose my Open Graph image?

No. Open Graph metadata and this robots directive serve different purposes. The directive controls the maximum search preview size.

Will changing the directive update results immediately?

No. Search engines need to recrawl the page, and they still choose how to present each result.