Precise range selection
Drag the waveform handles for a quick cut, then refine the boundaries with exact time fields and small nudge controls.
Mark the exact section you want to keep on the waveform or enter start and end times. Listen to the boundary, then export a new audio file while the source remains unchanged.
Supported inputs, outputs, time precision, URL behavior and file-size limits must come from the implementation rather than static marketing copy.
Read the full guideDrop an audio file here
or
Supported formats: MP3, WAV, M4A, AAC, OGG, FLAC
File size200 MB
URL mode downloads media from its host, so network access and the host’s CORS, authorization and range-request rules apply.
An audio trimmer keeps one continuous time range and removes the material before its start and after its end. It creates a new file; it does not split the source into several parts or repair the audio inside the selected range.
Drag the waveform handles for a quick cut, then refine the boundaries with exact time fields and small nudge controls.
Listen around the start and end to avoid cutting a word, beat or breath in the middle.
Choose only formats, bitrates, sample rates and channel modes the active encoder can actually create.
Choose a supported audio file or direct URL and confirm its duration and waveform.
Move the start and end handles or type exact times; the highlighted area is the output.
Select a compatible format; use a lossless option when another editing step follows and the encoder supports it.
Export the new file, then check its opening, ending, duration and playback compatibility before leaving the page.
Both values identify the kept region. The start must be at or after zero and the end cannot exceed the decoded duration.
Small time increments are useful for speech consonants, transients and frame-accurate workflows; actual precision depends on decoding and encoding.
Most browser workflows decode and re-encode the selected range, so a lossy export may add another generation of compression.
Verify the complete data path. Local-file copy may state browser processing only when decoding, preview, encoding, telemetry and storage do not transmit media. URL mode still downloads from the source host and can fail because of CORS, authorization or range support.
Move the boundary outward, zoom in and preview again. Waveform peaks do not always reveal the start of quiet consonants.
Move the boundary to a quieter point or apply a very short validated fade.
Codec delay, container timestamps and rounding can shift the measured result. Display the actual encoded duration.
Use a direct media URL whose server allows CORS and the requests required by the decoder, or download the file and select it locally.
Trimming keeps one continuous section. Splitting creates two or more separate files from one source.
Only if the implementation has a verified stream-copy path at valid codec boundaries. A waveform-based browser editor usually decodes and re-encodes.
The cut itself does not need to, but lossy re-encoding can introduce additional compression. Use a supported lossless output for intermediate work.
Use millisecond fields only when the implementation preserves that precision. The final boundary can still be affected by codec frames and timestamps.
No. A fade only changes gain near the boundary; it does not clean the selected audio.
Not with a single-range trimmer. Use Split Audio or a multi-track editor if several separate regions are needed.
No. The tool should produce a new trimmed file and leave the selected source untouched.
State browser-only processing only after the network, encoder, diagnostics and persistence code have been verified. URL input necessarily contacts the source server.