Give your links a useful preview when they are shared online

Automate your “link preview” thumbnails in minutes using HTML / CSS templates and a dead-simple, URL-based integration. This way, when your content is shared on other platforms, a nice, on-brand image with relevant information can be shown instead of a generic picture.Try it here

Read the docs
  • Infinitely customizable with the full power of HTML / CSS
  • Blazing fast CDN built on the Cloudflare network
  • Rendered pictures are cached and served at the edge

Example website for demo

Some longer website description for demo purposes

<meta property="og:image" content="<your-account>/blog.png" />

Preview how your current website looks like when shared

Enter the URL to a blog post, product page, etc, on a site and preview what it could look like with a starter template.

Use the

Thumbsmith GUI screenshot

Use our integrated online editor to create beautiful templates with real-time feedback.


Use the

Try it now !

Use your favorite code editor coupled with our live-updating development envionment.

Free for low traffic sites

Gain insights on your site's visibility across the webbeta

Thumbsmith stats page screenshot

We agregate logs from the CDN, clean them up, and make them available to you so you can get some awareness on how visible your links are across the internet.

Just give us some templates — we'll handle the rest

No need to manage file storage, cache invalidation, image generation or scalability.

Create a template or pick one from our list of starter templates, hook it up in your site's head and you're good to go !

Usage can vary a lot from site to site, so we got something for everyone.

How to estimate my usage ?

In general, you can expect 1 image per page that is shared at least once.

For example, if you have a website with 100 pages, and they all get shared and previewed once or more somewhere on the internet, that should cap at 100 images. Only the first request to a new image URL counts as an "image". You can also think of them as a "unique renders". If a cached image expires and is generated again, it will not be counted as a new image.

The pictures are only generated when needed. If you have a ten thousand URLs on day one, that doesn't mean that you will render ten thousand pictures. In other words, in general, only links that are shared / posted / seen somewhere on the internet get rendered and count towards your image counts.

For requests (traffic), it can vary a lot from site to site. We recommend you start with what makes sense, and adjust accordingly. Plan changes are prorated, so you won't be losing out by changing plans multiple times.

What happens if I go over my plan limit ?

From the settings page, you will be able to manage the "Overage strategy".
There are currently 2 options:

  • Stop processing the requests for non-cache hits
  • Keep rendering new pictures, but with a watermark

Cache hits will keep returning the thumbails as-is, but you should not rely on this as the cached assets aren't guaranteed to stay cached forever and are subject to CDN cache eviction.