Quick answer
Pollo AI does not have one durable “price per one-minute video.” The current cost depends on:
- whether you use the Pollo web app or the separate Pollo API;
- the selected tool and model;
- clip duration, output count, and resolution;
- how many attempts produce an accepted clip;
- extensions, upscales, audio, and post-production;
- the live plan, promotion, tax, and checkout terms for your account.
For a purchase decision, run one representative scene and calculate cost per accepted second. Then project that observed workflow to 60 seconds.
This guide was checked against Pollo’s official pricing surfaces on July 31, 2026. Verify the live account and checkout before buying because plan cards, promotions, model access, and credit draws can change.
First choose the right pricing surface
Pollo exposes creator and developer products with different billing logic:
| Surface | Use it when | Budget from |
|---|---|---|
| Pollo AI web app | A person creates inside Pollo’s interface | Current plan, included subscription credits, add-ons, and generation-panel credit draw |
| Pollo API | A product or backend sends programmatic jobs | API top-up balance, model-specific usage, logs, retries, and integration operations |
Do not mix the advertised volume from an API top-up with the credits included in a creator subscription.
Pollo’s API documentation currently says top-ups start at $80, with estimated usage of about 800 images or 500 videos. That estimate is not a fixed per-video rate: the same documentation says actual volume depends on the model and generation settings.
What current Pollo web credits mean
Pollo’s pricing FAQ says credit deductions depend on:
- the selected tool;
- the selected model;
- video duration;
- output quantity;
- image or video resolution.
That makes a headline credit count incomplete. Before comparing plans, record the credit draw shown for the exact model, duration, resolution, output count, and workflow you intend to use.
Subscription credits and add-on credits differ
Pollo’s current official FAQ states:
- unused subscription credits do not carry over to the next billing cycle;
- Pro users can purchase extra credits through the plan controls;
- Pro Yearly subscribers can buy one-time add-on packs;
- add-on credits do not expire, remain usable after the subscription ends, and are not refundable.
Recheck the live policy for the account and region before purchase. A subscription renewal, one-time add-on, and API top-up should remain separate lines in a cost model.
Is the free path enough?
Pollo’s pricing FAQ refers to Free users, but a plan label alone does not establish the current allowance or which models and tools are available.
Use free access to answer four fit questions:
- Does the selected model understand your shot brief?
- How many attempts produce one acceptable clip?
- Are the live duration, resolution, queue, export, and watermark boundaries acceptable?
- Can the account’s current usage terms support the intended publication?
Upgrade only after the test identifies which paid capability or additional volume you actually need.
Calculate a one-minute video from accepted clips
A one-minute edit is usually assembled from multiple generated clips. The safe calculation starts with the final edit, not a marketing estimate.
Step 1: define the edit
Create a shot list whose accepted durations add up to 60 seconds. If a scene needs four seconds in the edit, do not budget a ten-second generation without recording the unused output.
Step 2: test one representative shot
Record:
| Input | Example record |
|---|---|
| Model and mode | Exact label shown in Pollo |
| Generation path | Text-to-video, image-to-video, reference-to-video, or another tool |
| Requested output | Duration, resolution, aspect ratio, quantity, and audio |
| Credit draw | Live credits shown before submission |
| Attempts | All billed submissions, including rejected drafts |
| Accepted duration | Seconds that survive the final edit |
| Extra work | Extensions, upscales, audio, exports, and external editing |
Step 3: calculate observed unit cost
Use:
Credits per accepted second = all credits used for the test ÷ accepted seconds
Then:
Projected generation credits for one minute = credits per accepted second × 60
If a plan or API balance has a current dollar value, convert only after confirming the correct credit surface. Add editing time and external tool costs separately.
Step 4: model uncertainty
Use three retry cases:
- Low: the brief is stable and most clips pass.
- Expected: the representative test’s observed acceptance rate.
- High: difficult motion, continuity, hands, text, audio, or client revisions increase retries.
This produces a useful range without inventing a universal one-minute price.
Web plan or API top-up?
Choose a web plan when
- creation happens manually in Pollo;
- a creator needs a broad multi-model workspace;
- subscription features and included credits fit the observed monthly workload;
- billing-cycle credit expiry is manageable.
Choose API top-ups when
- generation must be triggered by your own application;
- job logs, webhooks, keys, and repeatable task tracking matter;
- model-specific usage must be attributed to customers or workflows;
- the team can operate retries, moderation, storage, and delivery.
The API top-up page is not evidence that every Pollo web-app feature, promotion, or model entitlement carries into the API.
Compare plans by accepted output
For each candidate plan, ask:
- Does it expose the exact model and tool used in the pilot?
- What does the live panel charge for the required duration, resolution, quantity, and audio?
- How many subscription credits expire unused?
- Are add-on credits needed for peak months?
- What are the checkout, renewal, cancellation, and refund terms?
- Do watermark, export, input, output, and commercial-use rules fit the project?
- What is the total cost per clip that passes review?
A plan with more credits is not automatically better value. A workflow that needs fewer rejected generations, less editing, or fewer external subscriptions may have the lower accepted-output cost.
Reduce waste without promising savings
Use a controlled production sequence:
- Approve the script and shot list before generating.
- Test composition and motion on one representative scene.
- Fix the prompt or reference before increasing duration or resolution.
- Generate only the seconds the edit needs.
- Escalate to more expensive settings after the direction passes review.
- Track rejected attempts and unused generated seconds.
- Recalculate before renewing or buying add-ons.
Image-to-video can provide more composition control when the team owns or is authorized to use the reference, but it does not guarantee fewer attempts. Measure it against text-to-video on the same acceptance criteria.
Related Flowith guides
Use the Pollo AI vs. Kling workflow comparison to design a same-brief test, the Kling pricing guide to normalize a second credit system, or the AI video workspace to explore a video workflow.
Pollo model availability does not establish Flowith availability. Verify the current Flowith model selector and billing surface independently.
Frequently asked questions
Is Pollo AI free?
Pollo’s current pricing FAQ refers to Free users, but the usable allowance, models, tools, resolution, and promotions can change. Treat free access as an evaluation path and verify the live account before planning production.
How does Pollo AI deduct credits?
Pollo says web-app credit use depends on the tool and model selected, video duration, output quantity, and image or video resolution. Check the live generation panel before each representative test.
How much does a one-minute Pollo AI video cost?
There is no single source-safe price. Divide 60 seconds into the clip lengths supported by the selected model, multiply by attempts per accepted clip and the live credit draw, then add upscales, extensions, audio, and editing. Map the result to either the current web plan or separate API balance.
Do Pollo AI credits roll over?
Pollo’s pricing FAQ says unused subscription credits do not carry into the next billing cycle. It separately says add-on credits do not expire and remain usable after a subscription ends, but are not refundable.
Are Pollo web-plan credits and API credits the same?
Do not treat them as the same balance or pricing surface. Web plans cover work inside Pollo’s creator product; Pollo API uses developer top-ups and model-specific programmatic usage.