Загрузить документ
Tool guide
The page opens your PDF with the PDF.js engine, paints every page onto a canvas and gives the result back as PNG images, one per page. The file is read straight from disk and never uploaded. Splitting a document into pictures is what you do when a PDF simply cannot go where a frame is needed: a slide in a deck, a contract page in a messenger, a price list spread on a product card, a cover in a social feed. It also shows how the document renders outside your own viewer. See also: putting the pictures back together as a PDF, saving the pages straight to JPG, packing all the exported pages into a ZIP.
The scale at which each page is painted onto the canvas. A PDF is vector data, so rendering can go as large as you like, but higher scale means far more memory per page. At the default scale body text reads cleanly while small footnotes and table captions can blur — for those, crop the region you need separately.
Documents encrypted at open require a password, and there is no field to supply one here, so rendering stops. Remove the protection in the application that created the file or wherever you hold the password, save an unencrypted copy and load that. Print and copy restrictions without an open password normally cause no trouble.
Every page is a separate canvas held in the tab's memory, so a 200-300 page document can genuinely crash the tab, especially on a phone. A few dozen pages are fine. For anything larger, split the file in a regular PDF viewer first and process it in chunks.
The export is PNG, a lossless format, which keeps text and thin lines crisp at the cost of larger files than JPEG. There is no ZIP step on this page; if you want one archive, run the saved PNGs through the batch image-to-ZIP tool in the same section.
That is usually fonts that were never embedded in the document: the engine substitutes something else and the layout falls apart. Less often it is unusual objects such as form fields or layers. Compare against an ordinary viewer — if the page is blank there too, the file itself is damaged rather than the rendering.
No. PDF.js does all the parsing inside your browser: the library is loaded onto the page, while the file itself is read locally and stays on your device. The contents are never sent out, so you can inspect contracts and internal reports without handing them to a third-party service.
Before: quarterly-review.pdf, 24 pages
After: page-07.png — the one slide you needed, pasted in as an image
Before: agreement.pdf, 5 pages
After: page-03.png with the signature page, sent without forwarding the whole file
Your rating and feedback help decide what to improve next.