Threads Ghost Posts: "Not Available" Is the Most Common Answer, and It Is Not a Bug

Someone in your feed posted something wrapped in a dotted bubble. You went to compose, looked for the ghost icon, and it is not there. Before you clear cache, reinstall, or file a bug report: look at what everyone else is searching for.

The autocomplete family for this feature is tiny and it is almost entirely one shape — not available, not working, not showing. Three ways of saying "I do not have it," and nothing else. When a new feature's entire search footprint is people reporting absence, that is a rollout in progress, not a fault on your device.

What a ghost post actually does

Meta launched ghost posts globally on 27 October 2025 on iOS and Android, describing the format as a way to share unfiltered thoughts without the pressure of permanence. The mechanics, as reported from Meta's announcement:

• It expires. The post disappears from everyone's feed 24 hours after publishing, the same clock as a Story.
• Replies go to your inbox. Rather than forming a public thread underneath, responses land in your messages.
• Engagement is asymmetric. Other people see smiley-face indicators showing that likes and replies exist. Only the author sees the actual numbers and who they came from.
• You keep a copy. After 24 hours the post moves to an archive section reachable from your settings — visible to you, gone for everyone else.
• It is visually marked. Ghost posts render with a dotted conversation bubble so the format is obvious in-feed.

Worth being precise about sourcing here: Meta's own announcement post was not retrievable when we checked, so the specifics above come from the tech press reporting on that announcement rather than from a live Meta page we read ourselves. Treat the 24-hour clock and the inbox routing as well-corroborated, and treat any number beyond that with the usual suspicion.

The part that matters is not the disappearing

Disappearing content is not new and it is not the interesting property here. The interesting property is that ghost posts delete the public reply thread.

On a normal Threads post, the comments are part of the content. On a ghost post, they are mail. That single change turns the format from broadcasting into asking.

Think about what that removes. No pile-on visible to strangers. No screenshot of the ratio. No quote-reply chain forming under something you posted at 1am. It also removes the thing a lot of accounts depend on — the reply section as social proof. If your posts get traction because people can see forty people arguing underneath, ghost posts will feel dead to you.

So the useful framing is: ghost posts are for the questions you want answers to but not an audience for. Polls of your own followers, awkward asks, half-formed opinions you want reactions to before committing. They are structurally bad for anything where the visible conversation is the point.

Why "I do not have it" is usually the whole story

Meta ships this class of feature in waves, and the waves are not documented publicly. There is no eligibility page for ghost posts of the kind YouTube publishes for its features. That means there is genuinely nothing for you to check, and the standard troubleshooting ritual — reinstall, log out, switch device — will produce a lot of activity and no information.

The one thing worth doing is confirming your app is current, because the compose-screen icon arrived in a client update rather than server-side. Beyond that, the honest answer is waiting.

This is a recurring shape on Meta surfaces. We saw the same absence-of-documentation problem with Threads scheduled posts, where the quotas that stop you are never named, and with Threads profile views, where an entire market of "viewer" tools grew up around a capability that does not exist.

What this format does to a posting plan

Two practical consequences if you run more than a hobby account.

First, ghost posts are not archivable as proof. They vanish from public view, so they cannot serve as a dated public record of anything — no announcements, no commitments, no claims you may need to point at later. Your private archive copy is not the same as a public one.

Second, the inbox becomes the workload. Moving replies into DMs sounds like relief until a post lands and you have two hundred individual conversations instead of one thread you could answer three times. If you already struggle to keep up with comments, this format makes that worse, not better.

It also collides with a habit a lot of accounts rely on: hashtags. Threads is unusually strict there — one tag per post is the entire allowance — so a ghost post gives you neither a public thread nor a tag cloud to be discovered through. It is a format for people who already follow you.

That second point is the one people underestimate. Reply volume is the thing that quietly ends most consistent posting habits, which is why NoobClaw exists in the first place — it reads the comments on your own logged-in accounts and drafts responses in your voice at a human pace, so keeping up does not mean sitting in an inbox. It is one approach among several, and for a DM-routed format like this it changes the arithmetic rather than removing the work.

How to tell a rollout from a fault, without reinstalling anything

The reason people burn an evening on this is that both situations look identical from inside the app: a feature other people have, that you do not. Three checks separate them, and none of them involve deleting your account data.

1. Look at the shape of the search demand. A defect produces varied complaints — it crashes, it posts twice, it shows the wrong timestamp. A rollout produces one complaint in three grammatical costumes: not available, not showing, not working. Ghost posts produce the second pattern almost exclusively.
2. Check whether an official eligibility page exists. If a platform gates something deliberately and permanently, it usually documents the gate, the way YouTube documents subscriber bands for its features. Meta ships consumer features in silent waves and documents nothing, which means there is no gate to satisfy — only a queue.
3. Update the app, then stop. Compose-screen features arrive in client builds. Once you are current, every further action is superstition.

That third point is the expensive one. The standard ritual — log out, reinstall, switch accounts, clear data — carries real risk on Meta properties, where a fresh login from a new session on an account that posts frequently is exactly the pattern that triggers a verification challenge. You can absolutely turn "I do not have a feature yet" into "I cannot get into my account today."

The most common cost of chasing a rollout is not the wasted hour. It is the security challenge you triggered by logging out of a working session for no reason.

FAQ

Can other people tell how many likes my ghost post got?

No. Reporting on Meta's announcement is consistent that viewers see indicator icons showing engagement exists, while only the author sees the real counts and the identities behind them.

Where do ghost posts go after 24 hours?

They leave everyone else's feed and move into an archive section the author can reach from the main settings menu. The content is not deleted for you, it is just no longer public.

Is ghost posting the same as a Threads Story?

No — Threads does not have Stories. Ghost posts borrow the 24-hour clock from Instagram Stories but live in the normal Threads feed while they are alive, marked with a dotted bubble, and their replies behave completely differently from Story replies.