Skip to content

max-image-preview and max-video-preview: values and effects

What max-image-preview (none, standard, large) and max-video-preview (seconds, 0, -1) do in Google and Bing, the defaults, Discover and how to set them.

By Crawlito · 8 min read

In short

  • max-image-preview takes none, standard or large; if you leave it out, Google may show an image preview of the default size, not a large one.
  • Google Discover's guidance recommends images at least 1200 px wide, enabled by max-image-preview:large or by using AMP.
  • max-video-preview takes a number of seconds: 0 allows at most a static image, -1 means no limit, and Google ignores the rule if the number cannot be parsed.
  • Google's AI features documentation names nosnippet, data-nosnippet, max-snippet and noindex as its controls; it does not list either preview rule.
  • Bing documents the same three image values and the same 0 and -1 video values, and accepts them in a robots meta tag or an X-Robots-Tag header.
On this page

max-image-preview sets how large an image preview a search engine may show for a page: none, standard or large. max-video-preview sets how many seconds of a video may play as a preview: a number, with 0 meaning a static image at most and -1 meaning no limit. Both go in a robots meta tag or an X-Robots-Tag header. If you set neither, Google may show a default-size image and decides the video preview length itself, so a non-AMP site that wants large image previews, including in Discover, has to add max-image-preview:large on purpose.

This post covers the two preview rules in detail. For the text controls that decide what AI Overviews and AI Mode may use (nosnippet, max-snippet, data-nosnippet), see noindex, nosnippet and X-Robots-Tag for AI search.

What max-image-preview does and which value to use

Google's robots meta tag documentation defines the rule as the maximum size of an image preview for the page in search results, and says it applies to all forms of search results, naming Google web search, Google Images, Discover and Assistant.

ValueGoogleBing
noneNo image preview is shownBing will not show an image preview
standardA default-size preview may be shownBing may show a standard size image
largeA larger preview, up to the width of the viewport, may be shownBing may show a standard or a large size optimized image
Rule absentGoogle may show a preview of the default sizeNot documented

The Bing column comes from Bing's announcement of these controls, which also says Bing treats them as directives, not hints.

The words "may be shown" matter. large is permission, not a request: the search engine still chooses whether to show an image at all and which one. It does not pick the image either. If Google shows the wrong picture for a page, the cause is usually elsewhere, as covered in why Google shows the wrong image for your page.

For most sites the choice is simple:

  • large for articles, recipes, product pages and anything where a big image helps a searcher decide to click. This is also what Discover recommends.
  • standard if you license images and do not want them shown at full width, or if you want to avoid the larger thumbnails that Google says can come from AMP or canonical article versions.
  • none for pages where any image preview is unwanted, such as images of people shown with consent for one context only.
html
<meta name="robots" content="max-image-preview:large">

The Discover large-image requirement

Google's Discover documentation recommends large, high-quality images that are at least 1200 px wide and enabled by the max-image-preview:large setting, or by using AMP. The same list recommends more than 300,000 total pixels and a 16x9 aspect ratio, and the page says Google tries to crop images automatically for use in Discover.

So a page with no max-image-preview rule, or with standard, is limited to the default preview size wherever Google honours the rule, and Discover is one of the surfaces Google lists. A non-AMP article that never sets large is the common case.

Discover also uses the image you point to. Google says to use schema.org markup or the og:image meta tag to specify a large, representative image, and to avoid generic images such as your site logo or text-heavy images there. The rule and the image work together:

html
<meta name="robots" content="max-image-preview:large">
<meta property="og:image" content="https://www.example.com/images/harbour-1600x900.jpg">

If you use AMP and want to keep Discover thumbnails small, Google's robots meta page says to set max-image-preview to standard or none.

What max-video-preview does: seconds, 0 and -1

max-video-preview:[number] tells Google to use at most that many seconds as a video snippet for videos on the page. Google's video best practices say Google selects a few seconds of a video to show a moving preview, and that you can set the maximum duration with this rule.

ValueGoogleBing
A positive number, such as 15At most that many secondsAt most that many seconds (an integer)
0At most a static image, following the max-image-preview settingBing may show a static image of the video
-1No limitAny preview length allowed
Rule absentGoogle may show a video snippet and decides how longNot documented
No parseable numberThe rule is ignoredNot documented

Two details catch people out:

  • 0 hands control to the image rule. With max-video-preview:0, max-image-preview:none, Google is told there should be no moving preview and no image preview. If you only want to stop the moving preview, pair 0 with standard or large.
  • A rule Google cannot parse is ignored, not treated as zero. Google says the rule is ignored if no parseable number is given, so a typo leaves you with Google's default behaviour. Use a plain integer.

A video preview also needs the video itself. Google says it must be able to fetch the actual bytes of the video file to enable features like video previews, and warns against blocking the video file URL with noindex or robots.txt. If the preview never appears, check the file and the watch page before the meta tag, as in video not indexed: test the watch page and thumbnail.

html
<!-- Up to 20 seconds of moving preview, large still image -->
<meta name="robots" content="max-video-preview:20, max-image-preview:large">

How the preview rules relate to nosnippet and max-snippet

The three max- rules control different things, and Google keeps them separate. Its documentation says max-snippet does not affect image or video previews.

RuleControlsEffect on images and video
max-snippet:[n]Length of the text snippet, and how much content AI Overviews and AI Mode may use as direct inputNone, by Google's documentation
max-image-preview:[value]Size of the image previewSets the image size
max-video-preview:[n]Seconds of video previewSets the video length
nosnippetNo text snippet or video preview; content not used as direct input for AI Overviews and AI ModeNo video preview; Google says a static image thumbnail may still be visible

That last row is the one to remember. nosnippet removes the video preview but not necessarily the still image, because Google says a static thumbnail may still appear when that is a better experience. To remove the image too, add max-image-preview:none.

When rules conflict, Google applies the more restrictive one. So a page with max-video-preview:-1 and nosnippet should get no video preview, because nosnippet is the stricter rule.

Google's robots meta page also says a publisher who has separately granted permission for content use, for example through in-page structured data or a license agreement with Google, keeps those more specific uses: the max-image-preview limit does not interrupt them.

What these rules mean for AI features

Google's AI features documentation says that to limit the information shown from your pages in Search, you use nosnippet, data-nosnippet, max-snippet or noindex. It does not list max-image-preview or max-video-preview, and the robots meta page attaches its AI Overviews and AI Mode wording only to nosnippet and max-snippet. At the time of writing, Google does not document how the two preview rules affect images or video in AI Overviews or AI Mode, so do not rely on them as an AI control. The wider eligibility picture is in Google AI Overviews: the technical requirements.

Bing's October 2025 data-nosnippet announcement lists the three max- rules as limits on the size or duration of preview content. It does not say whether they apply to Copilot answers.

At the time of writing, the crawler documentation from OpenAI, Anthropic and Perplexity covers robots.txt and does not mention either rule.

How to set the rules in a meta tag or X-Robots-Tag

Rules can be combined in one comma-separated list or split across several meta tags. Google says rule names and values are case-insensitive.

html
<!-- All crawlers that read robots meta tags -->
<meta name="robots" content="max-image-preview:large, max-video-preview:-1">

<!-- Google only -->
<meta name="googlebot" content="max-video-preview:10">

For images, videos and other files with no HTML head, send the same rules as a header. A rule without a user agent prefix applies to all crawlers:

http
HTTP/2 200
content-type: text/html; charset=utf-8
x-robots-tag: max-image-preview:large, max-video-preview:-1

In nginx, for every response from a location (add_header is not limited to HTML):

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

The server set-up for Apache, Cloudflare and Vercel is in the X-Robots-Tag guide. As with every robots rule, a crawler blocked by robots.txt never fetches the URL, so it never sees the tag or header.

WordPress already adds one

WordPress 5.7 and later add max-image-preview:large to sites that allow search engine indexing, through its Robots API. When "Discourage search engines from indexing this site" is on, WordPress outputs noindex, nofollow instead and leaves the directive out. To remove it in a theme or plugin:

php
remove_filter( 'wp_robots', 'wp_robots_max_image_preview_large' );

SEO plugins can output their own robots tag as well, so check the final HTML rather than the settings screen.

How to check what a page sends

Look at both places a rule can live, because a header and a meta tag both count and the more restrictive one wins.

bash
URL="https://www.example.com/article"

# Header rules
curl -sI "$URL" | grep -i '^x-robots-tag'

# Meta tag rules in the raw HTML
curl -s "$URL" | grep -Eio '<meta[^>]*name="(robots|googlebot)"[^>]*>'

Then check for these common mistakes:

  1. Two tags that disagree. A theme outputs max-image-preview:large and a plugin outputs max-image-preview:standard. Google applies the more restrictive value, so the page is limited to standard.
  2. A typo in the video value. Anything that is not a parseable number makes Google ignore max-video-preview.
  3. The rule set only by JavaScript. If the tag is injected after load, check the rendered HTML in Search Console's URL Inspection tool as well as the raw response.
  4. nosnippet left on article templates. It removes video previews and text snippets, and it also keeps the content from being used as direct input for AI Overviews and AI Mode.

Frequently asked questions

Is max-image-preview:large required for Google Discover?

Google's Discover guidance recommends images at least 1200 px wide that are enabled by max-image-preview:large or by using AMP. Without either, Google may show only a default-size preview.

What happens if I set max-video-preview:0?

Google will show at most a static image, following your max-image-preview setting, and no moving preview. Bing says it may show a static image of the video.

Does max-image-preview control images in AI Overviews?

Google does not document that. Its AI features page lists nosnippet, data-nosnippet, max-snippet and noindex as the controls, not the image or video preview rules.

Does max-snippet limit image or video previews?

No. Google's documentation says max-snippet does not affect image or video previews. Use max-image-preview and max-video-preview for those.

Does Bing support these rules?

Yes. Bing documents none, standard and large for images and seconds, 0 and -1 for video, in a robots meta tag or an X-Robots-Tag header.

Check the rules your pages really send

Templates, plugins and CDN rules can each add a robots tag, and the most restrictive one is what counts. After running the curl commands above, use the free check on an article or product page as a next step: it needs no account and shows whether the main AI crawlers can reach and read that page.

Filed under Access and robots.txt. Topics: meta-robots, google, images, video, bingbot