HN Explorer

27 comments

[ 2.9 ms ] story [ 49.3 ms ] thread
pdfmergely
Author here. Quick note on how the "no upload" claim actually works, since it deserves scrutiny.

There's no upload endpoint to send files to. When you pick a file, the browser hands the app the bytes directly; the work runs in a Web Worker on your device, with WebAssembly for the heavier parts like encryption. The finished PDF is built locally and downloaded. The page is also locked down with a strict CSP so file data has no network path out — you can open the Network tab and confirm nothing leaves while you work. After the first load it works fully offline, which is the easiest proof.

The honest tradeoff: because everything runs on your device, very large files depend on your machine's memory and a phone won't match a desktop. We process a page at a time to keep memory in check.

Tools today: merge, split, reorder, rotate, delete/extract pages, compress, watermark, page numbers, protect/unlock. Free, no sign-up. Would love feedback on what to add next.

da-x
Perhaps you can also provide a Tauri-based independent downloadable app.
sscaryterry
Where is the company registered? None of these details are on your website.
steveharrison
Love the idea, but would help trustworthiness if the design looked a little less vibe-coded.
[deleted]
(comment deleted)
jimjimjim
Question about merging: How do you handle merging multiple pdf that have forms? Are the form fields renamed to prevent form field name clashes?

And what pdf toolkit do you use?

gettalong
Why is it that everyone now duplicates/vibe-codes PDF tool websites? It seems that there is one new each week for about half a year now with none providing any outstanding features over the others.
cyanydeez
theyre the AI todo app: sufficiently complex and mildly useful. will fail when real use case outstrips its minimum depth.
jamessb
This one's website (and a dead comment replying to you) suggests that processing the PDF in the browser, rather than uploading to a server, is a point of differentiation.

However, there are older tools that do this, such as BentoPDF (which is also open source) [1].

[1]: https://www.bentopdf.com/

[deleted]
(comment deleted)
fp64
Which library did you compile to WASM for this? I doubt this is a from scratch implementation of full PDF
pdfmergely
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.
hasudon7171
To me, it looks like a design generated by AI. It had exactly the same vibe as those kinds of sites I see all the time.
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.

pmb_developer
Would you consider open-sourcing the client-side code? For privacy-focused PDF tools, that seems like the easiest way to make the “no upload” claim more trustworthy.
pixel_popping
OP, you already know your website will end up in the graveyard, I just don't understand how anyone can still put up the same exact template as the last 100K viby websites released, it's literally a prompt away to have an original design, type that prompt, PLEASE.
vedant_getbags
kindly improve the SEO to not end up in the vibecoded graveyard
pdfmergely
Point well taken. I appreciate it. It is being worked on .
kewop
I cannot be the only one expecting a github repo on the website, right?
pdfmergely
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.