Instagram export troubleshooting

Troubleshoot an Instagram JSON or ZIP export

Use the archive itself to diagnose missing relationship lists, wrong formats, incomplete requests, unreadable ZIPs, unsupported structures, and oversized media downloads before requesting the data again.

JSON or ZIP only
Split followers supported
Coverage-aware diagnosis
No result guessing

Analyze the export →

No social login · No password · Official export files

Supported scope

What this page is designed to help with

Format checks

Distinguish supported JSON and ZIP uploads from HTML downloads, nested archives, damaged files, and renamed non-export files.

Relationship paths

Check followers_1.json, additional numbered follower files, following.json, and other supported relationship records.

Partial-export diagnosis

Separate an intentionally narrow request from missing categories, empty datasets, changed structures, or the wrong selected profile.

Archive-size triage

Reduce media-heavy requests without removing the JSON records needed for the selected report.

Start here

Match the symptom to the evidence

An unsupported-file message usually means the upload is not JSON or ZIP, the ZIP cannot be opened, or the archive has no recognizable Instagram or Threads content. A report with missing sections is different: the archive was recognized, but a required dataset was absent, empty, oversize, or structurally unfamiliar.

Do not treat an empty result as proof that an account has no followers, comments, or history. First confirm the requested categories, profile, date range, format, and actual filenames.

No upload accepted: verify extension, upload size, and that the ZIP opens locally.
No relationship report: verify Followers and Following were selected.
Only part of the follower list appears: look for every followers_N.json file.
No Advanced Insights: request broader Instagram categories, not only Connections.
Threads shown instead of Instagram: verify the profile selected in Accounts Center.

Format and platform

Use JSON and select the intended Instagram profile

The importer accepts .json and .zip. HTML is designed for reading in a browser and is not a supported structured input. Renaming an HTML file to .json does not convert it.

The platform detector uses directory paths, wrapper keys, and profile-link hosts. An export containing Threads markers can be classified as Threads; a mixed archive follows the platform represented by its relationship files. Requesting the wrong profile is fixed at the export source, not by relabeling the ZIP.

Split follower files

followers_1.json is often only the first part

Instagram can split large follower lists into followers_1.json, followers_2.json, and additional numbered files. The importer merges every supported follower part and keeps one normalized username record.

Following uses following.json in the current supported layout. If you manually extract files, include the complete follower set and following.json. Uploading only followers_1.json can make a large account look artificially small.

Fictional complete relationship folder

connections/followers_and_following/
  followers_1.json
  followers_2.json
  followers_3.json
  following.json

All three follower parts contribute to the current follower set.

Paths and partial exports

Folder depth can vary, but recognizable records must still exist

The ZIP catalog matches supported filenames at any safe folder depth, so an extra top-level export folder is normally acceptable. Bare relationship JSON files are also supported. The JSON shape is validated instead of trusting the filename alone.

A narrow Connections-only request can build the Follower Report but cannot produce privacy, content, advertiser, or comment insights. Conversely, an activity-only export may contain useful JSON yet lack both lists needed to build relationship comparisons.

Relationship mode recognizes numbered followers files and supported account-list filenames.
Full-export mode is selected when broader Instagram category directories are present.
Known filenames with malformed or changed JSON are marked unrecognized.
Supported empty files are distinguished from missing files where the adapter can validate the empty wrapper.

Corrupt and unsafe archives

Upload the original ZIP, not a ZIP inside another ZIP

An unreadable ZIP stops parsing and returns a generic fresh-export error. Nested archives, unsafe paths, duplicate paths, extreme compression ratios, and oversize JSON entries are rejected by the archive catalog rather than extracted speculatively.

Current defaults cap the request at 64 MB, individual decoded JSON files at 16 MB, total decoded JSON at 96 MB, archive entries at 10,000, and expanded content at 1 GB. Production environment settings can lower or raise those defaults, so a deployment can have a different effective limit.

Media-heavy downloads

Photos and videos add size but not relationship evidence

The archive catalog counts common media files and skips them. Message bodies are also skipped. Those files can make an otherwise useful export exceed the upload limit without improving follower, Snapshot, advertiser, profile-history, content-timestamp, or comment analysis.

When requesting a replacement, choose the needed information categories, JSON, and a suitable date range. Reduce media quality or omit original media when the question only needs structured JSON records.

Interpret the fix

A repaired export improves coverage, not historical certainty

After the right files are present, current Followers and Following support current relationship calculations. They still do not reconstruct every earlier follower state.

Historical change needs an explicit platform history record or an earlier Snapshot. Troubleshooting should never convert a present-day mismatch into an unsupported dated unfollow claim.

Questions

Common questions

Can I upload followers_1.json by itself?

Yes, but it may be only one part and it cannot support mutual or one-sided calculations without Following. The original ZIP is usually a better diagnostic input.

Why was my ZIP recognized but no report created?

The archive may contain valid activity data but no usable Followers or Following records. Check the selected categories and coverage.

Does extracting the ZIP fix a corrupt archive?

If your computer cannot open it cleanly, request a fresh export. If it opens, upload the original ZIP or the required JSON files rather than nesting the ZIP again.

Why are photos and messages skipped?

They are not required for the supported relationship and insight calculations. Skipping their contents reduces unnecessary processing of private or large files.

Keep exploring

Instagram export analyzer

Review the relationship and Advanced Insights file requirements.
Download Instagram data

Follow the current Accounts Center request workflow.
Threads JSON export guide

Compare the distinct Threads paths and supported behavior.
Export privacy and processing

Understand what is read, skipped, retained, and excluded from indexing.

Try the corrected export

Upload the original JSON export or the complete supported relationship files after checking format, profile, paths, and size.