Methodology

Last updated 15 August 2026.

Data source

Every tool on this site reads public data through Bluesky's public AT Protocol API, the same endpoints that power the official app. No tool uses a login, requests your password, or accesses anything that Bluesky does not already serve publicly. Posts from private or protected accounts are not reachable and never appear in any result.

What is not collected

• No accounts, passwords, or authentication tokens.
• No storage of the URLs or handles you enter. Requests are handled live and discarded.
• No profile of you, and no selling or sharing of personal data.
• Looking up a profile or a post is invisible to its owner and generates no notification.

Profile Analytics

Sample: up to the 100 most recent public posts for the handle you enter. This is a recency sample, not lifetime history.

Derived figures: average likes and reposts are simple means across that sample. Best day and best time come from grouping the sample by weekday and by UTC hour band and comparing average engagement. Top posts are the three highest-liked posts in the sample.

Known limits: accounts with fewer than about 20 posts produce unstable averages, and patterns become more reliable past 50. Times are UTC and must be converted to your own timezone. Impressions, reach, profile views, and follower demographics are not available to anyone through the public API, so they are not shown and not estimated.

Trending Topics

Source: the Bluesky AppView public API, which reflects activity surfaced by the default AppView that powers bsky.app.

Refresh: automatically every 30 minutes, with a manual refresh available at any time.

Known limits: because Bluesky is decentralised, trending is not a single global truth. Users browsing through a different AppView, custom feeds, or an independent server can legitimately see a different picture. Post counts are approximate and scoped to the refresh window. No sentiment analysis is performed, so a topic may be trending because it is being criticised rather than celebrated. There is no promoted or sponsored placement in the list.

Handle Checker

Method: queries Bluesky's public identity resolution endpoint, the same lookup the official app uses to resolve a handle to a DID, and reports whether resolution succeeds.

Known limits: a result is a snapshot, not a reservation. Availability can change within seconds. Custom domain availability depends on domain registration, which is outside Bluesky's system.

Downloader and Screenshot Generator

Method: the post URL is resolved to the original media file that Bluesky already serves publicly, and that file is passed to your browser. Nothing is re-encoded, so quality is unchanged and no watermark is added. The screenshot generator renders post content fetched live from the public API.

Known limits: public posts only. Deleted media cannot be recovered. Engagement counts on a generated card are frozen at the moment of generation. Card text is always taken verbatim from the post and cannot be edited, deliberately, so cards cannot be used to fabricate quotes.

When this page changes

If a data source, refresh interval, or limitation changes, this page is updated and the date above is revised. Questions about methodology can go to hello@bskysuite.com.