What the Bluesky likes cleaner actually changes

A Bluesky like is a record created by your account that points to another post. The Likes workspace requests the liked-post feed for the account you authorize, follows available pagination, and displays the returned posts for review. You choose the records; BskyDelete does not score whether a like is embarrassing, outdated or unwanted, and it does not run an automatic cleanup schedule.

Deleting a selected like removes your like record. It does not delete the author's post, remove somebody else's likes, erase replies or reposts, or guarantee that cached counters update immediately. The useful outcome is deliberately narrower: the connected account stops liking the records that Bluesky confirms were removed. Reload the list and inspect important posts after each batch instead of treating the submitted count as proof.

Filters available while reviewing liked posts

Load the available likes first, then use filters as a review queue. Basic filters work on the returned post data; paid-plan filters add more ways to narrow that same loaded list.

Search for words or phrases in the liked post's visible text.
Filter by the original author's display name or handle.
On a paid plan, set minimum or maximum like, repost and reply counts for the referenced post.
On a paid plan, narrow visible text by mentioned accounts.
On a paid plan, filter for hashtags found in the returned post text.
Select individual records or select the currently filtered visible results before reviewing the final count.

Engagement counts describe the referenced post, not the strength or date of your like. BskyDelete's Likes workspace does not currently provide a like-date filter, so do not infer when you pressed Like from the post's publication time.

A controlled workflow for bulk removing likes

1
Connect the intended Bluesky account through the official AT Protocol OAuth flow, open Likes, and allow pagination to finish or pause it deliberately. Confirm that the account and returned list are the ones you intended to review.
2
Apply a keyword or author filter and, if your plan supports them, optional engagement, mention or hashtag filters. Open enough context to understand each referenced post; a filter match is only a candidate, not a deletion decision.
3
Select a small set first and recheck the active filters and selected count. Paid plans can export selected rows to CSV for reference, including author, text, record identifiers, publication time, links, media URLs and public engagement counts. The CSV is not a restore package.
4
Confirm the deletion, follow the per-batch progress, and distinguish successes from failures. Refresh Likes and verify the current state directly through Bluesky before retrying records or starting another large selection.

OAuth and browser-side processing boundaries

BskyDelete does not ask for a Bluesky password or App Password. The browser OAuth client manages the authorized session on your device, while requests for liked posts and deletion of selected like records still have to reach the Bluesky account provider. BskyDelete cannot perform those changes without the provider accepting each authorized request.

Returned post and selection data are processed for the action you request; BskyDelete application servers are not designed to persist a copy of your liked-post list. Separate account, analytics and subscription services operate under the current Privacy Policy. Disconnect the account after using a shared device, and never send a password, OAuth token or recovery code to support.

Unliking is different from deleting the original post

When Bluesky confirms deletion of a like record, that relationship is removed from your repository. The post remains controlled by its author, and copies, screenshots, embeds, search caches and third-party archives are outside this action. Other activity from your account—such as a repost, reply or quote—uses separate records and remains until you manage it separately.

BskyDelete does not provide an undo button. You may be able to like a still-available post again manually, but that creates a new current action rather than restoring the deleted record or its timing. Export important selections before deletion when you need a reference, test an unfamiliar filter with a nonessential like, and verify the result after processing.

Daily quotas, pagination and provider limits

The Free plan permits up to 30 successful deletion or unfollow actions per local calendar day across supported workspaces. Paid plans remove BskyDelete's daily action quota and enable selected-data export and advanced filters, but they do not remove Bluesky API rate limits, account-provider restrictions or temporary network failures.

Large histories require paginated reads and controlled deletion batches. If loading is paused, filters apply only to records already returned. If Bluesky limits or rejects a request, wait, reload, identify confirmed successes and retry only records that still exist. Repeated overlapping batches make partial results harder to audit.

Why a liked post may still appear

The liked-post list has not finished loading or has not been refreshed since the deletion.
Only part of the selected batch succeeded; use the reported failures and current list to identify what remains.
The OAuth session changed, expired or was revoked, so the account must be reconnected before another request.
Bluesky returned a rate limit, service error or changed-record response that BskyDelete cannot bypass.

Continue with an informed account review

Use these guides to understand the wider cleanup workflow, authorization boundary and privacy considerations before changing a large activity history.

Ready to review likes? Connect the correct account, load the Likes workspace and test one nonessential selection before expanding the batch.

Review likes in the workspace

Other BskyDelete features

Continue your account review with another focused BskyDelete workflow.

Filter and Delete Bluesky Likes in Reviewed Batches