What runs in your browser
The image, video, and PDF engines are WebAssembly builds of the same libraries desktop apps use: mozjpeg, oxipng, libwebp, libavif, ffmpeg, pdf-lib, and pdf.js. Your browser downloads that code from needfiles.com once, then runs it against your file on your own processor. The result is a file in your browser's memory, which you download or discard.
Because there is no processing server, the privacy claim is a fact about how the site is built rather than a policy. There is no server-side code path that could receive a file.
What we count
We use Vercel Analytics to count page views and to count how many times each tool completes. Those counts carry the tool name only. They never include file names, file sizes, or file contents, and analytics sets no cookies.
What we never collect
- Your files, in whole or in part.
- File names, metadata, or thumbnails.
- Accounts, email addresses, or payment details. The site has none.
Check it yourself
- Open the developer tools with F12, or ⌥ ⌘ I on a Mac.
- Pick the Network panel and leave it open.
- Drop a file on any tool and confirm it.
- Watch the panel. You will see the site load its own code and engine files, and no request that carries your file.
- Go offline and run the tool again. It still works, because nothing needs a server.