How to Turn Off Cross-Posting From Instagram to Threads — There Are Three Switches, Not One

You open Threads and your Instagram post is sitting there. You didn't put it there. You're fairly sure you never turned that on.

You go into settings, find something that looks right, switch it off — and a week later it happens again.

You're not misremembering, and you're not doing it wrong. There is more than one switch, and they're in different places.

First, the Part That Will Make You Feel Less Crazy

In a public post on Threads, Adam Mosseri — who runs Instagram — addressed this directly:

Your posts to Instagram should only go to Threads if you turn on cross-posting. If you go into the create flow you can see if Threads is checked under "Share to" on the last step of the flow. We shouldn't be turning this on for people, so if it's checked please uncheck it and I'll ask the team to look into it as well.

Two things are worth extracting from that carefully.

First, the intended behaviour is explicit: it should be off unless you turned it on. Second — and this is the part that matters to you — the head of Instagram is telling people to go check whether it's on, and to uncheck it if it is. That's an acknowledgement that people were finding it enabled without having enabled it, and it's an instruction to fix it on your end.

To be precise about what this is: it's a platform lead responding publicly to reports, not a formal announcement or a documented bug fix. But it's first-hand, it's from the person responsible, and it's more direct than anything in the help centre.

The Three Places the Setting Lives

Here's why turning it off once doesn't stick. The control isn't one control.

1. The per-post toggle (this is the one Mosseri points at)

When you share a post, tap Advanced Settings on the final screen, and look for Threads under the sharing options. Turn it off there.

This is the switch that catches everyone, because it lives on the last screen of the posting flow — the screen where you've already made every decision you cared about and you're tapping to get it over with.

2. Suggesting posts on other apps (account-level, in Instagram's privacy settings)

In your Instagram privacy settings there's a setting called Suggesting posts on other apps. This governs a broader category than a single post's share targets. It's the one people find when they go looking for "the" setting — and turning it off doesn't retroactively change a per-post toggle that's still set.

3. Account Center

Because Instagram, Threads and Facebook are linked at the account level, cross-app sharing behaviour is also governed from Account Center. This is where the relationship between the accounts is configured, and it's the layer most people never open.

Check All Three, in This Order

Do it once, properly, and it stops recurring:

• Start a post you don't intend to publish. Go all the way to the final screen, open Advanced Settings, and look at what's checked. This tells you the current state of the switch that actually fires. Then back out.
• Then the privacy setting. Suggesting posts on other apps, off.
• Then Account Center. Review what's linked and what's shared between the linked apps.
• Then publish one real post and check Threads. This is the only step that verifies anything. Everything before it is configuration; this is the test.

That last step matters more than it sounds. Settings screens tell you what a setting claims to be. A published post tells you what the system actually did.

Why Defaults Like This Are Worth Paying Attention To

It's tempting to treat this as a bug story. It's more useful as a pattern: when two products are owned by the same company and one of them needs users, sharing between them becomes the default — and the off switch ends up in a different place from the on switch.

The reason to care isn't philosophical. It's that a default is a decision someone already made for you, and defaults are where surprises live. The exact same shape shows up in the reverse direction with Facebook, which is why cross-posting between Instagram and Facebook breaking is such a persistent support question — it's one connection with several independent controls, so it half-works constantly.

A habit worth forming: every time you notice content appearing somewhere you didn't publish it, look for a second switch before concluding you already fixed it. There is nearly always a second switch.

If You Want Both — But on Your Terms

Not everyone wants cross-posting off. Plenty of people want the same content on both, they just don't want it happening automatically with an identical caption.

That distinction matters, because the two platforms reward different things. Threads posts are shorter, more conversational, and often work better as a claim plus a reply thread. An Instagram caption dropped verbatim into Threads reads like a press release. Automatic cross-posting always produces the second one.

This is the case for deliberate publishing over automatic mirroring, and it's the space NoobClaw works in: composing a per-platform version of the same idea and publishing each into your own logged-in browser session, from your own machine, rather than letting one platform mirror into another. The tradeoff is that it's more work than a checkbox — you're writing two versions instead of none. But the output is two posts that belong where they are, and the setting that surprised you stops being part of your workflow at all.

If you're already publishing to Threads on a schedule, it's also worth knowing that scheduled Threads posts fail in their own distinctive ways — a separate problem that gets blamed on cross-posting more often than it should.

Why You Might Not Want It On Even If You Like Threads

There's a version of this where cross-posting seems harmless — you want to be on both, so what's the difference? Three concrete reasons it's worth turning off even then.

• You lose the ability to tell what worked. If every Instagram post appears on Threads automatically, you can't compare an idea's performance across the two, because you never made a decision about either one. Everything is a duplicate, so nothing is a test.
• Timing gets decided for you. The moment that's right for an Instagram audience isn't automatically right for a Threads one. Mirroring hands both schedules to whichever platform you happened to open first.
• The format mismatch is visible to readers. An Instagram caption written to sit under an image reads oddly as a standalone text post. It's not that it fails — it's that it reads like something that was written for elsewhere, which is the exact impression you'd choose to avoid.

The counter-argument is real too: an imperfect post that exists beats a perfect one you never wrote. If the honest alternative to mirroring is an empty Threads profile, leave it on. Just make that an actual decision rather than something you discover by accident.

While You're In There

Two adjacent settings are worth a look in the same session, since they produce the same "I did not do that" feeling. One is how Instagram treats scheduled posts, which is the other thing people blame when a post behaves unexpectedly. The other is your Account Center link status itself — if Instagram, Threads and Facebook are all linked, every future sharing feature will default to the linked state, and you will be back here the next time one ships.

FAQ

How do I turn off cross posting on the Instagram app?

Open the create flow, go to the final screen, tap Advanced Settings, and turn off Threads under the sharing options. Then check the account-level setting (Suggesting posts on other apps) and Account Center separately — the app-level toggle doesn't cover them.

Can I stop Threads posts from appearing on Instagram?

Yes — that direction has its own control, inside Threads' own privacy settings rather than Instagram's. The two directions are configured separately, which is consistent with everything else here: each connection has its own switch.

Why does it turn itself back on?

Usually it didn't. Usually a different switch was on the whole time, and you turned off the one you found rather than the one that fires. Run the full three-place check and finish with a real test post — that's the only way to tell the difference between "it reset" and "I fixed the wrong one."