How to Require a Featured Image on WordPress Posts
By Aleksan Aharonyan ·
WordPress has no setting that makes a featured image mandatory. You require one by controlling how posts arrive: put a required featured image field in the submission form, hold every submission as Pending, and approve only the posts whose image is fit to publish. That works on any theme, needs no code, and covers what a form field alone cannot judge: whether the image is any good.
Key takeaways
- Add a Featured Image field to the form, mark it required, and place it above the content editor, so submitters see it before they start writing.
- Set the form to save new posts as Pending; a form that publishes immediately never gives you the chance to check the image itself.
- Before approving, check that the image is horizontal, sharp enough for the widest place it appears, and cleared for use on your site.
- Configure a fallback image for archives and social cards, so the few posts that still arrive without one do not leave an empty space.
Why a featured image matters more on user-submitted posts
The featured image does three jobs at once: it fills archive and listing views, it becomes the social sharing image when the post is shared, and it sets the visual tone of the single post. On a site with outside contributors all three fail quietly, because the person writing the post fills in a form and never sees the archive page where the gap shows up.
An author working inside wp-admin sees the site all day. A guest writing in a front-end form sees only the form. If the image field sits below the content editor, is labelled vaguely, or is easy to skip, a share of submissions will arrive without one. Nothing in WordPress warns you: a post with no thumbnail is still a valid post, and it publishes, appears in the loop, and shares with whatever fallback the theme or an SEO plugin finds.
That is why the fix has two parts. The form makes the image easy to supply, and the review step makes it hard to publish without one.
Add a Featured Image field to the submission form
To get images from contributors, put the upload in the form they already use, and build it so the image is one of the first things they meet rather than the last.
- Decide who can submit. Members and logged-in users submit through the normal form. If you accept posts from visitors without accounts, guest posting has to be turned on, and that is a Pro option.
- Add the Featured Image field in the drag-and-drop form builder, tick its Required setting, and move it directly under the Post Title field. With Required on, the form refuses to submit without an image, and submitters see the request before they write, not afterward when they are in a hurry to hit submit.
- Choose the uploader. The free version of Front User Submit, a free plugin for frontend post submission and guest posting forms, attaches a simple image uploader to the field. Pro adds the WordPress Media Library uploader for the same field, which lets a logged-in user pick a file they have already uploaded. The Featured Image field documentation covers the settings behind both.
- Write a label that says what you want. “Featured image” means nothing to someone who has never run a blog. A label such as “Main image for your post”, plus a one-line note about the kind of picture you want, gets better files than a bare field name.
- Submit a test post yourself, once without an image (the form should stop you) and once with one, and look at what arrives. Check that the thumbnail shows in the post list and that the image is attached to the post rather than sitting unattached in the media library.
A required field guarantees that a file arrives, not that it is the right one. A blurry phone screenshot or someone else’s photo passes the field just as easily, which is what the next step is for.
Hold posts without an image in Pending review instead of publishing
The reliable way to require a usable featured image is to make a person look at every submission before it goes live. Set the form’s post status to Pending, and the review step becomes the rule.
- Open the form’s post submit settings and set the post status to Pending rather than Publish. In Front User Submit this is set per form, so a trusted columnist’s form can publish directly while the public form always waits. The post submit settings page lists the status, redirect and message options that sit alongside it.
- Turn on the admin notification for the form, so you get an email when a post is submitted instead of remembering to check a dashboard. Front User Submit sends that email through the normal WordPress mail function and supports variables such as
[post_title]and[post_link]; the notification settings explain what each one does. - Give submitters the right role. For posts sent through the form, the form’s post status decides whether they wait, so the Pending setting is what holds them. The role still matters in wp-admin, where an Author can publish without review, so keep public submitters on Subscriber. The plugin gives Subscribers the right to upload files when it is activated, which the image field needs; a Contributor cannot upload files unless you add the
upload_filescapability to that role. - Work the queue where you already work. Pending submissions appear in the normal WordPress posts list under the Pending filter, so approving one is the usual edit screen.
Do not switch the form back to Publish later to save time. The queue is the only step that checks the image is fit to publish.
What the editor checks before approving a submission
Approving a submission is a short, repeatable check. Run the same list every time and the archive stays consistent.
- The image exists. Open the post and look at the Featured Image panel, not just the preview. A file placed in the post body is not the featured image.
- It is horizontal, not portrait. Cards, archive grids and social previews are wide. A tall poster-style image gets cropped through the subject or letterboxed with bars.
- It is large enough for the biggest place it appears. The single post header is usually the widest use. A small logo or a phone screenshot will look soft there even when it looks fine in the archive.
- It is not text-heavy. Screenshots of flyers, event posters and price lists read badly at thumbnail size. Ask for a photo instead.
- Someone has the right to use it. A submitted image is not automatically licensed for your site. Ask submitters to confirm they took the photo or have permission, and say so in the form’s help text.
- It has useful alt text. Alt text is set on the image in the media library. Write a short description when the submitter left it blank, because that is what screen readers and search engines read.
- The file is not enormous. A multi-megabyte photo straight from a camera slows the page. WordPress generates smaller sizes on upload, but the original still counts against your storage.
If an item fails, leave the post in Pending and reply with what you need. A specific request gets a result: “Can you send a horizontal photo at least as wide as the header?” works better than “image problem”.
Show the featured image in the post, archives and social cards
Once the image is on the post, the theme and your SEO plugin decide where it appears. Check all three places, because each one has its own setting.
On the single post, the theme’s template prints the featured image. In a block theme that is the Post Featured Image block inside the single post template; in a classic theme it is usually a call in the template, and some themes make it a per-post option.
On archives and listing pages, the theme decides whether thumbnails appear at all. Many themes have a setting for archive thumbnails, and post grids often use the featured image as the card background. If your archive shows no images, the missing field is not the problem; the theme is.
On social cards, the platform reads the sharing tags your site outputs. If you run an SEO plugin, it usually uses the featured image for the share image when one is set, and a sitewide default when it is not. After approving a post, load the URL into the sharing debugger for the platform you care about and confirm which image it picks.
A fallback image for the posts that still arrive without one
Even with a form field and a review queue, some published posts will have no image: older posts from before you added the field, a post approved in a hurry, a contributor who never sent a replacement. A fallback stops those from showing an empty box.
- Set a default share image. Most SEO plugins have a sitewide default for social sharing. Upload a branded image with your site name and use that as the fallback.
- Print a fallback in the theme. A few lines in a child theme can check
has_post_thumbnail()and output a default image when it returns false. That covers archives and single posts, not social cards, which come from your plugin or your own tags rather than the page. - Let the contributor fix it. Where the form allows front-end editing, the same submission can be reopened and the image added later, without an admin step. That is usually faster than an email exchange.
- Leave the older posts alone. Rewriting years of archives is rarely worth the hours. Apply the rule to new submissions and let the fallback handle the rest.
FAQ
Can I make the featured image required in WordPress itself?
No. WordPress has no core setting that makes a featured image mandatory, and the editor will save a post without one. Enforcement happens outside the post editor, in the form that collects the submission and in the review step that decides whether it publishes.
What happens if a post with no image gets approved by mistake?
It publishes, and the theme shows what it shows for a post without a thumbnail: usually nothing on archives, and a default image on social cards if your SEO plugin has one configured. You can add the image yourself in the post editor, or ask the contributor to add it through the front-end edit form, and the archive updates as soon as the thumbnail is saved.
Do I need code to require a featured image?
No. A required image field in the submission form plus Pending review covers it, and a person checking the image also catches things a snippet cannot judge, such as a license or a bad crop. Code helps in one place: a small function in a child theme that returns a post to Pending when it has no thumbnail catches submissions that bypass the form.