Google Discover Image Size: 1200x675 vs 1280x720

Google Discover needs images that are at least 1200 pixels wide and allowed to appear as large previews. In practice, 1200x675 is the lean production standard, while 1280x720 gives you more crop room for social reuse and higher-density screens.

Discover does not rank a page only because the image is big, but undersized artwork removes you from the best card treatment immediately. Once a publishing team accepts that rule, image sizing becomes an editorial systems problem rather than a design preference.

That is why the broader Google Discover image optimization guide should sit next to your design checklist. Size, crop safety, the max-image-preview:large tag, and a strong featured image layout work together, not in isolation.

The decision is less about a secret ranking boost and more about production convenience. Both dimensions are 16:9, both clear the minimum width rule, and both can support a strong Discover card when compression and subject framing are handled well.

• Choose 1200x675 when you want the smallest dependable asset for publishing speed and do not expect major post-publish crops.
• Choose 1280x720 when your design team wants extra room for text-safe padding, social reuse, or future derivatives without reopening the source file.
• Avoid switching ratios between posts because that creates inconsistent templates, confusing QA, and accidental subject cropping.
• Keep the main subject centered enough that either export still reads clearly inside a narrow mobile card.

A dependable workflow is more valuable than the dimension debate itself. The goal is to reduce variation between writers, designers, and publishers so every article gets a valid image without a last-minute scramble.

1. Design the source image on a 16:9 artboard so you do not have to guess the crop later.
2. Reserve the center third for the key subject and keep logos or small text away from the outer edges.
3. Export one master image at 1280x720 or larger, then create the production derivative with DiscoverImg.
4. Compress the file, check the preview, and publish only after the image still looks strong on mobile.

Most Discover image problems are not dramatic failures. They are small process mistakes that compound across a publishing calendar until the visual standard drifts downward.

• Publishing exactly 1200px wide but then letting the CMS generate a blurry, lower-quality derivative.
• Adding tiny text overlays that become unreadable or visually noisy once the card shrinks on mobile.
• Using a perfect size but forgetting the robots directive that allows large previews.
• Treating social image rules and Discover image rules as separate universes instead of building one reusable template.

Inside DiscoverImg, the easiest way to operationalize this is to upload the original asset, verify that the width clears 1200px, and then preview the card before download. That matters more than chasing theoretical pixel wins that do not survive compression or poor composition.

For most teams, the next useful reads are the WebP format guide and the og:image guide. Together they help you ship one featured image that works for Discover, social previews, and page speed. When the asset is ready, send it through DiscoverImg Optimizer before publishing.