Why I’m Building pdfzus

I’m building pdfzus because merging PDFs is still more complicated than it should be.

A lot of tools can technically combine files, but in practice the workflow often gets heavier than the task itself. If all you want is to put a few documents together, sort them properly, and send one clean PDF, you often end up dealing with account prompts, cluttered interfaces, uploads you may not want, or watermarks on the final file.

That was the starting point for pdfzus.

I wanted a browser-based PDF merge tool that stayed focused on the common path: add multiple PDFs, reorder them with drag and drop, merge them into one document, and compress the result if you need a smaller file for email or upload portals. No sign-up. No watermark. Just a simpler workflow for everyday document tasks.

The use cases are not exotic. They are the ordinary ones:

- job applications

- email attachments

- office paperwork

- online submission portals

Those are exactly the kinds of tasks where people do not want a giant document platform. They want something narrow, clear, and easy to trust.

One thing I got wrong at the beginning was thinking the problem was mostly technical, as if I just needed a better PDF merge engine. The real issue was workflow friction. A lot of existing solutions already “work,” but they still make a small task feel heavier than necessary.

That changed how I approached the product.

Instead of trying to build a broad PDF suite, I kept pdfzus intentionally small. The value is not in having the most features. The value is in making a repetitive task feel easier to finish.

That has shaped how I think about the product and how I’m sharing it publicly. the project now has a growing public footprint across GitHub, browser extension stores, software directories, and a few engineering-writing platforms. That has reinforced one lesson for me: utility products lose trust quickly when the story sounds bigger than the actual job being done.

So I’m trying to keep the product and the narrative aligned.

pdfzus is for straightforward document assembly in the browser. It works best when you need to combine files, keep them in the right order, and export one clean result. It is not meant to be a full enterprise document management system, and I think it gets stronger by staying honest about that boundary.

If you’ve built something similar, I’d be curious how you handled the tension between keeping a utility small and expanding into “just one more feature.”