Contact Us

Have a question or feedback? We'd love to hear from you.

Send us a Message

Name

Email *

Subject

Message *

Email Us Directly

Prefer email? Send us a message at:

support@audiokit.app

Response Time

We typically respond within 48 hours during business days. For urgent issues, please include "URGENT" in your subject line.

Common Questions

Before reaching out, check if your question is answered:

• How AudioKit works
• Privacy & data handling
• Terms of service

Bug Reports & Features

Found a bug? Have a feature idea? We'd love to hear about it! Include as much detail as possible: browser, device, steps to reproduce, etc.

Frequently Asked Questions

Quick answers to common questions about AudioKit

AudioKit uses WebAssembly technology to run FFmpeg (a professional audio processing tool) directly in your web browser. When you select a file, it's loaded into your browser's memory and processed locally on your device. This means your files never leave your computer - there are no uploads to any server. All processing happens client-side, ensuring complete privacy.

Absolutely. Your files are 100% safe because they never leave your device. Unlike traditional audio converters that upload your files to a server, AudioKit processes everything locally in your browser.

We can't access your files even if we wanted to - they're never transmitted over the internet. This design makes AudioKit one of the most private audio tools available. Read our Privacy Policy for more details.

AudioKit supports all major audio and video formats thanks to FFmpeg:

Audio Formats:

MP3 (most popular)
WAV (uncompressed)
FLAC (lossless)
M4A / AAC
OGG / Vorbis
WMA, AIFF, and more

Video Formats (for extraction):

MP4
AVI
MOV
MKV
WebM
FLV, and more

The first time you use AudioKit, your browser needs to download the FFmpeg.wasm library (about 30-40 MB). This is a one-time download that enables all audio processing functionality.

After the initial load, the library is cached in your browser, so subsequent uses will be much faster. If you install AudioKit as a PWA (Progressive Web App), it will work completely offline after the first load.

Yes! AudioKit is built as a Progressive Web App (PWA), which means you can install it on your device and use it completely offline.

To install:

Desktop: Look for the install icon in your browser's address bar
Mobile: Tap "Add to Home Screen" in your browser menu

Once installed, AudioKit will work even without an internet connection, making it perfect for on-the-go audio editing.

AudioKit doesn't impose artificial file size limits. However, since all processing happens in your browser, the practical limits depend on your device:

Available RAM: Your device needs enough memory to load and process the file
Browser capabilities: Some browsers handle large files better than others
Processing power: Larger files take longer to process

Most modern devices can easily handle files up to several hundred MB. For very large files (1GB+), you may need a device with more RAM.

Yes, AudioKit is completely free with no hidden costs:

✅ No subscription fees
✅ No usage limits
✅ No watermarks on output files
✅ No account required
✅ No credit card needed
✅ No ads (currently)

AudioKit is committed to keeping core audio conversion and editing tools free forever. Since processing happens on your device (not our servers), we don't have the high infrastructure costs of traditional services.

AudioKit works on all modern browsers that support WebAssembly:

Chrome / Edge: Version 57+ (recommended)
Firefox: Version 52+
Safari: Version 11+ (macOS and iOS)
Opera: Version 44+

For the best performance, we recommend using the latest version of Chrome, Edge, or Firefox. Safari works well but may be slightly slower for large files.

We love hearing from our users! Here's how you can reach us:

Contact Form: Use the form on this page to send us a message
Email: Send us an email at support@audiokit.app

When reporting bugs, please include:

Browser name and version
Device type (desktop/mobile, OS version)
Steps to reproduce the issue
File format you were working with
Any error messages you saw