Seedance Face Detected: Real Person Errors, Explained

A filmmaker posted to r/Seedance_AI in April with a problem that had nothing to do with deepfakes. He generated a video, pulled the end frame, and fed that frame back in as the reference for the next shot. Seedance face detected a person in his own model's output and blocked it.^[4] His summary: "no consistent characters, no narrative workflows, no filmmaking use."

That thread ran to 118 comments and it is still the most common complaint in the Seedance ecosystem. The errors arrive in three different wordings depending on which host you are on, they fire on faces that were never real, and the advice you find online is almost entirely about tricking the classifier. This piece does the other thing: what each error actually means, which layer emits it, why synthetic faces trip it, and where real-person references are a supported input instead of a thing to smuggle past a filter.

TL;DR

Three error strings, same family. "Input image may contain real person", "Images with faces are not allowed. Face detected in uploaded image", and "The images or videos provided may contain likenesses of real people or other private information that cannot be processed."^[5]^[6]^[7]
They fire on fully synthetic faces. The classifier keys on photorealism, not on provenance, so a character you generated yourself gets flagged for looking too good.^[6]
It is not one filter. Some hosts run their own face detector on upload; some pass the reference through and let the upstream review decide. Same model, different door, different verdict.
Seedance 2.5 makes references the product. ByteDance's launch describes up to 30 images, 10 video clips and 10 audio clips per generation.^[3] A blanket upload ban on faces removes most of that.
reAPI accepts real-person reference images and video. Material passes automated review before generation, and anything rejected fails with an error and a full refund.^[1]

The three errors and where each one comes from

The wording tells you roughly how far your request travelled before it died.

"Images with faces are not allowed. Face detected in uploaded image. Please use an image without real people." This one never left the platform. It is a face detector running on the host's own upload handler, and it makes no distinction between a photograph of your neighbour and a rendered character. A user hit it on a service that had been sold to them as the most permissive Seedance host available.^[5]

"Input image may contain real person." Reported against Seedance 2.0 on BytePlus by someone whose characters came out of ChatGPT. Their description of the failure mode is the clearest one I have read: "The face is just too photorealistic, so the filter thinks it's a real human. Same images work fine on Kling."^[6]

"The images or videos provided may contain likenesses of real people or other private information that cannot be processed." The longest of the three, reported in July by someone whose avatars had been working for weeks with no changes on their end. "Today literally every single one of them is getting rejected."^[7] A commenter in the same thread reported the identical break on fal.ai the same day.^[7]

That last detail matters more than it looks. When the same error appears across unrelated hosts on the same day, the change happened upstream, not at your provider. When it appears on one host and not another with identical inputs, the host added it.

Why Seedance face detected fires on a face you made yourself

The detector is a classifier, not a provenance check. It has no access to C2PA metadata, no record of which model produced the pixels, and no way to know that the woman in your reference photo does not exist. It scores photorealism and facial structure and blocks above a threshold.

That produces a perverse gradient: the better your image generator, the more likely its output is rejected. One commenter put the absurdity plainly. "We create human ai faces in NB but cant use it on SD 2. SD2 should be able to distinguish between ai generated human faces from real photo faces. Not sure what the use case is if we cant use ai faces."^[4]

There is a second, quieter failure. Thresholds move. Nothing on your side changes, and a workflow that ran for six weeks starts failing every request, which is exactly what the July thread describes.^[7] If your production pipeline depends on a classifier's mood, you have no pipeline.

What the bypass threads are doing, and why this is not one

Search Seedance face detected and most of what surfaces is circumvention. Grid overlays, scenery composites, selective blurring, sketch conversion, prompt-level laundering, several "DM me for the tool" replies. Some of them work. One post claimed a 90% success rate for its method.^[8]

I am not publishing those, for two reasons that have nothing to do with squeamishness.

The first is that the control exists for consent. A likeness check is the one piece of this stack that protects somebody who is not in the conversation. Defeating it with a blur filter defeats it for photographs of real people who never agreed to anything, not just for your synthetic actor. That is worth keeping intact even when it is annoying.

The second is that the techniques degrade what you paid for. Every one of them works by damaging the reference until the classifier stops recognising a face. The model then also gets a damaged reference, which is the input you were relying on for character consistency. You buy a pass at the door by throwing away the thing you came in for.

The useful question is not how to defeat the detector. It is which routes treat a real-person reference as a supported input with a review step, rather than as something to block on sight.

Reference material as a first-class input

Seedance 2.5's design assumes reference material. ByteDance's launch post leads with it: up to 30 images, 10 video clips and 10 audio clips in a single pass, with reference capabilities spanning motion, style and multi-subject scenes.^[3] A host that rejects any image containing a face has disabled most of that surface.

On reAPI the model id itself reflects the position. There is one customer-facing Seedance 2.5 id, doubao-seedance-2.5-face, with no faceless variant to fall back to.^[2] The published behaviour is that real-person reference images and videos are accepted, that reference material passes an automated review before generation runs, and that anything rejected fails with a clear error and a full refund of the reserve.^[1]

The refund is the part that changes how you work. A false positive on a synthetic character costs you a retry and nothing else, so you can test a reference set instead of rationing attempts against a filter that might be having a bad day.

Two obligations do not move. Named living people and recognisable third-party characters stay refused regardless of route, and that is the model's own line rather than a host's policy setting. And consent for anyone appearing in your reference material remains yours to obtain. An API that accepts the upload is not an API that acquired permission for you.

What reAPI accepts, exactly

Worth having in one place, because half the reference failures people report are format problems misread as moderation.^[2]

Field	Limit	Formats
`image_urls`	up to 30, each under 30 MB	jpeg, png, webp, bmp, tiff, gif, heic, heif
`image_with_roles`	first frame, or first + last (max 2)	same as above
`video_urls`	up to 10, each 2–30 s and under 200 MB, combined 30 s	mp4, mov, 480p to 4K
`audio_urls`	up to 10, each 2–30 s and under 15 MB	wav, mp3

One platform rule catches people out: every reference must be a public HTTP(S) URL. Base64 and data: payloads are rejected across the whole reAPI surface, not just this model.^[2] A r/VeniceAI thread in August shows what that looks like when a host changes it without warning, with several users hitting the same "needs an accessible URL" wall in one afternoon.^[9]

Two more constraints are enforced before submit rather than minutes later: image_urls and image_with_roles are mutually exclusive, and a first/last-frame job only accepts size: adaptive.^[2] Both return immediately instead of failing after the task starts.

FAQ

What does the Seedance face detected error actually mean?

That a classifier scored your uploaded image as containing a real human face. It is not a claim that the person is real, only that the image looks photographic enough to cross a threshold.^[6]

Why does it reject my AI-generated character?

Because photorealism is the signal. A stylised or obviously rendered face passes; a face good enough to be mistaken for a photograph does not. Several users report their best synthetic characters being the ones that fail.^[4]^[6]

Can I upload a real person's photo to Seedance 2.5 on reAPI?

Yes. Real-person reference images and video are accepted and go through automated review first, with a full refund if the review rejects them.^[1] Consent and likeness rights remain your responsibility.

Why did the same images stop working overnight?

Upstream thresholds get retuned. The July r/generativeAI thread documents exactly this, with the same failure appearing on more than one host on the same day.^[7]

Does turning off the safety checker fix face rejections?

No. nsfw_checker selects which route runs your task, and likeness checks are not the thing it removes.^[2] A reference rejection and a content rejection are different failures.

Will a rejected reference still charge me?

Not on reAPI. A task that fails review refunds the reserve in full.^[1]

Can I use a named celebrity as a reference?

No, on any route. That limit sits with the model and no parameter reaches it.

Are the bypass methods on Reddit safe to use?

They work by degrading the reference until the classifier stops seeing a face, which also degrades the input the model uses for character consistency. Applied to photographs of real people they defeat a consent control, which is a different problem from an inconvenience.

Getting a character through without fighting a classifier

If you are building a narrative workflow, the classifier is not a puzzle to solve, it is a routing question. Hosts that run their own face detector on upload will block your synthetic lead however many overlays you stack on it, and the overlays cost you the consistency you were buying. Hosts that treat references as a reviewed input give you a verdict, a reason, and your credits back when the verdict is wrong.

Check which kind you are on before you build a production pipeline on top of it. Upload a single frame of your main character and read what comes back. If the answer is an instant Seedance face detected refusal with no generation time attached, you are talking to a doorman, not to the model.

References

reAPI. Seedance 2.5 — model page, real-person reference support and refund behaviour. Retrieved August 2026 from reapi.ai/models/seedance-2-5
reAPI. doubao-seedance-2.5-face — reference field limits, formats and submit-time constraints. Retrieved August 2026 from reapi.ai/docs/seedance-2-5
ByteDance Seed. One-take Creation, Flexible Referencing: Introducing Seedance 2.5. Published 31 July 2026, retrieved August 2026 from seed.bytedance.com/en/blog/one-take-creation-flexible-referencing-introducing-seedance-2-5
r/Seedance_AI. Seedance 2.0 is becoming unusable for filmmaking – face detection blocks even AI-generated content. Posted 8 April 2026, retrieved August 2026 from reddit.com/r/Seedance_AI/comments/1sfp3ag
r/Seedance_AI. Why do some companies keep saying their Seedance 2.0 is uncensored and completely unfiltered. Posted 7 June 2026, retrieved August 2026 from reddit.com/r/Seedance_AI/comments/1tyzrun
r/generativeAI. Seedance keeps rejecting my AI images as "real person"; any fix? Posted 22 May 2026, retrieved August 2026 from reddit.com/r/generativeAI/comments/1tkkxjq
r/generativeAI. Anyone else getting hit with "likenesses of real people" errors on Seedance 2.0 all of a sudden?? Posted 7 July 2026, retrieved August 2026 from reddit.com/r/generativeAI/comments/1upwj55
r/seedance. 90% bypass rate on Seedance 2.0 face detection. Posted 17 April 2026, retrieved August 2026 from reddit.com/r/seedance/comments/1sog2st
r/VeniceAI. Reference videos now need accessible URL? What is this? Posted 1 August 2026, retrieved August 2026 from reddit.com/r/VeniceAI/comments/1vcbvpr