> For the complete documentation index, see [llms.txt](https://docs.apryse.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.apryse.com/web/audio/audio.md).

# JavaScript Audio Redaction Library

Redacting audio file has become easier with audio redaction JS. Apryse WebViewer use ffmpeg for redaction.Play, comment, and redact various audio formats directly in your browser. Explore the demo now

{% hint style="info" %}
New licenses for WebViewer Audio are no longer offered.
{% endhint %}

WebViewer Audio allows playback, commenting and redaction of `mp3`, `wav`, `flac`, `ogg` as well as video formats inside the browser (in addition to all standard [functionality](/web/what-is-webviewer/feature-support.md) and [supported file types](/web/what-is-webviewer/file-format-support.md)).

Annotations are kept separate from the underlying file and can be saved into a database, as a global XFDF file, or as separate XFDF files for each user. Permissions can be applied to the annotations, providing control over who can see annotations, whether or not some users are read-only, and whether or not they have an ability to annotate or redact

<a href="/web/audio/open-audio-file.md" class="button primary">Get started with WebViewer Audio</a>

## Get started

[Open an audio file](/web/audio/open-audio-file.md) Load a mp3, wav, flac, or ogg file.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.apryse.com/web/audio/audio.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.