Since then, I’ve added a set of image tools that also run entirely client-side:
- Image compress, resize, crop, rotate, and format conversion
- Image → PDF and mixed image + PDF workflows
- Basic photo editing (text, filters, watermarks)
- Upscaling and background removal
- HTML/URL → image capture and face blurring
Everything runs locally in the browser (Canvas, WASM).
No backend, no uploads, no tracking.
For context, the original post saw ~9.5k visitors over two weeks.
Average visit duration was ~40s, which fits the single-task nature of the tools.
Posting as a progress update rather than a re-launch.
I don’t have a role model, bro, and I don’t need to justify anything to you. You’re not that important-so yeah, go ahead and make some contribution to the world, not here
“Sorry about that. Some people jump to conclusions about things they don’t fully understand. I’m just trying to build something useful and contribute to the community, but reactions like this can make it difficult
Image-only PDFs (scans):
These are the hardest case. If a PDF is basically high-res images (like iPhone scans), browser-based tools have limits compared to ImageMagick, which has much finer control over resampling and JPEG compression. Ghostscript-style pipelines help, but ImageMagick often wins if you’re willing to discard more detail. Improving this is on the roadmap, but it’s genuinely tough in-browser.
PDF forms:
Adobe doesn’t own forms, but editable PDF forms are extremely complex and poorly standardized. Many free tools avoid true form editing because it’s easy to break files. That’s why I haven’t enabled it yet—possible, just time-consuming and error-prone.
Everything runs locally in the browser (Canvas, WASM). No backend, no uploads, no tracking.
For context, the original post saw ~9.5k visitors over two weeks.
Average visit duration was ~40s, which fits the single-task nature of the tools.
Posting as a progress update rather than a re-launch.