How Client-Side PDF Merging Works Without Server Transmission
Traditional online PDF converters require users to upload confidential documents—including corporate statements, medical summaries, and contracts—to unknown third-party cloud servers. ToolAcre replaces this obsolete architecture by porting compile-to-JS byte processing pipelines right to the browser.
When you drop your files into the workspace, the HTML5 File API allocates an isolated ArrayBuffer in your workstation's local RAM. Files never convert into outbound multipart payload packets.
The pdf-lib worker loads page dictionaries and serializes the requested edits without rasterizing page content.
Vector coordinates, outlines, raster layers, and annotations are concatenated into a unified target document tree with synchronized transformation matrices to prevent page overlap or scaling distortion.
The unified document is serialized into an in-memory binary Blob and downloaded without a server upload step.
Frequently Asked Questions
No document bytes or filenames are uploaded. Merging, splitting, and rendering happen in this browser through JavaScript and dedicated workers. Consented site analytics are separate and exclude document content.
PDF input is capped at 350 MB. Practical page and file-size limits can be much lower on memory-constrained devices because parsing and serialization require more memory than the stored file size.
Lossless optimisation rewrites PDF object streams. It does not deduplicate fonts, transcode JBIG2 images, or downsample photographs, and an already efficient file may become slightly larger.