Client-Side Architecture & PDF Processing

[scrollify-sound]

SimplyPDF uses pdf-lib and pdf.js for processing in the browser. Could you explain your architecture choices for handling performance and memory efficiency, especially for large PDFs?
1). How does the app avoid browser crashes with very large files?
2). Are there limits (e.g., file size or page count) you’ve tested against?

[ArshVermaGit]

We use pdf.js for rendering and pdf-lib for manipulation to keep memory usage low. Pages are rendered lazily and large operations run in Web Workers to avoid blocking the browser.

1. Large files are handled by streaming, on-demand page rendering, and releasing temporary canvases/arrays so we don’t keep everything in memory at once.
2. In testing, modern desktops handle PDFs up to ~150MB or 500+ pages; graphics-heavy or mobile devices hit limits earlier.