WordPress Featured Images: What Size And Why

The WordPress featured image is one of those settings that most sites configure once and never revisit. The default sizes from the theme template often weren't chosen for the modern context (social sharing, structured data, mobile display) and produce suboptimal results across multiple destinations.

The right featured image setup considers where the image actually appears: the post header, the social share preview, the structured data Article schema, the homepage thumbnail. Each of these has its own optimal size, and the image needs to work across all of them.

The dimensions that matter

For social sharing (Open Graph and Twitter Card), the recommended size is 1200x630 pixels, ratio 1.9:1. This size displays correctly on Facebook, Twitter (now X), LinkedIn, and most messaging apps. Smaller images get scaled up (showing pixelation); larger images get cropped (potentially cutting off important content).

For Article structured data schema, Google's documentation recommends images with at least 1200 pixels on the longest side. The aspect ratio matters less; the resolution matters more.

For the in-post display, the size depends on your theme. Most modern themes display featured images at 1200px or smaller on desktop, with responsive scaling for mobile.

The pattern that satisfies all destinations: upload at 1200x675 (close to 1.78:1 ratio for in-post display) and let the theme handle social share sizing through OG image meta tags that use a slightly different version, or upload at 1200x630 (the social share ideal) and accept that the in-post display will have a wider aspect ratio than typical hero images.

The OG image vs featured image distinction

WordPress doesn't natively distinguish between featured image (for in-post display) and Open Graph image (for social sharing). The same image typically does both jobs.

SEO plugins (Yoast, Rank Math) let you override the OG image per post. If you want to use a 1200x675 image for in-post display and a 1200x630 image for social sharing, you can upload both and configure them separately.

The honest assessment: for most sites, this level of differentiation isn't worth the operational complexity. Using a single 1200x630 image that displays acceptably in both contexts is simpler and produces good-enough results.

The file size and format

Featured images should be optimized for web. The 1200x630 image at high quality JPEG is typically 150-300KB. WebP or AVIF reduces this to 80-150KB.

The file size matters because featured images load on every visit to the post. A 500KB featured image adds half a second of load time on slow connections. A 150KB version of the same image looks identical to most users but loads in a third the time.

Format selection: WebP is supported by all modern browsers in 2026. AVIF support is more recent but increasingly broad. JPEG remains the universal fallback. Quality image optimization plugins (ShortPixel, Imagify) serve the right format to each browser automatically.

The content choice question

Featured images range from custom-illustrated header art to stock photography to topical photos to abstract decorations. The choice affects both visual identity and content appropriateness.

Custom illustration is best for content where visual identity is important but expensive and slow to produce. Stock photography is fast and cheap but produces sites that look like every other site using the same stock library. Topical photos (real images of the subject matter) are best for content where the image adds genuine context.

The mistake I see often: using stock photography that's tangentially related to the topic. A WordPress hosting article with a stock photo of a server room. A WordPress security article with a stock photo of a person at a computer. The images don't add context; they just fill space.

The improvement: either skip the featured image entirely on text-heavy content, or use images that genuinely relate. A WordPress hosting article could use a screenshot of an admin panel; a security article could use a relevant logo or diagram.

The alt text question

Featured images need alt text just like any other image. WordPress sometimes uses the image's title field or filename as alt text by default, which produces poor results.

The pattern that works: explicitly set the alt text in the WordPress media library when uploading the featured image. The alt text should describe the image content (not the article topic), with the target keyword included only if it actually appears in the image.

An article titled "How To Set Up WordPress Caching" with a featured image showing a dashboard screenshot might have alt text like "WordPress caching plugin settings dashboard with options for page cache and object cache enabled." This describes what's shown without keyword stuffing.

The structured data integration

Article schema includes an image field that should point to the featured image. Yoast and Rank Math handle this automatically. Verify by running a representative post through Google's Rich Results Test and checking that the Article schema includes the featured image URL.

If the image isn't appearing in the structured data, the SEO plugin might be configured to use a different image source (like the first image in the post body). Set it to use the featured image and re-test.

The featured image fallback question

Posts without featured images sometimes display awkwardly in themes that assume a featured image exists. The empty space looks broken; the social share preview falls back to a generic site image or no image.

The fix is either: ensure every post has a featured image (editorial discipline), or configure a default fallback image at the theme or SEO plugin level. The fallback should be a generic site-branded image that's at least recognizable as belonging to the site.

For sites where some content types don't fit featured-image patterns (text-only opinion pieces, for example), the fallback approach is reasonable. For sites where every post is image-appropriate, the discipline approach is better.