Free browser-based image converter for JPG, PNG, WebP, AVIF, GIF, HEIC, SVG and BMP - no upload. Plus 22 PDF tools and 18 developer utilities.
Replies
Best
Hunter
📌
Free file tools that run entirely in your browser - no upload.
Report
Hunter
Hi Product Hunt, I am the person behind PicConv.
The idea was embarrassingly simple. I needed to compress a photo for a government form, and the tool I found uploaded it to a server. That bothered me: the file was a scan of an identity document, and there was no way to know what happened to it afterwards.
So I built the opposite: every tool runs inside the browser using JavaScript and WebAssembly. There is no upload endpoint at all - open the Network panel and you will see requests for the page and its scripts, but never a request carrying your file. Turn off the network after the page loads and it still works.
That architecture has honest limits, and the site states them rather than hiding them. A browser cannot re-encode the images inside a PDF while keeping the text layer selectable, so PDF compression offers two modes: repackage (text stays, modest saving) or rasterise (big saving, text becomes an image). Creating AVIF only works in Chromium-based browsers. OCR needs a model we do not ship. TIFF has no native decoder. Every tool page says what it cannot do.
What is there: 86 tools across images (compression to an exact target size, HEIC, resize, crop, rotate, EXIF removal), PDFs (merge, split, organise, compress, page numbers, watermark, forms, protect, unlock), developer utilities (JSON, hashing, Base64, JWT), Markdown and SVG - in 14 languages, without an account or a watermark, funded by advertising rather than a task limit.
I would genuinely like feedback on two things: which tools are missing for your workflow, and whether the "no upload" claim is explained clearly enough to be believable.
Replies
Free file tools that run entirely in your browser - no upload.
Hi Product Hunt, I am the person behind PicConv.
The idea was embarrassingly simple. I needed to compress a photo for a government form, and the tool I found uploaded it to a server. That bothered me: the file was a scan of an identity document, and there was no way to know what happened to it afterwards.
So I built the opposite: every tool runs inside the browser using JavaScript and WebAssembly. There is no upload endpoint at all - open the Network panel and you will see requests for the page and its scripts, but never a request carrying your file. Turn off the network after the page loads and it still works.
That architecture has honest limits, and the site states them rather than hiding them. A browser cannot re-encode the images inside a PDF while keeping the text layer selectable, so PDF compression offers two modes: repackage (text stays, modest saving) or rasterise (big saving, text becomes an image). Creating AVIF only works in Chromium-based browsers. OCR needs a model we do not ship. TIFF has no native decoder. Every tool page says what it cannot do.
What is there: 86 tools across images (compression to an exact target size, HEIC, resize, crop, rotate, EXIF removal), PDFs (merge, split, organise, compress, page numbers, watermark, forms, protect, unlock), developer utilities (JSON, hashing, Base64, JWT), Markdown and SVG - in 14 languages, without an account or a watermark, funded by advertising rather than a task limit.
I would genuinely like feedback on two things: which tools are missing for your workflow, and whether the "no upload" claim is explained clearly enough to be believable.
Thanks for reading.