Back to blog
Project background
- Why the editor exists
- Audio-Editor Online came out of looking for a free, private audio editor that worked without catches — no mandatory sign-up, no watermark on the result, and no uploading a file to a server just to trim a few seconds. The tool was built for that case, and the articles are written for the same people it was made for.
- The central technical decision
- All processing happens in the browser tab, through the Web Audio API. That settles privacy by architecture rather than by policy: the audio is never uploaded to the application. The trade is a real limit — long files depend on device memory, and opening some formats depends on the browser decoder.
- Other projects on the same model
- The same local-processing principle runs SafeStudio, PhotoEditor.studio, and Edit-Video.online, maintained by the same person. Different tools, the same decision about where a user’s file should stay.
Editorial record
- 14 articles, in Portuguese and English
- Each version is written independently, for meaning and natural phrasing rather than literal translation.
- Dated version note
- Every article opens with the date of its last review and what changed in the tool since publication.
- Concept separated from feature
- Topics like LUFS, true peak, and parametric EQ appear as educational content and are identified as external or unavailable in the current editor.
Found a statement that does not match the tool? Reporting it is useful, and the correction is made at the source. Report a correction
Declared responsibilities
- Maintain the editor implementation and review changes that affect audio processing.
- Compare copy, metadata, FAQs, and structured data with the factual product matrix.
- Review technical articles and identify method, date, limitations, and sources when applicable.
- Correct or remove statements that cannot be reproduced in the current tool version.
Editorial method
Articles are not presented as professional advice. Review checks that the text separates general concepts from current editor capabilities and that technical claims have a reproducible test or primary source.
How the project is runLast reviewed: 28 August 2026.