To require a featured image before a WordPress post can be published, you need two separate things: featured-image support so the editor can assign one, and a publishing rule that blocks publication when no image is assigned. Adding theme support enables the feature; it does not make the image mandatory.
First, make sure the Featured Image control is available
WordPress also calls a featured image a post thumbnail. It represents an individual post, page, or custom post type, and a theme may display it in places such as an archive or above the post. The active theme must declare support before WordPress displays the Featured Image control on the edit screen. See the WordPress Theme Handbook’s featured-image documentation.
| # | Preview | Product | Price | |
|---|---|---|---|---|
| 1 |
|
WordPress Multisite Administration | $34.38 | Buy on Amazon |
| 2 |
|
Mon Site WordPress – Volume 2 – Administration & Utilisation (French Edition) | $9.90 | Buy on Amazon |
| 3 |
|
WordPress 24-Hour Trainer | $3.95 | Buy on Amazon |
| 4 |
|
Teacher Record Book | $4.89 | Buy on Amazon |
For standard posts, add this to the active theme’s functions.php file, or register it on the after_setup_theme action:
add_theme_support( 'post-thumbnails' );
The support declaration must be made before init. WordPress documents both placement options and the support declaration in its add_theme_support() reference.
The Tool Desk
Outbyte PC Repair FREERepair Windows errors before they cause bigger problemsFix Now →Outbyte Driver Updater FREEFix the driver behind crashes, sound loss and screen glitchesFind Drivers →#1 Best Overall
Limit support to selected post types
If only standard posts need featured images, scope the declaration rather than enabling it for every supported type:
add_theme_support( 'post-thumbnails', array( 'post' ) );
The second argument names the post types that should support thumbnails. For a custom post type, check its registration as well: it can declare thumbnail support when registered. The post_type_supports() reference documents how WordPress checks support for a post type.
If the control is still missing
- Confirm the active theme declares post-thumbnail support, rather than assuming another installed theme’s settings apply.
- Check that the declaration includes the post type you are editing.
- For a custom post type, inspect its registration for thumbnail support.
- If those checks pass, inspect the editor’s available panels and screen settings. Theme support and post-type support explain whether the feature is enabled, but do not by themselves establish why a particular editor panel might be hidden.
Theme support does not require an image
add_theme_support( 'post-thumbnails' ) makes the feature available; it does not stop someone from publishing without choosing an image. To make the image mandatory, add a separate validation layer that checks the relevant post type and publication transition and prevents publication when no thumbnail is assigned.
The right implementation depends on how posts are created. A plugin may be the simplest route for an editor-based workflow, while a custom server-side rule may suit a site with its own publishing process. The important distinction is whether the mechanism actually blocks publication or only displays a warning.
Quick wins for a faster PC:
Scan for outdated or missing drivers - takes under a minuteDriver Scan →Clear out junk files and repair common Windows errorsFree Scan →Rank #3
| Route | What to verify | Evidence and limits |
|---|---|---|
| Plugin | Does it cover the editor your team uses, including the block or classic editor as relevant? Does it block publication, and can it be scoped to the intended post types and statuses? Check current directory status, update history, compatibility, and behavior with scheduled posts. | The Require Featured Image project repository describes an editor-side block on publishing until a featured image is selected and notes that the content type needs thumbnail support. Its current listing, maintenance, and compatibility are not established here, so treat it as a candidate to evaluate, not a verified current recommendation. |
| Custom server-side validation | Validate the relevant post type and transition to a publishable status; reject or prevent that transition if no thumbnail is assigned. Confirm behavior for scheduled publication and every editor or workflow used by the site. | A particular production-ready hook implementation is not established by the cited documentation. Verify the current WordPress APIs and status-transition behavior before deploying custom code. |
| API or automation workflow rule | Ensure the media attachment exists, assign its ID to the post, and make the workflow fail rather than publish if the required image is absent. | The REST API documents the featured_media field and its attachment-ID handling. That field is not, by itself, a site-wide required-image policy. |
For REST API and automated publishing
WordPress REST API clients identify a post’s featured image with featured_media, using the ID of a media attachment. The Posts REST API reference describes the field, and WP_REST_Posts_Controller::handle_featured_media() documents how the controller handles it: an invalid ID returns an error, while an empty value removes the thumbnail.
Those behaviors describe field handling, not a rule that blocks every API publication request when the field is missing. If automated publishing must never create a published post without an image, enforce that requirement in the API workflow or another server-side validation layer. Have the workflow obtain or create the media attachment, send its valid ID as featured_media, and verify that the publishing request is rejected when the required image is absent.
Rank #4
- Keep track of everything from attendance to test scores
- Spiral bound
- Measures 8-1/2" x 11"
Test the rule across the publishing paths you use
- Try publishing a post of each in-scope type without a featured image. The operation should be blocked, not merely accompanied by a warning, if the requirement is mandatory.
- Assign an image and publish again; confirm the post can proceed and the image is saved.
- Check other routes your site uses, such as scheduled publishing, a different editor, or REST/API automation. An editor-side restriction does not establish that every other route is covered.
- Confirm that post types outside the rule remain unaffected, and decide whether the rule applies only to new publication or also to updates and existing posts.
WordPress’s documented theme and REST API behavior establishes how featured images are enabled and assigned. The enforcement behavior depends on the chosen plugin or custom workflow, so verify it against the actual publishing paths on your site.
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.

