About EbookScreensaver

Why it exists

Every e-reader expects its screensaver at one specific pixel size, and almost none of them scale gracefully. Feed a Kobo Clara an image meant for a Paperwhite and you get letterboxing or a stretched, soft picture. The correct dimensions are scattered across forum posts, spec sheets and manufacturer pages that often disagree.

The obvious fix is a resizer that already knows the right number for your device, so you pick a model instead of looking one up. That is the whole product. Everything else on the site — the size chart, the per-device pages, the setup guides — exists because getting the image right is only half the job. Actually putting it on the device is different on every platform.

Your images are never uploaded

All cropping and resizing happens locally, in your browser, using the HTML canvas API. Image files are never transmitted to a server, never stored, and never seen by anyone but you. There is no upload step to opt out of — the tool works offline once the page has loaded, which is the simplest way to verify the claim yourself.

There are no accounts, no watermarks, no paid tier and no export limits.

Where the device data comes from

The resolution, screen size and aspect ratio for each model are checked against the manufacturer's published specifications. Pixel density is not copied from anywhere — it is calculated from the resolution and the diagonal screen size, so it cannot drift out of step with the other numbers on the page.

Setup instructions are written per platform rather than per model, because the procedure is the same across a manufacturer's range. Where a menu path is stated — Kindle, Kobo and KOReader — it has been followed on the device. Where it has not, the guide describes the method without inventing firmware menu names, and says so.

If you find a wrong number or a menu path that has moved in a firmware update, please email me. Corrections are the most useful thing you can send.

Who makes it

EbookScreensaver is built and maintained by Aron, a solo developer and e-reader user. I maintain the device list myself and walk through each setup procedure on a device before publishing a guide. It is not a company and there is no team — which is worth saying plainly, because it also means there is one person to email when something is wrong.

Contact: aronbogo@proton.me