Capability guide
Browser audio work is shaped by more than one question. The browser may preview the file, fail decode for analysis, or export only a subset of target formats. This guide explains why Picmu keeps those states separate.
Tools
The related pages turn these capability limits into page-level product logic instead of hiding them behind generic media-tool copy.
Open audio toolsTrust and privacy
Quick flow
Benefits
A guide to browser audio support, decode constraints, MediaRecorder limits, and why page-level checks matter.
Once you see the support model clearly, it becomes easier to choose between inspect, trim, convert, compress, and batch pages.
A page that explains where it stops is more useful than one that hides the limit until after you import the file.
Reading the support picture early helps you switch browsers, switch formats, or pick a supported output before you waste effort.
Tradeoffs
Playback and waveform analysis do not rely on exactly the same path, and the page keeps that difference visible.
AAC and Opus export paths often hinge on MediaRecorder support, while WAV is the more dependable native floor.
That focus is a feature. A trim page and a metadata page can stay trustworthy precisely because they are not trying to be a whole DAW.
Best practices
FAQ
Open in Picmu
The related pages turn these capability limits into page-level product logic instead of hiding them behind generic media-tool copy.