Browser runs out of memory compressing a PDF locally — what now?

What you can do

• Change the pipeline: Use PDF Compress to recompress embedded images server-side; the tab mostly uploads and previews the result.
• Split first: Use PDF Organize, compress parts, then merge.
• Close heavy tabs during the job.
• Lighten the source: Lower export DPI; drop unused embeds.

Causes

• Browser processes have hard memory caps—especially on mobile.
• Keeping original page bitmaps plus encode buffers can peak at several× file size.

FAQ

Can I compress without uploading?

Yes, but large files are risky. Prefer desktop tools for offline; web flows fit mid-size files or short-lived server jobs (~10 minutes auto-clear on Sanye Hub).

Does failure mean a corrupt file?

Not always—OOM, encryption, or broken xref tables also fail. Try a smaller file; decrypt first if needed.

Does “extreme” quality use more browser RAM?

Server quality knobs mostly change bitmap resolution/JPEG quality. Versus full-page client rasterization, they still spare the tab.