pdfmergely

I appreciate the directness, and you are right.

The design has not yet earned trust, and that is on where I am working in.

For a tool people hand documents to, looking trustworthy and being trustworthy need to line up. Thank you for saying it plainly.

Ofc not the only one, and the expectation is reasonable. A repo is coming, and for a tool like this it arguably should have been there from the start. Thank you for the nudge.

A fair question. There is no from scratch PDF engine here. It is @cantoo/pdf-lib, a maintained fork of pdf-lib, running client side in a Web Worker, with WebAssembly handling the heavier parts such as encryption. I am happy to go deeper on any part of it.

Point well taken. I appreciate it. It is being worked on .

Thank you

Our merge is page-level, not form-aware. We copy the pages (including the visual appearance of form fields), but we don't merge the PDFs' AcroForm dictionaries.

As a result, form fields typically aren't fillable after merging, and field name conflicts aren't an issue, so we don't rename fields.

We use @cantoo/pdf-lib (a maintained fork of pdf-lib) running entirely client-side in a Web Worker, so all processing happens locally in the browser and no files leave the user's device.