Measured: converting here vs the time just to upload the file
A converter that works on a server cannot finish before the whole file has been sent to it, and the result still has to come back. To put a number on the sending alone, the conversion here was timed with a 728,935,720-byte, 10-minute MOV, and the upload with the measured upload rate of the same desktop PC, on 12 and 13 November 2026. While it was opened and converted to MP3 and M4A on the live site, the page sent 304 bytes of request bodies in total, one analytics event; the no-upload guide shows how to run that check yourself.
| Step | Time |
|---|---|
| Here: file opened, waveform ready | 3.6 s |
| Here: MP3 made (14 MB) | 10.7 s |
| Here: unchanged M4A copy (9.7 MB) | 1.9 s |
| Upload only, at this connection's measured 255 Mbit/s | about 23 s |
The upload rate is the average of three 100 MB uploads to Cloudflare's public speed test on 13 November 2026 (2.8, 3.9 and 3.2 s). That endpoint refuses a single 729 MB body, so the 23 s is the measured rate applied to the file size. It includes no queue, no conversion on a server and no download of the result. On a slower uplink the gap grows in proportion: at 20 Mbit/s the same upload alone would take about 4 min 52 s (728.9 MB × 8 ÷ 20). The local times do not depend on the connection.
What happens after you choose a file
PrivateMP3 first identifies the container, lists its audio tracks and reads the duration. It selects the first audio track and shows an Audio track picker only when more than one is found. The selected track is then decoded progressively to build the waveform. A re-encoded output waits for the Ready message; an eligible unchanged copy of AAC, AC-3 or E-AC-3 into M4A is the exception because it does not need decoded samples.
The Play button is a separate browser preview of the original local file. A disabled Play button does not by itself mean conversion will fail. The waveform and Convert status are the relevant checks for the selected audio track.
Two tasks, one editor
The Task switch above the drop zone decides what the highlighted range means. It can be changed before or after a file is open.
| Task | What is saved | Outputs |
|---|---|---|
| Convert or cut | The whole track, minus every interval you remove. A selection on its own changes nothing until you press Remove selection or Keep only selection. | MP3, M4A, WAV |
| Ringtone clip | Only the highlighted range. It starts as the first 30 seconds and has a 30 ms fade at each end, switched on. | M4A, MP3 |
Use the editor in this order
- Open a file already stored on your device.
- If an Audio track picker appears, choose the intended language or mix before editing.
- Wait for Ready, then drag over a section you want to inspect.
- Press Remove selection to delete that interval, or Keep only selection to discard everything outside it. Dragging a selection alone does not change the output.
- Repeat Remove selection for additional unwanted intervals. The kept sections remain in their source order.
- Choose an output, press Convert and use Save file only after the result is finished.
Changing the audio track after editing opens a warning because the selection, cuts, volume regions and undo history belong to the old timeline. Continuing clears them and starts a new waveform scan.
Remove a section or keep only one
The two cut buttons solve opposite jobs. Remove selection marks the highlighted interval as unwanted and keeps the rest of the file. Use it repeatedly to take several interruptions, pauses or false starts out of a longer recording. Keep only selection discards everything before and after the highlighted interval. It also replaces earlier cuts, so use it when the final result should be one continuous excerpt.
Touching or overlapping removed intervals are merged into one cut. The list below the waveform shows every resulting interval, its removed duration and an Undo button for that row. The exported segments are the complement of that list: they stay in their original order and are joined into one output timeline.
Use the time fields for a close boundary
The Start and End fields accept plain seconds such as 90, minutes and seconds such as 1:30.5, or an hour form such as 1:02:03.250. A comma is also accepted as the decimal separator. Values are kept inside the file duration, and the start cannot pass the end.
Keyboard controls provide smaller adjustments without trying to drag a narrow handle on a phone or trackpad. Left and Right move the focused selection or boundary by 0.1 seconds. The I and O keys set the start or end at the current playhead. Delete or Backspace applies Remove selection. Ctrl or Command with Z restores the preceding edit; Ctrl+Y or Command+Shift+Z reapplies it.
Volume edits belong to a selected interval
Up and Down change the selected interval by 1 dB, within the editor's −24 dB to +12 dB range. The change remains attached to source time, so it stays aligned when an earlier section is removed. Preview applies those volume regions as playback crosses them.
A volume change is not metadata. It changes decoded sample values and therefore prevents the unchanged packet copy, just as a cut does. Changing to another audio track also clears selections, cuts, volume changes and undo history after a confirmation because those times belong to the old track.
Removing pauses without marking each one
Once the waveform is ready, the Remove silence panel lists every stretch quieter than a limit it works out from the recording, and removes them in one step that Undo reverses. Each removed pause becomes an ordinary row in the cut list, so it can be restored on its own. The silence guide has the test against recordings with known gaps and the noise level where it stops working. The panel is not offered on the clip task, where the selection is the output.
MP3, M4A and WAV are different processing choices
| Output | What this implementation writes |
|---|---|
| MP3 | A new 192 kbps MP3 from the selected decodable track. |
| Unedited AAC, AC-3 or E-AC-3 → M4A | The original packets in a newly written M4A container. |
| Edited, or any other codec → M4A | New 192 kbps AAC after decoding. |
| WAV | Decoded audio as 16-bit PCM. |
There is no bitrate picker. MP3 and newly encoded M4A use the fixed 192 kbps target. M4A avoids re-encoding only when the visible copy note appears; a cut or volume change disables that route. On a 128 kbps recording that can make a shorter file larger: removing a quarter of a 10-minute test recording made its M4A grow by about 12 percent, as the guide to smaller lecture audio shows. WAV avoids another lossy encode, but it cannot improve a source that was already compressed.
Measured: cutting an MP3 makes a new, larger MP3
Tested on 6 October 2026 in Chrome 154.0.8037.98 and Edge 154.0.4258.53 on Windows 11 (Intel Core i5-13600KF, 32 GB), with files generated by FFmpeg from a 220 Hz tone and quiet pink noise. Times are from Chrome; Edge differed by at most 0.7 s on any row. Each saved file was read back with ffprobe. The method is described with the screen recording test results.
The source was a five-minute MP3 at 128 kbps, 44.1 kHz stereo, 4,801,140 bytes. File check listed it as MP3, 128 kbps. Exported unchanged in length:
| Output | Time | Saved size | What happened |
|---|---|---|---|
| MP3 | 2.7 s | 7,201,801 bytes | Decoded and encoded again at 192 kbps |
| M4A | 1.7 s | 7,255,842 bytes | New AAC at 192 kbps |
| WAV | 2.4 s | 52,927,532 bytes | 16-bit PCM, 44.1 kHz stereo |
The new MP3 is 50 percent larger than the 128 kbps original and cannot sound better than it; there is no packet-level MP3 cut here. When the source is already a small MP3 and the only job is trimming silence, expect the file to grow. The output also ran 94 ms longer than five minutes, which is encoder padding at the ends.
Making a ringtone clip
Choose Ringtone clip under Task, then open the file.
- Move past the introduction. The clip task starts with the first 30 seconds selected. That matches the iPhone limit below, but it is only a working range. Drag across the waveform or enter exact times to choose the part that reaches its recognizable sound quickly.
- Set both edges by ear. Put the left handle where the sound begins and the right handle before the unused tail.
- Preview the whole selection. The highlighted range is the output. Listen from its first attack through its last sound and leave a little breathing room when an immediate start feels abrupt.
- Compare the fade. It is enabled initially. Switch it off only after listening to both boundaries.
A shorter clip gets to the useful sound sooner during an incoming call and makes a smaller file. On iPhone the limit is 30 seconds; Google's Android instructions give none. A 30-second clip therefore works on both, and a shorter one rings sooner with the part you chose.
The fade is deliberately short
Cutting while the waveform is away from zero can create a discontinuity heard as a click. The fade control applies a 30 millisecond gain ramp to each end of the final clip. It softens that boundary; it is not a musical fade-in or a long fade-out. A fade changes samples and therefore requires re-encoding. Cutting on clean silence may sound better with it disabled, which is why previewing both ends matters.
Both clip formats are new encodes
PrivateMP3 writes MP3 or M4A ringtone clips with a 192 kbps target. There is no bitrate control. At a fixed target, file size mainly follows clip duration. MP3 is useful when the phone's sound picker or transfer instructions ask for MP3. M4A is useful when the next installation application accepts AAC.
Neither output is a packet copy here. The selected subsection changes the timeline, and the default fade changes sample values. Turning the fade off still leaves a trimmed selection that must be encoded again.
Measured: a 30-second clip with and without the fade
Tested on 10 October 2026 in Chrome 154 on Windows 11. The source was a ten-minute MOV with a continuous 220 Hz tone and quiet pink noise, so any cut lands mid-waveform, the case where a click is likely. The selection was 0:10 to 0:40. Each saved file was decoded to PCM and its level measured in 5 ms windows.
| Output | Saved size | Length | Level, first 5 / 10 / 15 / 20 / 25 / 30 ms |
|---|---|---|---|
| M4A, fade on (default) | 726,942 bytes | 30.016 s | -47.5, -43.8, -40.5, -34.9, -32.6, -30.6 dB |
| M4A, fade off | 727,126 bytes | 30.016 s | silent, -60.3, -31.1, -29.9, -30.2, -29.8 dB |
| MP3, fade on | 720,744 bytes | 30.024 s | silent, silent, -109.3, -95.2, -62.0, -46.6 dB; the ramp starts after 22 ms of encoder delay and reaches -36.2 dB by 40 ms |
The steady level of the clip was -30.4 dB. With the fade, the start climbs to it over about 30 ms and the end falls away the same way. Without it, the sound goes from nothing to full level within 5 ms, which is the step heard as a click. Both encoders add a little silence: about 9 ms at the start of the M4A and about 22 ms at the start of the MP3, which is the MP3 encoder's delay. Neither is audible on a ringtone, but it is why the files run slightly over 30 seconds. At 192 kbps a 30-second clip is about 0.72 MB in either format.
Save here, install on the phone
The page creates an audio clip; it does not install a ringtone or produce a device-specific ringtone package. These are the documented routes for the saved file.
- iPhone. Save the clip to Files. In GarageBand, open Files, browse items from the Files app, touch and hold the clip and drag it all the way to the left into the Tracks view. Then tap Share, Ringtone, give it a name and tap Export. Apple states ringtones can be up to 30 seconds long and offers to shorten a longer one. (Apple: create a custom ringtone on your iPhone)
- Android with Files by Google. Open Files by Google, go to Audio under Categories, play the clip, tap More, then Set as ringtone, and allow the app to modify system settings when asked. Google's page gives no format or length limit. (Files by Google Help: set an audio file as your ringtone)
- Pixel over USB. Connect the phone to a computer, copy the MP3 into the Ringtones folder, disconnect, then choose it in Settings, Sound & vibration, Ringtone. Google's instructions name MP3 for this route. (Pixel Phone Help: sound settings)
Other Android makers use their own menus. If a sound picker does not list the clip, try the MP3 version.
Supported container does not guarantee a usable codec
The file picker accepts MP4, MOV, MKV, WebM, MPEG-TS, MP3, M4A, AAC, WAV, OGG and FLAC inputs. A container can still hold an audio codec that the current browser cannot decode. Multiple tracks in one file can also have different codecs, so one may work while another displays no decoder.
AVI, WMV, WMA, FLV and AIFF are not accepted by the shipped container reader. Renaming an unsupported file does not change its internal format. If the container opens but the waveform does not, use the troubleshooting section of the format guide rather than guessing from the extension.
Local processing removes the upload, not device limits
The browser reads the selected file from local storage and the conversion worker processes it on the same device. Page assets, advertising, Google Analytics and Cloudflare performance measurement still make their own network requests, but those requests do not carry the selected media. The local-processing guide shows how to inspect this distinction.
The page imposes neither a subscription tier nor a configured byte limit. Large files still take longer to scan and convert, need sufficient browser storage for the output, and can be interrupted when a phone suspends a background tab. No untested gigabyte, duration or processing-time guarantee is used here.
Process only media you own or otherwise have the right to use. The page reads local files; it has no URL input, external download function or access-control bypass.
One converter for every container
MP4, MOV, MKV, WebM and M4A all open in the converter above; there is no separate page per format, because the work is the same. Dolby Digital tracks, which browsers cannot decode on their own, also become MP3 here; the MKV audio guide has the test results. What differs is the audio track inside, and the File check panel shows it once a file is open. The format guide covers the cases that need a decision, with measured results for MP4, MOV, WebM and M4A files, and what each message means when the waveform never appears.