- Does my PDF get uploaded to a server?
- No. The PDF is parsed and rendered by pdf.js running in your browser, and the JPGs are encoded by your browser's own canvas encoder. There is no upload request at all — Convertitive never sees the file.
- Which resolution should I pick?
- For viewing on screens, sharing in chat, or embedding in slides, 2× (192 DPI) is the sweet spot — sharp on high-density displays without huge files. If the images will be printed, use 3× (288 DPI), which is close to the 300 DPI print standard. 1× is fine for quick previews or thumbnails.
- Why isn't the text selectable in the output images?
- Because conversion here means rasterization: each page's vector text and graphics are painted into a grid of pixels, and a JPG stores only those pixels. The layout is preserved exactly, but the letters are no longer text objects — they are pictures of text. If you need selectable text, keep the PDF or run OCR on the images.
- Can I convert a password-protected PDF?
- Not with this tool. Encrypted PDFs need the password to be decrypted before any page can be rendered, and this tool does not prompt for one — you will see an error instead. Remove the password first (with the password, in a PDF viewer's export function), then convert.
- Is there a page limit?
- Yes — 100 pages per PDF, and 64 MB per file. Every page is rendered in your browser's memory, so very long documents at 3× resolution can get heavy; the cap keeps the tool responsive on ordinary machines. For longer documents, split the PDF first.
- Would PNG be better than JPG for page exports?
- It depends on the content. JPG is the right choice for pages with photos or scans — it compresses continuous-tone images far smaller than PNG. For pure line art, sharp text, or diagrams, PNG's lossless compression avoids the faint ringing artifacts JPG can leave around hard edges. This tool outputs JPG because it keeps multi-page exports at a practical size; at 90%+ quality the artifacts are hard to spot in practice.