Leave a tip

What happens to your image

Nothing. It never leaves the tab you opened. This page explains how that works and what the tool does store.

The short version

Thumbnail Factory has no server to upload anything to. The whole tool is one HTML file served as a static page. When you choose a picture, the browser reads it off your own disk and draws it onto a canvas in the page. The finished thumbnail is produced by that same canvas and handed straight to your downloads folder. At no point does the image travel anywhere. The same goes for a video you start from: the frames are picked by playing it inside the page, and the video itself is never sent anywhere.

There is no account, no sign-in, no cookie and no tracking pixel. The page does send a few anonymous counts, described below, and none of them carries your picture or anything you typed.

How to check, rather than take my word for it

Open your browser's developer tools, switch to the Network tab, and use the tool normally. Choose a picture, type a headline, download the result. You will see requests for the page itself, for the fonts, and small requests to us.aptabase.com when the page opens and when you download. Open any of those and read its body: an event name, a size such as youtube, a layout name, and your browser's language. No request carries your image or your text, because no such request is ever made.

You can also disconnect from the internet after the page loads. Everything keeps working, which is only possible because the work happens on your device. The only difference is that the counts described below fail quietly.

What is stored, and where

The tool remembers a few things between visits so you do not have to set them up again. They are kept in localStorage, which is a store your browser keeps on your own machine, scoped to this site. It is not sent anywhere, and it is not readable by other sites.

  • The two lines of headline text
  • The size you last picked, and any custom width and height
  • Your headline colours
  • Your template and its settings
  • A logo you uploaded, if you replaced the default one

The picture you are working on is not stored. It lives in memory while the tab is open and is gone when you close it.

To clear everything, clear this site's data in your browser settings, or use a private window, where nothing is kept once you close it.

What is counted

To learn which sizes and layouts people actually use, the tool sends three kinds of anonymous event to Aptabase, a privacy-focused analytics service:

  • Opened, with the size and layout the tool started on
  • Downloaded, with the size and layout of the image you saved
  • Downloaded every size, with the layout

Each event also carries your browser's language and a random session number that lasts for an hour of use. The number is held only in the open tab; it is not stored on your device, so there is nothing to tie one visit to the next. No cookies are set. The code that sends these counts is written out in the page itself, not loaded from anyone else, so you can read exactly what it does.

Blocking us.aptabase.com stops the counts and changes nothing else. Opening the page as a file from your own disk sends nothing at all.

What the page does load from elsewhere

One stylesheet, from Google Fonts, for the typefaces the page and the headlines are set in, and one more for each other font you pick in the Text panel. Each request tells Google a font was requested from this site, in the ordinary way any web font does. It carries nothing about your image or your text. If you would rather avoid it, the page still works with those requests blocked; the headline simply falls back to a system typeface.

Starting from a video, the first time only, loads Google's MediaPipe face detector: its code from cdn.jsdelivr.net, about 12 MB, and a small model file from this site. The detector runs in the page, on your device, and looks at frames of your video there; the requests only fetch the detector and carry nothing about the video. With them blocked, frames are still picked, just without noticing faces.

Headline suggestions are worked out in the page from what you type. In Chrome, Ask Chrome's on-device AI asks the language model built into Chrome, which runs on your device: the title is handed to it inside the browser and goes nowhere else. The first time, Chrome downloads that model itself; the button is the only thing that starts it.

A font file of your own is read in the browser, used in the open tab, and not sent anywhere.

Why it is built this way

Most free thumbnail tools upload your picture to process it. That is a reasonable engineering choice and it is also how you end up agreeing to terms about what may be done with what you uploaded. Drawing on a canvas in the browser avoids the question entirely. There is no copy of your work to keep, so there is no policy needed about keeping it.

Go and make one.