HN user

pratik227

79 karma
Posts14
Comments42
View on HN

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.

Good questions.

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.

Thanks for pointing this out. You’re right - some assets are currently loaded at runtime, which can cause actions to hang if the internet is cut mid-session. All PDF processing itself happens locally in the browser, and as you noticed, serving the page locally works fully offline. Improving offline behavior and making this easier to verify is on the roadmap