Privacy
The no-upload guide
WebpUndo is a static site. There is no conversion API. If you are deciding whether a team can drop client screenshots here, this page is the checklist.
What the page can see vs what a server can see
Loading webpundo.com (or your Cloudflare Pages URL) fetches HTML, CSS, and JavaScript — the app. That request looks like any other website visit: IP address, user agent, maybe a CDN cache log. It does not include the images you convert later.
Adding files happens after the page is running. input type="file"and drag-and-drop give JavaScript a File object. From there the script calls createImageBitmap and canvas.toBlob. Those APIs do not take a URL of our server. They take the local file.
How to verify in DevTools
- Open the converter and the Network panel.
- Clear the request list.
- Drop a WebP and download a PNG or ZIP.
- Confirm no new request carries the image as a payload.
You should see no POST of binary data. A ZIP download is a blob URL, which looks like blob:https://… and never hits our origin. After the first visit you can even toggle the browser offline and convert again — the page is already in cache.
What we do not store
- No accounts or conversion history.
- No IndexedDB of recent files.
- No analytics in the default static build.
- Object URLs are revoked when you press Clear or leave the page.
Ads, fonts, and third parties
Article pages reserve AdSense slots. Until you paste a publisher tag, those slots are empty placeholders and load no ad script. If you enable Google AdSense later, Google will set cookies and make its own requests. That is separate from the converter. Images you drop still do not upload.
WebpUndo uses system fonts on purpose so converting a file does not require a Google Fonts connection. See the legalPrivacy policy for the short version you can link from a footer.
Workplace use
If policy forbids “upload tools,” show this page and the Network test. Self-hosting on Cloudflare Pages (or any static host) keeps the same client-side code under your hostname. The README explains thedist/ deploy. You can also save the site and open it from a local folder after a build — there is still no backend to miss.