Key takeaways
- Two different failures look identical from the outside. Either the control is missing — greyed out, absent, replaced by three auto-generated frames — or the control is there and your file is being refused. The fixes have nothing in common, so establish which one you have before you do anything else.
- The single most common cause is still the dullest: the channel has never been phone-verified. YouTube's documentation lists custom thumbnails among the features phone verification unlocks, and there is no view, subscriber or watch-time threshold involved. It takes about ninety seconds in Studio.
- A live Community Guidelines strike removes the ability to create custom thumbnails for a week, alongside uploads, live streams, Premieres and playlist edits — and the clock does not start until you acknowledge the strike.
- As of 21 October 2026 there is a new reason that did not exist before: YouTube's Temporary Feature Pause freezes custom thumbnail uploads, among other features, when it detects possible unauthorised activity on a channel. The review is typically completed within 24 hours, and the right response is to secure the account rather than wait.
- The file-level ceiling most guides quote is out of date. YouTube's own help page now gives device-dependent limits — 2 MB from mobile, 50 MB from desktop — and recommends 3840 × 2160 with a 640-pixel minimum width. If a file is bouncing, the 2 MB figure usually means you are uploading from the phone app.
- Each surface has its own rules. Shorts thumbnails can only be uploaded in Studio on a computer, podcast playlists want a square image, and a video whose thumbnail vanished after it was working is a removal, an age restriction or a stale cache — never a missing feature.
The thumbnail is finished. It survived the shelf test, the text is legible at 168 pixels wide, and the whole point of the afternoon was to get it in front of viewers. Then Studio shows you three auto-generated frames from your own video and no way to upload anything else — or it shows you the upload box, accepts the click, and quietly does nothing.
This is one of those problems where almost every article you find answers a different version of the question than the one you have. Most of them say "verify your phone number" and stop, which is correct for maybe half of cases and useless for the other half. The genuinely useful answer is a decision tree, because there are now eight distinct mechanisms that produce the same symptom, one of them introduced only in late October 2026, and they are distinguished by details that take seconds to check once you know what you are looking at.
What follows is each mechanism, what it blocks, how to confirm it is the one you have, and how long it lasts. The order is roughly by frequency, which is also roughly the order you should check them in.
First: is the control missing, or is the upload failing?
Everything downstream depends on this, and it is the step people skip.
Open the video in YouTube Studio on a desktop browser — not the Studio mobile app, not the main YouTube app — and look at the Thumbnail block on the Details page. You are looking for one of three states:
- No upload option at all. You see auto-generated frames and perhaps a "Test & Compare" entry point, but nothing that lets you supply your own image. This is a feature-access problem: verification, a strike, a pause, or a role.
- The option is visible but greyed out or produces an error on click. Usually an active restriction, a daily limit, or a propagation delay after verifying.
- The option works, the file picker opens, and the upload fails or silently reverts. This is a file problem — size, format, dimensions — or the daily cap.
Only the third state is about your image. The first two are about your channel, and no amount of re-exporting the PNG will touch them.
Reason one: the channel has never been phone-verified
This is the default state of every new channel and it accounts for most of the cases. YouTube sorts creator features into tiers, and custom thumbnails are not in the set a channel gets on day one. The baseline tier covers uploading videos, creating and editing playlists, and adding collaborators to playlists. Custom thumbnails sit one step up, behind phone verification.
YouTube's page on unlocking features with phone verification lists custom thumbnails among the things verification turns on, alongside live streaming and longer uploads. The help page for adding custom thumbnails puts it from the other direction: you can choose from the auto-generated suggestions, or upload your own if your account is verified.
The useful thing about this gate is what is not in it. There is no subscriber count, no view threshold, no watch-hours requirement, no waiting period. A channel with zero uploads can verify and have custom thumbnails a minute later.
The route: Studio on a computer, Settings, Channel, then Feature eligibility. Expand the intermediate features section and work through the phone verification flow there.
Two constraints catch people out. The first is that YouTube limits a phone number to no more than two channels per year, which is exactly the wall creators hit when they spin up a second channel and reach for the same number. The second is about who is allowed to do it: on a Brand Account, the owner and managers can phone-verify a channel; without one, only the channel owner can — not managers, editors or viewers.
Worth separating from this: the advanced features tier, which covers things like pinned comments and higher daily upload limits, needs phone verification plus either enough channel history or ID or video verification, and YouTube notes that ID or video verification is not available to every creator. Custom thumbnails do not need any of that. If you are trying to clear the advanced tier to get thumbnails, you are solving a problem you do not have. The fuller version of that process is in our guide to getting verified on YouTube, which also untangles verification from the grey checkmark, a different thing entirely.
"I verified and it is still greyed out"
Common enough to deserve its own section, and almost always one of four things.
Propagation. Reports vary from instant to a short delay. Several creators in YouTube's own help forums describe the option appearing within seconds; others describe the eligibility page showing verified while the thumbnail control stayed dead for a while. Sign out, sign back in, hard-refresh Studio, and check again before assuming anything is wrong.
Wrong account. If you are signed into multiple Google accounts, Studio can be showing you a channel other than the one you verified. Check the avatar in the top right against the channel you expect.
Wrong surface. The mobile apps do not expose everything the desktop Studio does; reason eight below covers which parts go missing where.
Something else is also restricting you. Verification is necessary, not sufficient. A strike or a feature pause will hold the control shut on a fully verified channel, and the interface will not always explain which of the two it is.
Reason two: an active Community Guidelines strike
A strike is the loudest possible version of this problem and the one creators most often fail to connect to the thumbnail box, because the email is about a removed video and says nothing about packaging.
YouTube's strike basics documentation is specific about the first strike. For one week you cannot upload videos or live streams, schedule a public video or live stream, create a Premiere, create custom thumbnails or posts, or create, edit or add collaborators to playlists. Public videos that were already scheduled get set to private for the duration and have to be rescheduled afterwards.
Two details matter more than the list. The first is that the penalty period starts when you acknowledge the strike, so a strike sitting unopened in your notifications is a week that has not begun to run. The second is that the restriction lifts automatically — there is nothing to apply for — but the strike itself stays on the channel for 90 days, and a second strike inside that window brings a two-week restriction instead of one. Three in 90 days can end the channel.
If you believe the strike is wrong, appeal it: YouTube allows appeals on warnings and strikes for six months after they are issued, and each strike can be appealed once. Our post on what a Community Guidelines strike actually does covers the appeal mechanics and the warning-before-strike distinction in more detail.
Check your notifications before you check your file
Every restriction in this article except the file-level ones announces itself somewhere — a strike email, a Studio banner, a notification. Creators routinely spend an hour re-exporting images to beat a 2 MB limit that was never the problem, because they never looked at the alert sitting in Studio.
Reason three: custom thumbnail privileges removed after repeat thumbnail violations
This one is specific to thumbnails rather than a side effect of a general penalty, and it is the harshest of the ordinary cases.
YouTube's thumbnails policy bars images showing pornography, sexual acts, nudity including genitals, unwanted sexualisation, shock-driven violence, gore, or vulgar language, as well as thumbnails that mislead viewers into thinking they are about to see something that is not in the video. The policy applies across the platform, including to unlisted and private content.
The enforcement ladder has three rungs. A thumbnail that is unsuitable for some audiences without breaking the guidelines may get the video age-restricted or the thumbnail removed, with no strike; you are notified and can upload a replacement. A thumbnail that violates other policies gets removed and may bring a strike, though a first offence is likely to be a warning with no penalty. And repeat thumbnail violations, per the custom thumbnails help page, can cost the channel its custom thumbnail privileges for 30 days, or lead to termination outright. A pornographic thumbnail can skip the ladder entirely and terminate the channel.
For borderline images, YouTube describes its reviewers as weighing whether breasts, buttocks or genitals are the focal point of the frame, whether violence or gore is the central element, whether text appears intended to be vulgar or shocking, and whether the title and other metadata signal an intent to shock. That is a useful list to read as a designer, because it describes focal point and intent rather than subject matter — the same gore in a news context and a shock-bait context are not treated as the same frame.
Separately, the misleading-thumbnail rule has a sharper edge than most creators assume. YouTube's spam policy defines malicious clickbait as using maliciously misleading titles, thumbnails, descriptions or imagery to trick people into clicking something that does not deliver what was promised, and the example it gives is a title promising a full sports match over a video containing only a clip. That is a policy line, not a style note. Curiosity mechanics stay on the right side of that line as long as the thumbnail promises something the video genuinely contains.
Reason four: the Temporary Feature Pause, new as of October 2026
On 21 October 2026 YouTube announced a security mechanism that adds a genuinely new cause to this list, and because it is so recent, no older troubleshooting article mentions it at all.
The Temporary Feature Pause is automatic. When YouTube detects what it considers unusual or unauthorised activity on a channel, it freezes a specific set of features while its security team reviews the account. Per the coverage of the announcement, including Social Media Today's write-up, the blocked actions are: uploading or editing videos and Shorts, starting live streams, creating or adding videos to playlists, uploading custom thumbnails, and switching private videos to public or unlisted.
Three things about it are worth internalising.
It tells you. A paused channel sees a banner in YouTube Studio saying the account has been temporarily restricted for security. If there is no banner, this is not your problem.
It is short, and the clock is not yours. YouTube says the security review is typically completed within 24 hours; it has not published a maximum. If the channel is confirmed secure, access returns; if unauthorised activity is confirmed, YouTube says it will reach out with next steps for regaining access.
It is a symptom, not an inconvenience. This is the part creators get wrong. A pause means YouTube's systems saw something that looked like a takeover in progress. The correct response is not to wait it out so you can get back to uploading — it is to treat the account as possibly compromised and do the hardening pass now: check active sessions and connected apps, rotate the password, confirm two-step verification, review recent Studio activity. Our guide to what to do when a YouTube channel is hacked has that sequence in the order that matters, and the first hour is the part that decides how much you get back.
The reassuring half: existing videos stay watchable, viewers can still interact with the channel, and monetisation status is not affected by the pause. YouTube has not disclosed what specifically triggers one, which means there is no checklist for avoiding false positives — only the general advice to keep two-step verification on, which was already the advice.
Reason five: the daily custom thumbnail limit
Rare for most channels, routine for anyone doing a bulk packaging refresh across a back catalogue.
There is a cap on how many custom thumbnails a channel can upload per day. YouTube does not publish the number, and says it varies by country or region and by channel history. The error text to look for is "Daily custom thumbnail limit reached", and the documented fix is to try again in 24 hours.
The interesting part is what moves the limit. YouTube states that Community Guidelines strikes affect how many custom thumbnails you can upload, and that copyright strikes can affect channel-history eligibility. So a channel carrying enforcement history has a lower ceiling than a clean one, without being told what either number is. If you are relaunching old videos in batches, that is a reason to work in sessions across several days rather than one marathon. Spacing the swaps out is better measurement practice in any case: twenty simultaneous changes leave you unable to attribute whatever happens next to any one of them.
Reason six: the file is being refused
If the upload control is present and functioning, the problem is the image. The specifications here are also where the most stale advice on the internet lives.
YouTube's current help page for custom thumbnails gives limits that depend on the device you upload from, rather than one universal ceiling:
| Property | What YouTube's documentation gives |
|---|---|
| Formats | JPG, GIF or PNG |
| File size, mobile | 2 MB for video thumbnails, 10 MB for podcasts |
| File size, desktop | 50 MB for both video and podcast thumbnails |
| Recommended resolution | 3840 × 2160 pixels |
| Minimum width | 640 pixels |
| Shorts thumbnails | 9:16, 2160 × 3840 pixels, desktop Studio only |
Almost every third-party guide still quotes a flat 2 MB maximum and a 1280 × 720 recommendation, and for years that was right. Treat the device split as the operative rule: if your 4 MB export is bouncing, the overwhelmingly likely explanation is that you are uploading from the phone app, where the 2 MB ceiling still applies. Move to a desktop browser and the same file goes up.
Three practical notes. First, 1280 × 720 remains a perfectly good working size — it is 16:9, it clears the minimum width comfortably, and it is the smallest sensible export now that thumbnails get shown at near-full-screen sizes on TVs. Uploading at 1280 × 720 is not a mistake; believing it is a hard maximum is. Second, if a file genuinely needs to come down, do it by compression rather than by shrinking dimensions — our free image compressor will usually get a 4 MB PNG under 2 MB with no visible loss. Third, a thumbnail that uploaded successfully but looks soft is a different problem entirely — that is usually YouTube's re-encoding or a source image with too few pixels in it, not a refused upload.
Reason seven: the surface has its own rules
"Custom thumbnails" is not one feature. It behaves differently depending on what kind of upload you are packaging, and the differences are the source of a lot of false alarms.
| Surface | Where you can set a custom thumbnail |
|---|---|
| Long-form video | Anywhere Studio runs, desktop or mobile, subject to the device file limits |
| Shorts | Studio on a computer only; not available in the mobile app |
| Podcast playlist | Square image, set on the playlist rather than the episode |
| Live stream | Set in the Live Control Room before going live; verification applies there too |
The Shorts row is the one that generates most of the confusion, partly because YouTube's own documentation has not fully caught up with itself — one older Studio help page still says you cannot upload a custom Shorts thumbnail and should pick a frame instead, while the current pages describe uploading one in Studio on a computer. The behaviour to trust is the newer one. If you are looking for the Shorts thumbnail control in the phone app, it is not there, and that is by design rather than a fault on your channel. Our Shorts thumbnail guide covers what the image actually has to do once you can upload it, which is a different job from a long-form thumbnail.
Reason eight: your role on the channel, or the tool you are in
Two mundane cases that are easy to mistake for a channel-wide restriction.
The first is permissions. On a channel with multiple people, roles differ in what they can touch: managers can edit channel details and manage permissions, editors can edit and publish content, a limited editor loses revenue access, and a subtitle editor only ever sees the subtitles section of Studio. YouTube's role tables describe editors as able to edit content without naming thumbnails specifically, so if you are a collaborator who cannot upload one, the fastest test is to have the owner try the same action. Remember too that only the owner — or, on a Brand Account, the owner and managers — can phone-verify in the first place, so a team can be blocked by a verification step nobody present has the authority to complete. Mapping the roles against the actions you need is a five-minute job that saves an afternoon of guessing.
The second is the tool. The YouTube Studio app and the main YouTube app are not the same thing and neither is the full desktop Studio. When something that should exist does not, the first move is always the desktop browser. If you work mostly from a phone, assume one desktop session will be needed for the steps the apps do not expose — Shorts thumbnails and anything over 2 MB among them.
The thumbnail was there and then it was not
A separate symptom with a separate set of causes, and worth naming because it gets filed under the same search.
If a custom thumbnail you had uploaded is no longer showing, the candidates are: it was removed under the thumbnails policy, in which case you were notified and can upload a replacement; the video was age-restricted, which changes who sees it rather than removing the image; the upload never actually committed; or everything is fine on YouTube's side and a cache somewhere else is showing you a stale frame. That last case is far more common than it should be, because thumbnail previews are cached aggressively by social platforms and by YouTube's own surfaces at different intervals. The full diagnostic is in why your YouTube thumbnail is not showing, which separates the four cases in order of how long each takes to rule out.
The diagnostic, in order
Ten minutes, worst case, and it ends with a cause rather than a guess.
- Open desktop Studio. Not the app. Half of all reports end here.
- Look for a banner. A security-restriction notice means a Temporary Feature Pause; stop troubleshooting thumbnails and secure the account.
- Check notifications and email for a strike or a warning. An unacknowledged strike is a week that has not started counting.
- Settings, Channel, Feature eligibility. If intermediate features are not enabled, verify the phone number. This is the end of the story for most new channels.
- Confirm which channel you are in and which role you hold on it.
- Try the upload. If the control works but the file bounces, read the error: a size or format message is a file problem, "Daily custom thumbnail limit reached" is a 24-hour wait.
- Check the surface. Shorts need desktop Studio; podcasts want a square image on the playlist.
- If the control exists, the file is valid, and there is no banner or strike, sign out, sign back in and retry once before concluding anything. Studio's eligibility state is cached.
What to do with the waiting time
Most of the causes above resolve on a timer you do not control: 24 hours for a pause or a daily limit, a week for a first strike, 30 days for revoked thumbnail privileges. The temptation is to treat that as dead time. It is better treated as the one period where you can work on packaging without the pressure of a publish deadline.
Two things are genuinely worth doing. Build the thumbnails anyway, so that the moment access returns the queue goes out in one pass rather than becoming a second afternoon of design work — this is what Thumblore is for, and nothing about generating an image depends on your channel's feature eligibility. And use the gap to fix whatever caused the restriction, which for a strike means reading the policy that was cited rather than guessing, and for a pause means the security pass you have been putting off.
The deeper point is that custom thumbnails are a privilege in YouTube's model, not a property of your account. Verification grants it, enforcement takes it away, and a security system can suspend it without anyone having done anything wrong. That is worth knowing before the afternoon it matters, because the one thing none of these mechanisms allows is an exception for a video going live in an hour.