Skip to content
truescrape
Free key

What Can a Threads Profile Viewer See? Followers, Bio, Links and What Stays Hidden

A Threads profile viewer reads the public profile: name, bio, followers, thread count, verified badge and links. Following counts, private accounts and the posts themselves are not part of it. What each field means, and the one answer Threads gives for both a missing and a private account.

6 min read · 24 Oct 2026

A Threads profile viewer shows you the public part of a profile: the display name, the bio, the follower count, the number of threads the account has posted, whether it carries a verified badge, and any links it lists. It does not show who an account follows, it cannot see private accounts, and it does not return the posts themselves.

That is the whole answer. The rest of this page is what each of those fields means, where the edges are, and how it compares with looking an account up in Meta's official API.

You can try it on any public account with the free Threads profile viewer. It needs no account and no key.

What does a Threads profile viewer show?

Six things, all of them taken from what Threads serves to a visitor who is not signed in:

Field What it is When it is empty
Name and username The display name and the @handle Never
Bio The text under the name The account has not written one
Followers The count Threads publishes on the profile Shown as a dash if Threads does not publish it
Threads How many threads the account has posted Shown as a dash if absent
Verified Whether the profile carries the badge Shown as not verified
Links The URLs listed on the profile The account lists none

An empty field shows as a dash, never as a zero. A zero would say the account has no followers; a dash says Threads did not tell us.

Why is there no following count?

Threads does not publish it on a public profile, so a viewer that reads only the public page has nothing to show. If a tool gives you a following number for a Threads account, ask where it got it.

What happens with a private or missing account?

You get one answer for both: the account does not exist or is not public. Threads gives the same response either way, so a viewer cannot tell a typo from a private profile. Check the spelling first, then assume the account is not public.

This is also why a viewer is not a way to find out whether someone has an account. It only reads profiles that anyone can open.

Can you see their posts, replies or followers?

No. A profile viewer returns the profile card, not the content. Posts and replies are a separate surface, and this tool does not read them. It shows how many followers an account has, not who they are.

If you want to read public posts, that is a different job with different limits. Meta's Threads API gates it behind App Review and a follower floor, which is worth reading before you plan anything on top of it.

Is a Threads profile viewer the same as Meta's API?

No, and the difference is who can use it.

Meta's own profile_lookup returns a public profile by username, but only for apps Meta has approved, only for accounts above a follower floor, and until approval only for a handful of Meta-owned accounts. The details, with Meta's wording and the quotas, are in is there a Threads API for public posts.

A profile viewer reads the same public page any visitor can open. That is why it works for any public account today, and why it can only show what that page shows.

Is it allowed?

That depends on what you are doing with it, and it is worth being plain about.

The viewer reads public, logged-out pages only. It does not sign in and it does not touch anything behind a login. That is the posture we hold across all of these tools.

It is not the same as Threads permitting automated collection. Threads' own robots.txt says collection of data through automated means is prohibited without written permission, and the contract question is separate from the question of whether the data is public. We cover how those two come apart in logged-out scraping and platform terms. If you are building something that depends on this data, read that before you build.

The other free profile viewers

Threads is one of several. Each reads only the public, logged-out profile of its platform, and each shows a dash for anything the platform does not publish.

All of them are on the free tools page. They are free to use, with a per-hour limit for each visitor: past it, a tool stops with a message that says when it resets.

What if you need it in code?

The tool is a window onto an endpoint. GET /v1/threads/profile?handle=... returns the same fields as a unified creator object, at one credit per profile. A request that fails, or comes back empty, is not charged.

curl "https://api.truescrape.com/v1/threads/profile?handle=some_public_account" \
  -H "x-api-key: YOUR_KEY"

Following is null in the response for the reason above, and the field is there so the shape matches every other platform. A new key comes with free credits, so you can try the call before you pay for anything.

We sell an API that reads public Threads data, so we have an interest in you using it. Weigh that accordingly, and use the viewer first: if what you need is on the page it shows, you do not need the API at all.

Sources

Referenced in this post

Everything described here runs on the same API. You are never charged for a failed request, an empty result, or a cache hit.

Get a free keyAll posts