No face detected
Use an original frame where eyes, nose, mouth, and most of the jaw are visible. Reduce heavy crop, blur, shadow, glare, hair, hands, masks, or extreme profile angle.
Face swap troubleshooting
Face swap not working? Find the failed stage first
Choose the workflow and the last stage that definitely succeeded. The local decision tree separates upload validation, account checks, queue state, terminal failure, and visual quality so the next retry changes the right variable.
Local decision tree
Diagnose before you retry
Selections stay in this browser. No media is read or uploaded, no account is queried, and no generation request is created.
Choose one workflow and one observed stage.
- Exact workflow rule
- First action
- Avoid
Checklist
This decision tree organizes current product rules. It cannot inspect media, detect a face, read task state, diagnose an upstream service, or predict output quality.
Failure-stage map
Start with the last stage that definitely worked
A rejected upload, an accepted task, a terminal failure, and a completed result you dislike are different conditions. Treating them as one problem wastes retries.
| Observed condition | First action | Do not |
|---|---|---|
| Upload rejected before a task exists | Check the encoded type, size, count, and duration in the matching preflight before selecting new media. | Do not repeatedly rename or enlarge the same file; correct the actual encoded media. |
| Sign-in, verification, credits, or another task blocks submit | Sign in, verify the account email, compare the displayed required credits with the balance, and let any active generation finish. | Do not keep pressing generate while another task is already in progress. |
| Task is PENDING or PROCESSING | Open task history and wait for the accepted task to become COMPLETED or FAILED before deciding whether to retry. | Do not create a duplicate task after a refresh or temporary network interruption. |
| Task reached FAILED or shows an actionable error | Read the displayed task error, then change only the condition it names: face visibility, moderation, file validity, rate, timeout, or temporary service availability. | Do not retry the identical input repeatedly without a terminal error and one deliberate change. |
| Task completed but the result looks wrong | Keep the target fixed and change one source variable first: clarity, angle, expression, light, or obstruction. | Do not scale a weak sample into a batch or long clip before one representative result passes review. |
Visual symptoms
Change one variable that matches the visible defect
Identity is blurry or weak
Use a closer, sharper reference and the least-compressed target original. Enlarging a thumbnail does not recover identity detail.
Eyes, mouth, or jaw are distorted
Reduce the pose and expression difference between reference and target before changing resolution or retrying every setting.
The wrong person changed
Return to group mapping and verify every numbered target-reference assignment; do not assume left-to-right order.
Video or GIF flickers
Find the first weak frame and identify the turn, blur, occlusion, light change, cut, or tiny face that begins the instability.
Task and credit boundary
Confirm status before you compare the balance
Before acceptance
Missing inputs, unsupported media, limit violations, verification, or insufficient credits can stop submission before a task is accepted.
Accepted task
The five face-swap workflows create a PENDING credit record, then decrement the account balance only inside successful task settlement.
Failed task
A FAILED face-swap task marks the pending credit record failed instead of decrementing the balance. Verify history and balance before any replacement submission.
Troubleshooting questions
Direct answers before another attempt
Why can a detected face still produce a weak result?
Detection only finds a face-like region. It does not prove sufficient identity detail, compatible pose, clear boundaries, or stable motion.
Should I submit again while a task is pending?
No. Check task history and wait for COMPLETED or FAILED. A duplicate can consume more time and make the balance harder to interpret.
Does a failed face-swap task consume credits?
For the five current face-swap workflows, the balance is decremented during successful settlement. A failed task marks the pending credit record failed.
How do I fix a no-face-detected error?
Use a clearer original where the face is larger and less obstructed, with visible eyes, nose, mouth, and jaw. Avoid extreme profiles and repeated thumbnail upscaling.
Can this decision tree inspect my file or task?
No. It only combines the workflow and symptom you select. It does not read files, call an API, inspect an account, detect faces, or predict quality.
Evidence boundary
Verified against current DeepSwapAI validation and settlement paths
The Product Team checked the five public workflow limits, account requirements, generation lock, PENDING-to-terminal task states, success-only balance decrement, failed credit-log handling, and public input/quality guidance. No provider status, completion time, accuracy, or guaranteed fix is claimed. Read the verification methodology
Retry only after the failed stage is clear
Choose the exact workflow, verify the displayed limits and credits, and change one input condition at a time.