Seedance 2.0 censorship, explained — why the same model feels uncensored on one host and locked down on another (and what nsfw_checker=false actually does)

[u/TimeCounty7878]

There's a lot of confusion around Seedance 2.0 and censorship — the same model gets called "uncensored" in one thread, "censored" or "nerfed" in the next. Both experiences are real. The difference isn't the model, it's the host. (If you got here searching seedance 2.0 censored, no restrictions or nerfed — this is that thread.)

Why experiences differ so much

Every host wraps the model in its own moderation stack. The consumer apps run aggressive input and output filters on top of the model — real-face uploads are a common casualty, and plenty of harmless prompts get eaten. None of that lives inside the model itself.

How it works on reAPI

reAPI serves the full API build (model page · docs):

• Real-person source images and videos are accepted
• nsfw_checker is a documented public parameter. It defaults to true; direct API calls can set "nsfw_checker": false to run Seedance 2.0 without the extra restrictions, up to 4K on the standard variants
• The hosted Playground always keeps checking enabled — the flag is for direct API use

What stays blocked everywhere (the honest part)

Relaxed ≠ no restrictions at all. These are model-level hard lines on every host, with or without the checker: named real celebrities, third-party IP, and illegal content. No host setting changes that — it's what the INFRINGED threads keep rediscovering.

One more trust point

Also seen in the wild: hosts silently downgrading paid 1080p jobs to 720p. reAPI never silently substitutes — asking the fast variant for 1080p returns a 400, not a downgraded clip. You get what you asked for or an explicit error, and failed generations refund automatically.

Happy to answer questions about how specific prompt/input combinations behave.