You changed the thumbnail. Studio shows the new one. Everywhere else shows the old one. Or the upload button was never there. Or you sent the link to a group chat and last week's image came back.
These look like one problem. They are four, with four causes, and one has nothing to do with YouTube. Find your symptom, then read that section.
| What you are seeing | What is actually happening | Yours to fix? |
|---|---|---|
| No "Upload file" option under Thumbnail | The account is not verified. Custom thumbnails sit behind phone verification | ✓ |
| Upload fails or snaps back to the old image | Wrong format, or over the size limit for that device | ✓ |
| "Daily custom thumbnail limit reached" | The channel hit YouTube's per day upload cap | ✓ |
| Thumbnail vanished, and you got an email | Removed under the thumbnails policy, sometimes with a strike | ✓ |
| New on the watch page, old in feeds | Normal propagation across YouTube's own surfaces | ✗ |
| Old image in WhatsApp, Discord, Slack, Facebook | That app cached the picture against your link | ✗ |
Why is there no option to upload a custom thumbnail?
Because the account is not verified, and verification is the gate. YouTube's help page is direct about it: you can pick a suggested thumbnail, or upload your own "if your account is verified".
Verification means a phone number. YouTube sends a code by text or voice call, you enter it, and the feature turns on. No subscriber count, no watch hours, no waiting period. The same step also unlocks uploads longer than 15 minutes, live streaming, and appealing copyright claims.
This is not the verification badge next to big channel names. That is a separate programme. Phone verification is administrative, and open to everyone.
Why did my upload fail, or bounce back to the old image?
Three documented reasons, in the order you should check them.
The file. YouTube accepts JPG or PNG. The size cap depends on where you uploaded from, which is the part that catches people out: 2 MB for video thumbnails on mobile, 10 MB for podcasts, 50 MB on desktop. The same file can be rejected on your phone and sail through on a laptop. YouTube recommends 3840 by 2160, a minimum width of 640 pixels, and a 16:9 ratio. The full set of numbers is in the YouTube thumbnail size guide.
The daily cap. If you see "Daily custom thumbnail limit reached", you hit a per channel cap and YouTube tells you to try again in 24 hours. It publishes no fixed number, and says the limit varies by country or region and by channel history, with copyright strikes affecting eligibility. If you have been swapping thumbnails all afternoon, this is you.
The guidelines. Thumbnails are reviewed against Community Guidelines. YouTube lists nudity or sexually provocative content, hate speech, violence, and harmful or dangerous content, and says a thumbnail containing them may be rejected with a strike attached. Repeat offences can cost you custom thumbnails for 30 days, or the channel.
How long does a new thumbnail take to update everywhere?
YouTube does not publish a number. The only commitment on its help page is one sentence: "It may take time for your thumbnail changes to appear on YouTube." No hours, no upper bound, no status indicator. Anyone quoting a precise figure is quoting a forum post.
What creators consistently report, and what you can watch happen on your own video, is an order rather than a duration. Studio and the watch page flip first, usually at once. Already loaded feeds keep the old image until they fetch again. Search and the suggested sidebar settle last. That ordering is observed behaviour, not a published schedule.
Before deciding it is stuck, separate what YouTube is serving from what your browser is holding. Pull the image straight off YouTube's servers with the thumbnail grabber. New picture back means YouTube has it and the rest is caching. Old picture back means the save did not go through.
One documented case looks like a failure and is not. YouTube says vertical videos with 16:9 custom thumbnails "will be replaced by an auto-generated 4:5 thumbnail on the home, explore, and subscription pages", while your custom image still shows on the watch feed, watch history, and non-mobile platforms. Wrong on the phone home feed, right on desktop, nothing is broken.
Why does WhatsApp, Discord, Slack or Facebook still show the old thumbnail?
Because that app is not asking YouTube. It saved a copy of the image the first time somebody posted that link, and it is showing you its own copy. Almost every article on this gets it wrong, so it is worth being precise.
A YouTube watch page carries an og:image tag. On any watch page today it points at an address built from the video ID, in the shape i.ytimg.com/vi/VIDEO_ID/maxresdefault.jpg. Change your thumbnail and the picture at that address changes. The address does not. Chat and social platforms key their preview cache on the address, so a link they have seen before is never re-fetched.
Meta is the one platform that hands you a lever. Its sharing guidance tells developers to "pre-cache your images by running the URL through the URL Sharing Debugger tool", adding: "You should also do this if you update the image for a piece of content". Paste the watch URL into that debugger, press Scrape Again, and Facebook and Instagram previews correct themselves.
WhatsApp, Discord, Slack and iMessage publish no equivalent tool and no cache lifetime. What follows from the mechanism is to give them a link they have never seen. Add a parameter such as ?utm_source=newsletter, or switch between the youtube.com/watch?v= and youtu.be/ forms. Different string, different cache entry, fresh fetch. In Slack, users commonly report that deleting the message and posting again clears it, though Slack documents no refresh window.
The part nobody tells you: previews already sitting in other people's chat histories are not yours to change. Those images live inside messages that were already delivered, and there is no creator-side flush for them. If a thumbnail matters for a launch, settle it before the first share. Checking it against a feed mock in the thumbnail preview tool costs less than chasing caches afterwards.
Why is my thumbnail blurred or turned off in search?
Three things get called this: turned off in search, removed under policy, and blurred behind somebody else's search query. All three are documented, and only two are about your image.
Turned off, which YouTube documents. The help page carries a section headed "Why are my custom thumbnails turned off?", and the answer is one line: YouTube "may turn off custom thumbnails for certain search results when they're considered inappropriate for viewers." Turned off, not blurred. Your thumbnail is replaced in those results, with no notification and no appeal path.
Removed under policy, which YouTube also documents. This one is loud. You get an email and an alert in Channel Settings at your next sign in. The thumbnails policy splits the outcome in two. The softer one: "Sometimes, a thumbnail may not be appropriate for all audiences, but it doesn't violate our Community Guidelines. When that happens, we may age-restrict the video, or we may remove the thumbnail, but we don't issue a strike on your channel." The harder one: "If your thumbnail contains pornography, we may terminate your channel. If your thumbnail violates other policies, we remove the thumbnail and may issue a strike against your account." You can appeal, and YouTube says that if the appeal is approved "and you haven't already replaced the thumbnail, we may restore it." Read that clause twice. Putting a replacement up before you appeal removes the thing that would have been restored.
Blurred, which YouTube now documents, and which is not about your image. The trigger is the query the viewer typed. Under "Managing potentially sensitive search results", YouTube's page on how search works describes "measures for search queries that might lead to potentially sensitive or graphic content": when "your search query is identified as seeking this type of content, search result thumbnails will be blurred by default. Inline video playback will also be turned off." Every result on that page is blurred, not just yours. The viewer still sees "the video title, channel name, and details", and: "If you prefer to view the thumbnails as usual, you'll always have the option to turn off blurring." Reported as an experiment in April 2025, it is documentation now.
So if a viewer says your thumbnail looked blurred and you cannot reproduce it, the answer is the search they ran, not anything you did. Nothing is logged against your channel and there is nothing to appeal, because no action was taken against you. The only lever here is the viewer's own: they can turn blurring off.
The order to work through
- Is the upload option there? If not, verify the account. Nothing else matters yet.
- Did the save stick? Reload Studio. If the image bounced, check the format and the size limit for the device you uploaded from.
- Does the watch page show the new one? If yes, YouTube has your file, and everything after this is caching.
- Is the old image only in a chat or a social post? Their cache. Sharing Debugger for Meta, a changed URL everywhere else.
- Did you get an email or a Channel Settings alert? That is a policy removal. Appeal first, replace second.
- None of the above? Give it time. YouTube will not say how much, and no tool speeds its feeds up.
Three of these are yours and get fixed in minutes. Two are somebody else's cache, fixed by waiting or by changing the link. The useful skill is telling them apart before you spend an evening re-uploading the same file.
Every check above is free. Our thirteen browser tools run on your own machine, upload nothing and need no account. DesignerOP itself is prelaunch and waitlist only, so the builders are not open yet, and the FAQ lays out what is live today.