Privacy Policy
Last updated: July 2025
Your PDF Never Leaves Your Device
pdftoimage.app processes all PDF files entirely within your browser using Mozilla's PDF.js library and the HTML Canvas API. Your PDF files are never transmitted to any server, never stored on any external system, and never seen by anyone other than you. The moment you drop a PDF into the converter, it is read directly from your local filesystem into browser memory. All rendering, image encoding, and ZIP packaging happens on your device. Nothing is uploaded.
You can verify this yourself: open your browser's DevTools (press F12), navigate to the Network tab, then drop your PDF and click Convert. You will observe zero outbound file transfer requests to any server during the entire conversion process. You can even disconnect from the internet after the page loads — the converter will continue to work perfectly because it has no dependency on any external server once the page assets are cached.
This is not a policy commitment about what we do with files we receive. We structurally cannot access your PDF because we have no upload endpoint, no file storage, and no server-side processing pipeline. Zero data retention is guaranteed by architecture, not just policy.
Why This Matters for Sensitive Documents
PDFs routinely contain information that should never pass through a third-party server: legal contracts and NDAs, medical records and test results, financial statements and tax documents, business proposals with confidential data, and personal identification documents. Most online PDF tools — including well-known services — upload your file to their infrastructure to process it. Even services that claim to delete files immediately after processing create a window of exposure during transit and processing.
pdftoimage.app eliminates that window entirely. If you are handling documents subject to HIPAA, attorney-client privilege, financial confidentiality obligations, or simply documents you would not want a stranger to read, this tool is designed for you.
Data We Do Not Collect
We do not collect, store, or transmit:
- Your PDF files or any of their contents
- The images generated from your PDF
- Your name, email address, or any personal identifiers
- File names or metadata from your documents
- IP addresses associated with document conversions
- Any information about the content of files you process
No account is required to use this tool. We do not ask for an email address, we do not set user-specific identifiers, and we have no record of what you have converted.
Analytics (Google Analytics 4)
We use Google Analytics 4 to collect aggregated, anonymized usage data — specifically page view counts, session counts, approximate geographic region (country level), and browser/device type. This data helps us understand how the tool is being used so we can improve it.
Google Analytics does not receive any information about your PDF files, the images you generate, or any document content. The analytics data we collect is limited to standard website interaction metrics: which pages were visited, how long sessions lasted, and what browser and device type was used. No personally identifiable information is collected through our analytics configuration.
Google Analytics sets cookies in your browser to distinguish sessions. You can opt out of Google Analytics tracking across all websites by installing the Google Analytics Opt-out Browser Add-on.
Advertising (Google AdSense)
This site displays advertisements served by Google AdSense (Publisher ID: ca-pub-5035661017594256). Google AdSense uses cookies and similar technologies to serve ads based on your prior visits to this website and other websites. These cookies are set by Google, not by pdftoimage.app, and are governed by Google's own privacy policies.
Google's use of advertising cookies enables it and its partners to serve ads based on your browsing activity. You can opt out of personalized advertising by visiting Google's Ad Settings. For more information on how Google uses data when you visit sites that use its advertising services, see Google's Privacy & Terms.
GDPR and CCPA
Because we do not collect personal data beyond standard analytics (page views, session counts, country-level geography), our data footprint is minimal. We do not sell personal information. We do not share personal information with third parties beyond Google Analytics and Google AdSense, whose data practices are governed by Google's own GDPR and CCPA compliance frameworks.
Under GDPR, the legal basis for our analytics processing is legitimate interest in understanding aggregate usage patterns to improve the service. You may opt out of analytics tracking at any time using the Google Analytics opt-out tool linked above. Under CCPA, we do not sell personal information and do not share it for cross-context behavioral advertising beyond what Google AdSense manages under its own compliance obligations.
Contact
For privacy-related questions or concerns about this policy, you can reach us via the contact information listed on the About page. We will respond to reasonable privacy inquiries within 30 days.
Changes to This Policy
We may update this policy occasionally as the service evolves. Material changes will be reflected by an updated date at the top of this page. We will not retroactively apply policy changes to weaken protections that existed when you used the service.
How the Privacy-Preserving Architecture Works
pdftoimage.app is built on a privacy-by-architecture model rather than a privacy-by-policy model. When you load a PDF into the converter, Mozilla's PDF.js libraryreads the file directly from your local filesystem into browser memory — no data is transmitted over the network at any point. PDF.js renders each page onto an HTML Canvas element entirely within your browser process, using only your device's CPU and memory.
The Canvas API then exports each rendered page as a JPEG, PNG, or WebP image using canvas.toBlob() — a browser-native operation that keeps all image data local. JPEG provides efficient lossy compression ideal for photographs; PNG produces lossless pixel-perfect output required for text and diagrams; WebP offers the best quality-to-size ratio for modern web use. When multiple pages are ready, the JSZip library packages them into a ZIP archive entirely in memory, with zero server contact.
The key distinction is structural: pdftoimage.app has no server endpoint that could receive your file. This is fundamentally different from privacy commitments made by tools that do upload your files but promise to delete them quickly — those tools create a window of exposure during transit and processing that pdftoimage.app eliminates entirely. The DPI/resolution setting (1× through 3×) only affects local canvas size and output sharpness; it has no bearing on what data is transmitted, because nothing is transmitted regardless of setting.
Worked Example: Verifying Privacy Before Processing Privileged Documents
Sarah is an attorney at a law firm handling high-stakes litigation. Her team needs to convert court filings, deposition transcripts, and confidential exhibits to image format for a case management platform. Their IT security policy prohibits uploading privileged documents to any cloud service or third-party server.
Before using pdftoimage.app for the first time, Sarah performs a verification check. She opens Chrome DevTools (F12 → Network tab) and clears existing entries. She drops a sample deposition transcript into the converter and watches the Network panel in real time. During the entire conversion — loading the PDF, rendering each page, and exporting the images — the Network panel shows no outbound POST requests, no file uploads, and no data transfers beyond the initial static page assets. Satisfied, she shares the verification steps with her firm's CISO, who approves pdftoimage.app for use with privileged documents.
Sarah then processes a 200-page filing by selecting PNG at 2× scale (144 DPI) for sharp text output, and uses the custom page range field to convert in batches of 50 pages, downloading each batch as a ZIP. The entire operation completes on her laptop with no data leaving her network perimeter. She also notes that after the initial page load, she can enable airplane mode and the converter continues to work — confirming there is no hidden server dependency during conversion.
Key Factors in the Privacy Model
No Upload Architecture
Unlike tools that upload your PDF and promise to delete it, pdftoimage.app has no upload endpoint. Your file cannot be transmitted because there is nowhere to send it — guaranteed by the code structure, not by policy.
Browser-Only Processing
All PDF parsing, page rendering, image encoding (JPEG, PNG, or WebP), and ZIP packaging happens inside your browser tab. The output format and DPI setting you choose affect only local processing — higher DPI means a larger canvas and more CPU time, but does not change the fact that nothing leaves your device.
Analytics vs. File Data
Google Analytics 4 collects aggregate traffic metrics such as page views and country-level geography. This data is completely separate from your PDF — Google never receives your file, its filename, or any of its contents. File size, format choices, and page ranges are also not reported to analytics.
Offline Capability as Proof
Once the page has loaded and its assets have been cached by your browser, pdftoimage.app works without an internet connection. This is a direct technical demonstration that conversion requires no server — if it did, it could not function offline.
Multi-Page and File Size Considerations
Choosing higher resolution (3×, 216 DPI) or converting many pages at once increases local CPU usage and memory consumption on your device. It does not increase any data transmission, because there is none. The 50 MB soft file size limit exists purely for device performance, not for server capacity.
Frequently Asked Questions
What image formats does this converter support?
pdftoimage.app converts PDF pages to JPEG, PNG, and WebP. JPEG uses lossy compression and produces the smallest files, making it ideal for photographs and color-rich pages. PNG is lossless and the right choice for text documents, diagrams, and anything where every pixel must be preserved exactly. WebP delivers roughly 25–35% smaller files than JPEG at equivalent visual quality and is supported by all modern browsers. None of these format options affect whether data is transmitted — regardless of which format you choose, all processing stays local.
Is my PDF secure when I convert it?
Yes — your PDF is never uploaded, transmitted, or stored anywhere outside your own device. pdftoimage.app has no server-side processing and no upload endpoint, making it architecturally impossible to receive your file. You can confirm this by opening your browser's DevTools (F12 → Network tab) and converting a document — you will see zero outbound file transfer requests. The tool also works offline after the initial page load, which further demonstrates there is no hidden server dependency.
Can I convert multiple pages at once?
Yes — pdftoimage.app handles multi-page PDFs with no page limit. You can convert every page of a PDF or specify a custom range such as "1-10, 15, 20-30". When two or more pages are ready, a Download All as ZIP button appears so you can retrieve all images in a single archive. All ZIP creation happens locally in your browser — no page images are uploaded or stored externally. For very large documents, converting in batches using the custom range field keeps memory usage manageable.
What resolution/DPI should I use?
For most web and screen uses, the default 2× scale (144 DPI) is the best choice — sharp output with reasonable file sizes and fast processing. For print-quality or archival output, use 3× scale (216 DPI). For quick previews, 1× scale (72 DPI) is fastest and produces the smallest files. Scanned PDFs are limited by their original scan resolution (typically 150–300 DPI), so increasing the render scale beyond that point increases file size without improving clarity.
What is the maximum PDF file size?
The soft limit is 50 MB. Unlike server-based converters, there is no server storage capacity to worry about — the limit exists because very large PDFs consume significant memory and CPU on your local device. To handle large files, reduce the render scale to 1× or 2×, or use the custom page range feature to convert the document in smaller batches. There is no hard cap enforced by the tool — larger files will work if your device has sufficient memory.