A PDF can be converted to one tall PNG on Android by rendering every page in a mobile browser and stacking the pages from top to bottom. This produces one continuous image for sharing in chat, reviewing in a single scroll, or placing into a destination that accepts only one picture.
Use PDF to Long Image for this browser-based workflow. The selected PDF is processed locally and is never uploaded to Lizely. This route uses the web converter in your Android browser rather than requiring a separate native Android converter.
Convert a PDF to a long image on Android
- Open the converter in your Android browser. Load the PDF to Long Image page on your phone or tablet and locate its PDF selection control.
- Choose one PDF. Open the file picker and select the document you want to convert. Check that it is no larger than 25 MiB and contains no more than 40 pages before continuing.
- Select the rendering scale and page gap. The scale controls the raster dimensions used for each page. The gap can be set from 0 to 32 pixels and separates neighboring pages with white space.
- Tap Convert to Long PNG. Before encoding the final file, the tool calculates every scaled page viewport and the complete combined layout. It does not begin final encoding if one of the dimension or megapixel checks fails.
- Review the combined dimensions. Check the displayed width, height, and page count. This is the point to reconsider the scale or gap if the resulting image will be too large for its intended destination.
- Download the single PNG. Tap the download control after a successful conversion. The filename is based on the PDF name and ends with -long.png. If your browser asks for a save location, choose a folder accessible from Android. You can then open the downloaded file from the browser or file manager and use Android’s Share command to send it to another app.
The downloaded file is a raster rendering, not a modified PDF, and the original document remains untouched. If the destination app rejects a very tall image or handles it awkwardly, a lower scale may help, although using separate page images can be more practical for some apps.
How the pages are combined
Every page in the selected PDF is rendered and placed in one PNG from top to bottom. The widest rendered page determines the canvas width. Narrower pages are placed horizontally in the center without being stretched, so white side margins can appear beside portrait pages in a document that also contains landscape pages.
Pages may have different dimensions and orientations, but each one keeps its rendered proportions. The selected gap appears as white space between pages. Because scale is applied before stacking, increasing it can make small content clearer when the final image is viewed at full size. The trade-off is rapid growth in the image’s width, height, memory requirement, and download size.
The final file is explicitly encoded as a lossless PNG. That refers to the PNG encoding itself; the PDF pages are still rasterized at the selected scale rather than retained as searchable or editable PDF objects.
Limits checked before encoding
Several limits interact because a document that passes the page-level checks can still produce a final image that is too tall.
| Check | Maximum | Why it matters |
|---|---|---|
| Source file | 25 MiB | The selected PDF must fit within the converter’s bounded input size. |
| Number of pages | 40 pages | The converter processes one document containing up to 40 pages. |
| One rendered page | 12,000 pixels on either side and 40 megapixels | An individual page cannot exceed either the dimension or megapixel allowance. |
| All page renders together | 100 megapixels | The combined raster workload of every page is bounded. |
| Final combined canvas | 12,000 pixels per side and 100 megapixels | The finished long PNG must also pass both final-canvas limits. |
The preflight calculates the complete layout before final encoding, so an oversized page later in the document cannot leave a misleading partial result. A long document may still exceed the final height limit when every individual page is small. In that case, reduce the rendering scale or export the pages separately.
Encrypted, damaged, unsupported, and over-limit documents produce an error. The converter does not bypass passwords, repair damaged PDFs, verify digital signatures, or determine whether a document is trustworthy.
Pick the format that fits the Android app
A single tall PNG is only one way to distribute a PDF’s visible pages. Compare these options before converting on a phone:
| Output | File structure | Main trade-off | Best fit |
|---|---|---|---|
| PDF to Long Image | All pages in one lossless PNG | The file can be extremely tall and has no selectable PDF content | A chat, page, or app that specifically accepts one continuous picture |
| PDF to PNG | One lossless PNG per page | Creates multiple files but keeps each image at a conventional page size | Sharing selected pages or using tools that handle separate images more easily |
| PDF to JPG | One smaller, lossy JPG per page | Reduces file size at the cost of image quality | Quick transfers where smaller files matter and lossy output is acceptable |
The long-image option is designed for a continuous visual strip, not for every sharing situation. A very tall PNG can be awkward for printers, email clients, image editors, and social platforms. For print output, check PDF to Long Image for Printing: Sizing and Limits before committing to a tall canvas; a chat-oriented strip is not automatically print-ready.
What stays private and what the PNG keeps
PDF loading, every page render, stacking, PNG encoding, and download creation run locally in the browser. The document is never uploaded to Lizely, and the original PDF remains unchanged. The rendering library and shared worker are loaded only after you press Convert.
The result is a page rendering rather than a structural PDF conversion. It does not preserve selectable text, live links, form controls, layers, annotations as editable objects, document metadata, or the original internal images. The output filename, however, is derived from the input name after its PDF suffix is removed and unsafe filename characters are replaced.
Rendering is based on the Mozilla PDF.js project. PDF.js paints visible content, including text, vector artwork, photographs, fonts, clipping paths, and other page elements, onto individual canvases. The converter then copies those canvases into one final PNG. You can see the rendered appearance, but the finished file does not behave like the source PDF.
Fix common Android conversion problems
- The final canvas is too tall. Lower the rendering scale and try again. A smaller gap can also reduce total height, but scale is usually the more effective control. If the document still exceeds the final limit, export separate PNG pages.
- The PDF is too large or has too many pages. Prepare a smaller valid PDF in another authorized workflow, keeping the source within 25 MiB and 40 pages before retrying.
- The file is encrypted. The converter reports an error and does not bypass the password. An unprotected copy must be obtained through a separate process.
- The PDF is damaged or unsupported. The tool will not repair it. Obtain a valid PDF that its renderer can open.
- Narrow pages sit inside a wider canvas. This is expected. The widest page sets the output width, and narrower pages are centered with white margins rather than stretched.
- An Android app cannot handle the download. Test the destination before sending. Reduce the scale or choose separate PNG pages when the app expects ordinary page-sized images.
When one long image makes sense
A single long PNG works well when you want to share a short document in a chat, review slides in one continuous scroll, archive a multi-page reference as one picture, or place several pages into a destination that accepts only one image. It is most useful when the visual appearance matters more than searchable text, interactive controls, or editable PDF structure.
Keep the original PDF when you need selectable text, fillable fields, live navigation, annotations as editable objects, metadata, or reliable print output. If one tall picture is genuinely the required format, the Android browser workflow produces it as a single lossless PNG while leaving the source document untouched.
If you're weighing options, PDF to PNG on Android: A Complete Browser Guide covers this in detail.