Help
Help Center
This page covers the questions that matter during the rebuild: how to structure better Seedance requests, how credits fit into the reusable SaaS layer, and how to keep public content aligned with what the product really does.
How to prepare a better Seedance request
The strongest requests usually stay specific about one scene, one subject priority, and one camera intention. If the prompt tries to solve five ideas at once, the output brief becomes muddy before generation even starts.
For image-guided motion, start with a clean still frame and describe the movement, shot energy, and environment shift you want. For text-first generation, define subject, movement, lighting, and destination format in the first sentence.
- Lead with subject + motion + camera + lighting
- Keep the first pass narrower than your final ambition
- Use reference images when identity or framing matters
- Choose aspect ratio based on destination before you generate
How credits are treated in the current build
The project already includes login, pricing, payments, and record pages. Those layers are reusable and stay in place while the final provider configuration is completed.
Credit pricing can be adjusted later without reworking the homepage or studio. That is why the rebuild is separating interface structure from provider-side configuration.
- Pricing and checkout stay available during the rebuild
- Record history remains the reusable output archive surface
- Final per-generation credit mapping is a config-layer decision
If something feels off
If the homepage copy, studio controls, or pricing narrative stop matching the actual provider behavior, treat that as a product problem, not a cosmetic one. The fix is to bring the content back in line with the real workflow.
For account, billing, or access issues, use the support email so the operational layer can be corrected without muddying the public-facing product story.
- Update claims when provider limits change
- Keep support copy aligned with the live billing flow
- Do not leave outdated model claims on indexable pages
If you are changing model configuration next, update the homepage proof points, pricing details, and support copy together instead of treating them as separate tasks.
