
Seedance Human Face Detected: Fix Rejected Reference Images
Work out why Seedance rejects a face reference, separate AI characters from real-person photos, and test the appropriate Seedance 2.5 workflow on EvoLink.
On this page
Why Seedance detects a human face in an AI reference
InputImageSensitiveContentDetected.PrivacyInformation for an image that may contain a real person; the video counterpart is InputVideoSensitiveContentDetected.PrivacyInformation. These are ModelArk identifiers, not EvoLink error codes. Use the returned message to connect the privacy error to your particular input.content_policy_violation as non-retryable and distinguishes it from format and infrastructure failures. Save the error type, message, affected input field, request ID, endpoint and time. A policy category alone does not prove that a face caused the rejection; the message and context must support that diagnosis.An AI image's origin and its eligibility on a particular service are separate questions. Writing “this is AI-generated” in the prompt does not register the asset in a provider's trusted-media system.
Choose the fix that matches your material
| What you have | What to establish | Practical next step |
|---|---|---|
| A fictional, photorealistic AI character | Does this route document support for AI-generated human references? | Test the documented EvoLink Seedance 2.5 image workflow with one original character image. |
| A photo of a specific real person | Are permission and the provider's portrait onboarding requirements satisfied? | Confirm the supported real-person path before submitting; an AI-character capability does not settle this. |
| A product or location image without a person | Is the error actually about URL access, file format or parameters? | Fix the indicated input issue rather than assuming a face-policy block. |
| A completed video with a changing face | Was the input accepted, but identity continuity lost? | Simplify the shot and evaluate reference consistency; this is an output-quality problem. |
For EvoLink, use the current API documentation as the integration contract. Its explicit AI-generated-material support gives you a concrete workflow to evaluate; it does not guarantee that every reference or finished video passes review.
Test an AI character with Seedance 2.5 on EvoLink
1. Start with a minimal reference package
Keep the original AI-generated character image and its provenance. Pick one clear subject, a simple background and a visible face. Use that image alone for the first test, so a failure is easier to attribute. If you need to reproduce a real actor, use the real-person path instead of describing the photo as synthetic.
2. Choose the route by the task
3. Test one action before a full ad
401 as an authentication issue and 402 as insufficient quota; neither alone diagnoses a face rejection.Keep the camera still and ask for one action:
The current image-to-video documentation explicitly describes Chinese and English prompts. This copy-ready example uses English; we have not verified other prompt languages for this workflow.
The fictional adult presenter in the reference image lifts a plain ceramic mug, looks toward the camera, and smiles briefly. Preserve the character's facial features, short dark hair and teal jacket. Soft daylight, one continuous shot, no on-screen text.
This wording tests continuity and motion. It is not a control for changing moderation decisions. Add dialogue, camera movement and extra references only after the basic shot is usable.
4. Check completion and save the evidence
completed or failed. Task creation alone is not a successful video. Keep the request settings, task ID, final error or result, and actual usage. Download accepted output promptly; the documentation specifies that generated video links are valid for 24 hours.An accepted face reference still needs an output check

Compare the reference with the beginning, middle and end of the clip. Inspect face shape, hairline and clothing, then watch the full video at normal speed for identity changes during head turns. Check the hand and mug for deformation. If you add speech, review mouth timing and pronunciation separately.
When switching providers helps—and when to stay
If your current provider already accepts the assets and delivers usable shots at an acceptable cost, a face-related forum post is not a reason to migrate. For a specific real person, establish the supported authorization process first. A gateway change does not itself prove that an unsupported asset becomes eligible.
FAQ
Does a human-face error mean Seedance cannot generate people?
No. A reference-input restriction and the ability to generate a person are different. Check the provider, asset type and error details before deciding what to change.
Why was my AI-generated face rejected on fal?
Users report this symptom, but the exact request needs its own diagnosis. Inspect the error type, message and input location. Photorealistic appearance alone does not establish eligibility on that route.
Does EvoLink support AI-generated realistic human references?
Yes. The current Seedance 2.5 image-to-video and reference-to-video documents explicitly list that support. Evaluate your own assets; the statement is not an approval-rate guarantee.
Can I upload a real actor's photo instead?
Treat that as a separate asset category. Confirm permission and the current provider-specific onboarding requirements. Support for AI-generated people does not establish acceptance of every real-person photo.
Will changing the prompt or retrying fix the rejection?
For a confirmed input-policy rejection, use the documented asset workflow or request a review. Prompt edits can address the shot's creative direction; unchanged retries do not resolve an eligibility requirement.
Which Seedance 2.5 mode should I use?
Use Image-to-Video for a starting frame or first/last-frame pair; Reference-to-Video for references guiding new footage; Video Edit or Video Extend for an existing clip.
Is a completed task enough to approve the result?
No. Check identity through the full clip, hand-object interaction and any speech. Keep the task status and your creative acceptance decision separately.
Do I need to move my entire workflow from fal?
No. Test a representative, supported reference job first. Keep a working route unless the new route improves your measured workflow, integration burden or accepted-shot cost.
Sources
- EvoLink: Seedance 2.5 image-to-video — AI-generated realistic human materials, frame inputs and task handling.
- EvoLink: Seedance 2.5 reference-to-video — new-footage reference workflow and edit/extend distinction.
- BytePlus: portrait video creation — ModelArk-specific portrait-asset paths.
- fal: model errors — structured error classification and retry guidance.
- Community: AI-character face-detection reports — user problem discovery, not a cross-provider benchmark.
- BytePlus: error codes — ModelArk image/video privacy identifiers; not an EvoLink error schema.


