WordPress Featured Image Size: Optimal Dimensions in 2026
The right featured-image size for WordPress, plus a full reference for every default size WordPress generates on upload, theme-specific variations, and how to handle WebP without slowing your editorial workflow down.
Want to audit the images on your live WordPress site?
Scan your site →Looking for general (non-WordPress) sizes? See our full image size reference.
Quick Answer
For 90 percent of WordPress sites, these sizes work without theme-specific tuning:
- Featured image: 1200×630 (also serves as Open Graph)
- In-content image: 800×600 to 1200×800
- Cover / hero block: 1920×1080
- Author avatar: 200×200
- Logo: 400×100 (or SVG, which is better)
- Favicon (Site Icon): 512×512 minimum
The Featured Image Decision
The featured image is the most important asset on a WordPress post. It appears in archive pages, single-post layouts, social shares, RSS feeds, and (on most themes) at the top of the post body. Getting one size right covers all of those uses.
Use 1200×630 pixels. Three reasons:
- It matches the Open Graph specification, so your featured image doubles as the social-share preview without editorial overhead
- It is large enough for retina rendering on a typical 600-pixel post header container
- Almost every modern theme accommodates the 1.9:1 aspect ratio without awkward cropping
If your theme uses a much wider hero crop (some magazine-style themes do), step up to 1920×1080. If your theme uses a square crop, upload 1200×1200 instead and let the theme crop it down. Check the theme's documentation — most reputable themes publish their expected dimensions.
Default WordPress Image Sizes
When you upload one image, WordPress generates seven derivative files by default:
| Size Name | Dimensions | Behavior |
|---|---|---|
| thumbnail | 150×150 | Cropped to exact square |
| medium | 300×300 (max bounds) | Resized, not cropped |
| medium_large | 768 wide | Width-constrained (since 4.4) |
| large | 1024×1024 (max bounds) | Resized, not cropped |
| 1536×1536 | 1536 (max bounds) | Added in WP 5.3 |
| 2048×2048 | 2048 (max bounds) | Added in WP 5.3 |
| full | Original upload | Untouched source |
That means a single 4 MB photograph can generate 6–8 MB of derivative files. Themes and plugins frequently register additional custom sizes via add_image_size(), which compounds the storage cost. WooCommerce alone can add 3–5 more sizes on a typical shop.
Two ways to control this:
- Disable unused sizes via the "Settings → Media" admin (set width/height to 0 for sizes you don't use), or programmatically via
remove_image_size()in theme functions.php - Compress everything with an optimization plugin so even seven derivative files weigh as little as possible
Cover and Hero Blocks
The Gutenberg Cover block renders edge-to-edge by default. 1920×1080 pixels covers desktop viewports without forcing the browser to upscale. Compress aggressively (quality 70–75) — cover images are the largest single asset on most pages, and a 200 KB quality-70 image is virtually indistinguishable from the same source at quality 90 weighing 500 KB. The Cover block accepts mobile-specific overrides in some block themes; use those if your hero gets awkwardly cropped on phones.
Site Logo
Use SVG. WordPress supports SVG uploads via plugins (it's blocked by default for security reasons — only allow SVG uploads from trusted users). SVG stays sharp at every size and weighs less than a comparable PNG. If you must use a raster format, 400×100 pixels handles most theme header heights at 2× density. The site logo is one place where over-sizing genuinely matters — a 2000-pixel-wide logo in a 300-pixel header container is the single most common "why is my site slow" offender we see in scans.
Site Icon (Favicon)
WordPress requires the Site Icon (the official favicon) to be at least 512×512 pixels. WordPress derives the smaller favicon variants from this single upload. The 512 minimum looks excessive for a 32-pixel browser tab favicon, but it ensures iOS home-screen icons and Android adaptive icons are sharp. Upload at 512 or larger; PNG with transparency works fine.
WebP and AVIF: WordPress Doesn't Help You
WordPress 5.8 (July 2021) added support for uploading WebP files. WordPress 6.5 added AVIF. Both can now be uploaded as Featured Images, inserted in the editor, and served normally. What WordPress does not do is convert your JPGs and PNGs to modern formats automatically. If you upload a 2 MB JPG, WordPress serves a 2 MB JPG forever — even to browsers that would happily accept a 600 KB WebP version.
This is the single biggest performance win available on a typical WordPress site. Plugins handle the conversion automatically — you keep your existing editorial workflow (upload JPG, embed in post) and the plugin generates and serves WebP/AVIF derivatives in the background. We cover specific plugin recommendations below.
See exactly which images on your site need attention.
Run a free scan →Target File Sizes
File weight matters more than pixel dimensions for actual page speed. Reasonable targets per image type on a healthy WordPress site:
- Featured image (1200×630): 80–200 KB at JPG quality 80–85
- Cover / hero (1920×1080): 200–400 KB; compress aggressively
- In-content images: under 150 KB each
- Logo: SVG ideal (under 5 KB), PNG raster under 20 KB
- Site Icon (512×512): under 30 KB
Total page weight target: under 2 MB. Most slow WordPress sites are slow because a single oversized hero image is 3–5 MB by itself.
Common Mistakes
- Uploading images at full camera resolution. 6000×4000 phone photos get resized down to 2048 by WordPress, but the original full-size file is still stored — eating quotas and bloating backups. Resize to 2048 max before uploading.
- Using PNG for photos. PNG is lossless, so a JPG-suitable image becomes 5–10× larger as a PNG with no visible quality benefit. Use JPG for photos, PNG only for graphics with transparency or sharp edges.
- Not using the Set Featured Image button. Inserting an image directly into the post body does not make it the featured image. Themes pull from the featured image slot for archives and social previews — leaving it empty means broken cards on social sites.
- Skipping alt text. WordPress's media library has an Alt Text field that is empty by default. Empty alt is bad for accessibility and tells search engines nothing about the image. Fill it in at upload time, before you forget.
- Forgetting WebP exists. A typical WP site can cut image weight 40–60 percent by serving WebP via a plugin. There is no editorial cost — the plugin handles conversion in the background.
Image Optimization Plugins
The single highest-leverage performance change you can make on a WordPress site is installing an image optimization plugin that handles WebP/AVIF conversion and compression automatically. Two solid options:
ShortPixel
Compresses on upload, serves WebP and AVIF automatically to supporting browsers, and optimizes existing images via a bulk-process action. The free tier gives 100 images per month — enough for a small blog. Recurring paid plans scale with image volume. Strong choice if you have a large existing image library that needs retroactive optimization.
Try ShortPixelImagify
Built by the team behind WP Rocket. Automatic WebP and AVIF conversion, three compression levels, backup of originals so you can roll back if quality drops too far. Free tier covers 20 MB per month; paid plans are usage-based. Worth considering if you already use other WP Media products and want a single vendor.
Visit ImagifyPair Compression with Caching
Image optimization is half the page-speed picture. The other half is what happens after the first request: page caching, asset minification, deferred JavaScript, and sensible cache headers. A WordPress caching plugin handles the second half so the optimized images you ship actually arrive fast.
ShortPixel (compress + WebP) plus a cache plugin is the standard WP page-speed stack — and lifting Core Web Vitals scores generally requires both, not one.
FastPixel
WordPress caching plugin focused on Core Web Vitals — page caching, JS/CSS minification, lazy-loading, and CDN integration. Built by the same parent company as ShortPixel, so the two pair cleanly: ShortPixel handles image weight, FastPixel handles delivery and rendering. Useful if your scan flagged oversized images and your overall page-speed score is still poor after compressing.
Try FastPixelFrequently Asked Questions
What is the best featured image size for WordPress?
1200×630 pixels is the safest default. It matches the Open Graph specification, so the same asset works as both the in-page featured image and the social-share preview when someone posts your URL on Facebook, LinkedIn, or Slack. Most modern themes accommodate it cleanly. If your theme uses a wider hero crop, 1920×1080 is the next sensible step up.
What size featured image does WordPress use by default?
WordPress itself does not enforce a featured-image size — the dimensions used to display it depend entirely on your theme. The theme calls `the_post_thumbnail()` with a size argument like "thumbnail", "medium", "large", or "full", and WordPress serves whichever derivative was generated at upload time. If your theme expects 1200×630 but you upload 600×315, the image gets stretched and looks soft.
How many image sizes does WordPress generate per upload?
Seven by default as of WordPress 5.3+: thumbnail (150×150 cropped), medium (300×300 max), medium_large (768 wide), large (1024×1024 max), 1536×1536 max, 2048×2048 max, and the original full-size upload. Themes and plugins frequently add more via add_image_size(). A single 4 MB upload can easily generate 8–12 derivative files totaling 6–8 MB of storage.
Does WordPress automatically convert images to WebP?
No — not natively. WordPress added the ability to upload WebP files in 5.8 (July 2021) and AVIF in 6.5, but it does not automatically convert JPG or PNG uploads to WebP. You either upload WebP directly or use a plugin like ShortPixel or Imagify to handle conversion and delivery automatically.
What is the recommended size for WordPress hero or cover images?
1920×1080 pixels for full-bleed cover images on desktop. The Cover block (and most "hero" theme variants) renders edge-to-edge on the largest viewports, so a smaller source gets visibly stretched. If you target a 16:9 ratio you will not need a separate mobile crop on most themes.
How do I stop WordPress from generating so many image sizes?
Add a `remove_image_size()` call in your theme functions.php for sizes you do not use, or use the Image Sizes plugin to disable defaults from the WordPress admin. Be cautious with large-size deletions — themes and the editor expect medium and large to exist by default, and removing them can break image insertions.
Should I optimize images before uploading to WordPress?
It is faster and more reliable to install an optimization plugin that runs on upload than to remember to compress each image manually. ShortPixel and Imagify both convert to WebP/AVIF, compress losslessly or with chosen quality settings, and serve modern formats automatically — saving you the per-upload friction.
Related Guides
- Best image sizes for websites in 2026 — the full reference, covering hero, blog, social, and more across any platform.
- Shopify image sizes: complete guide — same depth, applied to Shopify stores instead of WordPress sites.
- Open Graph image size — your WordPress featured image often doubles as the og:image; this covers per-platform requirements.
- Social media image sizes — exact profile, post, and cover dimensions for every major social platform.
- Hero image size — above-the-fold dimensions and Core Web Vitals impact, useful for WP themes with full-width headers.
- Find oversized images on your website — the audit workflow for identifying images that need attention.
- Image formats compared: WebP vs PNG vs JPEG — when each format is the right choice.
- E-commerce product image dimensions — WooCommerce sits inside WordPress; this covers product image conventions across platforms.
- Email header image size — for WP-driven email programs and newsletter integrations.
Last updated: