keepfileslocal

turn PDF pages into images

Write each page as a picture, at a resolution you choose, without sending the document anywhere.

There is no Google Drive or Dropbox button on purpose: those send the file through a server. Here is what happens instead.

in three steps

  1. Drop the PDF in, or choose it. Its page count appears beside the name.
  2. Pick a format and a resolution; the tool says how wide an A4 page will come out in pixels.
  3. Write the pictures. One page comes back as an image, several as a zip named in page order.

how it works

A PDF page is measured in points, and there are 72 of them to an inch. Choosing a resolution decides how many pixels each of those points becomes: an A4 page is 595 points wide, so at 150 dpi it comes out 1240 pixels across. The tool shows you that number before you commit, because "300 dpi" means nothing until you know what it produces.

Pages are drawn one at a time, so a long document fills in progressively rather than arriving all at once, and the pictures are named with the page number padded — page-01, page-02 — so a folder of them sorts the way you expect.

why doing this locally matters here

Turning a document into pictures is usually the last step before it goes somewhere it cannot be edited: a page for a slide, a proof for a printer, a screenshot for a complaint. Which means the thing being rendered is the finished document, with everything in it.

Rendering it on a server means handing over exactly that, decoded and legible, to be drawn by someone else's machine. Here the drawing happens in the tab that already has the file.

questions

Where does my PDF go?

Nowhere. The pages are drawn by your own browser and encoded there too. The job log under the tool counts the requests the page made while working and how many of them left this site; the second number is zero, and your browser's network panel will agree.

Which resolution should I pick?

Good, at 150 dpi, is right for almost everything you will look at on a screen. Print, at 300, is what a printer wants and makes files about four times larger. Archive, at 600, is for scanning back in or reading very fine print, and the files get big quickly. Screen, at 96, is for when size matters more than detail.

JPEG or PNG?

JPEG for anything that started life as a scan or a photograph — smaller files, no visible difference at these sizes. PNG when the page is line art, a diagram or text on flat colour, where JPEG leaves a faint haze around the edges. PNG at 300 dpi and above produces very large files, and the tool says so before you commit.

Why are the files named with a zero in front?

So they sort correctly. A folder of files named page-1, page-2 … page-10 sorts as 1, 10, 2 in almost every file manager; page-01, page-02 … page-10 sorts the way you expect. It is a small thing that saves reordering a hundred files by hand.

Is there a limit on the number of pages?

Not one this site imposes, but there is one your device imposes: every page is held in memory while it is encoded. A four-hundred page document at 600 dpi is enough to exhaust a tab, and the tool warns you before you try rather than failing halfway.

Is this really free?

Yes. No account, no page cap, no watermark on the pictures. Advertising pays for the hosting, and since the document never reaches us there is nothing about it to sell.

next