How to check audio file compatibility before sending?
Learn to check the technical parameters of your audio files before sending them to a platform or client.
Try it now
Use our free online tool
Sending an incompatible audio file can have frustrating consequences: platform rejection, wasted time, or worse, a bad impression with a client or collaborator. Checking compatibility before sending is a crucial but often neglected step.
The technical parameters of an audio file – format, codec, bitrate, sample rate, number of channels – determine its compatibility with different destinations. A file perfect for SoundCloud may be unsuitable for radio broadcast or integration into a mobile application.
This article guides you through verification methods and teaches you how to anticipate compatibility issues before they occur, saving you valuable time.
Table of Contents
What technical parameters to check?
File format (container): MP3, WAV, FLAC, AAC, OGG, AIFF, etc. Each platform or device has its supported formats. MP3 is the most universal, WAV the most compatible with professional software.
Codec (encoding): sometimes format and codec differ. An .m4a file can contain AAC or ALAC. Check the actual codec, not just the extension.
Bitrate: expressed in kbps, it determines quality and size. 128 kbps is the minimum acceptable, 320 kbps is the maximum for MP3, and "lossless" for WAV/FLAC.
Sample rate: 44.1 kHz is the CD standard, 48 kHz the video standard, 96 kHz and above for high resolution. Frequency conversions can cause problems.
Number of channels: mono (1 channel), stereo (2 channels), or multichannel (5.1, 7.1). A 5.1 file won't play correctly on a stereo system without downmix.
Bit depth: 16 bits (CD standard), 24 bits (professional production), 32 bits (mixing). Some platforms only accept 16 bits.
Available verification tools
Convertly Audio: import your file and all technical characteristics are displayed automatically. It's the fastest and most complete way to check your files.
MediaInfo (free, Windows/Mac/Linux): powerful desktop tool that analyzes in detail any type of media file. Displays codec, bitrate, frequency, duration and metadata.
VLC Media Player: press Ctrl+I (or Cmd+I on Mac) to display information about the currently playing media. Convenient as VLC is often already installed.
System properties: on Windows (right-click > Properties > Details) or Mac (Finder > cmd+I), you get basic information.
FFprobe (command line): for technical users, FFprobe gives all information in one command: ffprobe -i myfile.mp3
Quick methods on each system
On Windows: right-click on the file > Properties > Details tab. You'll see duration, bitrate, and sometimes frequency. For more details, use MediaInfo or Convertly Audio.
On macOS: select the file in Finder, then Cmd+I. Basic information appears. For complete analysis, open in QuickTime and check Window > Inspector.
On Linux: use the command "file myfile.mp3" for basic type, or install mediainfo for detailed analysis.
On smartphone: audio playback apps like VLC mobile display properties. Otherwise, apps like "Audio Converter" or "Media Info" are available.
Reading recipient specifications
Before sending a file, always consult the recipient's technical documentation. Platforms publish their requirements in their FAQs or help pages.
For clients or collaborators, ask their technical preferences. A sound engineer will prefer 24-bit WAV, a web developer will want lightweight MP3.
Broadcasters (radio, TV) have strict standards: PCM format, exact frequency, calibrated sound levels (EBU R128 in Europe). Ask for their specifications.
For video games and applications, formats vary by platform: OGG for many games, AAC for iOS, MP3 for maximum compatibility.
When in doubt, the "safe bet" is: MP3 320 kbps, 44.1 kHz, stereo. This format is accepted almost everywhere and offers good quality.
Universal compatibility checklist
✅ Format: MP3 (maximum compatibility) or WAV (maximum quality)
✅ Bitrate: minimum 128 kbps, ideally 256-320 kbps for MP3
✅ Frequency: 44.1 kHz (audio standard) or 48 kHz (video standard)
✅ Channels: stereo for music, mono acceptable for voice
✅ Bit depth: 16 bits (compatible everywhere) or 24 bits (production)
✅ Size: check recipient limit (often 500 MB - 5 GB)
✅ Duration: respect limits (varies by platform)
✅ Metadata: title, artist, album filled if necessary
✅ Levels: peaks not exceeding 0 dB, ideally -1 dB
✅ Listening test: file plays without cuts or distortion
Creating verification presets
To save time, create a personalized checklist for each frequently used destination type.
Preset "Streaming platforms": MP3 320 kbps or WAV, 44.1 kHz, stereo, complete metadata.
Preset "Podcast": MP3 128-192 kbps, 44.1 kHz, mono or stereo, chaptering if supported.
Preset "Professional client": WAV 24 bits, 48 kHz, stereo, calibrated levels -14 LUFS.
Preset "Web/App": MP3 128-192 kbps, 44.1 kHz, optimized size, fast loading.
Note these presets in a document and check systematically before each send.
Ready to try?
Try Convert audioHow to do it in 3 steps
Import your file to Convertly Audio to automatically display all its technical parameters.
Compare the displayed characteristics with your destination requirements (platform, client, etc.).
If a parameter doesn't match, use the appropriate conversion tool and download the corrected file.
Pro Tips
- Create a "template file" for each destination and visually compare parameters.
- Automate your checks with scripts if you process many files.
- Keep a rejection log to identify recurring errors.
Common mistakes to avoid
- ✗Relying only on file extension. Solution: check actual metadata with an analysis tool.
- ✗Forgetting to check duration on platforms with limits. Solution: note the limits of each destination.
- ✗Ignoring metadata (title, artist) that may be required. Solution: systematically fill in the fields.
- ✗Not testing playback before sending (undetected corrupted file). Solution: listen to at least the beginning and end.
- ✗Sending a 48 kHz file to a destination requiring 44.1 kHz. Solution: check frequency and convert if necessary.
- ✗Forgetting email attachment size limit (often 25 MB). Solution: use a transfer service or compress.