The Seedance 2.5 Website Pack The complete guide to building cinematic, scroll-driven websites with Seedance 2.5 — what the model can and can’t do, the seven-step build recipe, and six copy-and-paste prompts that turn a sentence into a launched website.
What Seedance 2.5 Really Is
Seedance 2.5 is ByteDance’s multimodal video model in Higgsfield MCP. The most important feature for website work is duration: a single generation can run up to thirty seconds. That’s enough time for the entire scroll journey in one continuous take — no chaining, no splices, no loss of continuity. It also reads image, video, and audio references simultaneously and can extend or edit existing clips.
t2v modes (prompt only) · omni_reference (image / video / audio references) · video_edit (edit a reference video) · video_extension (extend a clip forward or backward)
Duration: 4 to 30 seconds. Default: 5. This is the main feature — nothing else here exceeds 15.
480p or 720p resolution. 720p is the limit — upscale the clip you keep before extracting frames from it.
References start_image, end_image, image_references, video_references, audio_references
Auto aspect ratios, 21:9, 16:9, 4:3, 1:1, 3:4, 9:16
Audio generate_audio defaults to true. Always set it to false for website work—you’re capturing frames, not publishing a video.
Cost: 6.5 credits per second at 720p. 3 credits per second at 480p. Exactly linear, so a 10-second clip at 720p costs 65 credits, and a full 30-second take costs 195.
Working in 720p
720p is the limit, so treat it as a design constraint. Frames extracted directly from a 720p render look soft and stretched in a full-bleed hero on a large screen—the fix is to run the clip you’re keeping through the video upscaler to 2K with the AIGC preset, then extract frames from the upscaled version at 1600 pixels wide. Generated material upscales cleanly, and only the final clip needs this. Draft in 480p while the camera movement is still being tested, then commit to 720p once it’s right.
How to build a website with it
The viral "3D scroll" effect isn’t Three.js. It’s a canvas image sequence scrub: a short cinematic clip is exported to about 180 numbered frames, all preloaded, and the frame drawn on the canvas is chosen by the scroll position. Scroll forward and backward, and the clip plays. The 3D effect comes entirely from the video. Here’s the full pipeline.
1 Paste the entire prompt without edits the first time. Each prompt below is a complete brief: the shots, site structure, design direction, and instruction to launch and verify. Run it as is once before you start customizing.
2 Generate ONE hero image first, then reference it everywhere. Create a single still with GPT Image 2 or Nano Banana Pro, then pass that job id as start_image in every clip. That’s what keeps your product, person, or building identical across shots. It’s the difference between a site that looks expensive and one that looks generated.
3 Choose the shape of your journey. One long take (up to 30s) is the cleanest option and exclusive to 2.5. To go further, chain clips by feeding the final frame of each clip in as the start_image for the next—extract it with ffmpeg, upload it, and reuse it. Or use video_extension to extend a clip you already like.
4 Ask for continuous motion, and say it twice. Put “one continuous take, no cuts, no camera shake” in every motion prompt. A hard cut looks broken when the visitor scrolls back, and handheld shake looks like a scrolling glitch.
5 Upscale before slicing. 720p frames stretched across a 27-inch hero look soft. Run the selected clip through the video upscaler to 2K first (the AIGC preset works well for generated material), then slice it. There’s no upfront cost check for upscaling, so check your balance before and after.
6 180 frames, 1600 pixels wide, quality 86. That’s the sweet spot: smooth enough to read as video, light enough to preload. More frames or larger frames add nothing but loading time.
7 Have the assistant start and verify before reporting completion. End every prompt with this instruction. “Run it on localhost and verify that every scroll animation works before telling me it’s ready” turns a hopeful build into a verified one.