PDF to JPG (or PNG): Free, In Your Browser

You need a PDF page as an image. To embed in a slide deck. To paste into a support ticket as a screenshot. To send the first page as a quick reference instead of forwarding the whole document. To use as a social media share. The job is conceptually simple — render the page, save it as a PNG or JPG — but the existing online tools tend to be either spammy free + paywalled HD, or buried under twelve other “PDF utility” advertisements.

Signegy converts PDF pages to images entirely in your browser. Drop the file, pick PNG or JPG, set the DPI, download individually or as a ZIP. Nothing uploads, no account, no quota.

How It Works

1. Drop your PDF onto the tool above. The first time, the tool renders every page at the default settings (PNG at 108 DPI) so you can preview.
2. Adjust format and DPI in the toolbar if you want different output. Click “Re-render” to apply the new settings to all pages.
3. Download. Click the arrow on a single thumbnail to download that one page as an image, or click “Download all as ZIP” in the toolbar to get every page as a single ZIP archive.

The conversion runs entirely in your browser — pdf.js renders each page to a canvas, then canvas.toBlob encodes it as PNG or JPG with your chosen settings. There’s no upload because there’s no server in the loop.

PNG vs JPG: When to Pick Which

PNG is lossless. Every pixel in the source page comes through unchanged. Transparency is preserved (if the original PDF page has transparent regions). The cost is file size — a typical document page can be 5-10x larger as PNG than as JPG.

JPG is lossy. The compression discards some detail in exchange for much smaller files. For text and simple graphics, the loss is usually invisible at 80-90% quality. For high-detail photographs, you can sometimes see compression artifacts at low quality settings. JPG doesn’t support transparency.

The right pick depends on the use:

• Slide decks: JPG, unless you need transparency over a colored background. Decks have a budget and you don’t want to bloat the file unnecessarily.
• Social media: JPG. Twitter, LinkedIn, Slack will recompress anyway.
• Print or design work: PNG, especially if the image will be re-edited.
• Archive or storage: JPG, since size matters and exact pixel accuracy usually doesn’t.
• Logos, line art, or anything with a transparent background: PNG, no contest.

If you’re not sure, start with JPG at 108 DPI. It’s right for most screen use cases.

DPI for Non-Designers

DPI (dots per inch) controls the resolution of the rendered image. The PDF itself doesn’t have a native DPI — pages are described in points (1/72 of an inch), and the rendering tool decides how many pixels per point to use. Higher DPI means more pixels per page, which means sharper output and larger files.

Calibration:

• 72 DPI: 1 point = 1 pixel. The “natural” resolution. Looks soft on modern screens.
• 108 DPI (default): 1.5x scale. Looks fine on standard displays, manageable file size.
• 144 DPI: 2x scale. Sharp on retina displays.
• 216 DPI: 3x scale. Print-quality. Files get large.
• Above 216 DPI: rare; usually overkill.

The slider in the toolbar shows the DPI in real time, so you can pick by feel rather than by formula.

Use Cases

The four most common are slides, support tickets, social shares, and previews.

For slides, exporting a single page as JPG and dropping it into PowerPoint or Keynote is faster than embedding the whole PDF (which most presentation tools handle awkwardly). One page → one slide → easy to caption and crop.

For support tickets and bug reports, screenshot tools usually can’t capture an entire PDF page in one shot. Exporting the page as JPG gives you a clean image you can mark up and attach. Faster than scrolling and stitching screenshots.

For social media — sharing the cover of a report, the front of a contract, or a single insight from a long document — image posts get more engagement than link previews. PDF page → JPG → upload.

For previews on a website or in an email newsletter, “first page as image” gives readers a sense of what the document is without making them download a multi-MB PDF first. Pair it with a download link to the full file.

Why This Isn’t a Server Upload

Most “convert PDF to JPG” sites work by uploading your PDF to their server, processing it, and giving you back a download link. For documents you don’t mind sharing, that’s fine. For documents with personal information, contractual details, or anything you’d rather not have a third party hold, it’s a privacy trade-off you may not realize you’re making.

Signegy renders the PDF in your browser using pdf.js (Mozilla’s PDF renderer, the same one Firefox uses to display PDFs). The resulting canvas is encoded as an image by the browser’s native toBlob method. No data leaves your tab. The download is a save action, not a transfer. Open DevTools and watch the Network tab — there are no requests to our origin during the conversion.

Pair It With the Toolkit

PDF-to-image often follows other tool steps. After splitting a long document down to the page you actually want, convert that single page to an image. After signing a PDF, export the signed page as an image to embed in an email confirmation. The toolkit is designed to compose without breaking the no-upload guarantee at any step.

The architecture is covered in detail on the private PDF signing page, and if you’re comparing online PDF utilities the Smallpdf alternative page breaks down how Signegy stacks up against the largest server-side competitor.