Contact

Get in touch

You can contact us for:

• Reporting bugs or technical issues
• Suggesting new features
• Privacy and data usage questions
• Data removal requests (GDPR / LGPD)
• Partnerships and collaborations

What to include when reporting an audio problem

Most problems opening or exporting a file come down to the specific browser and the specific file. Without these details the case usually cannot be reproduced, and the message ends without a useful answer.

Which tool you used

Cut, volume, speed, equalizer, compressor, fade, noise, silence, reverse, or merge.

File format and origin

MP3 and WAV are the tested inputs. Other formats depend on the browser decoder, so say whether the file came from a phone recorder, a download, or an export from another program.

Approximate length and size

Long files use more memory, and the practical limit varies by device. A problem that only appears past a certain duration is a useful clue.

Browser, version, and system

Chrome, Firefox, Safari, or Edge, on desktop or phone. Codec differences between browsers explain a large share of failures to open a file.

What you expected and what happened

Include the export format you chose (MP3, WAV, M4A/AAC, or FLAC) if the problem appeared while saving.

What this channel cannot do

The way the tool is built creates real limits on support. They are listed here so you are not left waiting on something that cannot happen.

Recovering a file

Audio is decoded and edited in your tab and is not sent to the application server. There is no copy of your file to recover once the tab is closed.

Inspecting what you edited

For the same reason, the content, filename, and history of what you processed cannot be seen. Any diagnosis depends on what you describe in the message.

Editing work on request

The project maintains the tool and its editorial material. There is no commissioned audio editing, mastering, or restoration service.