Remove your reshare, not the source post

Filter, Review and Delete Selected Bluesky Reposts

BskyDelete loads repost records from the connected account, narrows the list with supported filters, and submits deletion only for the records you confirm. Removing a repost does not delete the original author's post.

What deleting a Bluesky repost means

A Bluesky repost is a record created by your account that references another person's or your own post. The Reposts workspace loads supported repost entries, shows the referenced content and its author, and lets you select which reshare records to remove. It does not delete reposts automatically, decide whether a topic still represents you, or edit the original post.

A confirmed deletion removes your repost record when Bluesky accepts the request. The referenced post remains in its author's repository, and its replies, likes, quotes and other people's reposts remain separate. This distinction is important when a search result says “delete reposts”: the tool manages reshares made by the connected account, not content owned by somebody else.

Ways to narrow the repost list before selection

Start from a clear review reason, then combine only the filters you can explain. Wait for the relevant records to load before interpreting a filtered count.

  • Search words or phrases in the visible text of the referenced post.
  • Filter by the original author's display name or handle.
  • Limit results with the from and to date controls available in the Reposts workspace.
  • On a paid plan, set minimum or maximum public like, repost and reply counts.
  • On a paid plan, narrow returned text by mentioned accounts or hashtags.
  • Select individual repost records or the current filtered visible set, then inspect the selected count before confirming.

Engagement figures belong to the referenced post and can change. They are useful for narrowing a review list, not proof that a repost is valuable, harmful or safe to remove.

A reviewable bulk repost deletion workflow

  1. 1

    Connect the intended account through OAuth, open Reposts and let the available pages load. Verify the account before selecting anything, especially when you use more than one Bluesky identity.

  2. 2

    Apply keyword, author or date criteria and, on a paid plan, optional engagement, mention or hashtag filters. Read the referenced post and author context; a matching keyword alone does not explain why you originally reshared it.

  3. 3

    Select a small test group and recheck the filter state. Paid plans can export selected repost rows to CSV with author, text, original and repost identifiers, publication time, media or external links and public engagement counts. That export cannot recreate a deleted repost automatically.

  4. 4

    Confirm the selected deletion, monitor successes and failures, then reload Reposts and verify the current state. Retry only records that remain instead of submitting overlapping selections after a partial result.

OAuth, loaded content and provider boundaries

BskyDelete uses the official AT Protocol OAuth flow and does not request your Bluesky password or App Password. The authorized browser session requests repost data and submits deletion of selected repost records to Bluesky. The account provider can rate-limit, reject or delay those requests, and BskyDelete cannot override its response.

Referenced post and selection data are processed for the review you request; BskyDelete application servers are not designed to keep a persistent copy of your repost list. Separate account, analytics and subscription providers operate under the current Privacy Policy. Disconnect on shared devices and keep OAuth tokens and recovery credentials out of support messages.

What remains after your repost record is removed

Deleting your repost removes that reshare record from the connected repository. It does not remove the source post, a quote post you authored, a reply, a like, screenshots, embeds, search caches or copies held by third parties. Other accounts can continue to reference or reshare the source content under their own control.

There is no BskyDelete undo operation. If the source post is still available, you may manually repost it later, but that is a new record and does not restore the deleted record's original timing. Export a reference when useful, test a new filter with a low-risk record, and verify important changes directly in Bluesky after every batch.

Quotas, API rate limits and partial batches

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 quota and enable advanced filters and export, while Bluesky API limits, service availability and account restrictions continue to apply.

Repost histories can require multiple paginated reads, and deletion runs in controlled batches. When a provider response interrupts a batch, use the reported successes and failures, reload the list and retry only confirmed remaining records. A submitted batch size is not a guarantee that every request completed.

Why a repost may still be visible

  • The Reposts list or the Bluesky profile view is stale and needs to be reloaded before another request.
  • Only some selected repost records were deleted; review the item failures rather than repeating the whole batch.
  • The authorized session expired, changed accounts or was revoked and must be reconnected through OAuth.
  • The source or repost record changed, or Bluesky returned a rate-limit or availability error that cannot be bypassed.

Read the repost and deletion guidance

These guides explain the repost-specific steps, the authorization model and how to diagnose a record that still appears after a deletion attempt.

Ready to review reposts? Load the correct account, apply one explainable filter and test a small low-risk selection first.

Review reposts in the workspace

Other BskyDelete features

Continue your account review with another focused BskyDelete workflow.