Does an online MP3 cutter upload your file?

Two ways an online cutter can work

• Upload, cut on a server, download. Your file travels to the site's server, is cut there, and the result comes back. The file sits on someone else's computer for a while.
• Cut in the browser. The page reads your file from your disk, decodes and cuts it with code running in the tab, and saves the result as a download. Nothing needs to leave your device.

From the outside both look the same: you pick a file, drag two handles and get a download. The difference only shows in the network traffic, and every desktop browser lets you see that traffic.

How to check any online MP3 cutter in Chrome

These steps use the Network panel described in the Chrome DevTools documentation (developer.chrome.com). Use a file you don't mind testing with.

1. Open the cutter's page.
2. Open DevTools: F12 or Ctrl+Shift+I on Windows and Linux, Cmd+Option+I on a Mac. Click the Network tab.
3. Tick Preserve log, then click the Clear button (the circle with a line through it) so the list is empty.
4. Now open your file in the cutter, cut it, and download the result. Don't reload the page.
5. Look at the list. Right-click a column header and turn on Method if it isn't shown. An upload is a POST or PUT request. Type method:POST into the filter box to show only those.
6. Click a suspicious request and open its Payload tab. An upload carries your file or a large chunk of it.

Quick offline test: after the page has loaded, open the No throttling menu in the Network panel and choose Offline, then try to cut. A cutter that needs a server will fail or hang. One that works in the browser keeps working. Go back to No throttling when you are done.

How we tested

• Page: the live audio cutter at snipaudio.com, with its Google Analytics tag, opened in Chromium (Playwright 1.63.0), not a local copy.
• Files: a 3-minute stereo test signal we made (a 440 Hz tone with pink noise), saved as a 31,752,078-byte WAV and as a 2,880,574-byte MP3 at 128 kbps. No personal recordings were involved.
• Actions: open the file, set the region to 60.000 s through 90.000 s, download it as MP3 at 320 kbps, then as WAV.
• Capture: every request the tab made, recorded through the Network events of the Chrome DevTools Protocol, split into steps. We waited 3 seconds after each step so late requests would be counted.
• Offline run: the same steps with the browser set offline right after the page finished loading.
• Control: to prove the capture sees uploads, the page then sent the test file to this site with a POST request on purpose.

What the capture showed

The page load fetched the page, lame.min.js (the MP3 encoder) and app.js from this site, plus Google's gtag.js, and sent one Google Analytics page-view hit to region1.google-analytics.com. That hit was a POST with a 0-byte body: the visit details travel in the request address, not as an upload. Together the page load received about 255 KB (255,559 to 255,825 bytes across our runs on 2026-09-28; the number moves a little whenever the page changes), most of it the analytics script. After that the tab made no request at all: nothing was sent when the file was opened or the clip was saved. Before we added Google Analytics, the same test counted 3 requests at page load and 72,499 to 72,751 bytes received. The downloads were blob: links, which means the file was built inside the tab. A normal browser window usually also fetches the small icon shown on the tab (favicon.svg or favicon.ico, 236 or 3,420 bytes); our headless test browser did not request it. Like the other requests, it only downloads.

The control row is what an upload looks like. The POST request carried exactly as many bytes as the test file, 2,880,574 for the MP3 and 31,752,078 for the WAV. That is the pattern to look for when you check another cutter.

Offline, the cut came out the same

A tool that cut on a server could not have produced these files with the network off. It also shows you don't need a steady connection: once the page is open, the cutter keeps working.

What a clean capture does and doesn't prove

• It proves that during your session the file was not sent anywhere. Sites change their code, so a check is worth repeating if it matters to you.
• "Not uploaded" doesn't mean the site gets nothing. Loading any page sends normal browser information such as your IP address. This site also counts visits with Google Analytics. Both are covered in the privacy policy.
• On a phone you can't open the network panel easily. The offline test still works there: load the page, turn on airplane mode, then open your file.

Questions

Is an online MP3 cutter that uploads files unsafe? Not by itself, but your file is then on a server you don't control, under that site's rules. For private recordings, prefer a tool that passes the offline test.

Does cutting in the browser lose quality? Exporting MP3 re-encodes the clip, wherever the cutting happens. We measured how much in Does cutting an MP3 lose quality?

Do the other tools on this site upload files? Each tool page answers this in its FAQ, and you can check any of them with the same steps. To combine clips, use the audio joiner.