How Canva converts PDF to JPG
Converting a PDF to JPG inside Canva works like most cloud converters: you open Canva's editor, upload the PDF, wait while Canva's servers process the file, then download each page as a separate image. Canva documents the upload step on its PDF to JPG page and points readers to its privacy policy for how uploaded content is handled, which makes clear that the document is in motion across the network rather than processed only on the user's machine. The flow fits cleanly into the rest of Canva's design workflow — once the pages are images, they can be dragged into a Canva design, framed with a border, captioned, or shared to social media.
For many readers that flow is fine. The question is what happens the moment the document is a tax form, a job application, a signed contract, a school transcript, or a medical record. Those files are exactly the kind of PDF people often need as a JPG, and they are exactly the kind of file most readers want to keep off a third-party server during conversion.
Why a local browser converter is the cleaner choice
A local browser converter removes the upload step entirely. The PDF to JPG Converter loads PDF.js only after the user presses Convert, renders every page onto a hidden canvas, encodes the canvas explicitly as image/jpeg at the chosen quality, and presents a preview plus a download button for each finished page. The PDF itself, the canvas, and the encoded blobs all live inside the browser tab. Lizely does not run a conversion server for this tool, and the file never crosses the network once the page itself is loaded.
The render-based approach also differs from image extraction in one important way. Canva splits a PDF the way most cloud converters do — by recognizing pages and exporting each one as an image. A browser render uses PDF.js, the same PDF rendering engine used in Firefox, to draw the page exactly as the browser would display it. That is what produces crisp text on a white background at whatever scale the user picks, instead of a flat raster of whatever the original PDF happened to embed.
| Dimension | Canva's PDF to JPG flow | Local browser converter (Lizely) |
|---|---|---|
| Where the file goes during work | Uploaded to Canva's servers | Stays inside your browser tab |
| Conversion engine | Canva's server-side pipeline | PDF.js, the same renderer used by Firefox |
| Account required to convert | Yes | No |
| Quality slider | Not exposed to the user | User-adjustable, 0.60 to 1.00 |
| Render scale slider | Not exposed to the user | User-adjustable |
| Transparent page regions | Handled by Canva's pipeline | Flattened onto white because JPEG has no alpha channel |
| Filename ordering | Canva's naming scheme | Zero-padded page number, sorted in document order |
| File caps before work starts | Canva's upload limits | 25 MiB, 40 pages, 12,000 px per side, 40 MP per page, 100 MP total |
Convert PDF to JPG without Canva, step by step
Use this exact sequence inside the browser-based PDF to JPG Converter. Each step maps directly to a control on the tool and mirrors the three verified operating steps in Lizely's product contract.
- Open /pdf/pdf-to-jpg/ in any modern browser and choose one non-empty PDF up to 25 MiB from your device.
- Skim the safety caps listed next to the file picker before pressing anything: no more than 40 pages per document, no rendered page above 12,000 pixels on either side or 40 megapixels, and no conversion whose planned pages exceed 100 megapixels in total.
- Pick a render scale. A higher scale produces more output pixels and can make small text easier to read, but it also increases memory use, processing time, and download size.
- Pick a JPEG quality between 0.60 and 1.00. Higher quality usually retains more detail but does not restore detail that was missing from the source PDF.
- Click Convert to JPG. Conversion only begins after that button press; the PDF.js worker is loaded on demand and is not part of the page's initial interaction bundle.
- Wait for the page list to appear below the controls. Each finished row shows the exact pixel dimensions of that page and its own download button.
- Click Download next to the pages you want. The filename ends with a zero-padded page number so the files stay in document order when sorted.
- If you change the file, scale, or quality afterwards, the old result is invalidated automatically so that the controls never describe images generated with earlier settings.
If a previous run is still going when you start a new one, the older job is cancelled and its temporary canvases and object URLs are released. That is by design: the tool never lets two jobs share the same canvas or the same blob URL, and it never reuses an object URL after a result has been replaced.
PDF to JPG limits the browser enforces
The browser converter enforces five preflight checks, applied before and during the render rather than only when something fails:
- One PDF at a time, between a non-zero lower bound and a 25 MiB ceiling.
- A maximum of 40 pages per document.
- A maximum of 12,000 pixels on either side of any single rendered page.
- A maximum of 40 megapixels on any single rendered page.
- A maximum of 100 megapixels across every planned page in a single conversion.
These limits exist for a reason that has nothing to do with file safety. They keep the renderer from allocating a canvas the browser tab cannot realistically hold. A damaged, encrypted, unsupported, or unusually complex PDF can still fail inside those caps, and password protection is never bypassed. If a document hits the page or pixel ceiling, the practical fixes are usually to lower the scale, split the document first with a tool like Split PDF, or drop to JPEG quality 0.60 to keep pixel counts identical while shrinking file weight. The tool never guarantees a particular output file size, DPI, or print quality because those outcomes depend on page dimensions and content, which vary from one PDF to the next.
Scale, quality, and file naming explained
Render scale is a multiplier on the page's viewport in PDF coordinate space. Doubling the scale roughly quadruples the pixel count and the resulting JPG size. The smallest scale that keeps the smallest text legible on the screen or paper size that will actually receive the image is usually the right pick. JPEG quality is a separate dial that controls how aggressively the encoder discards high-frequency detail. At 1.00 the encoder keeps nearly everything the render produced; at 0.60 it discards enough detail to noticeably shrink the file while leaving photographs and large text looking clean.
Higher scale cannot invent detail the source PDF did not contain. A PDF created from a low-resolution scan stays a low-resolution scan no matter how high the scale is pushed — what changes is how many output pixels each existing pixel is repeated across. Higher scale also does not promise a particular DPI, because page dimensions vary across PDFs and the tool never assumes a target print size. The filename pattern is the small but useful piece: every downloaded file gets a zero-padded page number so a sorted folder always reads in document order without manual renaming.
JPG vs PNG vs long image: which export fits the job
JPG is the right format when the destination expects a common photographic image, when transparency is not required, and when a smaller lossy file is acceptable. That covers most social shares, slide embeds, and photographs extracted from a PDF. PNG is the better pick when every pixel has to round-trip identically — diagrams with thin lines, screenshots, anything where a hard edge matters more than file size. A long image is the right output when the reader wants every page stacked vertically into a single PNG that scrolls end to end, such as a chat-thread export or a long-form reading view.
| Output need | Best local export | Why |
|---|---|---|
| Photos and casual social sharing | PDF to JPG Converter | Small lossy files that look fine across the web |
| Crisp diagrams, screenshots, UI mockups | PDF to PNG | Lossless encoding preserves every pixel exactly |
| One scrolling image of the whole document | PDF to Long Image | Stacked PNG of every page in a single continuous file |
| Editable text, links, or form values | PDF to Text Converter | Renders discard the text layer; an extractor preserves it |
| Embedded photos only, skipping the page chrome | Extract Images from PDF | Exports the actual embedded images rather than re-rasterizing the page |
If the underlying reason for wanting JPG in Canva was to drop pages into a Canva design, a cleaner workflow is to export the pages locally with the converter above, save them outside the browser, and drag the folder onto Canva's upload area once. That single upload still moves the files to Canva, but it leaves a clean local copy as the original artifact and lets the reader set scale and quality themselves before the upload happens. The PDF itself is never modified by the converter — every downloaded JPG is a freshly rendered derivative.