Vidu S2 API Pricing: Costs, Billing Categories, and Integration

Vidu S2 has separate real-time Avatar, component Avatar, offline Avatar, and Editing billing contexts, so a rate copied from one documentation page should not be transferred to another without checking the endpoint.

Vidu S2 pricing and API access at a glance

The official Vidu API pricing page says one credit costs $0.005, before applicable sales tax. Its S2 table lists four usage categories:

At those listed rates, a 60-second session would consume approximately 90 credits ($0.45) for real-time Avatar, or 60 credits ($0.30) for the other three categories. These are direct calculations from Vidu’s published rates, not a quote for an enterprise plan.

Vidu also lists the first 10 voice clones as free for S2 real-time Avatar. Additional clones are listed at 899 credits, approximately $4.50 each. The first five concurrent sessions are listed as free; each additional concurrent session is listed at 416,000 credits per month, approximately $2,080. Confirm the exact product scope before relying on those allowances.

What Vidu S2 actually includes

The official Vidu S2 paper, submitted on September 10, 2026, describes S2-Avatar as a real-time interactive digital-character model and S2-Editing as a real-time video-editing model.

S2-Avatar is designed for an image-based character that responds to audio or instructions. The paper reports 720p generation at approximately 25–42 FPS, dynamic reference images that can be updated during generation, and stronger action following such as dancing. S2-Editing targets live-stream changes including style rendering, clothing replacement, character replacement, and background replacement.

These are research-system figures, not a universal production-latency guarantee; the paper provides no standardized end-to-end latency number across hardware and deployments.

The offline-avatar documentation describes an asynchronous image-plus-audio/text workflow with timelines, callbacks, polling, and 540p/720p examples, but its vidu-s1 example does not specify every S2 real-time mode.

Vidu S2 API pricing: the numbers that matter

The safest way to budget Vidu S2 is to keep three variables separate: category, duration, and optional services.

The official pricing page contains multiple billing contexts. The general page uses $0.005 per credit, while the offline-avatar reference describes billing by generated duration in a different API context. Confirm the endpoint and account region before applying any rate.

Credits can be purchased as needed; high-volume buyers should confirm current pricing, access, tax, and concurrency terms with Vidu.

The API workflow you need to build

Vidu’s documented avatar integration is asynchronous. A production integration should be designed around task state rather than assuming the create request returns a finished video.

1. Prepare the assets. The documentation accepts public URLs, Base64 data with a MIME prefix, or platform asset IDs. The character image should contain one person; failed face or body detection can cause task errors.
2. Submit a task. Send the image plus audio or text. An optional timeline can specify actions such as “make a heart gesture” over a defined time range. The create response returns a task ID and an initial state.
3. Poll or receive a callback. The documented states include created, queueing, processing, success, and failed. Vidu recommends polling no more frequently than every two seconds; a 3–5 second starting interval with backoff is safer.
4. Verify callbacks. Callback requests use HMAC-SHA256 according to the documentation. Verify the signature before accepting a success event or downloading an artifact.
5. Persist the result immediately. The example output URLs include X-Amz-Expires=86400; the documentation says video and cover URLs are valid for 24 hours. Copy successful artifacts to storage you control.
6. Use actual consumption for billing records. The query response reports actual credits and duration. The create-task example’s credit field is not the final amount to use for accounting.

This workflow has two easy failure points: treating task acceptance as completed generation, and storing Vidu’s temporary URL as if it were permanent.

Choose the endpoint by workload

Vidu’s official launch post confirms S2 is live, but independent hands-on evidence is still thin. A real-user analysis by @tsukitama_ai marked itself as not personally tested; plan an API pilot rather than assume stable long-running streams at scale.

Vidu S2 API FAQ

Is Vidu S2 officially released?

Yes. Vidu’s official product page and official account announced that Vidu S2 was live, while the paper and API pages describe S2-Avatar and S2-Editing. Public access, regional availability, and account permissions can still vary.

How much does Vidu S2 cost?

The official pricing page lists $0.005 per credit. S2 real-time Avatar is listed at 1.5 credits per second, while Avatar component, Avatar non-real-time, and Editing are each listed at 1 credit per second.

Is Vidu S2 real-time or asynchronous?

Both descriptions exist because they refer to different modes. The launch material emphasizes real-time Avatar and Editing, while the documented offline-avatar API uses asynchronous task creation followed by polling or callbacks.

Does Vidu S2 support webhooks?

The avatar API documentation supports a callback URL and documents HMAC-SHA256 verification. A resilient integration should support both callback handling and a polling fallback.

How long do Vidu result URLs last?

The documented avatar result, cover, and watermarked URLs are temporary and expire after 24 hours. Copy the files to your own storage after a successful task.

Is Vidu S2 open source?

The available product and API material does not establish that the production S2 models and weights are openly released. Treat S2 as an accessed product/API unless Vidu publishes a separate license and weight release.

For a first pilot, cap the spend, record actual credits from completed tasks, verify callback signatures, and copy every successful artifact before its 24-hour URL expires. This will show whether Vidu S2’s documented price and workflow fit your application before you depend on real-time claims at scale.