Seedance 2.0 "Not Eligible": Why It Happens, What Works

If Seedance 2.0 keeps stamping "Not eligible" on your reference image, you are not being throttled and you did not break a hidden rate limit. You are hitting a content check that ByteDance enforces at the model level, and its two triggers are documented in the company's own API rules: real human faces and protected intellectual property^[1]. No platform can wave it off, and most platforms do not even document it, which is why the error feels random.

This post assembles what is actually written down: ByteDance's own eligibility rules and error codes, what the platforms' interfaces are really checking, why the same face passes one day and fails the next, and the routes that legitimately work when your project involves real people.

TL;DR

• "Not eligible" is face and IP detection. Higgsfield's own interface explains the failed state as "This image contains faces or IP and cannot be used," and refunds the credits^[2][3].
• The rule comes from ByteDance, not the platform. The official API documentation states Seedance 2.0 models "do not support direct upload of reference images or videos containing real human faces"^[1], and Higgsfield's team has said publicly the detection "is on Seedance 2.0's side"^[4].
• There is no moderation off-switch. The official Seedance 2.0 API exposes no safety parameter; input and output are both screened, always^[1][5].
• "Sometimes it works" has boring explanations: older Seedance 1.5 Pro is not under the same face restriction on Dreamina^[6], platforms stack their own filters on top, and detection is threshold-based, so borderline images flip between runs.
• Legitimate routes exist: ByteDance documents three exemption paths, including a consent-verified upload channel^[7], and reAPI's face-enabled Seedance tier is built for exactly that workflow.
• Bypass tricks circulating on Reddit violate the acceptable-use policy you agreed to, and the model re-screens outputs anyway^[5].

What "not eligible" actually means

Higgsfield is where most people meet this error, so start there. The platform runs every reference through a content check with three states, and the interface strings are unambiguous: "Checking content…", "Eligible", "Not eligible." When the check fails, the interface says why: "This image contains faces or IP and cannot be used," or on generations, "This generation may involve protected IP or likeness rights"^[2]. The pipeline even has a dedicated IP-detection stage, and flagged requests are not charged; Higgsfield's docs confirm credits come back automatically^[3].

So the error is not about image quality, format, or your account standing. It is a verdict on the content: the system believes your reference contains a real person's face or someone's protected property.

And it is not Higgsfield's verdict. When users complained on Reddit, the Higgsfield team answered directly: "The face detection you're running into is on Seedance 2.0's side, not something Higgsfield controls"^[4]. Every platform serving Seedance 2.0 inherits this.

The rule underneath: no real faces, no protected IP

The primary source is ByteDance's own API documentation, which states it plainly: Seedance 2.0 series models "do not support direct upload of reference images or videos containing real human faces"^[1]. The error-code catalog is just as direct. InputImageSensitiveContentDetected.PrivacyInformation means the input "may contain real person"; the .PolicyViolation variant flags material that "may be related to copyright restrictions"^[5].

The consumer side matches. When CapCut rolled Seedance 2.0 out globally on Dreamina, its newsroom post said the launch was "restricting certain capabilities… including the ability to make videos from images or videos that contain real faces," alongside technology "designed to block the unauthorized generation of intellectual property" and invisible watermarking of outputs^[6]. Dreamina's model picker labels Seedance 2.0 with a flat "Real human faces are not supported."

The why is not mysterious either: Seedance 2.0's launch collided with studio copyright disputes serious enough that ByteDance paused the global rollout for a month^[8]. Deepfake liability plus IP litigation equals a hard filter at the model boundary.

Worth knowing: there is no toggle. The official API's parameter set contains no moderation switch of any kind; screening runs on inputs and outputs both, and the acceptable-use policy you sign prohibits depicting "a person (living or dead)'s voice or likeness without appropriate consent" and any attempt to bypass safety filters^[9].

Why the same image passes one day and fails the next

The inconsistency has three documented-or-observable causes, and none of them is luck.

Different models, different rules. On Dreamina, the "real faces not supported" label sits on Seedance 2.0 and 2.0 Fast, but not on the older Seedance 1.5 Pro^[6]. If a workflow "used to work," it may have been running a different model, and some platforms switch backend versions without announcing it.

Platforms stack their own filters. Higgsfield's trust page notes that moderation "is applied at the model level" and that "content policies may vary depending on the model being used"^[2], and platforms layer additional checks with their own thresholds on top of ByteDance's. Same image, different platform, different verdict.

Detection is probabilistic. Community testing shows the frustrating edge: stylized and even fully AI-generated faces get flagged as "real" people regularly, and borderline images flip verdicts between attempts^[10]. A threshold classifier near its threshold is noisy. Celebrity likenesses appear to face an additional recognition layer that composition tricks do not move, which is consistent with the "protected likeness" framing in Higgsfield's interface strings^[2].

One more source of confusion worth killing: "visual restriction" has no official definition anywhere in ByteDance's or CapCut's published documentation. It circulates in third-party SEO posts, and its practical meaning is simply the face-and-IP restriction described above. Dreamina's own "not eligible" string, separately, is an age-gate message unrelated to image checks.

The routes that legitimately work

Start with the split that matters: is your subject a real person, or is the detector wrong about a synthetic one?

If your character is synthetic and still gets flagged, you are fighting a false positive. The legitimate fixes are compositional: avoid tight, passport-style close-ups as the reference; prefer fuller scenes where the face is smaller in frame; and if the platform offers a first-frame mode alongside a universal reference mode, feed the character through the first frame, which is treated as scene context rather than a face reference. These adjust what the classifier sees; they do not defeat a correct detection.

If your subject is a real person, the answer is consent infrastructure, not tricks. ByteDance's own docs describe three exemption channels: content the platform itself generated for your account within the last 30 days can be trusted as input; a library of preset virtual avatars; and a verified route where a real person's identity and authorization are confirmed, after which their material is referenced through a dedicated asset ID^[7]. That last one is the official answer to "how do I make videos of myself."

On reAPI, the Seedance 2.0 face tier is built for real-person reference workflows where you hold the subject's consent and the necessary rights, priced above the standard tier, with the same per-second billing and the same one-line model switch. Failed generations refund automatically, so an unexpected rejection costs nothing but time.

What not to do: the grid-overlay and face-obscuring hacks that circulate on Reddit. They violate the acceptable-use terms you agreed to^[9], output screening re-checks the result anyway^[7], and platforms refund flagged attempts precisely because they expect the filter to catch things. Build on the sanctioned routes and the error stops being part of your workflow.

FAQ

What does "not eligible" mean on Seedance 2.0?

The reference you uploaded failed a content check for real human faces or protected intellectual property. Higgsfield's interface states it directly: "This image contains faces or IP and cannot be used"^[2]. The check originates with ByteDance's model rules, not the platform^[1][4].

Why does Seedance 2.0 block my AI-generated character?

False positive. The face detector estimates "is this a real person," and photorealistic synthetic faces sit near its threshold, so they get flagged often and inconsistently^[10]. Looser framing and first-frame placement usually resolve it for genuinely synthetic subjects.

What is "visual restriction" on Seedance 2.0?

An unofficial phrase with no definition in any ByteDance or CapCut documentation. In practice it refers to the same documented restriction: no real faces, no protected IP in reference material^[1][6].

Can I turn off Seedance 2.0's content moderation?

No. The official API has no moderation parameter, screening applies to both inputs and outputs, and the acceptable-use policy forbids circumventing it^[5][9].

Which platform has the fewest Seedance restrictions?

The face and IP rules travel with the model, so no platform escapes them^[4]; platforms differ only in the extra filters they stack on top and in how clearly they surface the error. The real lever is not platform-shopping, it is using the consent-based channels for real-person work^[7].

Do failed "not eligible" generations cost money?

Generally no. Higgsfield auto-refunds flagged requests^[3], and on reAPI failed tasks refund automatically as well.

Why are celebrities blocked even in stylized images?

Likeness protection appears to run as an additional recognition layer beyond generic face detection, matching the "protected IP or likeness rights" language in platform interfaces^[2]. Composition changes do not move it, by design.

How do I make Seedance 2.0 videos with my own face?

Through the verified-consent route: ByteDance's documentation describes identity verification plus authorization, after which your material is referenced via a dedicated asset channel^[7]. reAPI's face-enabled tier supports real-person reference workflows for API users who hold the subject's consent.

Designing around the rules, not against them

The pattern behind every "not eligible" story is the same: a model-level filter, documented by ByteDance and inherited by every platform, doing exactly what its owner intends after a copyright firestorm. Fighting it wastes credits and violates terms; understanding it turns the error into a routing decision. Synthetic subjects get compositional fixes, real people get the consent channels, and the face-enabled Seedance 2.0 tier on reAPI turns the sanctioned path into an API call. That is the entire playbook for making Seedance 2.0 not eligible errors disappear from your pipeline.

References

1. BytePlus (ByteDance). ModelArk — Seedance 2.0 input rules ("do not support direct upload of reference images or videos containing real human faces"). Retrieved July 2026 from docs.byteplus.com/en/docs/ModelArk/1520757
2. Higgsfield. Trust & safety page and production interface strings ("Not eligible", "contains faces or IP"). Retrieved July 2026 from higgsfield.ai/trust
3. Higgsfield. API documentation FAQ — flagged requests are not charged. Retrieved July 2026 from docs.higgsfield.ai/docs/help/faq
4. Higgsfield team (official account). Reddit reply: "The face detection… is on Seedance 2.0's side." Retrieved July 2026 from reddit.com/r/HiggsfieldAI/comments/1sq1hms
5. BytePlus (ByteDance). ModelArk — content moderation error codes (PrivacyInformation, PolicyViolation). Retrieved July 2026 from docs.byteplus.com/en/docs/ModelArk/1299023
6. CapCut Newsroom. Dreamina Seedance 2.0 global rollout — face and IP restrictions, invisible watermarking. Retrieved July 2026 from capcut.com/newsroom/dreamina-seedance-2
7. BytePlus (ByteDance). ModelArk — trusted-input exemptions and consent-verified asset channel. Retrieved July 2026 from docs.byteplus.com/en/docs/ModelArk/2291680
8. Reuters. ByteDance suspends launch of video AI model after copyright disputes. Retrieved July 2026 from reuters.com/technology/bytedance-suspends-launch-video-ai-model
9. BytePlus. Generative AI Acceptable Use Policy. Retrieved July 2026 from docs.byteplus.com/en/docs/legal/acceptable_use_policy_byteplus_genai
10. r/Seedance_AI (community). Face detection blocks even AI-generated content — discussion thread. Retrieved July 2026 from reddit.com/r/Seedance_AI/comments/1sfp3ag

Further reading

• reAPI. What Is Seedance 2.0 and How to Use It (2026 Guide). reapi.ai/blog/what-is-seedance-2-0-and-how-to-use-it
• reAPI. Seedance 2.0 API documentation. reapi.ai/docs/seedance-2-0
• CapCut. Dreamina Community Guidelines. capcut.com/clause/dreamina-community-guidelines