How to Verify Your Files Stay Private

Don't take our word for it. Every modern browser has a built-in network inspector that shows every single request a webpage makes. If a tool claims "no upload," you can prove it in under a minute. This guide works for any browser-based tool, not just ours.

What you need

• A desktop browser: Chrome, Edge, Firefox, or Safari.
• A file to test with (any MP3, WAV, or audio file you have handy).
• About 60 seconds.

Step-by-step

1. Open the tool page you want to test. For example, MP3 Cutter or Audio Converter.
2. Open DevTools.
   • Windows / Linux: press F12, or Ctrl+Shift+I.
   • Mac: press Cmd+Option+I.
   A panel opens at the bottom or side of the screen.
3. Click the "Network" tab at the top of DevTools.
4. Check "Preserve log" (a checkbox near the top). This keeps the list even if the page navigates. Optionally click the clear button (a circle with a line) to start with an empty list.
5. Use the tool normally. Drop your audio file in, trim it, convert it, and download the result.
6. Look at the Network list. Each row is one request the page made.
   • Filter by method: In the filter bar, type method:POST or method:PUT. These are the HTTP methods used to send data to a server.
   • Check the size: If you see any POST/PUT, click it and open the Payload (or "Request Body") tab. A real file upload would show a payload matching your file size (e.g., 5 MB for a 5 MB MP3). Analytics pings are typically under 1 KB and contain no file content.
7. That's it. If no request carries your file data, the tool processed everything locally in your browser.

What requests are normal?

Even a fully local tool makes some requests. Here's what to expect and what would be a red flag:

Try it right now

Pick any tool below, open DevTools first, then use it:

• MP3 Cutter — drop an audio file, trim it, download. Expected uploads: 0.
• Audio Converter — drop a file, convert to MP3 or WAV. Expected uploads: 0.
• Voice Noise Remover — drop a recording. Expected uploads: 0 (AI model downloads on first use).
• Speech to Text — drop a recording. Expected uploads: 0 (Whisper AI model downloads on first use).

Can a page hide requests from DevTools?

No. The browser's Network tab captures every HTTP and HTTPS request the page makes, including fetch(), XMLHttpRequest, WebSocket frames, and navigator.sendBeacon(). A webpage cannot bypass this. The only blind spots are browser extensions or OS-level proxies, which are outside any website's control.

What about FreeSoundTools' tools specifically?

All of our tools process audio entirely in your browser using JavaScript and WebAssembly. Your recordings and audio files are never sent to our servers or any third party. A few tools do make specific, limited network requests:

• AI-powered tools (Speech to Text, Text to Speech, Meeting Notes, Noise Remover, Humming to MIDI): download an AI model on first use (tens to hundreds of MB). The model runs on your device; your audio stays local.

Every other tool (MP3 Cutter, Audio Converter, Volume Booster, Ringtone Maker, and all others) makes zero network requests beyond loading the page itself.

Each tool's page has a "How it works" section with the specific details. But again: don't take our word for it. Open DevTools and check.

FAQ