Most import problems come from the wrong format, missing relationship files, or an oversized archive. The web analyzer stops when it cannot interpret the required data instead of treating missing information as zero.
You downloaded HTML instead of JSON
HTML is designed for reading in a browser. This analyzer expects JSON relationship records.
Request another export and select JSON. Renaming an .html file to .json will not convert it. Follow the export instructions to choose the format at the source.
The report says following.json is missing
Choose both the followers files and following.json from the same export. A followers file alone cannot show who does not follow you back because it does not say whom you follow.
If the archive does not contain the required files, request an export that includes followers and following information.
Your ZIP also contains Threads data
A complete download can contain your_instagram_activity/threads/followers.json alongside your Instagram files. These describe different services and must not be combined.
The analyzer reads Instagram relationship files only from connections/followers_and_following inside the ZIP. If you select individual JSON files, choose them from that directory. A bare filename cannot establish which service or account a manually selected file came from.
Your followers are split across files
Include followers_1.json and every additional numbered part. If you select parts 1 and 3 but omit part 2, the analyzer reports a missing part.
The tool cannot detect every possible omission. For example, if you select only part 1, it may not know that a later part exists. Select all parts and check the export yourself before relying on the result.
You selected files from multiple exports
Use one account and one export per analysis. Duplicate filenames are rejected because silently combining them could produce a misleading relationship report.
Files with different names can still come from different accounts. The tool cannot prove ownership from relationship records alone.
The archive is too large
The selected files must total no more than 100 MB. Individual supported JSON files are limited to 12 MB, and total extracted supported JSON data is limited to 32 MB. These limits help keep local browser analysis responsive.
Extract the archive on your device, then choose only the relationship JSON files. Photos and videos are skipped. Selecting only relationship files gives a relationship-only report; a full ZIP is needed for activity and insight sections.
The JSON is broken or has an unsupported structure
Use original files rather than manually edited copies. Try downloading the archive again. If the format has changed, the website may need an update; do not remove records merely to make the file pass validation.
When reporting an issue, describe the error and the file structure. Do not send your private export by default. See support for the available contact route.
Confirm the tool works before trying again
Open the sample report to explore the interface without private data. Then return to the analyzer and choose a fresh export.
Make your data readable.
Explore a sample or create a private report in your browser.
Open the analyzer ↗Full lists and more in Reports for iOS. Subscription required for full access.