One PDF page becomes one raster image
The browser draws each selected page at a fixed 2× PDF.js scale, preserving page order, dimensions, orientation, and PDF rotation in the rendered pixels. It processes pages sequentially. The result is an image representation: selectable text, vector editability, interactive forms, hyperlinks, accessibility structure, layers, and PDF metadata do not remain interactive or editable.
Example PDF to image results
These values come from generated fixtures decoded after conversion in Chromium. They are reproducible examples, not file-size guarantees.
| Fixture | PDF geometry | Output | Pixels | Bytes |
|---|
| Portrait text page | 612×792 points | PNG | 1224×1584 | 51,928 |
| Landscape text page | 792×612 points | JPG | 1584×1224 | 20,458 |
| 90° rotated page | 612×792 points, rotated | PNG | 1584×1224 | 52,127 |
A three-page fixture with portrait, landscape, and square pages produced 1224×1584, 1584×1224, and 800×800 PNG files in order. Its ZIP measured 124,280 bytes.
Points, pixels, and DPI
PDF page geometry is measured in points independently from output pixels. Rasterization at 2× produces twice the point width and height in pixels. FiloTool does not explicitly write DPI metadata, so it makes no 300-DPI, print-ready, or original-resolution claim.
PNG or JPG?
PNG is lossless and preserves sharp rendered edges, which suits text, diagrams, and screenshots. JPG uses lossy encoding at 0.92 browser quality and is always opaque; it may be smaller for photographic pages but can add artifacts around fine text. PDF pages render on the canvas background; this workflow does not promise transparent PNG output.
Page order, names, and ZIP
All-pages mode creates one image per page in document order. Names are page-1.png or page-1.jpg, then increment by page. Individual downloads remain available; the lazy-loaded ZIP includes every successfully completed image and is named pdf-pages-png.zip or pdf-pages-jpg.zip.
Browser capacity and failed documents
There is currently no explicit byte or page-count cap in this converter; browser memory and canvas limits are practical constraints. Pages render sequentially and canvases are released, but completed image Blobs remain until reset or replacement. A malformed, encrypted, unusually complex, or oversized document may fail without partial results.
Rendering is not OCR
Both scanned and digitally generated PDFs can be rendered when the browser PDF renderer can open them, but the output contains pixels rather than extracted words. Use PDF to Text for embedded selectable text or OCR PDF for scanned pages. After exporting many images, use the Batch Image Optimizer; use Image Compressor for one output.
PDF to image questions
How are PDF points converted to pixels?
FiloTool renders each page at a fixed 2× PDF.js scale. A 612×792-point page therefore produced a 1224×1584-pixel image in the reproducible fixture test.
Does PDF to Image set a DPI value?
No explicit DPI metadata is set. Pixel dimensions come from the 2× rendering scale, so the output should not be described as 300 DPI, print-ready, or the PDF's original resolution.
What happens with a multi-page PDF?
One image is generated for each selected page in page order. Each image can be downloaded separately, and all-pages results can be downloaded as a ZIP containing page-1, page-2, and later numbered files.
Can this converter open an encrypted PDF?
No password field is provided. Password-protected PDFs are rejected and must be opened with an authorized workflow before conversion.
Are PDF contents uploaded?
No. Your PDF is rendered into images locally in your browser and is not uploaded to FiloTool for conversion.