1Drop in the PDF
Up to 30 pages. The pages are rendered on our side, so nothing heavy happens in your browser.
2Every page becomes an image
Each one is rendered at a resolution that keeps body text readable, then compressed like any other image.
3Download the pages
One zip with the lot, in page order, or save any single page from its row.
Questions
Why would I want images instead of the PDF?
Because plenty of things take a picture and refuse a document. Marketplace listings, older upload forms, messaging apps, and the image field on a web page all want a JPEG. Pulling out page four as a picture is also a good deal less than sending somebody a fourteen-page report.
Will the text still be readable?
Yes for anything meant to be read on screen. Pages are rendered at 150 dpi, which keeps ordinary body text comfortable — a page of a contract comes back around 200 KB. It is not the resolution you would choose for print or for running text recognition over afterwards.
Can it go the other way — images into a PDF?
No, and it is not planned. This turns documents into pictures, not pictures into documents. If you photographed pages and want them smaller before you assemble a PDF yourself, that is what the scanned-documents page is for.
Can it make my PDF smaller and still a PDF?
No. That is a genuinely different job — it means taking the document apart, recompressing what is inside it, and putting it back together, and this does not do that. What you get here is images.
Why the 30-page limit?
Rendering happens while you wait, at roughly forty milliseconds a page, so thirty is about the point where the wait stops feeling like a page load. Longer documents work in batches of thirty, and the settings stay put between them.
What happens to my document?
It is rendered, the pages are stored at a random unguessable address, and everything is deleted within the hour. The PDF itself is discarded as soon as the pages are made — it is never stored. Nothing reads the contents.