Skip to content
SWRFlow
Troubleshooting / Troubleshooting

Seedance reference image not working? What to check

When a Seedance reference image is not working, first identify where the process stopped. A file that will not upload, an accepted request that fails and a completed video that ignores the reference need different responses. Start with the checks below before paying for another attempt.

The starting point

Check the generation mode, the actual file format and the upload status first. Then read the selected model's limits and any displayed error. If a task already exists, inspect its status before submitting again.

On this page

Before you begin

  • The exact model and mode you selected.
  • The message shown by the uploader or generator.
  • The task identifier if a generation was already submitted.

Identify the stage of the problem

Match the symptom to the next check
SymptomStart here
The file cannot be selected or uploadedFormat, file size and the uploader's message.
The image is visible but Generate is unavailableMode, required fields, model limits and upload completion.
A submitted task failsThe task's error and the model's input restrictions.
The output looks unlike the referenceReference clarity, motion and prompt instructions.
A completed output will not downloadDownload status and browser behavior, not a new generation.

1. Check the model and input mode

Confirm the full model name and choose image-to-video if that is the workflow you want. Check again after switching models, opening a saved draft or following a link from another page. A reference accepted by one model is not automatically valid for another.

Different controls mean different things. A reference can guide appearance, while a dedicated first/last-frame mode constrains endpoints. In SWRFlow's current Seedance 2.5 route, do not expect a first/last-frame control that the interface does not expose. The quick video generator accepts images, not audio or video references.

2. Check the real file format

Follow the accepted formats and size limit shown in the uploader. If your image is in an unsupported format, convert it with an image tool and reopen the converted file to verify it. Changing a filename from .heic to .jpg does not convert the file's contents.

Keep the original, especially before repeated compression. When the image is too large, make a smaller copy and confirm that the subject and important details are still clear. Avoid pushing a file just below a limit by stripping away the information the model needs.

3. Confirm the upload finished

A preview can appear before a file is ready for a generation. Wait for the uploader to complete, read any status message and check your connection if the transfer stops. If there is an error, address it before assuming that the reference has been attached to the request.

If a task has already been submitted, check the existing task first. Repeatedly clicking Generate can create separate requests. Refreshing a page or reopening a saved draft is not a substitute for checking the task's actual state.

4. Check reference count and subject restrictions

For the current Seedance 2.5 integration, SWRFlow allows up to 16 image references. The exact ceiling can differ for other models. Start with one clear image when diagnosing a failure, even if the interface permits more.

Real-person photos can require a supplier review workflow that is not currently available in this SWRFlow route. Use appropriate object, landscape or illustrated references. Do not repeatedly alter a rejected photo in an attempt to bypass a restriction; choose an input supported by the workflow.

If a request is rejected, follow the actual message. Not every failure is a content restriction: unsupported settings, a transfer issue and temporary service problems can look similar until you inspect the task details.

5. If generation succeeds but the reference changes

  1. Use a clearer image with one main subject.
  2. Reduce large camera changes that require the model to invent unseen surfaces.
  3. State what should move and what must stay the same.
  4. Remove conflicting descriptions that redesign the subject.
  5. Keep the model and settings fixed while testing one prompt change.

For example, a product that changes shape during a full rotation may need a smaller camera arc or better source views. That is a creative reliability issue, not proof that the upload failed. The product-image tutorial includes a review checklist for this situation.

When to contact support

Contact support when a task remains unclear, an error repeats with a supported input or the displayed balance does not match the task outcome. Include the task identifier, approximate time, model, settings and exact error text. Avoid sending passwords, payment card details or private material that is not needed to explain the issue.

If the result exists but cannot be downloaded, check the browser's downloads and whether the task is complete. Preserve the task information and ask for help recovering that output before buying a duplicate generation.

Questions

Why does the image upload but the task still fail?

Uploading and generating are separate stages. The uploaded file may still violate the selected model's input restrictions, or the generation service may return another error. Read the task message and compare it with the model settings rather than assuming the file-transfer step proves the request is supported.

Why are my reference images ignored?

A reference can guide a result without fixing every detail. Unclear images, competing references, strong camera movement or contradictory prompt wording can make it harder to preserve a subject. Try one clean reference with a simple action and review one change at a time.

Should I keep retrying a stalled generation?

Check the current task before submitting another one. A request that is still processing is different from a confirmed failure. If its state is unclear or it remains stuck, keep its identifier and contact support so you do not create unnecessary duplicate requests.

References & useful links

Put the next step into practice

Confirm the model, mode and reference status before trying again.

Check your video settings