Do these 3 things before closing this tab:
1Fix the driver behind crashes, sound loss and screen glitches2Clear out junk files and repair common Windows errors3Scan for outdated or missing drivers - takes under a minuteSome links on this page are affiliate links: if you buy through them we may earn a commission, at no extra cost to you.
There is no single best thumbnail ratio for every website. Choose the shape of the rendered slot, then create image variants at the pixel widths your layouts and devices require. Use 16:9 for Google Discover and standard YouTube videos, 9:16 for YouTube Shorts, and square imagery where WordPress or a podcast playlist calls for it. Keep important subjects inside each crop because platforms can crop or select previews automatically.
Choose the ratio from the display context
An aspect ratio describes shape, not image quality or file size. A 16:9 image can be delivered at 640, 1280 or 3840 pixels wide; those files have the same shape but different detail and download costs. Start by listing every place a thumbnail appears and define a crop for each slot.
| Placement | Ratio | Documented dimensions or limits | Crop and selection behavior |
|---|---|---|---|
| Google Discover large preview | 16:9 landscape is the documented example | At least 1,200 px wide and more than 300,000 total pixels; Google gives 1,280 × 720 (921,600 pixels) | Google may crop automatically. Keep the subject and essential text visible in the landscape crop. Large previews require max-image-preview:large or AMP. |
| YouTube standard video | 16:9 | Recommended 3,840 × 2,160; minimum width 640 px. The cited Help page lists JPG and PNG, with upload limits of 2 MB on mobile and 50 MB on desktop. | YouTube controls placement rendering; verify current limits before uploading. |
| YouTube Shorts | 9:16 | Recommended 2,160 × 3,840; minimum height 640 px. | A vertical video using a 16:9 custom thumbnail can appear as an automatically generated 4:5 thumbnail in Home, Explore and subscription pages, while the custom image appears in some other placements. |
| YouTube podcast playlist | 1:1 square | YouTube asks for a square thumbnail rather than 16:9. | Use a centered composition that survives a square crop. |
| WordPress default thumbnail | 1:1 square | Default size is 150 × 150 px, and the setting can be changed. | Responsive image attributes let the browser choose another generated file for viewport or pixel-density needs. |
| Custom site card or search result | Defined by your component | No universal standard | Set an explicit crop and provide art-directed variants when one source cannot work in both landscape and portrait slots. |
These are placement-specific recommendations, not a universal web rule. Social and search services can change specifications, so check the destination’s current documentation when you publish.
Google Discover and Search: prepare a representative image
Discover requirements
For Discover, use a relevant landscape image at least 1,200 pixels wide and above 300,000 total pixels. Google’s 1,280 × 720 example is 16:9. Supply a deliberate landscape crop rather than assuming a tall original will be reframed well. Keep faces, products and other decisive details away from edges where an automatic crop could remove them.
#1 Best Overall
- HTML CSS Design and Build Web Sites
- Comes with secure packaging
- It can be a gift option
Google’s guidance says to avoid automatically applying an aspect ratio. It can crop and position the image itself, so treat your supplied crop as a safe composition, not a guarantee of the final preview. Add max-image-preview:large when you want to be eligible for large previews (or use AMP as applicable).
Metadata helps, but does not control the result
Identify a representative image with og:image and an image in schema.org structured data. This gives crawlers clear candidates, but Google says image-preview selection is fully automated and can use multiple sources. Avoid generic logos, text-heavy graphics and extreme ratios. A metadata URL cannot force a particular crop or guarantee that Google will show that asset.
YouTube ratios and source dimensions
Standard videos
Prepare a 16:9 thumbnail. YouTube recommends 3,840 × 2,160 and accepts a source at least 640 pixels wide. JPG and PNG are among the listed formats. The cited limits differ by upload device: mobile video thumbnails are listed at 2 MB, while desktop video, Shorts and podcast thumbnails are listed at 50 MB. Compress within the applicable limit without making small text unreadable.
The Tool Desk
Outbyte PC Repair FREEClear out junk files and repair common Windows errorsFree Scan →Outbyte Driver Updater FREEScan for outdated or missing drivers - takes under a minuteDriver Scan →Shorts
Use a 9:16 canvas, with 2,160 × 3,840 recommended and at least 640 pixels in height. Do not assume the custom vertical image is identical everywhere: YouTube notes that some Home, Explore and subscription views can show an automatically generated 4:5 image instead.
Podcast playlists
Use a 1:1 square thumbnail. Design the central artwork to remain legible when reduced and avoid details that depend on a wide banner.
WordPress and responsive website cards
WordPress’s default thumbnail size is 150 × 150 pixels, but administrators can change image sizes and themes can register additional crops. The default is a preset, not a recommendation for every screen.
Separate crop from responsive delivery
Use a fixed ratio (or an art-directed crop) for the component, then generate several widths of that crop. In HTML, provide srcset and sizes so the browser can select an appropriate source. Explicit width and height, or a CSS aspect-ratio, reserves space before the image arrives and reduces layout movement.
Quick wins for a faster PC:
Fix the driver behind crashes, sound loss and screen glitchesFind Drivers →Repair Windows errors before they cause bigger problemsFix Now →Scan for outdated or missing drivers - takes under a minuteDriver Scan →<img
src="/images/story-640.webp"
srcset="/images/story-320.webp 320w,
/images/story-640.webp 640w,
/images/story-1280.webp 1280w"
sizes="(max-width: 640px) 100vw, 33vw"
width="1280" height="720"
alt="Description of the story image">The CSS ratio should match the selected crop:
.card-media {
aspect-ratio: 16 / 9;
overflow: hidden;
}
.card-media img {
width: 100%;
height: 100%;
object-fit: cover;
}If a portrait feed and a landscape card both need the same source, test both crops. When the subject cannot survive both, create separate art-directed files rather than relying on one automatic center crop.
A practical thumbnail workflow
- Inventory slots. Record the component, rendered CSS width, expected device-pixel ratio, and whether a platform will recrop it.
- Choose a composition. Select 16:9, 9:16, 1:1 or your component’s measured shape. Keep faces, logos and labels inside a generous safe area.
- Generate variants. Export multiple widths for each crop. Do not confuse the CSS display width with the only source width; high-density screens may need more pixels.
- Publish metadata. Set
og:imageand relevant structured-data image properties for pages that can appear in search or sharing previews. - Reserve layout space. Add intrinsic dimensions or a CSS aspect-ratio constraint before lazy loading.
- Inspect real placements. Check narrow and wide viewports, 1× and 2× displays, slow loading, missing images and the platform’s own preview tools.
- Recheck volatile rules. Upload limits, accepted formats and automatic crops can change; verify official destination documentation before a release.
Image format, crop and performance decisions
Choose a format your destination accepts and that preserves the image’s important detail at the target byte size. A thumbnail that is technically the right ratio but unreadable after compression fails its purpose. Keep text large enough for the smallest rendered slot, and avoid putting critical information at the extreme edges.
Rank #3
Use lazy loading for below-the-fold cards, but do not lazy-load the primary image needed immediately for a page’s first view. Serve only the selected width rather than downloading a full-resolution master into a small card. Caching and a consistent naming scheme make regenerated crops easier to roll out.
Common mistakes and fixes
Using one ratio everywhere
Symptom: a face or product is cut off in a portrait feed or square widget. Fix: create a slot-specific crop, or protect the subject with a safe area and test the actual platform crop.
Meeting a ratio but not a pixel requirement
Symptom: a 16:9 image looks soft in a large preview. Fix: increase source width and provide responsive variants; ratio alone does not create detail.
Relying on metadata to force a preview
Symptom: a search or social preview shows another image. Fix: make the representative image relevant, expose it through og:image and structured data, and accept that selection and cropping remain automated.
Rank #4
- Brand: Wiley
- Set of 2 Volumes
- A handy two-book set that uniquely combines related technologies Highly visual format and accessible language makes these books highly effective learning tools Perfect for beginning web designers and front-end developers
Layout shift while images load
Symptom: text jumps when a card image arrives. Fix: include dimensions or an aspect-ratio constraint before the request completes.
Unexpected YouTube Shorts crop
Symptom: the custom 9:16 artwork is not shown in every feed. Fix: design a readable central region that also works in YouTube’s possible 4:5 automatic representation.
Free tools Windows power users keep installed
One-click scans. No signup required.
Or skip the browser setup
If you need rendered website thumbnails rather than source-art files, ScreenshotNeo returns a PNG, JPEG, WebP or PDF from one GET request. It can load lazy images, capture a CSS-selected element, set a viewport or device preset, use retina scale, dark mode, custom CSS and JavaScript, click before capture, wait for a selector, delay or network idle, block ads and trackers, supply headers, cookies, a user agent, authorization, timezone or geolocation, resize output, cache with a chosen TTL, create signed image links, run asynchronous jobs with signed webhooks, capture up to 100 URLs per bulk call and report usage. Its 63 options include the parameter names used by other screenshot APIs, which eases migration.
Before capture it accepts cookie or consent banners and removes more than 60 known consent platforms, newsletter popups and chat widgets; each cleanup step can be disabled. Bot checks, CAPTCHAs, blank pages, timeouts, failed loads and cache hits are not billed, and response headers identify the page verdict and billing result.
Use the API documentation at screenshotneo.com/docs/ for the complete option list.
cURL
curl -G "https://api.screenshotneo.com/v1/shot" -d access_key=YOUR_API_KEY --data-urlencode url=https://stripe.com -o shot.webpPython
import requests
r = requests.get("https://api.screenshotneo.com/v1/shot", params={"access_key": "YOUR_API_KEY", "url": "https://stripe.com"}, timeout=90)
open("shot.webp", "wb").write(r.content)Node.js
const q = new URLSearchParams({ access_key: 'YOUR_API_KEY', url: 'https://stripe.com' });
const res = await fetch(`https://api.screenshotneo.com/v1/shot?${q}`);ScreenshotNeo also provides an MCP server with take_screenshot, get_page_info and capture_pdf tools for Claude, Cursor and other MCP clients. The Free plan includes 1,000 shots per month without a card; paid plans start at $5 for 3,000 shots. Other plans are Starter $5/3,000, Growth $15/15,000, Pro $39/60,000, Scale $99/250,000 and Business $249/1,000,000; yearly billing gives two months free, and every feature is on every plan. Sign up for the free plan.
Frequently Asked Questions
Should every website thumbnail be 16:9?
No. Use the ratio of the rendered slot: 16:9 is common for landscape previews, 1:1 for square components and 9:16 for portrait feeds such as Shorts.
Is a larger image always better?
Only when the display needs the extra pixels. Keep the ratio and crop correct, then let responsive image selection deliver an appropriate width for the viewport and pixel density.
Can I guarantee which image Google shows?
No. Representative metadata improves the candidate signal, but Google selects and crops previews automatically.
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.
