BskyDelete's Following workspace loads the accounts that you currently follow. It lets you narrow that list with current profile and relationship data, select specific accounts, and explicitly confirm an unfollow action. It does not automatically decide which relationships should end.
Understand the Relationship Direction
Following is not the same as followers. This workflow changes accounts that you follow; it does not remove people who follow you. “Not following back” describes a current relationship, not a historical unfollow event.
The official AT Protocol getFollows Lexicon defines the current following list. Complete lists can require cursor pagination, so wait for loading to finish before reviewing the total.
Bulk Unfollow Step by Step
- Connect the Bluesky account through OAuth. BskyDelete does not request a Bluesky App Password.
- Open Following and load the current list.
- Use basic filters for handle, display name, bio, and current mutual-follow status.
- If you have Pro, optionally use public profile-count ranges, the inactive-account heuristic, the suspicious-bot score, or the whitelist. Heuristic signals are review aids and do not prove that an account is abandoned or automated.
- Inspect the filtered profiles and select only the accounts you intend to unfollow. Changing a filter clears the selection.
- With Pro, export the selected following rows to CSV before changing the relationship if you need a reference. The CSV does not automatically restore the relationship.
- Confirm the selected action and review the reported successes and failures.
The action is processed through Bluesky in batches. Completion time varies with selection size, API limits, retries, and temporary service conditions. Start with a smaller set when testing a filter and check partial failures before retrying.
What the Filters Can and Cannot Tell You
The inactive-account signal compares public post count with account age. It does not check a private activity history or confirm the person's last use of Bluesky. The bot score uses public signals such as profile completeness, account age, moderation labels, and count ratios. Neither is a factual label.
Similarly, a non-mutual relationship is not necessarily a reason to unfollow. Review whether the account still provides information you want in your feed rather than applying one rule to every result.
Build a Reviewable Batch
A filter narrows the candidates; it does not make every matching account equivalent. Before selecting, write down one review rule you can apply consistently, such as a current relationship state or a profile characteristic you have checked. Open profiles when the visible summary is not enough to make a decision.
For a long list, process one clearly defined group at a time. Changing a Following filter clears the selection, so verify the filter state after each change and rebuild the selection deliberately. After each batch, reload the list and compare the reported successes and failures with the accounts that remain. If you export a CSV, treat it as a review record rather than proof that every unfollow succeeded.
Quotas and Product Boundaries
The Free plan can complete up to 30 successful delete or unfollow operations per local calendar day across supported workspaces. Paid plans remove BskyDelete's own daily quota, but Bluesky API limits and service availability still apply.
BskyDelete does not keep historical unfollow records, provide follower-audience analytics, run scheduled cleanup rules, or follow accounts in bulk. Bulk unfollowing changes real relationships, so review every selection and confirm only the accounts you are prepared to stop following.