Troubleshooting
Converted audio duration is wrong
A damaged timestamp table, truncated source, variable frame timing, or an incorrect trim value can produce an unexpected duration.
Reviewed against current browser behavior and AudioFetcher test fixtures on July 28, 2026.
Check these first
- 1
Play the source to the end.
- 2
Inspect reported duration in two tools.
- 3
Check trim and split values.
- 4
Compare the output waveform with the source.
Reliable fixes
- Remux or decode the source to PCM before editing.
- Avoid relying on a damaged container's duration field.
- Retain the original while troubleshooting.
Change one variable at a time and test with a short known-good file. That separates a damaged source from a browser, codec, or memory limitation.
Questions about Converted audio duration is wrong
What is the short answer to "Converted audio duration is wrong"?
A damaged timestamp table, truncated source, variable frame timing, or an incorrect trim value can produce an unexpected duration.
Does the linked AudioFetcher tool upload my media?
The local tools linked from this article process selected media in the browser. Read each tool's limits before using a large or uncommon file.
What is the most important practical point?
Remux or decode the source to PCM before editing.