Virtual try-on
What to check when a virtual try-on rejects your photo
Separate upload failures, photo requirements, and unusable generated results, then choose a specific next step without guessing at the cause.
When a virtual try-on rejects a photo, start with the message shown in the tool. Separate an upload that did not complete, a photo that does not meet requirements, and a generated result you dislike. They are different problems and may need different next steps.
Do not assume the cause from one symptom. A clear image can still encounter an account, connection, or service issue; an accepted image can still produce an unusable preview.
Record what actually happened
Note the stage, the visible message, and whether an image was produced. Keep sensitive details out of any screenshot you plan to share with support.
A hypothetical diagnostic note might say “Upload did not finish; no generated image; tool displayed a connection message.” That is more useful than “AI rejected my outfit,” which mixes an observed event with an unverified explanation.
This guide does not establish specific Tryoom error messages or a universal validation policy. Follow the current instructions in the service you are using.
If the upload did not complete
Check the tool's stated file requirements and whether the file opens normally on your device. Review relevant permission prompts and visible connection information. Do not assume changing the photograph will solve a failure unrelated to its contents.
Use the service's documented retry behavior. Before repeating a request, check the visible status and any stated usage or billing effects; do not assume a failed-looking attempt was never submitted.
If the problem persists, use the official support channel with the stage and exact message. You do not need to expose your full photo library or account credentials to explain it.
If the message concerns framing or visibility, review the person photo against that service’s requirements.
If the tool identifies a photo requirement
Read that requirement and compare it with the actual image. Check framing, relevant visibility, and other criteria the tool explicitly states. Use an image you own or have permission to use for this purpose.
Do not borrow another product's rules as if they apply here. A service may accept a selfie, a full-body image, or another format under different workflows. Its current instructions determine the next step.
Do not alter an image to evade a restriction. Choose a permitted photo or stop the attempt if you cannot meet the requirement.
If the issue points to the clothing reference, review the garment photo for missing views or ambiguous item identity before changing the person input.
If an image was generated but looks wrong
An unattractive or inconsistent output is not the same as an input rejection. Compare it with the person and garment references, then identify the detail that changed.
| Observed state | Useful next step |
|---|---|
| No completed upload | Check stated file, permission, and connection information |
| Explicit photo requirement message | Follow that service's requirement |
| Generated garment differs from source | Inspect and reject for affected decisions |
| Person features changed | Compare with original; do not treat output as a body assessment |
| Cause still unclear | Seek service-specific help with the exact symptom |
The virtual try-on guide explains the separate limit: even an accepted, convincing image does not establish physical fit.
For a support request, gather the minimum useful context: the approximate time, the step where the issue occurred, the exact visible message, and the permitted file details requested by the service. Share the photo itself only through a channel and under terms you understand. Never provide account passwords or payment credentials to explain an image problem.
If you are unsure whether an attempt completed, inspect the tool's history or status controls if available before trying again. Where no reliable status is visible, ask the service rather than claiming the request failed or that no usage was counted. A symptom-based note leaves room for the real cause to be investigated and avoids promising that a generic retry will correct every problem.
Stop when retries stop teaching you anything
Change one relevant input only when you have a reason. Repeating the same attempt without new information may not clarify the cause.
If a problem remains, preserve the message and contact support or choose another way to compare clothes. A physical outfit test or item-only board can still serve the underlying style question. The goal is a useful clothing decision, not an endless sequence of attempts to make one preview work.