PixVerse V6: What's New, What It's Good For, and What It Costs

Every "PixVerse V6" search result tells you the model is better, but almost none of them tell you what actually changed. This guide pulls it together from PixVerse's official release notes, capability matrix, and pricing docs: what V6 adds over V5.6, what it's good for, what a clip costs, and, at the end, how to use it through the API if you're making clips in bulk.

The short answer: what's new in PixVerse V6

PixVerse V6 is the AI video model PixVerse released on March 29, 2026. It makes clips of up to 15 seconds at up to 1080p from a text prompt or an image, and its big change is that one prompt can now produce a multi-shot short with synchronized sound, no separate editing or audio step.

Beyond that, V6 is better at camera moves, at keeping a character's emotion and expression steady across shots, at objects that touch and collide realistically, and at text inside the frame in English, Chinese, and other languages. A later update added reference videos: you can give V6 a clip and have it copy the motion, swap the subject, or recreate the scene.

You can try V6 in the PixVerse web or mobile app; the free plan gives daily credits with a watermark. Billing also changed: V6 is charged per second of video rather than per clip, which makes short 5-second clips a little more expensive than on V5.6 and longer ones cheaper (the numbers are below).

What Changed in PixVerse V6: The Version Timeline

PixVerse has shipped a new model roughly every few months. The official changelog documents the sequence: V5 (August 29, 2025), V5.5 (December 2, 2025), V5.6 (January 26, 2026), V6 (March 29, 2026), and C1 (April 7, 2026). V6 was the headline release; C1 is a separate model aimed at film production, and the two are not interchangeable (more on that below).

Per the official launch announcement, V6's headline improvements are:

• Camera work: tracking, perspective shifts, and environmental reveals render with greater accuracy and fewer artifacts than previous releases.
• Character performance: emotion holds across frames more reliably; facial expressions and body language keep continuity through scene changes.
• Physical interaction realism: collisions, movement, and spatial relationships between objects behave more consistently.
• Multilingual in-frame text: text rendered inside frames is supported with accurate placement across English, Chinese, and other languages.
• Multi-shot generation with native audio: a single prompt can produce a multi-shot short with synchronized audio, without a separate audio pass. The launch post is explicit that what previously needed multiple tools and production stages (editing, audio) now completes in one generation.

The capability matrix confirms what the launch post implies: V6 supports text-to-video, image-to-video, first/last-frame transition, reference-to-video (Fusion), and video extension. C1 supports everything except video extension. Legacy models "vary" per capability. Both V6 and C1 cap at 15 seconds and 1080p.

A later changelog entry added the biggest change since launch: V6 reference-to-video can now take reference videos, not just images. What that lets you do is covered in the next section.

What PixVerse V6 is good for

Read the feature list as a set of jobs V6 now handles in one generation:

• Short social clips with sound. Multi-shot output with native audio means a short of up to 15 seconds, with several cuts and a soundtrack, comes out of one prompt, instead of three clips stitched together and scored afterwards.
• Camera-led shots. Tracking shots, reveals, and perspective changes are where V6 improved most, so product fly-arounds, travel B-roll, and establishing shots are a good fit.
• Character scenes. Because expression and body language hold across scene changes, a character who looks worried in shot one still looks worried in shot three.
• Clips with words in them. Signs, titles, and captions rendered inside the frame, including Chinese and other non-English text.
• Remixing a clip you already have. With reference videos, PixVerse's guide says V6 "can understand and reference subjects, actions, scenes, camera movements, and visual styles from input videos," so you can swap the subject, recreate a video in a new setting, or copy a motion from a prompt. You can use up to two reference videos, 15 seconds in total, and the output matches the length of the longest one. Reference videos double the credit cost.

Where V6 is not the pick: if you need clips longer than 15 seconds or above 1080p, V6 won't get you there. If you're working on film-style production and don't need video extension, PixVerse positions C1 for that.

What PixVerse V6 Costs: Per-Second Credits and the V5.6 Comparison

The most consequential change for anyone paying for V6 is billing. V6 is billed per second; V5.6 and older models are billed per fixed clip duration. The official pricing page states the anchor: $1 = 5 videos (V6, 720p, 5s, no audio, with Starter pack).

V6 per-second credit consumption (official pricing table), credits per second:

V5.6, by contrast, charges a flat per-clip amount. Official rows (no audio / with audio):

Run the same clip through both models and the winner depends on duration. A 5-second 1080p clip costs 90 V6 credits (5s × 18) versus 75 V5.6 credits, so V5.6 is cheaper. An 8-second 1080p clip costs 144 V6 credits (8s × 18) versus 150 V5.6 credits, so V6 is cheaper. Per-second billing rewards longer clips; fixed-duration billing rewards short ones. If you mostly generate 5-second clips, the change is a price increase; if you generate 8 to 15-second clips, it's roughly a wash or a saving.

When you add video references, V6 Fusion consumption doubles (official Fusion guide): 1080p goes from 18 to 36 credits per second (no audio) or 23 to 46 (with audio).

One billing detail worth knowing before you estimate a budget: PixVerse's own pricing page qualifies the $1 = 5-videos anchor as applying "with Starter pack". The same page lists different per-second rates for C1 and separate fixed-duration tables for legacy models, so the effective per-video cost shifts depending on which model, pack, and clip length you use. If you're projecting cost for a high-volume pipeline, pull the official pricing page and model your actual mix rather than assuming the anchor rate holds everywhere. These tables are PixVerse Platform credits; the app's monthly plans are billed separately, and our PixVerse pricing guide covers both.

These are PixVerse Platform credits, not Modellix US dollars. The two pricing systems are separate and we are not converting between them here. Mentioning the Modellix price next to them is a convenience, not a claim that either route is cheaper; per-clip cost depends on your credit pack, clip length, and quality.

Using V6 through the API: endpoints, video references, and common mistakes

If you're generating clips in bulk, for a shop, a channel, or an app, the API replaces clicking with code. V6 exposes five generation endpoints, all documented with "model": "v6" in the official V6 documentation:

All five share a common parameter set: prompt (≤ 5,000 characters), duration (1 to 15 seconds), quality (360p / 540p / 720p / 1080p), generate_audio_switch, and seed. Text-to-video and Fusion additionally accept aspect_ratio (16:9, 4:3, 1:1, 3:4, 9:16, 2:3, 3:2, 21:9). Multi-clip generation (generate_multi_clip_switch) is available on text-to-video and image-to-video only. The launch post also notes that V6 is reachable through PixVerse's CLI, which it says works with coding agents including Claude Code, Codex, Cursor, and OpenClaw.

The API uses an asynchronous submit-poll-retrieve lifecycle. Before you can call it, you need an API key: per the official quick start, create one in the API Keys section of the PixVerse platform console, and top up credits on the billing page. Reference media must be uploaded through the media endpoint; raw URLs are accepted by the upload endpoint, but the Fusion body itself only takes media_id values. A minimal Python skeleton for a V6 Fusion call with a video reference, mirroring the official integration guide:

import requests, time

BASE = "https://app-api.pixverse.ai/openapi/v2"
HEADERS = {
    "API-KEY": "YOUR_API_KEY",
    "Ai-trace-id": "your-unique-trace-id",   # unique per request
    "Content-Type": "application/json",
}

# 1. Upload the reference video -> media_id
with open("reference.mp4", "rb") as f:
    up = requests.post(f"{BASE}/media/upload",
                       headers={"API-KEY": HEADERS["API-KEY"]},
                       files={"file": f})
media_id = up.json()["Resp"]["media_id"]

# 2. Generate with the video reference
body = {
    "model": "v6",
    "reference_mode": "omni",
    "video_references": [{"media_id": media_id}],
    "prompt": "@clip plays in a neon-lit city at night",
    "duration": 0,                # required when using video references
    "quality": "720p",
    "aspect_ratio": "auto",       # omni mode supports "auto"
}
gen = requests.post(f"{BASE}/video/fusion/generate",
                    headers=HEADERS, json=body).json()
video_id = gen["Resp"]["video_id"]

# 3. Poll until status flips from 5 (in progress) to 1 (success)
while True:
    st = requests.get(f"{BASE}/video/status",
                      headers=HEADERS, params={"video_id": video_id}).json()
    if st["Resp"]["status"] == 1:      # 1 = success; 5 = in progress
        print(st["Resp"]["url"])       # final video URL
        break
    time.sleep(5)

Per the official Fusion integration guide and Fusion API reference, the status endpoint returns 1 when generation is complete and 5 while it is in progress; poll until it returns 1. This skeleton mirrors the guide's request shape; run it against your own API key and confirm the current endpoint domain on the docs page before production use.

Figure: the V6 Fusion API lifecycle: upload, generate with video_references, poll status 5→1. Diagram generated for this guide.

The video-reference parameters that matter

The constraints are exact, and violating any of them returns an error (or silently changes behavior):

The duration: 0 rule is the one that surprises people: with a video reference, you do not pick the output length. If you need a fixed output length, extend or trim the reference video before uploading, or generate without video_references and use duration normally.

Common mistakes and how to fix them

Setting duration to a non-zero value while using video references. The Fusion guide requires duration: 0 when video_references is present. Set it to 0 and let the output align to the reference.

Passing more than two reference videos. The cap is two per request, and all references combined must stay under 15 seconds. Split long source footage into segments and run separate generations.

Using reference_mode: "omni" with a legacy model. Video references are supported only by V6, per the integration guide. If your request names an older model, the reference parameters are not supported and the request will not behave as intended.

Passing a raw video URL into the Fusion body. The video_references array takes media_id values from the media upload endpoint. Also note that multi-clip generation isn't available on Fusion, so a video-reference request returns a single clip.

Forgetting the unique Ai-trace-id header. The PixVerse API expects a unique trace ID per request; reusing one across requests is a documented source of failures.

Misreading the poll status. Status 5 means in progress, 1 means success. Polling once and treating a 5 as done is the most common integration bug.

Treating official credits as Modellix USD. PixVerse Platform credits and Modellix per-second USD pricing are two separate systems. Compare them on cost-per-output for your actual clip length, not on the raw numbers.

Using V6 on Modellix

If you'd rather not track PixVerse credit packs at all, Modellix offers V6 and C1 reference-to-video over a unified REST API with per-second USD pricing: V6 R2V at $0.0575 to $0.2645/sec and C1 R2V at $0.0690 to $0.2760/sec. The same key also reaches other video models, so you can run one prompt across several and compare. Our PixVerse API guide covers the general workflow.

Frequently Asked Questions About PixVerse V6

What is the difference between PixVerse V6 and V5.6? V6 (released March 29, 2026) adds multi-shot generation with native audio, better camera work and character performance, multilingual in-frame text, video extension, and per-second credit billing. V5.6 uses fixed-duration billing (e.g., 75 credits for a 5-second 1080p clip). See the official changelog for the full sequence.

How much does PixVerse V6 cost? Officially, $1 = 5 videos at 720p, 5 seconds, no audio, with the Starter pack. Per-second credits run 5 to 23 (no audio / with audio, 360p to 1080p), and double when video references are used. On Modellix, V6 R2V is priced per second in USD ($0.0575 to $0.2645/sec); see the official pricing page for PixVerse's credit packs.

What is the maximum video length for V6? 15 seconds at up to 1080p, across all five generation endpoints. When using video references, the output length automatically matches the longest reference video instead of a duration you set.

PixVerse V6 vs C1: which should I use? Both are per-second-billed models supporting text-to-video, image-to-video, transition, and Fusion. C1 does not support video extension, and it was positioned for film-production workflows. If you need extension or the latest consumer-quality output, V6 is the safer default; the capability matrix has the full comparison.

Is PixVerse a Chinese company? It has roots in China and an international base in Singapore. PixVerse is built by AIsphere (爱诗科技), founded in Beijing in 2023 by former Microsoft Research Asia and ByteDance researcher Wang Changhu; its later launch announcements are datelined Singapore, where it runs its global operations, and Alibaba led one of its funding rounds (SCMP). It is not a Modellix entity; the two are separate companies.

Can I use PixVerse V6 through Modellix? Yes. Modellix carries the V6 R2V (reference-to-video) model at per-second USD pricing, plus C1 R2V and lipsync. Modellix does not resell PixVerse's Growth Studio, Image Avatar, or custom voice cloning; those are PixVerse platform products, not API models in the Modellix catalog.

Does PixVerse V6 generate audio? Yes. V6 can produce synchronized audio natively in the same generation (generate_audio_switch in the API), and video references work with audio enabled. Note the boundary on the Modellix side: audio is accepted as input (e.g., for lipsync), but Modellix does not offer audio generation models.

Where can I see real V6 output tests? PixVerse published a hands-on review with a test methodology, benchmark observations, and a V5.6 comparison: PixVerse V6 Review. The official launch post is also worth reading for the product-level context.