Shedance AI creator community
Product feedback
Send suggestions, model requests and reproducible problems to support@shedance.ai. Use an account support ticket for anything that needs access to a job or billing record. We do not advertise an unconfigured chat server or promise real-time support.
Share responsibly
Share only work and reference media you have permission to disclose. Obtain necessary consent for a person's likeness. Do not publish private job links, prompts, invoices or account details in a public discussion. Label AI-generated media where viewers could otherwise be misled.
Creative examples
The video gallery contains creative previews for inspiration. A public example is not a customer testimonial or a guarantee of an identical result. Your private account history is separate from content deliberately made public. Read the creation guide for a practical workflow.
Rules for discussion and submissions
Be constructive and respectful. Do not post illegal or exploitative content, non-consensual intimate material, impersonation, harassment, spam or media you are not authorized to share. Do not try to evade content review or misuse the service. The acceptable-use policy applies to requests and shared materials.
Report a concern
Contact support@shedance.ai with the relevant public URL or job identifier and a factual description. Avoid reposting harmful or private media. Account and payment questions belong in Support.
Ask for feedback on one shot decision
A useful critique starts with the purpose of the scene. Explain what the viewer should notice first, which subject should move and whether the camera should stay still. Then ask one question: is the action readable, does the framing establish the location, or does the ending leave enough room for an edit? These questions produce more actionable feedback than asking whether a clip is good.
Describe a revision in the same terms. If the first attempt changes the architecture while moving down a street, a second attempt could use a fixed camera. Keep other settings stable when possible. You can share that reasoning without disclosing private prompts or the reference image itself.
Keep a comparison useful
When you are authorized to share both versions, label their order and identify the single change. Compare the clips at the same size and inspect the first frame, the main action and the last frame. Check whether the apparent improvement survives normal playback rather than relying on one attractive still image.
Do not present these comparisons as a controlled benchmark unless you actually performed and documented one. Different inputs, model options and output settings can affect results. Use the shot-planning guide for a starting checklist and keep account-specific troubleshooting in a private support conversation.