What this tool does
The thumbnail maker takes one image — pulled from a YouTube link or chosen from your device — sets a kicker and a headline over it in one of 5 templates, shows the result at the small sizes the YouTube thumbnail specs guide says matter, and exports a 1280×720JPG or PNG that it decodes again before offering the download. Every rule below is the engine’s own; the methodology collects the same rules for every tool.
One fixed canvas
The renderer draws on exactly 1280 by 720 pixels, a 16:9ratio, and every export is checked against those two numbers. The size is the engine’s, not the platform’s. The table carries what YouTube’s own help page states, with the date each figure was read.
| YouTube thumbnail | Official value | Status | Verified |
|---|
| recommended resolution | 3840×2160 pixels (16:9) for videos; 2160×3840 for Shorts | Changed since the August 2026 guide | 2 October 2026 |
| minimum width | 640 pixels wide (videos); 640 pixels tall for Shorts | Confirmed | 2 October 2026 |
| aspect ratio | 16:9 for videos | Confirmed | 2 October 2026 |
| file size limit | 2 MB when uploading from mobile; 50 MB when uploading from desktop (video thumbnails) | Changed since the August 2026 guide | 2 October 2026 |
| accepted image formats | Image formats such as JPG or PNG | Changed since the August 2026 guide | 2 October 2026 |
Read the first row against the canvas. A 1280×720 export satisfies the stated minimum width and the 16:9 ratio, but it is not the recommended resolution, and the tool does not upscale to reach it. Verify against the official page before a launch, as the guide says.
Reading a YouTube link
The parser reduces whatever you paste to one video id or refuses it with a specific message. A bare id is accepted as it is. Otherwise the text is read as a URL — a missing scheme is tolerated — and the host must be one the engine lists: the platform’s own hosts and its short share domain. On the share domain the id is the first path segment; elsewhere it is the v parameter or the second segment of a Shorts, embed, live or v path. Each result below is computed from the fictional id aB3dE5fG7hI.
| Input | What it is | Parser result |
|---|
| https://www.youtube.com/watch?v=aB3dE5fG7hI&list=PLx9 | Watch URL with a playlist parameter | id aB3dE5fG7hI |
| youtu.be/aB3dE5fG7hI?t=42 | Share link, timestamp, no scheme | id aB3dE5fG7hI |
| https://www.youtube.com/shorts/aB3dE5fG7hI | Shorts URL | id aB3dE5fG7hI |
| aB3dE5fG7hI | The bare id | id aB3dE5fG7hI |
| https://example.com/watch?v=aB3dE5fG7hI | A host that is not YouTube | “This is not a supported YouTube URL.” |
Which platform image it fetches
With an id, the tool asks the platform’s own image host for its stored thumbnails, largest first, and accepts the first that decodes and clears that candidate’s width floor (plus a small height floor the engine keeps). For the same fictional id, in the order tried:
| Candidate | URL requested | Width floor |
|---|
| Maximum resolution | https://i.ytimg.com/vi/aB3dE5fG7hI/maxresdefault.jpg | 1000 pixels |
| Standard definition | https://i.ytimg.com/vi/aB3dE5fG7hI/sddefault.jpg | 600 pixels |
| High quality | https://i.ytimg.com/vi/aB3dE5fG7hI/hqdefault.jpg | 400 pixels |
| Medium quality | https://i.ytimg.com/vi/aB3dE5fG7hI/mqdefault.jpg | 300 pixels |
The notice reports which candidate loaded and its decoded size; if every candidate fails, nothing is loaded. Pulling is the only time the tool fetches an image. One chosen from your device — a JPG, PNG or WebP under the ceiling the tool keeps — is read locally, and the notice says so.
Fitting the picture, then shading it
Any image is cover-fitted: scaled until it fills the canvas, then cropped on the overhanging axis. The renderer accepts an optional focus point and a clamped zoom; the tool page leaves both at their defaults, so the crop is centred. A source narrower than the canvas is enlarged by the same fit; no pixels are added. With no image, the renderer paints a dark field crossed by diagonal accent rules so the type can be judged first.
Two gradients then go over the picture. The image-shade slider drives the first, whose direction follows the text position — from the left edge, from the right edge, or radially from the centre — so the darkening sits behind the words; the renderer clamps the slider to its own range. The second is always drawn: a protective scrim down the text band, light at the top, passing through the engine’s scrim opacity of 0.76 (76%) part-way down and darker still at the bottom edge. It spans the full width when the text is centred and a fixed band on the text’s side otherwise. The slider is yours; the scrim is the engine’s.
The 5 templates
- Editorial — Ink gradient and eucalyptus rule.
- Tutorial — Clear label and structured title block.
- Interview — Quiet lower-third composition.
- Minimal — Image-led with restrained typography.
- Before / after — Measured split-field comparison.
Only 3 of the 5 have their own code path in the renderer. Before / after tints the left half and draws an accent divider down the centre line at x = 640; Tutorial paints a block in the resolved accent behind the kicker and sets the kicker in near-white on top of it; Minimal starts the headline at a smaller preferred size and a lighter weight. Editorial and Interview share the default drawing and differ only in their names and descriptions.
The one colour the site changes
Across PromoGenerator a picked colour is honoured exactly and readability is only advised; the methodology sets out that doctrine. The overlay title is its single exception, because the type is drawn over a photograph the design cannot predict. The renderer does not read the photo. It assumes the hardest case for light text — a pure white background — composites the scrim’s dark tone over it at 0.76 opacity, giving the protected background #454948, and checks the requested colour against that. A colour meeting the engine’s default minimum ratio, which matches the WCAG AA text figure of 4.5:1 (verified 2 October 2026), is kept; one that fails becomes the engine’s dark ink or white, whichever contrasts more. The kicker is requested in the accent, the headline in white.
| Requested | Resolved | Contrast against #454948 |
|---|
| White, #ffffff | kept #ffffff | 9.13:1 |
| A warm yellow (fictional), #f5d547 | kept #f5d547 | 6.30:1 |
| A muted green (fictional), #4a7c6f | replaced by #ffffff | 9.13:1 |
| A dark slate (fictional), #23302b | replaced by #ffffff | 9.13:1 |
Because the protected background is the same every time, the substitute is too: the muted green and the dark slate both come back as #ffffff, while the yellow survives at 6.30:1. A kicker that should carry the accent needs a light accent.
How the headline is fitted
The kicker is set in capitals on one line; an empty kicker falls back to NEW RELEASE and an empty headline to Your thumbnail title. The headline goes through the shared fitter: from the template’s preferred size it wraps the words into the title box and steps the size down one pixel at a time until every line fits; if even the minimum size cannot hold them, it keeps the lines that fit and ends the last with an ellipsis, flagging the layout as truncated. The box is a fixed band in the middle of the canvas, narrower for left- and right-anchored text. A fictional box shows the mechanism: 600px wide and 300px tall, preferred size 80px, minimum 40px, measured by a stand-in that charges every character 0.55of the font size because no canvas exists at build time. In it, “Seven ways to light a small kitchen without rewiring anything” settles at 64px over 4 lines: Seven ways to / light a small / kitchen without / rewiring anything. In a 120px-tall box of the same width it reaches the box’s minimum of 40px and is truncated: Seven ways to light a small / kitchen without rewiring a…The renderer’s own box, minimum size and line spacing are different, and it measures real glyphs, so this is the fitter’s behaviour, not a prediction of the tool’s output.
Safe zones and the small previews
With the checkbox on, the preview draws dashed zones for the duration badge (bottom-right), the hover controls (top-right) and the bottom strip. Only the first rests on a guide sentence — the duration-badge figure has no official source and keeps its August 2026 wording (No official source; August 2026 wording kept); the others are the tool’s own reservations. Every zone is preview-only: the export is rendered without them. Beneath the main canvas the same rendering appears in a strip of small previews labelled home, search, sidebar and mobile, each with a mock duration badge, because the design must survive the smallest of them.
Export and verification
Export re-renders the canvas without the safe zones and encodes it as JPG at a fixed quality or as lossless PNG. A JPG above the tool’s size target is encoded once more at a lower quality; a PNG is never shrunk. The blob is decoded again and its pixel size compared with 1280 by 720; a mismatch throws and no file is offered. The notice reports the verified size, the format and the file size in megabytes. The clean thumbnail never receives a QR code.
Where it stops
- It renders at 1280×720 only: no upscaling to the recommended resolution, no vertical Shorts image.
- It does not read your photo: the colour check assumes a white background, so a dark photo is protected more than required, never less.
- It does not judge the design or claim how a thumbnail will perform; the small previews show the degradation and the decision is yours.
- It does not enforce the platform’s file-size limits beyond the single JPG re-encode.
Common misreadings
- “Verified” means decoded and measured — the pulled image at its reported size, the export at 1280×720. It is not an opinion on the picture.
- “Maximum resolution” is the first candidate the engine tries, the one with the highest width floor (1000 pixels); it can still be narrower than the canvas, and the renderer enlarges it.
- Turning the image-shade slider to its minimum does not remove the scrim behind the type; the two are separate layers and only the first is yours.
Questions
- Why is the export fixed at 1280×720 when the official page recommends a larger resolution?
- The canvas size is the engine's constant and every export is checked against it. The official recommendation read on 2 October 2026 is 3840×2160 pixels (16:9) for videos; 2160×3840 for Shorts. A 1280×720 export still meets the stated minimum width and the 16:9 ratio, but it is not the recommended resolution, and the tool does not upscale.
- Does the tool read my photo to decide the title colour?
- No. The renderer assumes a pure white background behind the type, composites its scrim's dark tone over it at 0.76 opacity to get #454948, and checks the requested colour against that. A colour below the engine's default minimum ratio, which matches the WCAG AA figure of 4.5:1 (verified 2 October 2026), is replaced by the engine's dark ink or white, whichever contrasts more.
- Why did my kicker come out white?
- The kicker is requested in the accent colour. A mid-tone accent such as the fictional #4a7c6f fails the check and is replaced by #ffffff, which measures 9.13:1. A lighter accent such as the fictional #f5d547 is kept at 6.30:1.
- Is anything uploaded when I pull a thumbnail or choose an image?
- Pulling fetches the platform's stored images for the video id from its own image host, in the order Maximum resolution, Standard definition, High quality, Medium quality, and keeps the first that decodes and clears its width floor. An image chosen from your device is read locally; the notice confirms that nothing was uploaded.
- Why is the duration safe zone in the bottom-right corner?
- Because the guide's sentence places the badge there: YouTube overlays the video duration badge on the bottom-right corner of every thumbnail (site wording, Verified August 2026). The hover-controls and bottom-strip zones are the tool's own reservations. Every zone is a preview aid; the export is rendered without them.
- Can I put a QR code on the thumbnail?
- No. The clean thumbnail never receives a QR code. QR and clickable actions go on the coordinated off-platform assets where they help instead of covering the YouTube creative.
Everything here runs in your browser: the tools compute on your device and the Studio’s package is assembled on the device. The methodology documents every rule the tools apply.