PDF compression guides
PDF Processing and Browser Memory
Plan around the document, browser, and device—not just the PDF's byte size.
Last updated
Browser PDF processing uses the device's available memory and can become difficult when a document has many pages, large images, unusual structures, or several copies open at once. Close unrelated tabs, keep the source and output separate, and try a smaller batch when appropriate. If the browser becomes unresponsive, stop and use a suitable device rather than repeatedly retrying.
Byte size is only one memory signal
Two PDFs with the same byte size can require different resources because page count, image dimensions, fonts, and internal structure differ. PDFStay's normal processing is designed for the current browser session, so available device memory and the browser's workload matter during the task.1, 2
| Signal | Risk | Response |
|---|---|---|
| Many pages | Long processing and high working memory | Close tabs and work in smaller groups if the task allows |
| Large raster images | Peak memory during decoding | Use an appropriate device and avoid parallel copies |
Use a bounded recovery workflow
- Keep the original file saved before starting.
- Close unrelated tabs and applications.
- Wait for one task at a time and save each output.
- If it fails, try a smaller or simpler operation on a copy.
FAQ
Does a small PDF always process easily?
No. Internal structure, image dimensions, page count, and the device's available memory all influence the workload.
What should I do when the browser freezes?
Wait briefly, avoid opening more copies, and stop if the task does not recover. Preserve the source and use a suitable device or smaller workflow.
Sources
- PDFStay — Compress PDF workflowPDFStay first-party methodologySource reviewed:
- PDFStay Privacy PolicyPDFStay first-party methodologySource reviewed: