PixVerse credits have no single price, because PixVerse has two wallets: a consumer subscription behind the website and the app, and a developer wallet on the API platform. The rate card below is published, complete, and belongs to the second wallet.
Two wallets, and why your number belongs to one of them
The API platform’s subscription guide opens with warnings instead of instructions: API memberships are separate from PixVerse Web (app.pixverse.ai) Membership, and API credits cannot be used with the PixVerse Web. Same login, different money. A consumer account can sign in to the platform directly, and that is where the sharing stops.
PixVerse’s own comparison writing repeats the split, saying a web subscription and an API project should be evaluated as different products. Nine credits per second means nothing until you say whose nine credits. Everything numeric here is API-ledger; the PixVerse hub holds the model line.
The published per-second rate card
Generation bills per second: the standard column reads 1s, under the heading Calculated per second.
| Model and quality | No audio | With audio |
|---|---|---|
| V6 360p | 5 | 7 |
| V6 540p | 7 | 9 |
| V6 720p | 9 | 12 |
| V6 1080p | 18 | 23 |
| C1 360p | 6 | 8 |
| C1 540p | 8 | 10 |
| C1 720p | 10 | 13 |
| C1 1080p | 19 | 24 |
One input multiplies all of it: a V6 request carrying video_references, the path also called Fusion, is published at double, from 360p 10 or 14 up to 1080p 36 or 46. C1 has no reference multiplier and sits one credit per second above V6 without audio.
Two whole-clip totals are also printed: a 5-second 720p C1 clip costs 50 credits without audio or 65 credits with audio, and A 15-second 1080p C1 clip costs 285 credits without audio or 360 credits with audio. No 4K row exists, because the capability matrix caps both models at Max resolution 1080p. The cheapest and dearest V6 settings are five and forty-six credits per second — roughly nine times the same prompt.
Not every capability is billed per second
Most capabilities bill per second of video, one bills per request, and the legacy models bill per clip.
| Capability | Billing rule | Published figure |
|---|---|---|
| Sound effects | +2 Credits per 1 second | 5s → 10, 10s → 20 |
| Restyle | per second | 10 credits |
| Upscale | per second | 5 credits |
| Lip sync | per second of audio, or per 15 UTF-8 bytes | 4 credits |
| Avatar | per second, by resolution | 5 / 10 / 15 / 20 |
| Swap mask selection | per request | 2 credits |
| Multi-transition | tiered by duration | 23 at one second, 270 at thirty |
Versions 5.5 and 5.6 are priced per clip by duration instead, and on versions 4.5, 4 and 3.5 the page adds that When motion_mode is set to fast, credit consumption is doubled (×2). So the credit count depends on five things: model, resolution, duration, audio switch, capability.
The plan prices PixVerse does publish
The API ledger is not secret. Its pricing page lists three memberships, each with a monthly grant and a reference video count:
| Membership | Price | Monthly credits | Videos generated |
|---|---|---|---|
| Essential | $100 | 15,000 | 333 |
| Scale | $1,500 | 239,230 | 5,316 |
| Business | $6,000 | 1,069,500 | 23,766 |
The footnote makes the table comparable: Calculated based on V3.5 Turbo / 540P 5s video. Credits are also sold outright, from $10 for 1,000 to $5,000 for 500,000. The headline conversion is $1 = 5 videos (v6, 720p, 5s, no audio, with Starter pack), and Starter pack is not among the membership names, which the rate-limit page lists as Free, Essential, Scale and Business. PixVerse has not explained that mismatch. Two more edges: Upgrading/Downgrading Your Plan is marked Not supporting yet, and custom plans run through api_business@pixverse.ai. Read the PixVerse API guide before pricing a batch.
A worked example: one prompt, two price tags
PixVerse’s own review page publishes test prompts beside a description of what came back, so credits can attach to something concrete.
Example one: the vendor’s test prompt at 720p
Prompt: A paper airplane speeds through a grand library. Pages fly around it. It enters a glowing cosmic portal.
Input: a still frame of a paper airplane inside a grand old library
Model: c1
quality: 720pThe vendor describes the output as holding the forward rush cleanly as the plane cut through the aisle, loose pages spinning around it while the background stayed readable despite the speed, with the portal transition smooth and No obvious flickering. C1 at 720p costs 10 credits per second without audio, 13 with, and the published 5-second example for that row is 50 or 65 credits.
Example two: the same clip after you edit it
Same clip, then two add-ons:
sound_effect: on
restyle: onEditing is its own line item. Sound effects are published as 5s → 10 Credits at two credits per second; Restyle is 10 credits per second and Upscale 5, so a ten-second clip that gets restyled and upscaled carries 100 and 50 credits on top of the render — our arithmetic on published rates, not a total PixVerse prints.
Where to see what a run actually cost
Two wallets means two balances, and the API returns both: credit_monthly for membership credits that reset monthly, and credit_package for credits bought in packages.
Refunds are partial rather than automatic. Generation failures refund credits, failed moderation refunds credits, and a job running past two hours refunds credits, but a job past ten minutes only releases the concurrency slot — the docs say that case does not refund credits. Reuse an Ai-trace-id and You won't get a new video generated, costing time instead of money. Concurrency runs from Free at three requests to Business at twenty-five.
What PixVerse has not published about credits
Third-party pages fill these gaps confidently, so they are worth naming. The web subscription’s tier prices, its monthly grant and its free daily allowance are not on any page we could open; the vendor says only that the daily figure varies by account, region and product route. Nothing states that the web wallet shares the API rate card, only that the two are separate.
Frequently asked questions
How many credits does a PixVerse video use? Five to forty-six per second for V6 and six to twenty-four for C1, on the published API card. The web wallet’s rate card is not published.
What is the PixVerse V6 1080p rate? Eighteen credits per second without audio, twenty-three with. Add video_references and that row becomes thirty-six and forty-six.
Is there a cheaper way to test one prompt? Yes: refine at 540p or 720p, then move the best candidate to 1080p. Editing bills separately, so a re-render costs less than a re-edit. The PixVerse walkthrough covers those settings.
Can I spend one wallet on the other? No. API credits cannot be used with the PixVerse Web, which is why nothing here is quoted as a web-app price.
Decide which ledger is paying before you decide which clip to render.