Profile-Level Versus Post-Level: Two Kinds of AI Disclosure

Most disclosure advice treats "should I label this as AI" as one decision that applies the same way every time. It isn't. A tag on a single post and a badge on an entire account are answering different questions, to different effect, and conflating them is how a creator ends up either over-tagging content that didn't need it or under-tagging in a way that reads as evasive the moment someone checks the profile.

The distinction is really about where the effort inference lives. A viewer who sees one tagged post makes a judgment about that post and moves on. A viewer who sees an account-level badge makes a judgment about the creator — how much of what they see from this person, going forward, involves a machine doing part of the work — and that judgment doesn't reset between posts the way a per-post tag does. Choosing the wrong scope doesn't just mis-disclose one piece of content; it sets an assumption that follows every post after it.

What Instagram actually shipped

In May 2026, Instagram began testing an account-level "AI creator" label — a self-applied badge distinct from the platform's existing per-post "AI info" tag. Creators who opt in get a line reading "This profile posts content that was generated or modified with AI" attached to their account, and the badge surfaces in the bio and alongside individual posts and Reels, carrying into Explore as well. It's explicitly optional and currently a test — Meta is encouraging adoption, not requiring it, and participation remains voluntary, which means plenty of AI content will keep shipping with the older, vaguer "AI info" label or no visible label at all.

One detail matters more than it looks: Instagram has said the two labels don't stack. When a piece of content already carries the automated "AI info" tag and the account also carries the "AI creator" badge, the post shows the "AI info" label instead of the profile badge — the more specific, per-post signal wins over the account-level one on that particular piece of content. Even the platform building this system treats post-level and profile-level disclosure as answering different questions, not as two flavors of the same checkbox.

Why the two scopes aren't interchangeable

A post-level tag is situational. It discloses exactly one thing: this specific image or video involved AI. It resets with every new post — tag the ones that need it, skip the ones that don't, and a viewer scrolling the profile sees a mix that (accurately) reflects a mixed production process.

A profile-level badge changes something different: the default assumption a viewer brings to every post on that account, including ones posted before the badge existed and ones that involved no AI at all. That's the real cost of the account-level option — it isn't scoped to the content that earned it. Once a profile reads "AI creator," a viewer's baseline effort-inference shifts for the whole catalog, and an occasional post that was shot on an iPhone with zero AI involvement doesn't get to opt back out of that inference individually.

This lines up with how the distinction is usually drawn generally: an AI content label is fundamentally a platform-applied or creator-applied tag — a visible badge, separate from the legal disclosure obligations that exist independently of any single platform's interface. What Instagram shipped in May is squarely in the tag category on both counts. Nothing about opting into the profile badge changes whatever binding disclosure requirements might apply in a given jurisdiction; those obligations sit in a different bucket entirely, described more fully under synthetic media disclosure. A voluntary platform badge and a legal requirement can point in the same direction, but they are not the same instrument, and satisfying one says nothing about the other.

A decision rule, not a default

The honest answer to "which scope should I use" depends on how AI actually shows up in the account's output, not on which option feels more transparent in the abstract.

Profile-level tends to make sense when:

• The large majority of what's posted involves AI generation or modification, so the badge is describing the account accurately rather than as a blanket over occasional use.
• The aesthetic is consistent enough that viewers benefit from knowing the frame once, rather than being re-told on every single post.
• It's a dedicated, purpose-built account — a faceless format, a branded series — where there's no mixed-method content the badge would misrepresent.

Post-level tends to make sense when:

• AI use is occasional or mixed in with organic, non-AI content on the same account.
• The account has an existing audience relationship built before AI tools were part of the workflow, where a blanket badge would recontextualize a large back catalog that doesn't deserve it.
• Different content types on the same account carry different levels of AI involvement — a generated product shot next to an unedited behind-the-scenes clip — and collapsing that into one account-wide signal would flatten a real distinction.
• The account is run by or for a brand with multiple contributors, where "this account is an AI creator" is a much stronger and stranger claim to make than "this particular asset was AI-assisted."

Neither option is the safer default in the abstract. The actual risk in each direction is different, too: under-scoping (post-level tags on an account that's now functionally all-AI) reads as reluctant transparency once a viewer notices the pattern across enough posts. Over-scoping (a profile badge on an account that's mostly organic with occasional AI assistance) overstates the machine's role in work that was mostly human, which has its own credibility cost. Matching the scope to the actual mix is the only version of this that holds up under scrutiny either way.

An account built around Reels-first content is a useful test case precisely because it tends to sit at the boundary — enough volume and consistency that the profile badge is tempting for convenience, but often still mixing in enough non-AI clips that a blanket label overstates how the account actually works. That's exactly the situation where the two-question framing above earns its keep instead of collapsing into a coin flip.

The publishing step doesn't make this decision for you

It's worth being precise about where this choice actually lives, because it's easy to assume a scheduling tool handles it automatically. The profile-level badge is a setting a creator turns on directly in their own Instagram account — it isn't something a third-party publishing call sets on their behalf, and it isn't scoped per-post the way a caption or a media URL is. Whatever gets the finished piece onto the platform — including posting or scheduling to social media from inside Versely — publishes the content itself; the account-level disclosure decision is made once, separately, in Instagram's own settings, and stays in effect regardless of which tool published any individual post afterward.

What is a per-post decision, every time, is whatever you write into the caption or say on camera about how a piece was made — the situational disclosure that post-level tagging is actually for. That's the judgment call worth making deliberately on each post, independent of whatever the account-level badge is set to.

Treat it as two questions, not one

"Should this be labeled as AI" is really two separate questions wearing one sentence: does this specific post need situational disclosure, and does this account's overall output justify a standing badge. Most of the bad outcomes — over-tagging a mostly-organic account, or under-tagging an account that's functionally all AI — come from answering only one of those questions and assuming it covers the other. It doesn't. They're different scopes, they don't stack the way you'd expect, and Instagram's own implementation treats them as separate enough that the more specific one wins when they'd otherwise conflict.