Higher DPI increases pixel dimensions and file size. Very large pages are scaled down so the canvas stays within browser limits.
When on, PDF.js paints on a clear canvas (works best for PDFs without full-page white fills). Off composites on white before export.
zlib 1–9
PDF parsing runs in a PDF.js worker; PNG DEFLATE may run in a separate Web Worker. Nothing is uploaded to SynthQuery. Up to 10 PDFs, 100.00 MB each; up to 300 pages per document per run.
Scanned PDFs are images inside a PDF—export quality matches the embedded scan resolution, not “infinite” vector sharpness. Password-protected PDFs must be unlocked before opening here.
About this tool
Portable Document Format files bundle vector instructions, embedded fonts, raster XObjects, transparency groups, and optional text layers into a single interchange container that has dominated business, academia, and government for decades. Yet many downstream workflows—slide decks, CMS media libraries, Figma mood boards, email-safe attachments, and quick Slack reviews—still expect PNG screenshots because PNG is lossless, widely supported, and carries an alpha channel without the block artifacts JPEG introduces around sharp edges. SynthQuery’s free PDF to PNG Converter closes that gap in the browser: you upload PDFs, choose DPI and page scope, optionally keep transparent pixels where the artwork allows, tune zlib compression, and download individual PNGs or a ZIP archive. Parsing and rasterization use Mozilla PDF.js inside a dedicated worker while PNG encoding can offload DEFLATE work to another Web Worker, which keeps the tab responsive during larger batches. Your file bytes never leave your machine for conversion, which matters when contracts, financial statements, or unreleased creative decks are involved.
Unlike server-side converters that may retain uploads on shared storage, this tool reads each PDF with the File API, renders selected pages to an HTML canvas at the scale implied by your DPI choice, samples RGBA pixels, and writes truecolor PNG IDAT streams with a compression level you control. That pipeline is ideal when you need predictable, repeatable exports for design QA or when corporate policy forbids sending certain PDFs to third-party SaaS. It is not a replacement for prepress RIPs, color-managed print proofs, or OCR pipelines—those domains need ICC profiles, spot colors, and specialized engines—but it excels at fast, explainable page grabs you can reason about from the settings panel alone.
What this tool does
The hero workflow mirrors other SynthQuery image utilities: drag up to ten PDFs into the dashed drop zone or use the hidden file input, confirm filenames and sizes in the queue, adjust conversion options, then press Convert to PNG. Each PDF loads through PDF.js with verbosity suppressed so console noise stays minimal; page numbers resolve from your mode—every page, only the first page, or a specific list such as one comma three five dash eight that expands into a sorted unique set bounded by the document’s page count. A safety cap prevents accidentally rasterizing hundreds of slides in one go on a low-memory tablet; if you hit the cap, the interface explains that only the leading pages exported and you can split the job across multiple runs.
DPI presets map directly to the viewport scale PDF.js uses when painting into the canvas: seventy-two corresponds to one PDF user unit per pixel at nominal screen resolution, one hundred fifty is a common web-and-light-print compromise, three hundred targets office-quality print when the source vectors justify it, and six hundred is available for archival crops where disk space is acceptable. Extremely large physical pages automatically scale down so neither dimension exceeds an internal canvas guardrail, which avoids silent tab crashes when someone drops a poster-sized engineering drawing. The transparent background toggle asks the renderer to treat the canvas as clear rather than prefilled white; PDFs that already paint opaque rectangles will still look like white pages, but icons, diagrams, and lightly structured pages can produce PNGs you can overlay in presentation tools. PNG compression level one through nine maps to zlib DEFLATE effort in our truecolor encoder: higher numbers spend more CPU searching redundancy in scanlines, often shrinking IDAT chunks for screenshots with large flat fills.
Batch downloads support per-thumbnail saves, a staggered multi-download button for browsers that throttle rapid anchors, and a JSZip-powered archive that never transits SynthQuery infrastructure. Thumbnails reuse the same blob URLs as downloads so you can visually confirm crop and contrast before sharing. Mobile layouts stack options above the drop zone, maintain forty-four-pixel touch targets on primary buttons, and keep status text exposed to screen readers while conversion runs.
Technical details
PDF stores painting operators—move to, line to, curve to, shade fills, text show, and inline images—in a structured content stream. PDF.js interprets those operators, resolves fonts and color spaces, and issues draw calls into a canvas-backed surface. That step is fundamentally a vector-to-raster projection: Bézier paths become anti-aliased pixel coverage, gradients become interpolated samples, and transparency compositing follows the PDF transparency model within browser graphics limits. Export quality therefore depends on DPI, which sets how many pixels represent each inch of the PDF page, and on the renderer’s hinting, not on PNG itself—PNG only losslessly stores whatever raster the canvas captured.
Higher DPI multiplies width and height roughly linearly with scale and drives file size up with the square of scale in detailed pages because more pixels mean more entropy for zlib to compress. Transparency in PNG is straight alpha in RGBA mode; semi-transparent soft shadows survive when the PDF actually emits coverage values below one. Text sharpness is governed by subpixel anti-aliasing and hinting choices inside PDF.js and the operating system font stack—very small type at low DPI may look softer than print-focused desktop viewers that use different text rendering paths. Scanned PDFs are simply bitmaps wrapped in PDF containers; you cannot recover sharper text than the embedded scan resolution by increasing DPI here—you only interpolate pixels, which helps smoothness but not legibility.
Compared to JPEG exports from PDF, PNG avoids blocky ringing around high-contrast edges and supports uniform transparency, at the cost of larger files on photographic pages. Palette PNG modes are outside this tool’s path: we focus on truecolor RGB or RGBA suited to screenshots and vector-derived art. Color management is browser-sRGB pragmatic: mission-critical CMYK separations still belong in Acrobat preflight, Affinity Publisher, or similar ICC-aware suites.
Use cases
Product designers export presentation PDFs from Figma or Keynote, then pull individual slides as PNG for Notion galleries or Jira attachments where inline PDF viewers behave inconsistently. Researchers extract figure panels from camera-ready papers—often vector in the original—to embed in thesis chapters or grant appendices that mandate raster images at explicit pixel widths. Technical writers snapshot diagram pages from architecture PDFs for wiki pages that strip interactive PDF features but accept PNG callouts.
Marketing teams harvest hero stills from multi-page brand decks without asking IT to install desktop batch tools on locked laptops. Customer support converts invoice PDFs to PNG when ticketing systems reject application/pdf uploads but allow images. Archivists who need a lossless, non-PDF snapshot for digital preservation can store PNG sidecars alongside the canonical PDF/A master, understanding that the raster copy is a convenience derivative, not a vector-equivalent replacement.
Educators building slide decks from journal articles grab single pages containing charts while respecting fair-use scope—always verify copyright and licensing before redistribution. Developers testing PDF.js integrations can compare SynthQuery’s export against their own viewers for pixel diffs. Whenever accompanying blog posts might include AI-assisted explanations of the visuals, pair image extraction with textual review using SynthQuery’s AI Detector and Humanizer linked from the global tools directory at https://synthquery.com/tools.
How SynthQuery compares
Adobe Acrobat Pro provides polished export presets, OCR, redaction, and print-centric color management that browsers cannot replicate. Ghostscript and ImageMagick excel at scripted server pipelines with fine-grained color and subsetting controls. macOS Preview offers fast single-document export for users already on Apple hardware. SynthQuery targets a different scenario: zero install, explainable limits, and strict local processing when privacy policies disallow uploads. The comparison below is directional—pick tools based on compliance, automation, and fidelity requirements, not headline features alone.
Aspect
SynthQuery
Typical alternatives
Privacy posture
PDF.js parses in a worker; PNG zlib may run in another worker; raster bytes stay in your browser tab.
Many “free online PDF converters” upload to shared infrastructure—read terms before confidential PDFs.
Color & print
sRGB canvas path; no CMYK plate control; ideal for screen-first exports.
Acrobat and professional RIPs manage ICC profiles, spot colors, and proofing.
Automation
Interactive UI with DPI, page selection, compression, ZIP—no shell scripting.
Ghostscript/ImageMagick shine for headless batch on servers you control.
Ecosystem
Listed on /free-tools beside PNG Compressor, Image Resizer, WebP Converter; footer links to /tools.
Desktop suites stand alone unless you integrate them into DAM workflows manually.
How to use this tool effectively
Start from the highest-fidelity PDF you own—re-export from the authoring application when possible because repeated screen grabs of compressed attachments accumulate JPEG noise inside XObjects. Click the drop zone or use your platform file picker to add up to ten documents ending in .pdf; each row shows monospace filename and byte size so you can catch mistaken zip-renamed files before work begins. Open Conversion options: pick a DPI that matches your destination. If you only need a quick Teams preview, seventy-two or one hundred fifty keeps files small; if a print vendor asked for three hundred PPI on embedded figures, match that expectation here rather than upsampling later in an editor.
Choose Pages according to the task. All pages suits handoffs where someone asked for every slide as a static image. First page only is perfect for insurance cards, cover sheets, or certificate thumbnails. Specific pages accepts comma-separated integers and inclusive ranges; malformed tokens are ignored, and if nothing valid remains the tool falls back to page one with an inline hint so you are not stuck silent. Toggle Transparent background when you intend to composite exported art on arbitrary slide colors; leave it off when you want predictable white behind legacy text PDFs that assume opaque paper. Set PNG compression: six is the balanced default, nine when archives must shrink before email, one when you want the fastest encode on enormous canvases.
Press Convert to PNG and watch the status line cycle through load and per-page progress. When the grid fills, scan thumbnails for accidental cropping or empty pages, then download individually, trigger staggered all downloads, or fetch a single ZIP. If a PDF is password encrypted, PDF.js will surface an error—unlock or print-to-PDF locally first. When finished, scroll to About & FAQ for format theory or jump to https://synthquery.com/free-tools to discover adjacent utilities such as the PNG Compressor and Image Resizer.
Limitations and best practices
Password-protected PDFs must be decrypted before loading—supply an unlocked copy or print to a new PDF locally. Very large page dimensions automatically scale down to protect memory, which may reduce effective DPI; split posters or split runs if you need maximum resolution on one panel. Forms with dynamic JavaScript may not render exactly like desktop Acrobat because PDF.js focuses on safe display semantics. Layered optional content (OCGs) follows default visibility unless you customize PDF.js elsewhere—this page uses stock rendering. Keep archival masters in PDF/A or original authoring formats; treat PNG exports as derivatives. When files balloon, run outputs through the PNG Compressor or convert photos to WebP with the WebP Converter before publishing.
If JPEG screenshots feed your pipeline, convert them to PNG before stacking with PDF-derived assets.
Frequently asked questions
PNG is lossless and preserves hard edges, flat UI, and transparency—choose it for diagrams, logos, slides with text, and any overlay work. JPEG is lossy and usually smaller on photographs but introduces block artifacts around type and line art. If you need both, export PNG here for precision-critical pages and use the WebP Converter or an external JPEG encoder for photo-heavy pages after conscious quality trade-offs.
There is no universal “best”—match the pixel density of your destination. Seventy-two to ninety-six suits on-screen previews; one hundred fifty is a pragmatic web default; three hundred aligns with many print conversations when the PDF actually contains vector detail worth sampling; six hundred is for archival or crop workflows where file size is acceptable. Scanned pages will not gain real detail beyond their embedded resolution by cranking DPI; you only interpolate new pixels.
Enable the Transparent background toggle so PDF.js paints onto a clear canvas. Whether pixels look transparent depends on the PDF: pages that already draw white rectangles will still appear white in PNG, while sparse diagrams or icons on an empty page may export with useful alpha. Turn the toggle off to composite translucent edges onto white before encoding, which reduces fringe when placing art on light backgrounds in older slide tools.
Yes in the sense that PDF.js renders vectors to pixels using the same operator stream as other viewers—lines, fills, and text become anti-aliased raster coverage at your chosen DPI. You do not receive editable SVG or PDF layers in the PNG; the vector path is flattened. For infinite zoom, keep the original PDF; use PNG when a bitmap interchange format is explicitly required.
Each run processes up to three hundred pages per PDF to keep consumer devices stable, and you may queue up to ten PDFs. If a document exceeds the cap, export in chunks using Specific pages ranges—for example one dash one fifty, then one fifty one dash three hundred. There is no server-side page limit because nothing is uploaded; practical ceilings are RAM and patience.
You can rasterize them, but quality is bounded by the scan resolution embedded in the PDF. Increasing DPI here does not recover fine text that was never scanned; it only interpolates. For searchable scans, run OCR in a dedicated tool first, then capture PNGs if you still need bitmaps for layout.
Conversion executes locally: PDF buffers, canvas pixels, and PNG bytes stay inside your browser unless you download or upload them elsewhere yourself. You still load the app shell, scripts, and fonts over HTTPS like any website, and your deployment might include analytics, but SynthQuery does not receive the PDF payload for this tool’s encode path. Review your organization’s browser policies for local storage and logging if you operate under strict compliance regimes.
Sharpness is determined by DPI, font hinting, and PDF.js text rendering—not by PNG compression, which is lossless here. Small type at low DPI may look soft compared to print-focused viewers. If text looks blurry, raise DPI, zoom the source PDF to confirm vectors are crisp, and avoid re-encoding PNGs through lossy pipelines before publishing.