Tube Site Script
Content and encoding

Video thumbnails, hover previews and timeline thumbnails: why they matter for clicks

How thumbnails, hover preview clips and timeline thumbnails affect click-through on a tube site, and how to choose, size and generate them with ffmpeg.

Updated 4 minute read The Tube Site Script team

Thumbnails, hover previews and timeline thumbnails are the three images that sell a video before anyone presses play. The thumbnail decides whether a visitor clicks from a listing page, the hover preview shows a few seconds of motion so they can judge the video without opening it, and timeline thumbnails let them scrub to the part they want once they are watching. Together they have more effect on click-through and viewing time than almost any other design choice on a tube site.

Why thumbnails matter so much

A tube site's listing pages are grids of small images. Visitors scan them in seconds and click on whatever looks most relevant and clear. A dark, blurry or misleading frame gets skipped, however good the video is. The same thumbnail also appears in search results that show video previews, in social shares through Open Graph and Twitter cards, and in your RSS feed. Improving thumbnails across a library is one of the cheapest ways to raise click-through rate.

Choosing a good thumbnail

  • Sharp and well lit. Avoid frames with motion blur, fades or dark scenes.
  • Clear subject. One readable subject works better than a busy wide shot at small sizes.
  • Representative. The thumbnail should honestly reflect the video. Misleading thumbnails raise clicks but increase bounces and complaints.
  • No intro cards or black frames. The first frame is often a logo or black; grab frames from across the video instead.
  • Consistent shape. Use one aspect ratio across a site so the grid stays tidy.

Generating several candidate frames automatically and letting an editor pick the best is a practical compromise for large libraries. Where you have click data, letting the best-performing frame rise to the top is better still.

Size and format

Thumbnails should be just large enough for the largest size your layout shows them, typically 320 to 640 pixels wide, and compressed as JPEG or WebP. Oversized thumbnails slow down listing pages, which matters on mobile. Set explicit width and height (or an aspect ratio in CSS) so the grid does not jump as images load, and lazy-load images below the first screen. The speed and mobile guide has more on this.

Hover previews

A hover preview is a short, silent clip that plays when a visitor points at a thumbnail on desktop, or in some layouts when it scrolls into view on mobile. It is usually built from several one or two second fragments taken from across the video, giving a quick overview of the content. Good practice:

  • Keep it short (a few seconds) and small (a few hundred kilobytes) so it starts instantly.
  • Encode at thumbnail size, not at full video resolution.
  • Only load it when it is needed, not for every card on page load.
  • Strip the audio.

Previews help visitors decide faster, which tends to increase clicks on the videos they do choose and reduce quick exits.

Timeline thumbnails

Timeline thumbnails (sometimes called scrub previews) appear above the player's progress bar as the viewer moves along it. They are usually generated as a single sprite image containing a grid of small frames, plus a WebVTT file that tells the player which part of the sprite matches each time range. This lets the browser load one image instead of hundreds. Viewers can jump to the section they want without guessing, which keeps them watching longer.

Generating them with ffmpeg

All three are normally created at encoding time with ffmpeg. Thumbnails are frames grabbed at set points; previews are short clips cut and joined; timeline sprites are frames taken at intervals and tiled into one image. Because this is done during encoding, a well-set-up encoding server produces them with no manual work. See video encoding settings for the web and installing ffmpeg.

Thumbnails for imported videos

When you import hotlinked or embedded videos, nothing is encoded locally, so you rely on the thumbnail URL the partner supplies. Download and store it on your own server or CDN if your terms allow, so it does not disappear or load slowly. See importing videos from CSV, XML and feeds.

Measuring the effect

Track click-through rate on listing pages: clicks divided by impressions. Compare it before and after changing thumbnail rules, layouts or preview behaviour. Watch for videos with many impressions but few clicks; a new thumbnail often fixes them. Thumbnail shape and size also differ between templates, so test what works for each site; see tube site template design.

How Tube Site Script handles thumbnails and previews

When Tube Site Script encodes a video with ffmpeg, it creates 10 thumbnails, an animated hover preview and timeline thumbnails (a sprite with a VTT file) used by the Video.js player. Cards in the bundled templates play the hover preview, and listing pages track clicks so the home page can be ordered by click-through. For imported hotlinks and embeds, you can supply a thumbnail URL in the thumb column.

Each site in a network can set its own thumbnail size and shape and choose what shows on its thumbnails through its template's appearance settings, so the same library can look quite different on each site. See the PHP tube script features and pricing.

Frequently asked questions

What size should video thumbnails be?

Just large enough for the biggest size your layout displays, typically 320 to 640 pixels wide. Larger images slow listing pages without looking better.

Do hover previews slow down a page?

Not if they are small and only load when a visitor points at a thumbnail. Loading every preview on page load would.

What is a VTT sprite?

It is one image containing many small frames from a video, plus a WebVTT file that tells the player which frame to show for each point on the timeline.

Get three guides like this every month, plus software update notices.Subscribe →