Internet desks still meet a video job as a file someone emails over. The trouble starts when that file is supposed to come from aSeedance API endpoint that nobody has run as a prompt, a still, or a reference. A developer can paste a payload into a ticket and still hand an editor a clip the desk will reject, because the console and the code answer different questions. One asks whether the request is valid. The other asks whether the shot is usable.

The open studio is the right place for the second question. Seedance keeps a create panel beside the API notes: a prompt box capped at 30,000 characters, an aspect-ratio control sitting on adaptive, a duration control, resolution buttons for 480p, 720p, and 1080p, plus Generate Audio and Public Visibility. Text to Video, Image, and Reference are separate routes on that same panel. If those controls cannot describe the shot, wiring the endpoint only moves the argument into code review.

What The Console Asks For First

The prompt field is not a caption box. The page asks for the subject, the scene, the camera movement, the lighting, the mood, the action, the style, and the visual direction. A product desk that writes only "cinematic bottle, nice light" has not filled that brief. The camera move and the lighting are the parts a later grade cannot invent without a reshoot, so they belong in the first prompt, not in a follow-up comment.

The panel also shows a duration value and a resolution choice before any generate button. On the open page the duration read 5, with 480p, 720p, and 1080p available. Aspect ratio was set to adaptive rather than a locked frame. Those three controls decide whether the clip can sit in a story, a square post, or a vertical cut. Leaving them at whatever the page loaded is a choice, and it should be a conscious one.

Write The Scene Before The Model

Pick the route before you pick a model name. Text to Video is for a shot that exists only as words. Image is for a still you already trust. Reference is for motion, style, or a camera path you want followed. A build that always sends text, even when the brand already has a hero still, throws away the input the page built the Image route for. Write the scene so a colleague can tell which route you meant without opening the ticket.

Lock The Ratio Before You Generate

Adaptive aspect ratio will follow the job only if someone has said what the job is. A 16:9 master and a vertical teaser are different crops, and the page does not promise that one generate fills both. Lock the ratio in the brief, then match the control. If the duration on the panel is still the loaded value of 5 and the spot needs a longer hold, change it before the first preview. A wrong length is a rework, not a note for the developer.

How The Four Studio Steps Run

The page lays out four moves, and a trial should follow them in that order. Skipping to the last move is how a team compares outputs that were never aimed at the same brief. The steps are short. The discipline is in not adding a fifth step the page does not show, such as a hidden export preset or a model the picker does not list.

1. Choose fast generation when you need speed, quality-focused output when the asset has to look finished, or lightweight generation when the draft is cost-sensitive.
2. Write the subject, scene, camera movement, lighting, mood, action, style, and visual direction in the prompt.
3. Add a photo, a character frame, or a reference video when motion, style, or camera should follow something you already have.
4. Generate in the studio, compare the result with the brief, refine the prompt, and only then carry that same workflow toward an integration.

Pick Fast Quality Or Lite First

Fast, Quality, and Lite are the three options the page names for that first move. Fast is the quick draft. Quality is the polished pass. Lite is the cost-efficient draft. They are not three names for the same render. A desk that runs Quality on every scratch test will queue work it does not need, and a desk that ships a Lite draft as the master will fail the check the page itself calls polished output. Say which option the preview used, in the same note as the prompt.

Add A Still Or A Reference

Step three is optional only when the shot truly starts from text. If the job is to move a product photo, or to follow a camera path you already filmed, the reference is the brief. The page describes image-to-video and reference input as the way to keep visual direction while the motion changes. A text-only prompt beside a hero still is how the product drifts into a different bottle. Put the still on the Image route, or the clip on Reference, before anyone argues about adjectives.

What To Check Before A Payload

Two model lines cover the jobs a team can run today. Seedance 1.5 is the high-throughput line for text-to-video and image-to-video, aimed at prompt adherence and bulk production. Seedance 2.0 is the cinematic line: image, video, and audio can drive motion transfer and lip-sync, with the page stressing character consistency and more complex camera paths. The studio can be used without writing code, and the same page says a developer can export the matching payload after the preview. That order matters. The payload should record a preview someone has already compared with the brief.

The model strip on the page shows an identifier, seedance-1-5-pro, for the 1.5 Pro slot. Treat that string as the thing to copy, not a nickname you invent in the ticket. The 2.0 line on the picker splits further into an Ultra card, a Fast card, and a Mini card, each marked Audio. You do not need all three in the first trial. You do need the note to say which card the preview used, because Fast and Ultra are not interchangeable once the clip is supposed to be finished.

Here the Seedance 2.0 API question becomes practical. If the shot needs a reference video or an audio drive, the 2.0 line is the one the page describes for that input. If the shot is a high volume of text or image clips and the priority is throughput, 1.5 is the line the page describes. Choosing in the ticket without choosing on the panel is how the wrong model ships.

Where A Studio Preview Goes Wrong

A preview goes wrong in ways a status code will not catch. The subject can drift: the bottle shape changes, the presenter's face is a different person by the second beat, or the camera move in the prompt fights the camera move in the reference. Any of those is a reject. The page's own language about character consistency is the standard, not a compliment. If the identity does not hold, the clip cannot go to the editor, and another adjective in the prompt is the wrong fix.

Text inside the frame is the other common failure. A label, a lower-third, or a lyric line that becomes unreadable is a failed take even when the lighting looks expensive. The panel has a Generate Audio control. Turn it on only when the spot needs sound from the model. A silent product loop with audio enabled is a different job, and it can waste the review time the desk thought it was spending on picture.

Public Visibility is on the same panel. A trial prompt that includes an unreleased product should not be treated as a private default just because the team meant it that way. Check the control before generate. A leaked preview is a business failure, not a model failure, and it still costs the afternoon.

A Desk Check After The Preview

Compare the preview with the written brief, not with the mood of the room. Use a short list and keep it boring.

• The route matches the input: text, a still, or a reference.
• Fast, Quality, or Lite is named in the note.
• Duration and resolution match the placement, and the ratio is not an accident of the loaded page.
• The subject does not drift, and any required words stay readable.
• The payload identifier matches the card you actually selected.

If one line fails, the clip stays in the studio. Sending it downstream so a developer can "try a tweak in code" doubles the time. The rework belongs in the prompt, the reference, or the option, which are the controls the page actually offers. The Upgrade to generate button on the open panel is a gate, not a quality score. Clearing it does not mean the shot passed the list above.

Before You Wire The Live Endpoint

Seedance fits a desk that can spare one preview cycle before an integration ticket. The studio, the four steps, and the split between the 1.5 throughput line and the 2.0 reference line are enough to decide whether the shot is even a candidate. It is a poor fit when the team wants a finished campaign grade with no one assigned to reject a drifted face, or when the only success test is that the request returned a file.

Run the prompt, the ratio, and the option on the panel. Compare once. If the preview is wrong, fix it there. Wire the endpoint after that check, not before.