Your follower count drops, but X gives you no name, no explanation, and no useful alert. You check Notifications, scan your profile, and wonder whether a recent post pushed someone away or whether the platform removed a suspicious account.

The practical answer to how to know who unfollowed you on Twitter is less direct than most guides suggest. You need dated follower snapshots, careful account-level comparison, and a way to distinguish a genuine unfollow from a deactivation, suspension, block, or spam filter. You also need to decide whether instant alerts are worth giving a third-party service access to your account.

Table of Contents

• Why Tracking Follower Loss Is Harder Than It Looks

  • A lower count doesn't identify the cause

• Manual Snapshot Comparison Method

  • Capture the complete list

• Using the X Data Archive for Follower History

  • Request and preserve each archive

  • Understand the trade-off

• Third-Party Unfollower Apps Risks and Rewards

• Distinguishing Unfollows From Other Changes

• Building a Sustainable Follower Retention Workflow

Why Tracking Follower Loss Is Harder Than It Looks

Suppose your follower count falls overnight. You remember posting a strong opinion the previous day, so you look for the person who must have left. X shows the lower total, but it doesn't identify the account behind the change. A smaller number is a net result, not an event log.

X doesn't provide a native historical “unfollowed you” log, and it doesn't send a notification when someone leaves. The Notifications timeline can show new followers, but it can't provide the reverse event, as explained in X's following FAQs. If Alex followed you on Monday and disappeared from your Followers list on Friday, X won't send a message saying Alex unfollowed you.

A lower count doesn't identify the cause

A missing account can represent several different changes:

• Voluntary unfollow: The person chose to stop following you.

• Deactivation: The account owner turned off the account.

• Suspension: X restricted or removed the account.

• Blocking: The account relationship changed in a way that affects visibility.

• Spam filtering: X hid or removed an account from the visible follower list.

That ambiguity makes one-off checking unreliable. If you search for a name after noticing a loss, you may find that the profile is unavailable. You still won't know whether the person unfollowed first, deactivated the account, or was removed by X.

Practical rule: Treat a disappearing account as “no longer present” until you confirm that the profile still exists and is otherwise accessible.

The same principle applies to other social platforms. If you manage multiple communities, this guide to measuring Instagram follower changes offers useful context for comparing audience movement without treating every fluctuation as a content verdict. For X-specific growth measurement, keep a dated record alongside the broader framework in this guide to Twitter and X follower growth over time.

The straightforward expectation is simple: X can show the relationship state today, but it can't reconstruct the exact history of every relationship for you. You create that history yourself by capturing the complete follower list repeatedly.

Manual Snapshot Comparison Method

A follower count drops between two checks, and the missing account is no longer visible. A snapshot comparison can show exactly which IDs disappeared, but it cannot prove that each account chose to unfollow you. That distinction matters because deactivation, suspension, blocking, and spam filtering can produce the same visible result.

The safest manual method is to capture the complete follower list on one date, repeat the capture later, and compare the two sets. It does not require handing your password to an unfollower service. It also produces a narrower, more honest finding: an account was present in the earlier snapshot and absent from the later one.

Capture the complete list

Record the stable user ID for every follower. Handles and display names can change, so comparing names alone may treat a rename as a departure. Keep the ID, current handle, display name, profile URL when available, and capture date together.

X's follower documentation describes paginated results, with 20 accounts returned by default and a maximum of 200 per request at that time. The limits appear in X's follower and following endpoint overview. Retrieve every page until no further followers are returned. Reading only the first visible group creates an incomplete snapshot.

For example, a creator with 1,000 followers who records only 200 accounts has captured just 20% of the audience. The comparison may then miss most changes. The pagination limits and this calculation come from the same X reference.

Use one repeatable capture routine: label the file with the account ID and date, retrieve every page, save stable IDs as the comparison key, repeat the process later, then identify IDs found in the earlier set but missing from the later set. Keep the original files unchanged so you can audit how the result was produced.

API access can also constrain the process. X's documented paths have included a limit of 15 requests per 15-minute window for the legacy follower ID endpoint under user and application authentication. Newer follows documentation describes up to 1,000 user objects per page for a newer comparison path. These details may change, so review X's migration documentation for follows before building a collector. If the workflow requires credentials, use official access and limit permissions. A third-party automation tool may save manual work, but sharing account access introduces a separate security risk.

For a smaller audience, place the earlier IDs in one spreadsheet column and the later IDs in another, then mark entries that appear only in the earlier snapshot. A local script or database handles larger sets faster, while using the same set-comparison logic.

The result identifies who disappeared between two observations. It does not identify the exact time, reason, or intent.

Check each flagged account before contacting anyone. If the profile remains active and accessible, you can describe it with greater confidence as an account that no longer follows you. If the profile is unavailable, classify the change as uncertain rather than treating it as a confirmed voluntary unfollow.

Using the X Data Archive for Follower History

The X Data Archive is the most privacy-conscious official route for building follower history. It doesn't give you a live unfollower dashboard, but it lets you request your own account data and compare dated exports without giving an unfamiliar tracker access to your account.

X provides follower and following lists in a downloadable archive, rather than a historical unfollow report. Its official instructions for accessing your X data explain that the archive is machine-readable and includes follower data, but X must prepare it after you request it.

Request and preserve each archive

Open your account settings and request the archive of your data. When X makes it available, download the files and preserve the original archive rather than editing it directly. Give each copy a clear date, such as the account name and the day you requested or downloaded it.

The archive can contain follower and following information in HTML and JSON formats, which gives you two practical ways to work:

• HTML: Useful for visually checking profiles and reviewing the information manually.

• JSON: Better for structured comparison, especially when the archive contains many records.

For a spreadsheet workflow, extract the follower identifiers from the first archive into one sheet and the identifiers from the later archive into another. Use a lookup or set comparison to mark entries that existed before but not afterward. Keep the original files so you can investigate a disputed result later.

Understand the trade-off

This approach is safer from an access-control perspective because you aren't authorizing an unknown service to read your account continuously. It also creates a defensible record of what your follower list contained at each capture point.

The cost is speed. You have to request the archive and wait for X to prepare it, so this isn't suitable for instant alerts. It also can't identify an unfollow that happened between two exports with exact timing. If someone left and returned before your next archive, your files may never show the temporary change.

For most creators, that limitation is acceptable. The archive is useful for periodic retention analysis, while daily curiosity is usually a poor reason to introduce another application into your account. A dated archive gives you a baseline and lets you connect audience changes with your publishing activity without pretending the data is more precise than it is.

Third-Party Unfollower Apps Risks and Rewards

You notice a follower count drop before a client report is due, and a third-party tracker promises the answer in a dashboard. It may show relationship changes faster than manual exports, but the result is not automatically an intentional unfollow. Deactivations, suspensions, and spam filtering can all make an account disappear. The tool may also create a larger account-security problem than the original question.

Start with the access model. A service that asks for your X password directly should be treated as unsafe. OAuth is preferable because X handles the authorization step, but approval alone does not make an app trustworthy. Read the requested permissions, privacy policy, data-retention terms, and access-revocation process before connecting it.

X states that third-party activity counts toward API limits. It also limits account actions and monitors behavior associated with aggressive following and unfollowing, as described in X's rules on platform limits. A read-only tracker has a different risk profile from software that follows, unfollows, posts, or sends messages automatically. Check that distinction carefully, because some services combine monitoring with actions designed to increase engagement.

The practical trade-off is straightforward:

• Manual comparison: Slow and dependent on your capture schedule, but generally low risk when files stay on your device.

• X Data Archive: Useful for retrospective checks, with low access risk and direct control over the files.

• API-based tracker: Convenient for recurring monitoring, while risk depends on permissions, behavior, and how the provider stores data.

• Automated follow or unfollow workflow: Fast for account actions, but exposes you to greater platform and security risk.

Some services claim to show mutual relationships without requiring an account login. spot mutual followers without login can help you examine that category, but no-login access is not a complete safety assessment. Confirm what information the service can view, whether it stores results, and whether it only reads public data. A tool that avoids login may still collect searches, profiles, or usage details.

Security check: A dashboard is not worth a compromised account, unexplained API activity, or automation that resembles platform manipulation.

Before authorization, answer four questions:

• Access scope: Can the app only read follower information, or can it post, follow, unfollow, and message?

• Data storage: Does the provider retain your follower history on its servers?

• Revocation: Can you remove access easily through X account settings?

• Automation: Does the product promote follow-back campaigns or bulk unfollowing?

For broader reporting, compare the feature set and permission model with these X analytics tools. Choose the smallest access level that supports the job.

In practice, monitoring net follower change, retention over a defined period, and the posts preceding sustained gains or losses often supports better decisions than chasing a definitive list of names. Third-party tools should improve publishing analysis, not encourage retaliation against accounts whose disappearance may have another explanation.

Distinguishing Unfollows From Other Changes

A follower disappears after a weekly snapshot. That looks like an unfollow, but the evidence is incomplete. X says the account may have unfollowed you, been deactivated, or been hidden because of suspected spam activity. Turning off the quality filter can reveal more of the follower list, including accounts identified as potential spam, as explained in X's guidance on common following issues.

Classify the change before drawing a conclusion. Start by opening the profile from the earlier snapshot. If it loads normally, check whether the account still appears in your Followers list. If it does not, record the account as accessible but no longer following you. If the profile is unavailable, look for signs of suspension, deactivation, or removed content. Then check whether your quality or spam-filter settings changed between snapshots.

Use “likely no longer follows” when the cause remains uncertain. “Definitely unfollowed” is too strong for an unavailable profile.

A simple record can separate real audience movement from platform cleanup:

Accessible account: the profile loads, but it is absent from your Followers list. This is the clearest sign of an unfollow, although it still does not explain why the person left.

Unavailable account: the profile cannot be checked reliably. Treat the loss as unresolved because suspension, deactivation, and other status changes can produce the same result.

Group change: several unavailable accounts vanish together. That pattern points more toward filtering or platform enforcement than a sudden reaction to one post.

This distinction matters for content decisions. Repeated losses from accessible accounts after a specific format or topic deserve analysis. A cluster of unavailable accounts does not justify changing your editorial direction.

The same caution applies to other networks. You can track unfollows on Instagram with a separate workflow, but a missing profile still needs context before it becomes a conclusion.

Avoid messaging a suspected unfollower for an explanation unless you already have a genuine relationship and a sensible reason to contact them. Individual losses rarely provide enough evidence for personal outreach.

Privacy settings add another variable. Review how to make your Twitter account private before relying on visibility alone to interpret another account's status. Third-party automation can also create security and access risks, so do not trade uncertain follower data for broad account permissions.

Building a Sustainable Follower Retention Workflow

A useful workflow separates measurement from reaction. Capture a complete baseline, preserve the date, and repeat the process on a consistent schedule. Use the X Data Archive for a low-access approach, or perform a local snapshot comparison if you can retrieve every page reliably.

A practical routine has four parts:

• Record the audience: Save dated follower IDs and the total follower count.

• Review exceptions: Investigate missing accounts for accessibility, suspension, deactivation, and spam filtering.

• Annotate content: Mark the posts that preceded noticeable gains or losses.

• Adjust thoughtfully: Change topics, hooks, formats, or posting habits only when a pattern persists.

Keep the focus on retention and content impact, not punishment. The X Coach growth workflow can help turn those observations into practical improvements, while your own snapshots preserve the evidence behind each decision.

The safest operating principle is straightforward: collect less sensitive access, measure consistently, and treat every apparent unfollow as a clue rather than a verdict.

SupaBird helps creators turn follower data into a repeatable X growth system with content ideas, engagement opportunities, draft improvements, scheduling, and practical coaching. Visit SupaBird to build a safer publishing workflow that improves retention without relying on aggressive unfollow automation.