GUIDE · LOCAL FILES
Get a useful comparison from your files.
MutualLens compares your uploaded followers and following immediately. An account label, date and completeness checkbox are not required.
A whole direction is missing
Include both followers and following. A missing file is different from a recognized list containing zero records. The checker requests the missing direction instead of silently treating it as empty.
A file needs a direction
Some loose files contain valid relationship records without identifying whether they are followers or following. Use the file assignment controls and choose from the original export context. Never infer direction from which list has more accounts.
Split files and ZIP downloads
Select all relevant parts together, including multiple ZIP downloads from the same export. Nested relationship folders are recognized. The importer selects relevant relationship entries without expanding unrelated photos, videos or messages.
Known omissions still produce useful results
If both lists are usable but numbered parts or individual records are missing, the report shows qualified differences such as “Not found in supplied followers.” It explains skipped or isolated records and includes these limitations in downloads. This is a comparison of usable supplied records, not a confirmed current relationship claim.
JSON, HTML and saved MutualLens datasets
Supported relationship JSON and HTML exports can be selected directly or inside ZIP archives. HTML is read as inert data: uploaded scripts, images and links are not executed or fetched. MutualLens dataset JSON can be reopened after schema validation. Renaming an unrelated file does not make it a relationship list.
Corrupt files or resource limits
Keep the original files and follow the specific error. Archive metadata, relevant decompression and parsed relationship data have security budgets. A rejected corrupt or oversized relevant entry needs a fresh export or the smallest useful selection of followers and following parts; it is not an account-count cutoff.
Optional history details
Basic comparison does not need your username or source date. Compatible historical comparison needs a matching known account label or stable ID and known, ordered collection dates. Two unlabeled snapshots are not assumed to describe the same account.