> 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.md). # Audio - [JavaScript Audio Redaction Library](https://docs.apryse.com/web/audio/audio.md): 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 - [Redact audio using JavaScript](https://docs.apryse.com/web/audio/audio/redact-audio-file.md): Learn how to redact audio programmatically using JavaScript. This snippet demonstrates how to redact specific time ranges in audio files, ensuring seamless operation and customization. The Apryse Web - [Play audio files using JavaScript](https://docs.apryse.com/web/audio/open-audio-file.md): Enhance your web applications by learning how to play audio files using JavaScript. Integrate audio features seamlessly with this comprehensive guide for web. The Apryse Web SDK streamlines secure, se - [Audio Redaction](https://docs.apryse.com/web/audio/audio-redaction.md): Enhance your video redaction process with WebViewer Audio, leveraging ffmpeg for seamless frame editing. Follow our guide to set up a server and integrate it into your application effortlessly. Optima - [Audio Changelog](https://docs.apryse.com/web/audio/changelog.md): Enhance your web experience with the latest updates in our Audio Changelog. Stay informed on fixes, features, and improvements for seamless audio functionality. The Apryse Web SDK streamlines secure, --- # 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.md?ask=&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.