Threads is now rewarding conversation, not follower count

Threads just put a new signal in the feed, and it is not about who has the biggest account.

It is a badge called a Gem. It sits on public posts and replies that the app decides started or continued a standout conversation. Meta published the support page for it in early October. The Verge and Social Media Today both covered the rollout around October 8 and 9, 2026. Android Central reported the same window as a U.S. test.

This is not a new monetization program. It is not a verification badge. It is not a follower milestone. It is Threads telling you, in public, what kind of post it wants more of: original, native writing that creates back-and-forth, not recycled crossposts that land and die.

This edition breaks down what Gems actually are, who can earn them, what gets excluded, why that matters for how you use Threads next to Instagram, and what to change in your posting habit this week.

What a Threads Gem actually is

According to Meta's "About Gems on Threads" help page, as summarized by The Verge, Social Media Today, Android Central, and Dongle Media Lab, Gems highlight standout conversations on Threads. A Gem appears on eligible public posts and replies. Everyone on Threads can see those badges in the feed, including people outside the United States.

Selection is automated. Threads says it chooses Gems once a day and covers a range of topics. The criteria Meta lists are perspective, discussion, and originality. Perspective means a fresh take with unique value. Discussion means real back-and-forth that keeps the conversation moving. Originality means your own work, not something recycled from elsewhere online.

That last point is the one most creators will feel first. Social Media Today quotes Threads on originality and notes that posts cannot be crossposted from another app. Dongle Media Lab, writing on October 13, 2026, spells out the practical version: if you publish on Instagram and share to Threads at the same time, that post is not eligible for a Gem.

You get a notification if your post or reply receives a Gem. Reporting also says you can decline or hide the recognition. Social Media Today notes that Threads framed the award as something you can share with a special post, with the option to decline.

Most posts will not get a Gem. Meta is explicit that missing one does not change your profile or how many people see your posts. That sentence matters. It means Gems are a recognition layer first, not a documented reach booster. Whether Gem posts get an invisible distribution bump is still unverified in the reporting. Do not build a strategy on a boost Meta has not promised.

Who can get one, and who cannot

Eligibility is narrower than the feed makes it look.

Right now, only posts and replies from people in the United States can receive Gems, according to Meta's help language as cited across The Verge, Social Media Today, Android Central, and Dongle Media Lab. You may still see Gems in your feed if you live elsewhere. Seeing a Gem and being able to earn one are different things.

The profile must be public. The account holder must be 18 or older. The content must follow Meta's Community Standards and be appropriate for the wider Threads audience.

On the content side, the rules get sharper. The post or reply must be created on Threads. It cannot be deleted or hidden. It cannot be a repost. It cannot be a crosspost from Instagram or another app. If it is a reply, it must be a direct reply to a post, not a reply to a reply.

That last filter is easy to miss when you are deep in a thread. The witty third-level reply that keeps a joke going may feel like the best writing you did that day. Under the current rules, it is not Gem-eligible. The direct reply under the original post is.

Put simply: native Threads writing from a public U.S. adult account, on an original post or a first-level reply, is in the pool. Crossposts, reposts, nested replies, private accounts, and non-U.S. authors are out of the pool for earning, even if they can still see Gems.

Why Meta is doing this now

Threads has always sold itself as a place for conversation more than polished performance. Gems are that pitch made visible.

When a platform puts a badge on a behavior, it is teaching both creators and viewers what "good" looks like. Gems teach that good means conversation quality, not follower count. Meta's own wording, as reported by Social Media Today and Android Central, stresses that selection is based on the conversation created or continued, not on how many followers a profile has.

That is a different incentive from the classic growth loop on Instagram or TikTok, where reach and follower velocity often become the scoreboard. It is closer to the forum and comment-section culture Threads has tried to borrow. Android Central compared the feel to community badges. Social Media Today compared the idea, carefully, to X's short-lived "Bangers" recognition, with the important difference that Gems are designed as an automated daily system rather than a one-month editorial stunt.

There is also a product logic underneath the community language. Crossposting from Instagram is convenient. It is also a weak Threads session. A user who sees the same caption they already scrolled past on Instagram has less reason to stay, reply, or come back tomorrow. By excluding crossposts from Gems, Threads is not only defining originality. It is quietly ranking native effort above syndication.

None of that requires you to abandon Instagram. It does require you to stop treating Threads as a free mirror of your Instagram feed if you care about whatever status Gems end up carrying inside the app.

What this means for creators at different stages

If you are early and posting mainly on one platform, Gems are a simple test. If Threads is already in your mix and you are in the United States with a public account, write a few posts that only exist on Threads. Ask a real question. Take a clear position. Reply directly under posts in your niche instead of only broadcasting. Measure whether those native posts pull more replies than your old crossposts did. The badge is optional. The reply rate is the useful metric.

If you are mid-stage and your Threads presence is mostly "share to Threads" from Instagram, you now have a documented ceiling. Those posts will not enter the Gem pool. That does not mean they stop working for awareness. It means the platform has told you they will never be the posts it celebrates. If you want Threads to feel like a second home rather than a mirror, schedule a small native block: two or three Threads-only posts a week, plus deliberate first-level replies on posts your audience already cares about.

If you are established and using Threads to move people toward a newsletter, product, or community, treat Gems as a conversation KPI, not a vanity trophy. A Gem on a post that does not point anywhere useful is still just a badge. A native Threads post that earns replies and then sends people to a destination you own is still the better business outcome, with or without the purple icon.

If you are outside the United States, you cannot earn Gems under the current rules. You can still study which posts receive them. Dongle Media Lab makes that point clearly: even when you are not eligible, Gem posts in the feed are a free map of what Threads currently treats as high-quality conversation. Use that map. Do not wait for eligibility to start writing natively.

What creators should do right now

First, audit your last ten Threads posts. Count how many were written on Threads and how many arrived as Instagram crossposts. If most are crossposts, you already know why Gems are irrelevant to your account today.

Second, if you are eligible, publish one Threads-native post this week that would not work as an Instagram caption. Longer. More specific. Built to invite a reply. End with a clear prompt that asks for experience, disagreement, or a concrete example, not a generic "thoughts?"

Third, spend fifteen minutes leaving direct replies on other people's posts in your niche. First-level replies only if you care about Gem eligibility. More important than eligibility: replies are how Threads sessions deepen. Gems simply made that behavior more visible.

Fourth, separate your Instagram and Threads workflows for a month. Keep crossposting if it is useful for reach. Add a native Threads layer on top instead of replacing everything overnight. The goal is not purity. The goal is to stop letting the lowest-effort path be your only path.

Fifth, do not overfit to the badge. Meta says missing a Gem does not reduce your reach. Social Media Today also flags a real risk of any automated conversation award: systems that optimize for "discussion" can surface heat as easily as insight. Write for the conversation you want to host. Let the badge be a side effect.

There is a quieter operational point for teams. If someone on your team "owns Instagram" and someone else occasionally toggles share-to-Threads, Gems will mostly ignore that workflow. Conversation recognition requires a person who actually reads Threads, replies in public, and writes posts that only make sense in that room. That is a staffing choice as much as a content choice. A VA who crossposts captions is not the same resource as a writer who can hold a thread.

Brand accounts should read the originality rule twice. A polished announcement copied from an Instagram carousel into Threads may still inform followers. It will not enter the Gem pool. The posts more likely to qualify are the ones that feel slightly less "campaign" and slightly more "point of view": a founder reply under a category debate, a practitioner unpacking a mistake, a specific take that invites disagreement from people who do the same work.

How to write for conversation without becoming bait

The risk with any discussion badge is that creators optimize for argument instead of usefulness. Heat generates replies. It also generates the wrong room.

A better standard is specificity. Name the tactic, the audience, the constraint, or the tradeoff. "Engagement is down" is too broad to answer well. "Replies on my Threads posts fell after I started crossposting every Instagram caption" is answerable. People can compare notes. That is discussion.

Another standard is stakes that stay professional. Ask what changed in someone's process, what they stopped doing, or what they would not recommend to a beginner. Avoid bait that only works if strangers insult each other. Meta's help language emphasizes perspective, discussion, and originality. None of those require cruelty.

Structure helps. Open with the claim. Give one concrete example from your own work. Ask for a parallel example from readers. Stay present in the first hour to reply to the first serious answers. First-level replies from you keep the thread eligible energy high even when you are not chasing a Gem. The habit matters more than the icon.

If you use Threads to support a newsletter, end native posts with one owned destination, not five links. Platforms that reward staying in-app still tolerate a single clear next step when the conversation was real. The Gem is not the conversion. The reply thread is the relationship. The email list is the asset that survives the next badge experiment.

What this does not mean

It is worth being precise, because badge news travels faster than the footnotes.

This is not proof that Gem posts get more distribution. Meta's public language, as reported, says non-winners are not penalized on reach. It does not publish a formula that boosts winners. Until that changes, treat Gems as recognition and social proof inside the feed, not as a growth hack.

This is not a global creator program. U.S. authors only, for now, for earning. A worldwide feed that can display Gems is not the same thing as worldwide eligibility.

This is not a reason to delete your Instagram-to-Threads share habit on day one. Crossposts can still introduce you to people. They simply sit outside the recognition system Threads just turned on.

And this is not the same thing as a community champion badge. Meta's help language, as summarized in the coverage, distinguishes Gems, which mark a post or reply, from community champion recognition, which marks a person's contributions inside a specific community. Do not confuse a post award with a profile status.

What every creator should understand

Creators on X have watched platform experiments that celebrate "banger" posts, original writing, and conversation quality, then watched those experiments fade or change. Social Media Today explicitly links Gems to that pattern when it mentions X's short "Bangers" recognition run.

The lesson is not that badges are fake. The lesson is that platforms use recognition to steer behavior long before they publish a perfect monetization rule around it. When X highlighted certain posts, creators adjusted hooks and formats. When Threads puts Gems on conversation, creators who want room in that culture will write for replies, not only for impressions.

You have seen a related shift inside Meta already. Instagram has pushed creators toward Reels, carousels, and now AI-assisted editing inside Edits. Threads is pushing toward native text conversation. Same company. Different product jobs. If your Meta strategy is only Instagram performance content, you are ignoring the product that is literally badging discussion.

Threads is not asking you to become a different person. It is asking you to stop treating the app like a carbon copy of Instagram. Gems make that request visible. Write where the badge can find you, or keep mirroring and accept that the new signal was never built for that workflow.

New: Useful Bots 🤖

I just launched a small side newsletter: every Friday, one free Grok Bot template you can copy in one click. Bots that draft your posts, prep a launch, or turn one sentence into an animated story series.

It's free, short, and separate from this newsletter. 👉 Get the next template