Seedance 2.0 'Not Eligible': What It Means and How to Fix It

"Not eligible." Two words, no explanation, and your generation is dead before it starts.

If you're running into this on Seedance 2.0, you're not alone. It's one of the most searched errors on the platform, and the reason it's so frustrating is that the message is the same whether the block is about a face, a copyrighted character, a post-generation output flag, or a platform-specific restriction. Same two words, four different causes, four different fixes.

This guide covers all of them.

TL;DR

• Real human face in your reference image → blocked at input. Fix: use an AI-generated portrait from Seedream instead of a real photo.
• Copyright content in your reference → blocked before generation. Fix: abstract the visual description, remove IP-specific details.
• Element eligibility check (Higgsfield and some other platforms) → seemingly random, platform-specific. Fix: try a different angle or background in your reference image; or switch platforms.
• Post-generation flag → the video generated but got flagged on output. Fix: click "Confirm rights" when the prompt appears — the video is already there and can be unlocked in two seconds.
• Platform-added restrictions → the underlying Seedance 2.0 model isn't the blocker; the wrapper platform is. Fix: use a different access point for the same model.

---

Trigger 1: Real human face in your reference image

This is the most common cause. The standard Seedance 2.0 model has a hard upstream restriction: reference images and videos containing detectable real human faces are blocked at the input layer, before any video generation begins.^[1]

The error typically surfaces as "Input image may contain real person" or, on some platforms, simply as "not eligible" on the reference image thumbnail.

What triggers it on the standard model:

• Real photos of anyone, including yourself
• Photorealistic AI-generated portraits that the face detector classifies as real (this happens more often than you'd expect with high-quality outputs from GPT-4o Image or Flux)
• Stock photos with people in them
• Screenshots from video calls or social media

What doesn't help on the standard model: cropping the face partially, adding sunglasses, blurring features, or overlaying text. The filter checks the source image data and runs multiple detection passes. Evasion attempts that partially occlude the face are a known failure mode.

Two fixes, depending on which model you're using:

Fix A — Use the Portrait model tier on seedance2.so. This is the fastest path if you need real human faces. seedance2.so offers a face-enabled model tier that explicitly supports real-person and portrait content. In the reference-to-video studio, look for models tagged "Portrait" in the model selector — you upload real photos directly and generation proceeds without the face block.

Fix B — Use an AI-generated portrait instead. If you're on a platform that doesn't offer the face-enabled tier, generate a fictional portrait with Seedream and use that as the reference. AI-generated portraits of fictional characters pass the standard filter reliably — ByteDance documents this as an intended workaround for likeness use.^[1] Cost: roughly $0.04 per portrait.

There's a full guide to both approaches in Seedance 2.0 face limit: the 3 legit workarounds.

---

Trigger 2: Copyright content in your reference image or prompt

The second trigger is copyright detection, and this one is subtle because it fires on feature combinations, not just named characters.

You don't have to type "Spider-Man" to get this block. Describe a character in a red-and-blue suit shooting webs from their hands, and the classifier will often match that combination to protected IP. The same logic applies to costume patterns, logo shapes, distinctive weapon designs, and animation style signatures associated with specific franchises.

The error here might be "due to copyright restrictions" or the generation might be blocked outright as "not eligible" before processing starts.

What triggers it:

• Named copyrighted characters in prompts or visible in reference images
• Visual combinations that pattern-match to known IP even without naming the character
• Reference images that contain recognizable franchise visuals (Ghibli-style backgrounds, specific vehicle designs, etc.)
• Branded logos in reference images

The fix: Abstract the visual description. Instead of franchise-specific details, describe the underlying visual properties: "figure in dark form-fitting tactical armor" instead of the character name, "vehicle with sleek aerodynamic body and glowing underbody strip" instead of a named car. For reference images, swap out anything with a recognizable IP stamp for a visually similar original.

The Seedance 2.0 content filter guide has a full table of what substitutions consistently pass, including tested alternatives for the most common action and character archetypes.

---

Trigger 3: Element eligibility check (platform-specific)

This is the most confusing one, and it's mostly a Higgsfield issue (though other platforms have equivalent checks).

Some platforms run their own pre-screening layer before submitting to the Seedance 2.0 API. On Higgsfield, this shows up as an "element eligibility" status that gets attached to your uploaded reference image. The image goes into a "checking" state, and when it comes out the other side, it might be "eligible" or "not eligible" — often for no reason that's apparent from the image itself.

The community understanding of what's happening: the platform's eligibility algorithm occasionally misidentifies AI-generated or original characters as known public figures or celebrities.^[2] Two images with similar visual profiles (same lighting, same framing, same roughly-human subject) can produce different eligibility outcomes because one happens to score above a threshold and the other doesn't.

Users report: images generated with the same base model, same prompt style, same approximate character design — one passes, one doesn't, with no visible explanation.^[2]

What to try:

• Change the angle: A three-quarter view often passes where a straight-on frontal portrait fails.
• Change the background: Solid-color or neutral gradient backgrounds reduce false positives compared to contextual environments.
• Change the lighting: High-contrast dramatic lighting creates facial feature patterns that can trip misidentification. Soft diffuse lighting tends to produce cleaner eligibility results.
• Generate more variations: Because the classifier is probabilistic, a new generation of the same character with slightly different parameters sometimes passes where the first didn't.
• Use a different access point: If the underlying model's block rate doesn't match what you're seeing, the platform layer is adding restrictions. On seedance2.so/reference-to-video, the eligibility check goes to the ByteDance API directly without a separate pre-screening layer.

---

Trigger 4: Post-generation flag ("Rights verification required")

This one is actually recoverable, and most people don't realize it.

When Seedance 2.0's post-generation filter flags a video, some platforms now show a popup that says "Rights verification required" instead of simply blocking the output. This is different from a pre-generation block: the video was generated and does exist, and you can unlock it.

The unlock flow:^[3]

1. Click on the video thumbnail (it may show as "not eligible" or "blocked")
2. A popup appears asking you to confirm rights
3. Click "I confirm" or "Confirm rights"
4. The video unlocks immediately

This only works when the video thumbnail is visible — meaning the generation ran to completion. If the block happened before generation started, there's nothing to recover. But if you can see a thumbnail in your output queue, the rights confirmation flow is worth trying before assuming the generation is lost.

The reason this exists: ByteDance rolled out this mechanism after realizing that strict post-generation filters were catching large amounts of content that wasn't actually problematic, frustrating legitimate creators. The confirmation acts as a user-level override.^[3]

---

What platform you're using matters

The same Seedance 2.0 model. Different access points. Different block rates.

Seedance 2.0 has a fixed set of restrictions at the model layer — the real-face block and copyright blocks apply universally. But platforms that wrap the model add their own filtering layers on top. Higgsfield's element eligibility check is one example. Some platforms add further prompt filtering, resolution caps, or rate limits on retries.

Two things set seedance2.so apart here. First, if you need real human faces, the Portrait model tier handles that directly — upload a real photo and generate without the standard face block. Second, for standard generation, there's no supplementary filtering layer beyond what the model enforces upstream.

Free credits on signup. No credit card required. If you want to test whether a block you're hitting is model-level or platform-level, it's a low-cost way to find out.

---

Summary: which fix to use

---

References

1. ByteDance/Volcengine Seedance 2.0 API documentation. Real person handling and asset ID system. volcengine.com/docs/6791/1399098
2. r/HiggsfieldAI community discussion on element eligibility. reddit.com/r/HiggsfieldAI/comments/1sokdol
3. r/generativeAI community thread on rights verification unlock flow. reddit.com/r/generativeAI/comments/1sxccz1