How to Hide Featured Image in Post WordPress
The short answer: look in your post editor first, because most modern themes have a switch for this. If yours does not, install Conditionally display featured image on singular posts and pages. It is free, it is on 30,000-plus sites, it was updated three months ago and tested against WordPress 6.9.7, and it does exactly the right thing: hides the image on the single post while keeping it in your archives, related-post widgets and social previews. That last part is why it beats a blanket CSS rule.
Reach for CSS only if you cannot add a plugin. Reach for a bulk tool only if you are changing hundreds of posts at once.
Hide, not delete
Those are two different jobs, and mixing them up costs you traffic. The featured image is what Facebook, X, LinkedIn and Pinterest pull when someone shares your post. It is also what your theme puts in archive listings, related posts and recent-post widgets. Delete it and all of that goes blank. Hide it and only the single post view changes.
So the usual reason to do this is layout, not dislike. A post that opens with a large image immediately followed by a chart, a screenshot or a hero graphic in the body reads as cluttered, and on a phone the featured image can eat the whole first screen before a single word appears. Hiding it on that one post fixes the page without touching how it is shared.
Method 1: check your theme first
Featured image display is the theme’s decision, so the theme is where the switch usually lives. Any theme built in the last few years is likely to have one.
- Go to Posts > All Posts and open the post you want to change.
- In the editor sidebar, look under the post settings for an option named something like Disable Featured Image, Hide Featured Image or Featured Image Position.
- Some themes put it in a separate panel of their own, often labelled with the theme’s name.
- Others put a site-wide version in Appearance > Customize under blog or single-post settings.
If you cannot find it, search your theme’s name plus “hide featured image”. Two minutes of looking saves you a plugin.
Method 2: use a plugin
Conditionally display featured image on singular posts and pages
This is the one to install. Activate it and a checkbox appears in the editor under Featured Image, reading “Display featured image in post lists only, hide on singular views”. Tick it and the image drops off the post while staying everywhere else.
It is on more than 30,000 sites, was last updated three months ago and is tested to WordPress 6.9.7, which means you are not adopting an abandoned dependency to solve a two-minute problem.
WP Hide Show Featured Image
The site-wide alternative, and the second-best maintained option here: around 4,000 installs, updated within the last year, tested to WordPress 6.8.5. Its settings page sits under Settings and switches featured images off across all posts and pages in one go. It also throws in some unrelated admin tidying, such as hiding the toolbar and removing the “Howdy” greeting.
WP Hide Show Featured Image on WordPress.org
Quick Featured Images, for bulk work
This one does not hide anything. It manages featured images in bulk: set, replace and delete them across many posts at once, apply presets so new posts pick up a default image, and filter which posts a change applies to. If your real problem is that 400 posts have the wrong image rather than that one post shows it, this is the tool.
It is on 50,000-plus sites, was updated four months ago and is tested to WordPress 7.0.4. A pro version adds videos and custom post types.
Quick Featured Images on WordPress.org
Two you will find recommended elsewhere, and should skip
Hide Featured Image still turns up at the top of most search results for this task. It has around 10,000 installs, but it was last updated eight years ago and tested only to WordPress 4.9.31. It may still work. It is also code nobody is watching, and outdated plugins are one of the commonest ways WordPress sites get compromised.
Hide featured image on all single page/post is a neat idea, with no settings page at all: it simply stops the theme reading the featured image when it builds a single view. Around 4,000 sites use it. It was last updated five years ago and tested to WordPress 5.9.16, so WP Hide Show Featured Image is the safer pick for the same job.
Method 3: one line of CSS
If you would rather not add a plugin, add CSS. Go to Appearance > Customize > Additional CSS and paste one of these.
To hide the featured image on every single post:
.single .post-thumbnail { display: none; }
To hide it on one post only, replacing 111 with that post’s ID:
.post-111 .post-image { display: none; }
To hide it on the homepage:
body.home .entry-thumbnail { display: none; }
Two warnings. The class names differ between themes, so open your post, use your browser’s inspector on the image, and copy the class your theme actually applies. And be careful with anything as broad as .single .entry-content img: that hides every image inside the post body, not just the featured one. Target the featured image wrapper, not all images.
CSS also only hides the image visually. It still loads, so you save no bandwidth, and a screen reader may still announce it. That is the trade for not installing anything.
The opposite problem: several images per post
Sometimes you do not want fewer featured images but more, for a product gallery or a paired header. Options here are thinner than they look.
Multiple Featured Images adds extra thumbnails to posts, pages, custom post types and WooCommerce products, with shortcode and widget support. Around 5,000 installs, but last updated six years ago and tested to WordPress 5.5.18, and it needs template code rather than working out of the box.
Multiple Post Thumbnails does the same, registering additional thumbnails per post type. It has around 20,000 installs and a good rating, but it was last updated eight years ago and tested to WordPress 5.0.27, with reported problems in the block editor.
Multiple Post Thumbnails on WordPress.org
A third plugin, Dynamic Featured Image, is still widely recommended for this. Do not install it: WordPress.org closed it on 2 September 2024 over a security issue and it is no longer available for download. If you already have it active, deactivate and delete it, then use your theme’s own gallery block or a maintained gallery plugin instead.
Honestly, for most sites a gallery block in the post body is a better answer than any of these.
While you are here: compress the image
A featured image you decided to keep is worth optimising, because it is usually the largest file on the page and often the element the browser paints last.
ShortPixel Image Optimizer is the safe default. It runs lossy or lossless compression on JPG, PNG, GIF and PDF files, converts to WebP and AVIF, and does the work in its own cloud so your server is not doing the lifting. It is on more than 300,000 sites, was updated two weeks ago and is tested to WordPress 7.1. You get 100 free credits a month, with paid top-ups beyond that.
ShortPixel Image Optimizer on WordPress.org
Optimole is the alternative if you want a CDN alongside the compression. It resizes and delivers images from a global network and handles lazy loading itself. Around 200,000 installs, updated within the last week, tested to WordPress 7.1. The free tier covers a modest amount of monthly traffic.
Imagify and Smush are both credible and both widely used. Imagify offers three compression levels and keeps a backup of the original so you can restore it. Smush bundles compression with lazy loading and bulk resizing. Either is fine; we compare the whole field in our roundup of WordPress image optimizer plugins, and cover the loading side in WordPress lazy load plugins.
Which to choose
- One post, or some posts: your theme’s setting, or the Conditionally display plugin.
- Every post, site-wide: WP Hide Show Featured Image.
- No plugins allowed: targeted CSS on the featured image wrapper.
- Hundreds of images to fix: Quick Featured Images.
Whichever you use, keep the image assigned to the post. Hiding it costs you nothing. Removing it costs you your social previews and your archive thumbnails.
Also read:
