Instagram export not working? Here is how to fix it

Requesting your Instagram data from Meta's Accounts Center should be simple, but the process fails in predictable ways. Below are the issues we hear about most often from Stats Insta users, in roughly the order people encounter them. If your problem is not listed, the FAQ covers analyzer-side questions, and you can always reach us via the contact page.

1. The export is stuck on "pending"

A pending request is usually not a broken request. Meta prepares exports in a queue, and large accounts can wait anywhere from a few hours to several days. The notification goes to the email address on the account and appears in the app — check your spam folder before assuming it never arrived.

If a request has been pending for more than four days, cancel it in Accounts Center and submit a smaller one: choose Some of your information, select only Messages, and set media quality to Low. Smaller requests complete noticeably faster, and messages are all an analyzer needs.

2. You downloaded HTML instead of JSON

This is the single most common failure. During the request, the format defaults to HTML on many accounts. HTML exports are meant for viewing in a browser; chat analyzers, including Stats Insta, cannot read them as data.

There is no reliable way to convert an HTML export into the JSON structure. Submit a new request and this time set Format: JSON explicitly before confirming. While you are there, set the date range to All time unless you deliberately want only recent messages.

3. There is no messages/inbox folder

First, make sure you fully extracted the ZIP file — some phones preview the archive's contents without actually unpacking it, and folders can appear missing. Extract it with your file manager or a computer, then look again.

If the extracted archive genuinely has no messages folder, the original request did not include Messages. This happens when "Some of your information" was chosen but Messages was left unchecked. Re-request with Messages selected. Note that the folder can also be named with a prefix in some export layouts, so search the extracted archive for message_1.json before re-requesting.

4. The download link has expired

Meta download links stay valid for only a few days for security reasons. An expired link cannot be revived; request a fresh export. When the new email arrives, download the file the same day and keep the ZIP somewhere safe so you do not have to repeat the wait.

5. message_1.json is empty or the analyzer finds no messages

• Wrong conversation folder: each folder inside messages/inbox is one conversation, and brand-new or cleared chats can be nearly empty. Try the folder you actually chat in.
• Split files: long conversations are divided into message_1.json, message_2.json, and so on. Select all of the numbered files for that conversation in the analyzer — it merges them.
• Date range: if you requested only the last year, older messages simply are not in the file.
• Still a ZIP: the analyzer needs the extracted .json file, not the archive itself.

6. Names and text look garbled

If names show strange characters or emojis look like code, you are probably viewing the raw file in a text editor. Meta encodes some characters in a way that plain editors display incorrectly. This is a display quirk, not corrupted data — Stats Insta decodes it automatically. The guide to reading message_1.json explains the encoding in detail.

7. The file is too large to handle comfortably

Decade-old group chats can produce JSON files of tens of megabytes, which can choke phone browsers and text editors. Work on a computer if you can, close other heavy tabs, and load the conversation's files on their own rather than selecting your entire inbox at once. Because Stats Insta processes everything locally, your device's memory is the limit — it is a good reason to analyze one conversation at a time.

Still stuck?

Note down which step you reached and exactly what you see on screen, then send us a message. Please never send your message_1.json file or your Instagram password — we will never ask for either, and neither is needed to diagnose an export problem.