There is no single featured-image size that works for every website. Your theme and each image placement determine the crop and displayed dimensions. For Google Discover, Google’s current guidance is to use a relevant image at least 1,200 pixels wide and with more than 300,000 total pixels. Those are Discover recommendations—not universal website requirements or a promise that Google will select the image.
The practical approach is to prepare a sufficiently large, well-composed source image, then check how your site crops and delivers it in each intended location. If you also want a large Discover preview, configure the relevant metadata and preview permission; uploading a large image alone is not enough.
Why there is no universal featured-image dimension
A featured image can appear as a wide article header, a compact archive card, a homepage tile, or a search or social preview. Those placements may use different proportions and crops. A theme can register custom image sizes and decide how an image is displayed, so the dimensions of the uploaded original do not necessarily match the image file or crop shown to a visitor.
In WordPress, themes declare support for featured images and can register their own image sizes. WordPress does not impose one universal featured-image dimension. Check the active theme’s documentation or settings and inspect the actual output for each placement you use. The WordPress Developer Resources’ Featured Images & Post Thumbnails – Theme Handbook explains the theme-controlled role of featured images and registered sizes.
#1 Best Overall
- HTML CSS Design and Build Web Sites
- Comes with secure packaging
- It can be a gift option
Start with the placements, not a magic number
- Article header: Find out whether the theme displays the image at its original proportions or crops it into a set frame.
- Archive and homepage cards: Check these separately; a compact card can crop a subject that looks fine in a full-width header.
- Search or sharing preview: Check the image specified in page metadata as well as the featured-image field. They are related but should not be assumed to be identical.
Record the actual shapes your site uses, then compose the source image so its important content survives those crops. For a site with multiple placements, a larger original can provide room for the theme to make smaller versions, but it does not eliminate the need to check the resulting crops.
Image dimensions for Google Discover
Google Search Central’s Discover guidance, updated March 9, 2026, recommends an image at least 1,200 pixels wide and with more than 300,000 total pixels. Google gives 1,280 × 720 pixels as an example of a 16:9 image exceeding that pixel-area recommendation. These figures apply to Discover guidance; they are not WordPress defaults or required dimensions for every page and theme.
A 16:9 landscape crop is a useful option when the subject suits it. But do not force every source into that shape: a portrait image or a subject near the edges may lose important content. Google’s guidance says: “If you choose to crop your images yourself, be sure your images are well-cropped and positioned for landscape usage, and avoid automatically applying an aspect ratio.” Check the framing rather than treating 16:9 as an automatic rule.
Relevance matters as much as size
Choose an image that represents the page. Google advises against relying on a generic logo or a text-heavy image as the preferred image for Discover. A technically large file cannot make an unrelated or poorly framed image representative of the article.
Free tools Windows power users keep installed
One-click scans. No signup required.
Set the preferred image and preview permission
Google says a preferred image can be indicated with structured data or the og:image metadata property. For large image previews, set max-image-preview:large or use AMP. These settings affect eligibility and presentation; they do not guarantee that a page will appear in Discover or that Google will choose a particular image.
In particular, do not assume that setting a WordPress featured image automatically sets every image Google may use. Inspect the rendered page’s metadata and confirm that the intended image is identified in the appropriate way.
Choose a source image and crop that survive every placement
Once you know the actual destinations, prepare the image around the most demanding crop. Keep faces, products, and other meaningful details away from edges that a card or cover crop might remove. If one image has to serve both landscape and square placements, preview both; if the subject cannot remain clear in both, consider whether your theme or publishing workflow allows a separate crop.
For a landscape crop intended for Discover, check that it remains well-positioned at the width of a smaller card as well as in the full article header. A wide image can meet a pixel-width recommendation and still look poor when the central subject is cropped out or reduced to an indistinct detail.
Use focal-point and cover controls deliberately
WordPress’s Image block documentation describes aspect-ratio, cover-crop, and focal-point controls. When an editor applies a fixed aspect ratio with cover scaling, parts of the source can be cropped. Set the focal point on the part of the image that must remain visible, then preview the result at each important size. The documentation recommends leaving width and height on Auto in most cases and avoiding a fixed height unless the design requires one.
Serve responsive images instead of one oversized file everywhere
Responsive image markup lets the browser choose an appropriate available resource for the screen and layout. WordPress has supported responsive images using srcset and sizes since WordPress 4.4 and generates smaller image sizes on upload. The available sizes and the markup actually delivered still depend on theme additions and media settings.
Rank #3
When you inspect a rendered image, look for a normal src fallback as well as srcset and sizes. Google’s image SEO guidance recommends preserving a fallback URL when using responsive markup such as srcset or <picture>. WordPress also notes that explicit width and height attributes help improve layout-shift behavior.
What to verify in the markup
srcpoints to a usable fallback image.srcsetoffers the intended responsive alternatives, andsizesdescribes the layout slot where the image is displayed.- Width and height attributes are present when the image is output.
- The file or crop shown at each placement matches the image you intended to serve.
Do not add responsive attributes blindly or assume that every theme exposes the same generated sizes. Confirm the actual rendered HTML and inspect the browser’s selected image at the relevant viewport widths.
Outdated Drivers Are Slowing You Down
One free scan finds every outdated or missing driver and matches the right update for your exact hardware.Free scan · exact hardware matchPC Slower Than It Used to Be?
A free scan shows the junk files, broken settings and background clutter dragging Windows down - then fixes them in one click.Free scan · Windows 10 & 11A practical workflow for choosing the right size
- Inspect the active theme. Identify its registered image sizes, featured-image support, crop behavior, and the places where featured images appear.
- List the intended destinations. Check the article header, archive card, homepage card, and any search or sharing preview separately. Note their shapes and whether the theme crops the source.
- Prepare the source for the most demanding use. If Discover is a goal, follow Google’s recommendation of at least 1,200 pixels in width and more than 300,000 total pixels. Choose a landscape crop only when it preserves the subject.
- Set the preferred image and preview metadata. Check the page’s structured data or
og:imageand itsmax-image-preview:largesetting if you want to enable large image previews. - Preview actual crops. Use the theme’s preview or editor controls to inspect the image in each placement and adjust the focal point if necessary.
- Inspect the rendered page. Verify the fallback
src, responsivesrcsetandsizes, dimensions, and intended metadata rather than relying only on the media-library thumbnail.
For a CMS other than WordPress, the same image-composition and verification principles apply, but the theme and responsive-image controls differ. The sources cited here do not establish one implementation or dimension table for every CMS.
Check the result with a rendered-page screenshot
A screenshot is useful for checking what a visitor actually sees: whether a crop cuts off the subject, a card image looks too small, or the layout shifts around the image. Compare the header and card at the viewports your theme is designed to support. A screenshot only shows the visual result; it does not confirm that your page has the desired metadata, responsive markup, or Discover settings. Inspect the rendered HTML for those.
For a quick visual check, you can capture the published page with a browser-based screenshot API. Keep the page URL and viewport consistent when comparing versions so you can see whether a crop or layout change helped.
Rank #4
- Brand: Wiley
- Set of 2 Volumes
- A handy two-book set that uniquely combines related technologies Highly visual format and accessible language makes these books highly effective learning tools Perfect for beginning web designers and front-end developers
Or skip the browser setup
ScreenshotNeo can capture a page from one API request, which is handy for reviewing how featured images render without setting up a browser automation environment. It accepts cookie or consent banners before capture and removes more than 60 known consent platforms, newsletter popups, and chat widgets; each of those steps can be turned off. Bot checks or CAPTCHAs, blank pages, timeouts, failed loads, and cache hits are not billed, and the response identifies the page verdict and billing status in headers. ScreenshotNeo also has an MCP server with take_screenshot, get_page_info, and capture_pdf tools for AI agents.
Example cURL request (replace the URL with your published page):
curl -G "https://api.screenshotneo.com/v1/shot" -d access_key=YOUR_API_KEY --data-urlencode url=https://freedom251.com -o shot.webpSee the ScreenshotNeo documentation for API details. The Free plan includes 1,000 shots per month with no card; paid plans start at $5 for 3,000 shots. Sign up free for 1,000 screenshots a month, no card required.
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.Troubleshooting common image problems
The image looks cropped differently from the upload
Check whether the theme is using a registered crop or a fixed-ratio cover frame. Inspect the placement itself, then adjust the crop or focal point so the subject stays visible. Do not judge the final appearance from the original file alone.
The featured image is not the image shown in a preview
Inspect the rendered page’s metadata. Google says the preferred Discover image may be specified with structured data or og:image; the featured-image field alone should not be presumed to set every preview destination.
The page loads a large image on a small screen
Check whether the rendered image has useful srcset and sizes values and a fallback src. WordPress generates smaller sizes, but theme additions and media settings affect what is available. Confirm the actual markup and selected resource instead of assuming responsive delivery is configured as intended.
The image causes visible layout movement
Check that the output includes width and height attributes so the browser can account for image space as it lays out the page. WordPress notes that explicit dimensions improve layout-shift behavior.
The Discover image is large but not selected
The width and pixel-area recommendations are not a selection guarantee. Check image relevance, framing, preferred-image metadata, and large-preview permission; Google says its recommendation can influence thumbnail choice, not guarantee it.
What to take away
Choose dimensions from your theme’s real placements, not from a universal featured-image chart. For Discover, use Google’s current size recommendations as a specific target, provide a relevant preferred image, and enable large previews. Then verify the actual crop, responsive markup, and metadata on the rendered page.
The Tool Desk
Outbyte Driver Updater FREEFix the driver behind crashes, sound loss and screen glitchesFind Drivers →Outbyte PC Repair FREERepair Windows errors before they cause bigger problemsFix Now →Frequently Asked Questions
Can I use the screenshot alone to confirm Discover image settings?
No. A screenshot shows the rendered appearance, not the page’s structured data, og:image, responsive image markup, or preview directive. Inspect the rendered HTML for those settings.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
