# Chat file download format **URL:** \ **Category:** Meetings\ **Created:** [February 1, 2023, 10:34pm UTC](https://devforum.zoom.us/t/chat-file-download-format/82490 "2023-02-01T22:34:40Z")\ **Posts on this page:** 7\ **Page:** 1
**Author:** ![afinkel](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/afinkel/32/44821_2.png) [@afinkel](https://devforum.zoom.us/u/afinkel)\ **Post date:** [February 1, 2023, 10:34pm UTC](https://devforum.zoom.us/t/chat-file-download-format/82490/1 "2023-02-01T22:34:40Z")
**API Endpoint(s) and/or Zoom API Event(s)** [https://marketplace.zoom.us/docs/api-reference/zoom-api/methods/#operation/recordingGet](https://marketplace.zoom.us/docs/api-reference/zoom-api/methods/#operation/recordingGet) **Description** Is there a documented definition of what format the chat files are that are references in the `recordingGet` endpoint? Until recently we understood the format to be : `\t:\t`. However recently we noticed that on occasion the tabs (\t) are spaces. We have a solution in place to handle this new observed behavior, but if there’s documentation that is a ground truth on what the format should be, we’d be able to build the most robust solution. Thanks! ---
**Author:** ![elisa.zoom](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/elisa.zoom/32/47836_2.png) [@elisa.zoom](https://devforum.zoom.us/u/elisa.zoom)\ **Post date:** [February 3, 2023, 7:45pm UTC](https://devforum.zoom.us/t/chat-file-download-format/82490/2 "2023-02-03T19:45:19Z")
Hi @afinkel Thanks for reaching out to the Zoom Developer Forum and welcome to our community! I am happy to help here! I do not think there is other documentation available about this, other than the endpoint you mentioned. But let me look into this internally and I will come back with an update shortly. Best, Elisa ---
**Author:** ![afinkel](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/afinkel/32/44821_2.png) [@afinkel](https://devforum.zoom.us/u/afinkel)\ **Post date:** [February 13, 2023, 5:02pm UTC](https://devforum.zoom.us/t/chat-file-download-format/82490/3 "2023-02-13T17:02:07Z")
Hi! Any update on this? It’s important to us that any further modification of file formats are notified to us, since we parse those files. And if the format changes our parsing will need to be updated accordingly. Thanks! Asher ---
**Author:** ![elisa.zoom](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/elisa.zoom/32/47836_2.png) [@elisa.zoom](https://devforum.zoom.us/u/elisa.zoom)\ **Post date:** [February 13, 2023, 8:19pm UTC](https://devforum.zoom.us/t/chat-file-download-format/82490/4 "2023-02-13T20:19:30Z")
Hi @afinkel Sorry for the late reply. I am still looking internally if we have public documentation available for this. ---
**Author:** ![elisa.zoom](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/elisa.zoom/32/47836_2.png) [@elisa.zoom](https://devforum.zoom.us/u/elisa.zoom)\ **Post date:** [March 7, 2023, 3:02pm UTC](https://devforum.zoom.us/t/chat-file-download-format/82490/6 "2023-03-07T15:02:24Z")
HI @afinkel Sorry for the late reply I heard back from our Engineering team about this issue. It looks like the behavior that you noticed was caused by a task we ran in one of our releases. We have identified it and we will fix it this weekend, so the format will go back to `\t:\t` . Hope this helps, Elisa ---
**Author:** ![afinkel](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/afinkel/32/44821_2.png) [@afinkel](https://devforum.zoom.us/u/afinkel)\ **Post date:** [March 7, 2023, 7:33pm UTC](https://devforum.zoom.us/t/chat-file-download-format/82490/7 "2023-03-07T19:33:02Z")
These seem like breaking changes that should be mentioned in release notes. Is there a plan for this going forward? ---
**Author:** ![elisa.zoom](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/elisa.zoom/32/47836_2.png) [@elisa.zoom](https://devforum.zoom.us/u/elisa.zoom)\ **Post date:** [March 7, 2023, 7:59pm UTC](https://devforum.zoom.us/t/chat-file-download-format/82490/8 "2023-03-07T19:59:57Z")
@afinkel I agree with you and yes this will be in our release notes, I will confirm with Engineering team on this