# Wisper API not recognizing .m4a file format

**URL:** <https://community.openai.com/t/wisper-api-not-recognizing-m4a-file-format/141251>\
**Category:** API\
**Created:** [April 4, 2023, 11:09pm UTC](https://community.openai.com/t/wisper-api-not-recognizing-m4a-file-format/141251 "2023-04-04T23:09:11Z")\
**Posts on this page:** 1\
**Showing post:** 4

<div class="post-metadata">

**Author:** ![debloper](https://sea2.discourse-cdn.com/openai1/user_avatar/community.openai.com/debloper/32/66018_2.png) [@debloper](https://community.openai.com/u/debloper)\
**Post date:** [April 5, 2023, 4:53pm UTC](https://community.openai.com/t/wisper-api-not-recognizing-m4a-file-format/141251/4 "2023-04-05T16:53:10Z")

</div>

Not certain if it’s the case with you, but m4a files are notorious for having moov atoms at the end of the file (instead of beginning). Please verify whether that’s the case with your file. If you just want to somehow make it work without getting into the moov atom locating rabbit hole, then simply try:

```bash
ffmpeg -i input.m4a output.mp3 # or, even better, output.wav

```

…and then use the MP3 (or WAV) file instead of the M4A (MP3, among many other formats, is guaranteed to have moov atom at the start of the file). So if that was the reason for the issue, it should be fixed.

**Quick Context:**

 ![image](https://us1.discourse-cdn.com/openai1/original/3X/4/7/479d6f3db635cedfb702cd596a37f84a48320bc3.png)

---

_[View the full topic](https://community.openai.com/t/wisper-api-not-recognizing-m4a-file-format/141251)._