Social Media Thumbnail Size: A Complete Platform Guide

There is no single correct social media thumbnail size. The right dimensions depend on the platform and the placement: a video cover, feed image and link preview use different aspect ratios and may crop the same file differently.

As a practical starting point, use the table below, then confirm the platform’s current upload guidance before publishing. YouTube’s current official recommendation for a standard-video custom thumbnail is 3840 × 2160 pixels (16:9). For Shorts, it recommends 2160 × 3840 pixels (9:16). The other figures in the table are secondary-reference starting points rather than universal official specifications.

Quick reference by platform and placement

Platform	Placement	Starting dimensions	Aspect ratio	Source status
YouTube	Standard video custom thumbnail	3840 × 2160 px	16:9	Current official guidance
YouTube	Shorts custom thumbnail	2160 × 3840 px	9:16	Current official guidance
Instagram	Feed image	1080 × 1350 px	4:5	Secondary reference
Facebook	Link preview	1200 × 630 px	1.91:1	Secondary reference
X	Image or card-style preview	1600 × 900 px	16:9	Secondary reference
LinkedIn	Link preview	1200 × 627 px	1.91:1	Secondary reference
TikTok	Vertical video cover	1080 × 1920 px	9:16	Secondary reference

The non-YouTube figures above come from a SocialRoute cross-platform reference updated in August 2026. Treat them as production starting points and check the destination’s current documentation, because platforms can change rendering and upload rules.

Why dimensions and aspect ratio both matter

Pixel dimensions describe the file’s resolution. Aspect ratio describes its shape. Two files can contain the same subject but display very differently when one is 16:9 and the other is 9:16.

16:9 landscape: common for standard video thumbnails and wide previews.
9:16 portrait: used by Shorts and vertical-video surfaces.
4:5 portrait: a useful feed canvas when you want more vertical space without filling a phone screen.
1.91:1 link preview: a wide card shape used by several social link-preview layouts.

Design the subject and essential text for the crop, not only for the original canvas. Keep faces, product edges and key words away from the outer margins. There is no universal safe-area measurement across all platforms, and overlays or responsive crops can differ by surface.

YouTube thumbnail size and current rules

YouTube’s custom-thumbnail guidance says standard videos should use a 16:9 image and recommends 3840 × 2160 pixels. Shorts use 9:16 at 2160 × 3840 pixels. YouTube also says the custom thumbnail should be as large as possible.

Do not confuse 1280 × 720 with the current recommendation

1280 × 720 is still relevant in YouTube’s thumbnail experiment documentation: images below 720p are downscaled to 854 × 480 for experiments. That threshold does not replace the current 3840 × 2160 recommendation for standard-video uploads.

Shorts can appear with different crops

For vertical videos, YouTube may replace a custom 16:9 thumbnail with an automatically generated 4:5 thumbnail on Home, Explore and subscription pages. The custom image can still appear on other listed surfaces, including the watch feed, watch history and non-mobile platforms. Shorts thumbnail changes are currently available through YouTube Studio on a computer.

YouTube file checks

Use JPG or PNG.
Keep the standard-video canvas at 16:9 and the Shorts canvas at 9:16.
Mobile upload limits listed by YouTube are 2 MB for video thumbnails and 10 MB for podcasts.
Desktop limits listed by YouTube are 50 MB for video, Shorts and podcast thumbnails.

Choosing a size when one design must serve several platforms

List every placement. Separate video covers, feed posts and link previews.
Choose the dominant crop. Use 16:9 for landscape video, 9:16 for vertical video, 4:5 for a tall feed image, or 1.91:1 for a link card.
Build a master file. Work at the largest required dimensions, then create explicit derivatives rather than relying on automatic cropping.
Keep the focal subject central enough to survive cropping. Leave room for platform badges, timestamps and title overlays.
Export and inspect each derivative at phone size. Fine text that looks readable at full resolution may disappear in a feed.

Export checklist

Confirm the exact placement: video thumbnail, feed image or link preview.
Set the intended aspect ratio before composing.
Export at the target pixel dimensions or larger.
Use JPG for photographs and PNG when transparency or sharp graphic edges matter.
Compress until the file meets the destination’s current limit.
Check faces, logos and text after the platform’s expected crop.
Preview on both desktop and a narrow phone viewport.
Recheck official specifications before a scheduled campaign.

Generate and inspect thumbnails programmatically

If you produce many thumbnails from web pages, you can capture a page or a specific element at the required viewport and then resize the resulting image to each platform’s canvas. A browser-based workflow gives you control over viewport, device scale and CSS.

DIY browser workflow

Open the page in a headless browser at the target aspect ratio.
Wait for the hero image and fonts to load.
Hide cookie banners, chat widgets and other overlays.
Capture the full page or the thumbnail element.
Resize or crop into 16:9, 9:16, 4:5 and 1.91:1 derivatives.
Inspect the exports at the destination’s display size.

Automated captures should also handle lazy-loaded images, consent dialogs, bot checks, timeouts and pages that render different content by device or location.

Or skip the browser setup

ScreenshotNeo returns a PNG, JPEG, WebP or PDF from one GET request and supports full-page or CSS-element captures, viewport and device presets, retina scale, custom CSS and JavaScript, waits, blocked resources, headers, cookies, user agents, timezone and geolocation. Cookie and consent banners, newsletter popups and chat widgets are removed before the shot. Bot checks, blank pages, failed loads, timeouts and cache hits are not billed, and the response reports the page verdict and billing status in headers.

See the ScreenshotNeo API documentation for all options.

cURL

curl -G "https://api.screenshotneo.com/v1/shot" -d access_key=YOUR_API_KEY --data-urlencode url=https://example.com -o thumbnail.webp

Python

import requests
r = requests.get("https://api.screenshotneo.com/v1/shot", params={"access_key": "YOUR_API_KEY", "url": "https://example.com"}, timeout=90)
r.raise_for_status()
open("thumbnail.webp", "wb").write(r.content)

Node.js

const q = new URLSearchParams({ access_key: 'YOUR_API_KEY', url: 'https://example.com' });
const res = await fetch(`https://api.screenshotneo.com/v1/shot?${q}`);
if (!res.ok) throw new Error(`HTTP ${res.status}`);
const buffer = Buffer.from(await res.arrayBuffer());
require('fs').writeFileSync('thumbnail.webp', buffer);

ScreenshotNeo includes an MCP server with take_screenshot, get_page_info and capture_pdf tools for Claude, Cursor and other MCP clients. It also supports caching with a chosen TTL, asynchronous jobs with signed webhooks, bulk capture of up to 100 URLs per call and a usage API. The Free plan includes 1,000 shots per month without a card; paid plans start at $5 for 3,000 shots. Every feature is available on every plan.

Create a free ScreenshotNeo account and start with 1,000 screenshots per month at no charge.

Troubleshooting

Problem	Likely cause	Fix
Text is cut off	The platform applied a tighter crop.	Move critical content inward and export a placement-specific derivative.
Thumbnail looks soft	The source is too small or was enlarged repeatedly.	Start from the recommended pixel dimensions or larger and export once.
Important subject disappears on Shorts	A 16:9 composition was used for a 9:16 surface.	Create a dedicated 9:16 version and check YouTube’s surface-specific crop.
Link preview has the wrong shape	A feed or video canvas was supplied to a link-preview slot.	Use the destination’s link-preview ratio, such as the 1.91:1 starting point, and verify current guidance.
Automated capture contains a popup	The page overlay appeared after the initial load.	Wait for the selector or network idle, hide the popup selector, or use ScreenshotNeo’s consent and widget removal.
Capture is blank or blocked	Bot checks, failed resources or a timeout interrupted rendering.	Inspect the response verdict headers, increase the wait or timeout, and retry with appropriate headers or user agent.

Performance, reliability and cost notes

Render only the viewport or element you need when a full-page capture is unnecessary.
Use caching with a TTL for unchanged pages and batch up to 100 URLs when generating a set.
Wait for a selector or network idle when fonts and lazy images affect the composition; fixed delays are simpler but can waste time.
For production pipelines, use asynchronous jobs and signed webhooks so a slow page does not block a request worker.
Read X-Page-Verdict and X-Billed to distinguish a clean, billable shot from a failed or free result.
Costs depend on successful clean shots: failed loads, bot checks, blank pages, timeouts and cache hits are not billed.

FAQ

No. It is a common 16:9 working size and a YouTube experiment threshold, but YouTube’s current standard-video recommendation is 3840 × 2160.

Should every platform get the same image?

No. Create derivatives for each placement’s ratio and crop behavior.

What size should a link preview be?

Use the platform’s current link-preview specification. The 1200 × 630 and 1200 × 627 figures are practical secondary-reference starting points for Facebook and LinkedIn.

Can I use a vertical thumbnail for a standard YouTube video?

You can upload different artwork, but standard videos are designed for 16:9 and vertical-video surfaces may crop or replace the image.

How often should I recheck these dimensions?

Before a new campaign, product launch or publishing integration, because platform specifications and surface behavior can change.