← Blog

TikTok's AI Label Is Hidden, Off by Default, and You Cannot Add It Later

There are plenty of good explainers on what TikTok's AI disclosure rules say. This is not one of them. This is about the part that actually catches people: the mechanics of the toggle itself, which are hostile to the exact person who intends to comply.

We know because we shipped a video without it. Not through carelessness about the rule, we had the rule written down, with the toggle's location documented two days earlier. It still went out unlabelled, and we could not fix it.

The three properties that combine badly

Individually each is reasonable. Together they produce a predictable failure.

It is hidden. In the web upload flow the AI-generated content switch is not on the main form. It sits inside a collapsed "Show more" section that you have to expand deliberately. If you fill in the caption, pick the cover, set visibility and hit Post, you will never have seen it.

It is off by default. Every time. There is no "remember this" that carries your last choice forward.

It is per post. Not a profile setting, not a channel-level declaration. Every single upload is its own decision, which means your compliance rate is only as good as your worst-attention day.

Now put those together with the fourth fact.

You cannot add it afterwards

The edit screen for a published video does not offer the toggle. Once a post is live without the label, the label is not something you can go back and apply.

That leaves two options, both bad. Leave it and carry the enforcement risk. Or delete and re-upload, which throws away whatever distribution the post has already accumulated, and on short video most of a post's life happens in its first hours.

This is what makes the AI label different from almost every other posting mistake. A weak caption can be edited. A bad cover can be swapped. A missing hashtag can be added in a comment. This one is a one-shot decision with no undo, hidden behind a collapse, defaulting to the wrong answer.

Why "I'll remember" does not work

We had it written down. The location, the confirmation dialog, the verification anchor — all documented, two days before we posted without it. Our own note even said the check should become a pre-publish gate.

Writing it down and doing it are different things, and the gap between them shows up precisely when you are busy doing several things at once. That is not a discipline problem you can solve with more resolve. It is a design problem, and the fix is structural: the check has to sit in the path, not in your memory.

Concretely, that means the label check belongs in the same place as pressing Post, not on a list you consult beforehand. If your process is a person following steps, the toggle has to be a step that blocks the next one. If your process is scripted, it should refuse to submit until the switch is verified on screen.

A pre-publish sequence that survives a distracted day

Four checks, in this order, immediately before Post:

  1. Expand "Show more". Not optional, not "if I remember". The section is collapsed on every upload.
  2. Verify the AI switch is on, by looking at it. Not "I clicked it" — a click that missed and a click that landed feel identical.
  3. Screenshot the form before submitting. One image covering preview, cover, the AI switch and visibility. It costs two seconds and it is the only evidence that survives if you need to answer "was it labelled?" later.
  4. Then post. Anything you were going to check after posting, check now instead, because the list of things you can fix after posting does not include this one.

The failure is not rare, it is the default outcome

Worth being blunt about the base rate, because "I would never forget that" is what everyone thinks before the first time.

Consider what has to go right on every single upload. You have to remember a setting that nothing on the visible form mentions. You have to expand a section you have no other reason to open. You have to notice a switch that is already in the wrong position. And you have to do all three while your attention is on the things the interface is asking you about — caption, cover, sound, visibility, product tagging.

An interface that hides a control, defaults it to the wrong value, and resets it every time is not neutral about your compliance rate. It is quietly setting it, and it is not setting it to 100%.

So the useful question is not "how do I remember?" It is "what in my process makes forgetting impossible?" Those are different questions with different answers, and only the second one holds up on a day when three things go wrong before lunch.

What the label does and does not cost you

The honest answer on reach: we do not know, and we are not going to guess. We label every post, so we have no unlabelled control group. Anyone telling you the label costs you X% is either measuring something we would like to see, or making it up.

What is documented is the other direction. Undisclosed synthetic content is what platforms enforce against, with reduced distribution and takedowns as the stated consequences, and automated detection is what finds it. So the comparison is not "labelled versus unlabelled reach". It is "labelled reach versus a risk you are carrying without pricing it".

Separately, and worth keeping distinct: whether AI-made video gets watched at all is a different question with an actual answer, and we wrote up the distribution we measured in do AI videos actually get views. Distribution and disclosure are two questions, and conflating them is how people end up deciding compliance policy on vibes.

One category worth checking separately

Rules in this area change faster than blog posts do, and some of them are not about the label at all. As one example, AI voices have been restricted in promotional livestreams since May 2026 — a rule that has nothing to do with the upload toggle and would not be caught by any amount of care on the posting form.

Check the current policy directly rather than trusting any third-party summary, including this one. What ages well here is not the specific rules, it is the operational habit: assume the disclosure control is hidden and off, verify it with your eyes, and capture evidence before the irreversible step.

Where this fits if you make AI video at volume

If you are producing one video a week, a checklist is enough. At ten a week it will fail, because the failure mode is attention rather than intent.

That is the reason our own publishing path treats the label as a blocking pre-flight check rather than a reminder: the step that submits refuses to run until the switch has been verified on screen. We built that after shipping one without it, which is usually when people build these things.

If you would rather not build any of that, Riffkit produces the video and the caption from one source video you already know performed — you riff the formula, not the video — and the posting decision stays with you, where the label lives. Related reading if you are earlier in the process: how to find winning TikTok videos worth modelling.

FAQ

Where is the AI-generated content toggle when posting to TikTok?

It is not on the main upload form. In the web upload flow it sits inside a collapsed 'Show more' section, it is off by default, and it is set per post rather than once per account. That combination is why people who fully intend to disclose still ship unlabelled videos: nothing on the visible form reminds them, and the setting does not carry over from the last upload.

Can you add the AI label to a TikTok video after posting?

No. The edit screen for an already-published video does not expose that toggle, so a post that went out unlabelled stays unlabelled. The only remedies are leaving it as is and accepting the risk, or deleting and re-uploading, which costs you whatever distribution the post had already earned. This is why the check has to happen before you press Post, not after.

Does labelling a video as AI-generated reduce its reach?

We cannot answer that from our own data, and we would rather say so than guess: we label every post, so we have no unlabelled control group to compare against. What we can say is that undisclosed synthetic content is what platforms act against, with reduced distribution and takedowns as the documented consequences. Choosing not to label is not a neutral experiment, it is an enforcement risk.

What counts as AI-generated for TikTok's disclosure rules?

The rules cover fully or significantly AI-generated or AI-altered media, including AI-generated backgrounds, scenes, and people. Light post-production such as colour correction, cleanup, or background removal is generally treated like ordinary editing. If a viewer would be misled about whether a person, place, or product is real, that is the case the rule exists for. Check TikTok's current policy directly before relying on any third-party summary, this one included.

Keep reading

Open-Sora Alternatives, Sorted by the GPU You Actually Have

Open-Sora 2.0 needs 52GB or more of VRAM. Here are the honest alternatives sorted by hardware budget, from 8GB consumer cards to no GPU at all.

How to Use Open-Sora 2.0: The Real Setup Guide, Including the VRAM Number

A practical Open-Sora 2.0 setup guide: the exact conda and pip commands, weight download, inference syntax, and the honest hardware requirement (52.5GB VRAM at 256px) that most guides leave out.

Open Generative AI Alternatives: What to Use Instead, by What You Actually Want

Honest alternatives to the Open Generative AI studio, sorted by intent: local image generation, local video, agentic production, short-form automation, and the hosted lane where you skip the GPU entirely.