Quick wins for a faster PC:
Clear out junk files and repair common Windows errorsFree Scan →Scan for outdated or missing drivers - takes under a minuteDriver Scan →There is no single correct featured-image size for every website. Your theme or CMS controls the image sizes it generates, the shape of each placement, and how aggressively it crops. For Google Discover, Google’s current recommendation is an image at least 1,200 pixels wide and larger than 300,000 total pixels; 1,280 × 720 is one example that meets that area recommendation. Those are Discover recommendations, not a universal WordPress setting or a guarantee that Google will select your image.
The reliable approach is to prepare a sufficiently large, relevant original, understand every placement your theme uses, deliver responsive variants, and inspect the rendered crop and metadata on the live page.
What size should a website featured image be in 2026?
Use the largest practical source image your design needs, then let the site deliver smaller versions to smaller screens. If Google Discover is an important destination, make the source at least 1,200 pixels wide and more than 300,000 pixels in total area. A 1,280 × 720 landscape image is a straightforward example. Google describes these as recommendations that can influence the thumbnail it chooses, not as a promise of inclusion or traffic.
A 16:9 version is useful when your site’s hero or card is landscape. Do not force every original image into 16:9: a vertical portrait, product package, chart, or screenshot may lose essential information. Google’s guidance says that when you crop yourself, the result should be well positioned for landscape use and you should avoid automatically applying an aspect ratio.
Recommended Free Tools
#1 Best Overall
- HTML CSS Design and Build Web Sites
- Comes with secure packaging
- It can be a gift option
A practical starting point
| Use case | Starting guidance | Important qualification |
|---|---|---|
| General article feature | Choose dimensions at least as large as the widest theme placement. | The active theme, not WordPress itself, determines the registered sizes and crop rules. |
| Landscape hero or card | Keep a carefully composed 16:9 crop available when that shape is actually used. | Do not crop away faces, labels, or other essential subjects. |
| Google Discover | At least 1,200 px wide and more than 300,000 total pixels; 1,280 × 720 is an example. | This is a Discover recommendation, not a selection guarantee. |
| Portrait or unusual source | Preserve the source orientation when it communicates the subject better. | Check how the theme’s cover crop behaves before publishing. |
Why one “featured-image size” does not exist
In WordPress, a featured image is content that a theme can place in an article header, archive card, homepage module, search result, or another template. Themes declare support for featured images and can register custom image sizes, including hard crops. The uploaded original may therefore be represented by several generated files, none of which is a universal default.
Audit the active theme
- Open the theme documentation or code and identify featured-image support and registered sizes.
- List every destination: single-post header, category and tag cards, homepage cards, related-post modules, and any author or search templates.
- Record each destination’s displayed width, aspect ratio, and whether it uses a hard crop or cover-style scaling.
- Upload a representative image and inspect the actual rendered result rather than assuming the original file is shown.
If the site is not WordPress, apply the same reasoning through that platform’s image pipeline. The exact controls and naming conventions differ by CMS, so use its responsive-image and preview tools instead of copying WordPress settings.
Choose dimensions by placement, not by a generic chart
One image may appear in several shapes. A wide article header can preserve a different region than a square archive card. Prepare the composition for the smallest important placement: keep the subject away from edges that may be trimmed, and avoid putting text where an overlay, badge, or automatic crop can hide it.
When to prepare multiple crops
- Prepare a dedicated landscape crop when the site consistently uses a wide hero or when Discover previews matter.
- Keep a portrait original when height conveys meaning, such as a person, poster, phone screenshot, or infographic.
- Use focal-point controls when the editor or theme offers them; select the face, product, or chart area that must survive a cover crop.
- Test at card size because details that look clear in the editor can disappear in a small module.
WordPress’s Image block documentation recommends leaving width and height on Auto in most cases and avoiding a fixed height unless the design requires it. A fixed aspect ratio with cover scaling can remove part of the source image, so verify the focal point at each placement.
Free tools Windows power users keep installed
One-click scans. No signup required.
Meet Google Discover’s image requirements without overpromising
For Discover, use an image that is relevant and representative of the page. Google advises against a generic logo or text-heavy artwork as the preferred image. A large file alone is not sufficient.
Provide a preferred image signal
Specify the preferred image with either og:image metadata or appropriate structured data. Also allow large previews with max-image-preview:large (or use AMP where applicable). These settings affect eligibility and presentation; they do not guarantee that Discover will show the article or use the image you selected.
Keep the image editorially safe for automatic cropping
Place the principal subject near the visual center, leave breathing room around faces and products, and avoid tiny text. If you create a 16:9 derivative, review it at the smallest card size you expect. Do not turn a vertical source into a forced landscape crop when that would remove information.
Responsive delivery: srcset, sizes, and dimensions
Responsive markup lets the browser download an image suited to the current viewport instead of sending the largest file everywhere. WordPress has supported responsive images with srcset and sizes since WordPress 4.4 and generates smaller sizes when an image is uploaded, subject to the theme and media settings.
The Tool Desk
Outbyte PC Repair FREEClear out junk files and repair common Windows errorsFree Scan →Outbyte Driver Updater FREEScan for outdated or missing drivers - takes under a minuteDriver Scan →What the rendered markup should contain
srcset: a list of available width variants.sizes: a hint describing how wide the image will be at different viewport widths.- Fallback
src: an ordinary URL that remains usable if responsive selection is unavailable. Google’s image guidance recommends retaining this fallback. - Width and height attributes: explicit intrinsic dimensions that help the browser reserve space and reduce layout shift.
Inspect the final HTML in your browser’s developer tools, not only the media-library screen. Confirm that the selected resource is large enough for the rendered slot, that the fallback URL works, and that the dimensions match the intrinsic file.
A repeatable workflow for selecting and verifying your image
- Map placements. Write down the pixel width and shape of the single-post header, archive cards, homepage modules, and social or discovery preview.
- Prepare the source. Start with a relevant image at least as wide as the largest placement. If Discover matters, meet the 1,200-pixel width and more-than-300,000-pixel area recommendations.
- Compose the crop. Make a deliberate landscape derivative only where the design needs it. Keep key subjects inside the safe area.
- Upload and inspect generated variants. Check which sizes the theme and WordPress actually create.
- Set metadata. Confirm
og:imageor structured data points to the intended image and thatmax-image-preview:largeis allowed. - Test responsive selection. Resize the browser and inspect the selected
srcsetcandidate,sizeshint, fallbacksrc, and width/height attributes. - Check real crops. Review desktop, mobile, archive, and card layouts. Adjust the focal point or create another crop if an important detail disappears.
- Recheck after theme changes. A redesign can alter registered sizes and crop behavior without changing the image in your media library.
Inspect the live result with a clean screenshot
A browser preview can be misleading when cookie banners, newsletter prompts, or chat widgets cover the featured image. Capture the published URL at desktop and mobile widths, then compare the visible crop with the intended composition. For a manual check, open a private browser window, dismiss consent and overlays, set the viewport to the target dimensions, and save screenshots of the article header and representative cards.
Or skip the browser setup
ScreenshotNeo can capture the live page through one request while removing cookie or consent banners, newsletter popups, and chat widgets before the shot. Only clean shots are billed; bot checks, blank pages, timeouts, failed loads, and cache hits cost nothing, and the response identifies the page verdict and billing status in headers. Its MCP server gives Claude, Cursor, and other MCP clients take_screenshot, get_page_info, and capture_pdf tools.
Example cURL request (see the ScreenshotNeo API documentation):
Rank #3
curl -G "https://api.screenshotneo.com/v1/shot" -d access_key=YOUR_API_KEY --data-urlencode url=https://example.com/article -o shot.webpPython:
import requests
r = requests.get("https://api.screenshotneo.com/v1/shot", params={"access_key": "YOUR_API_KEY", "url": "https://example.com/article"}, timeout=90)
open("shot.webp", "wb").write(r.content)Node.js:
const q = new URLSearchParams({ access_key: 'YOUR_API_KEY', url: 'https://example.com/article' });
const res = await fetch(`https://api.screenshotneo.com/v1/shot?${q}`);ScreenshotNeo includes 63 options for workflows such as full-page capture with lazy images loaded, CSS-selector element capture, device presets, retina scale, custom CSS or JavaScript, click and wait conditions, blocked resources, cookies and headers, timezone and geolocation, resizing, caching with a chosen TTL, signed image links, asynchronous jobs, webhooks, bulk capture of up to 100 URLs per call, usage reporting, and PDF output. Every feature is on every plan. The Free plan includes 1,000 screenshots per month with no card; paid plans start at $5 for 3,000. Create a free ScreenshotNeo account to check your featured-image crops without setting up a browser.
Troubleshooting featured-image problems
The image looks blurry on a large screen
The theme may be selecting a generated variant narrower than the rendered slot, or the uploaded source may be too small. Inspect the chosen srcset candidate and upload a larger original when necessary.
The subject is cut off in cards
A hard crop or cover rule is removing part of the source. Change the focal point, create a placement-specific crop, or redesign the card to avoid a fixed ratio.
Mobile downloads the desktop-sized file
Check the sizes attribute and confirm that mobile variants exist. A missing or inaccurate hint can cause the browser to choose an unnecessarily large resource.
Google shows a different image
Discover can choose among eligible images. Confirm that the page’s og:image or structured data identifies the preferred image, that large previews are allowed, and that the image is relevant and representative. None of these settings guarantees selection.
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
Layout jumps while the image loads
Add correct width and height attributes and avoid CSS that changes the reserved box after load. Recheck lazy-loading and theme modifications that alter intrinsic dimensions.
An overlay hides the image during testing
Dismiss consent, newsletter, and chat interfaces before capturing. If you automate checks, use a clean screenshot service that removes those overlays before capture, then verify the resulting image against the live page.
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.Performance, reliability, and cost considerations
Large originals improve crop flexibility but should not be delivered at full size to every visitor. Let responsive markup choose an appropriate resource, compress according to the image format your site supports, and reserve space with dimensions. Keep the original high enough quality for the widest placement and any required crop; generate delivery variants automatically rather than maintaining unrelated manual files.
Image dimensions are only one part of reliability. A correct URL, valid fallback, stable metadata, and a tested crop matter just as much. After changing themes, lazy-loading behavior, or image settings, repeat the live-page inspection because generated sizes and placement rules can change.
Featured-image checklist for publication
- The source is relevant to the page and large enough for the widest placement.
- If Discover matters, it is at least 1,200 px wide and exceeds 300,000 total pixels.
- A deliberate landscape crop exists only where the design needs one.
- Faces, products, labels, and other key details survive the smallest card crop.
srcset,sizes, fallbacksrc, width, and height are present and correct.og:imageor structured data identifies the preferred image.max-image-preview:largeis permitted when large previews are desired.- The live page has been checked at desktop, mobile, archive, and discovery-oriented placements.
Frequently Asked Questions
Is 1,200 × 675 px the required featured-image size?
No. Google’s 1,200-pixel width and more-than-300,000-pixel area guidance applies to Discover recommendations. Your theme may require different dimensions and crops.
Should every featured image be 16:9?
No. Use 16:9 when the placement is landscape and the crop preserves the subject. Keep vertical or irregular images in a shape that communicates their content.
Does a WordPress featured image automatically become the Discover image?
Not necessarily. Verify the rendered page’s og:image or structured data and large-preview setting; Discover still makes its own selection.
Why do two pages using the same source image look different?
Their templates may request different registered sizes or apply different crop and focal-point rules.
The Bottom Line
Choose featured-image dimensions from your theme’s real placements, not a universal chart. Keep a relevant source at least 1,200 pixels wide and above 300,000 pixels when Discover matters, deliver responsive variants with correct metadata, and verify every crop on the live page.
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.
