Manus Pricing: Manus AI Pricing, Credits, Cost per Task and Every Plan

Manus costs $20 a month at the entry level, and there is a permanent Free plan. Above that, the price depends entirely on how many credits you buy each month. The pricing page shows three cards at $20, $40 and $200, but the $40 and $200 cards each have a credit dropdown that changes the price, so the real range for an individual subscription runs from $20 to $20,000 a month.

The $40 tier carries a 7-day free trial, according to Manus's billing help center. Prices are in US dollars everywhere, and Manus notes that sales tax and card fees can push the final charge above the list price.

Two costs sit outside the subscription and catch people later. Websites you publish with Manus WebDev run on a separate pay-as-you-go balance for hosting, database and API usage, and a site on a custom domain goes offline if the subscription lapses. Manus Cloud Computer, a persistent Ubuntu server, is billed on its own at $10, $30 or $50 a month depending on RAM and storage.

This is the table the Manus pricing page does not show on one screen. We selected every option in both dropdowns, on monthly and annual billing, on September 22, 2026.

Three things fall out of it. First, there is no volume discount at all until you pass $200 a month. Everything from 4,000 to 40,000 credits costs exactly $5 per 1,000, so the $40 and $100 options are simply more of the same credits, not a better deal. Second, the discount starts at 63,000 credits and levels off at 17% from 480,000 upward, with one last step to 20% at 5,000,000. Third, annual billing stacks on top: the 5,000,000 credit option billed yearly works out to $3.33 per 1,000 credits, a third below the monthly entry rate.

A common claim in third-party reviews is that Manus charges a flat $0.005 per credit on every tier. That holds only up to 40,000 credits. Above that line the per-credit price drops, and a team spending $2,000 a month is paying about $0.0042 per credit on monthly billing.

Manus publishes three worked examples of real tasks and the credits they used. At the $5 per 1,000 rate that applies to every tier up to $200, they convert like this.

So the $20 tier buys roughly 20 short analyses, 11 simple websites or 4 complex builds a month, and not all three. Treat those as best cases. The examples are single runs that worked, and Manus bills every credit a task uses, including the rounds where you ask it to fix something. Manus refunds credits only for tasks that fail because of a technical problem on its side.

What drives the count, in Manus's words, is three things: model tokens for planning and output, virtual machine time for browsing, files and code, and third-party API calls for data it pulls in. Credits are consumed only while a task is actively running. Finished tasks and stored or deployed outputs use nothing, so there is no reason to delete old work.

The practical budgeting rule: if your work is mostly research and documents, a credit goes further than if it is mostly building and deploying apps, because app work runs longer and touches more tools. Count your expected jobs by type, use the table above, and add a third for retries.

Manus runs four kinds of credits at once, and they are spent in a fixed order: event credits first, then daily refresh credits, then monthly credits, then add-on credits, then free credits.

The daily credits look generous on paper. At 300 a day, a paid account collects about 9,000 Lite credits a month, more than twice the monthly allowance of the $20 tier. But they only run the Lite model, they vanish every midnight UTC, and they cannot be banked for a heavy week. They are useful for quick questions and light tasks, not for the long research and build jobs that are the reason to pay for Manus.

The add-on rule is the one that shapes plan choice. An individual subscriber who runs out cannot buy a small top-up unless they are already on the highest tier; the route is to move up a tier. That is why the smaller tier is the safer first purchase: moving up is immediate, while monthly credits you did not use are simply gone at the end of the cycle.

Cancellation follows the same logic. When a subscription ends, unused monthly credits reset to zero and are not reinstated if you come back. On the $40 tier's 7-day trial, canceling before the first charge costs nothing, but Manus does not refund a charge once it has been taken; it only stops the next renewal.

Manus Team costs $20 per seat per month, or $200 per seat per year, which is $16.67 a month. Each billed seat adds 4,000 credits to one shared pool, so heavy users draw on what light users leave. Owners and admins can buy add-on credits from Team settings and turn on auto-purchase so work does not stop when the pool runs low. Seats can be added at any time, and the bill adjusts at the next billing cycle.

Two details change the math. Guest users are free and unlimited: they can view, download and comment on everything the team produces but cannot start a task or prompt Manus, so reviewers, clients and managers do not need a paid seat. And single sign-on has its own price. Manus charges a flat $150 plus tax for the SSO subscription when a team has fewer than 30 seats and waives it at 30 seats or more. Manus's help page describes an SSO billing cycle but does not state its length; the table below assumes it is monthly.

The 29 and 30 seat rows are the point. If SSO is a requirement, a team of 23 to 29 people pays less by buying seats up to 30 than by paying the SSO fee, because each extra seat costs $20 and the fee is $150. At 23 seats, going to 30 costs $140 more in seats and saves the $150 fee. Those extra seats are not wasted either: each one adds 4,000 credits to the pool.

One more comparison worth making before you buy Team. A Team seat and an entry Pro subscription cost the same $20 and carry the same 4,000 credits. What Team adds is the shared pool, central billing, the admin dashboard, audit logs and SSO. A single power user gets the same credits per dollar on Pro, and gets the volume discount above 40,000 credits, which Team seat pricing does not show.

Manus is usually compared with the general AI assistants that now run agents too. On the seat price they look the same. The difference is what the seat includes and how overage is billed.

The honest read is that none of these is cheaper in general. They are priced for different work. ChatGPT, Claude and Copilot are assistants first, and their seats cover heavy daily chat without a per-message meter. Manus is an agent first: every task is metered, and in exchange it runs long, multi-step jobs in its own cloud browser and virtual machine, builds and deploys websites and apps, and runs up to 20 tasks in parallel. If most of your use is conversation, a Manus seat is poor value. If most of it is handing off whole jobs, Manus prices that work more transparently than an assistant with an unpublished usage cap.

For deeper vendor-by-vendor numbers, see our pages on ChatGPT Enterprise and Business pricing, Claude Enterprise and Team pricing and Amazon Quick pricing, or the side by side of thirteen vendors in AI agent platforms compared.