Manus Credits: What They Buy and How to Spend Fewer

The first thing that confuses new Manus users is that a credit is not a message. You can send one sentence and spend hundreds of credits, or hold a long conversation and spend none. Once you understand what is actually being metered, the numbers stop feeling random.

This guide covers what credits pay for, the five different kinds Manus issues and the order it burns them in, which ones expire, what a real task tends to cost, and the specific habits Manus itself recommends for spending fewer. Everything is drawn from their documentation and help centre, linked at the end.

What do Manus credits actually pay for?

Three resources, bundled into one number. Manus's help centre lists them explicitly: the model tokens used for task planning, decision making and output generation, the virtual machines that provide the cloud environment for file operations, browser automation and code execution, and third party APIs used to reach integrated external services.

That bundling is why a credit does not map neatly to a word count. A task that reads twenty web pages is paying for browser time on a cloud machine as well as for tokens. A task that queries a paid data source is paying that provider too. Manus describes credits simply as its unit of measurement for usage, with longer and more complex tasks costing more.

When are credits not consumed?

When nothing is running. Manus's help centre states that credits are only consumed during active task processing, and that completed tasks and the storage or deployment of their outputs do not consume any credits. Your finished report does not cost you anything to keep.

Chat is the other free surface. Manus's help article on the desktop app is direct about it: if you are using chat mode to ask questions or converse without triggering an agent workflow, no credits are consumed. The same article notes the desktop app shares one credit pool with your web account rather than having its own, and that credit usage depends on the resources consumed rather than on where the processing happens.

What are the different kinds of credits?

Manus issues five, and they are not interchangeable. The help centre names event credits, daily credits, monthly credits, add-on credits and free credits, and states that they are consumed in exactly that order.

That ordering is genuinely useful to know. Because the shortest lived credits are spent first and the permanent ones last, Manus is drawing down the balance you were going to lose anyway before it touches the balance you keep. You do not have to manage that yourself.

The add-on row deserves the caveat. Manus's plans documentation says purchased add-on credits never expire and can be used at any time, while the help centre article on consumption rules describes add-on credits as rolling over while a paid subscription is active but becoming inactive if you cancel. Those are not the same statement, so if you are considering buying a top up before cancelling a plan, ask their support directly rather than trusting either page.

Do unused credits roll over?

Plan credits do not. Manus's help centre states plainly that unused credits do not roll over to the next cycle, and its plans documentation repeats that plan credits reset monthly. If your month is quiet, that allowance is gone.

This is the opposite of how most people intuitively budget, and it changes how you should sequence work. If you have a backlog of research tasks and a monthly allowance you are not using, the cheapest month to run them is the month you already paid for, not next month.

There is one refund path worth knowing about. Manus's help centre states that it provides a full refund of consumed credits for tasks that fail due to technical issues on their end. That does not cover a task that ran fine but produced something you did not want, which is a different problem and the one the rest of this guide is about.

What does a typical task cost?

Manus's own credits page gives two reference points: around 200 credits for a fifteen minute data analysis task, and around 900 credits for an eighty minute app development project. Roughly speaking, minutes of agent time are the thing you are buying.

Independent estimates fill in the middle, and they should be read as estimates rather than rates. An analysis published by No Code MBA, updated in June 2026, put simple queries at 10 to 50 credits, web research at 100 to 300, deep research across multiple sources at 500 to 900, code generation and execution at 200 to 500, and larger parallel research jobs higher still. A Plus AI reviewer separately observed roughly 200 credits for a ten slide presentation and noted the figure is not officially published.

Two honest caveats about all of those numbers. They come from other people's accounts on other people's tasks, and the same nominal task can vary widely depending on how many pages the agent decides to read. Run one representative task, note your balance before and after, and use that as your planning number instead.

How do you make the same work cost less?

Stop paying for repeated attempts. Manus's own guidance on optimising credit usage identifies three cost drivers, and every one of them is about doing the same thing twice: separate attempts at related questions, unclear instructions that force extra tries, and asking variations of a question you already asked.

Spending fewer credits on the same result

1. Group related questions into one task — Manus recommends grouping related or similar questions together rather than firing them separately, because each separate attempt consumes credits of its own. One task with five questions costs less than five tasks with one.
2. State the expected outcome once, clearly — Their guidance asks for clear, concise and direct instructions in one consolidated step instead of several vague ones. A vague brief is not cheaper, it is more expensive, because the agent explores more to work out what you meant.
3. Read the answer before you rephrase — Manus explicitly advises reviewing what came back carefully before resubmitting a similar query, and refining based on the response rather than rewording the same request repeatedly.
4. Settle the plan in chat first — Conversation that does not trigger an agent workflow does not consume credits, so agree the scope and the deliverable before you start the run.
5. Pilot at small scale — Ask for five results before you ask for fifty. If the shape is wrong you have paid a tenth of the price to find out, which is the single largest saving available to you.
6. Watch the first minutes of a long run — One independent analysis flagged that there are no real time usage alerts, so an autonomous run can browse more pages than you expected. Catching a wrong direction early is what keeps that from mattering.

Read that list again and notice what it is really describing. Almost all of it is the cost of an agent that starts every task with no memory of the last one, so you re-explain your context, it re-explores, and you pay for the exploration again.

That specific cost is the one we designed out at Sistava. You hire an AI Employee, it keeps your context, your files and your tools between tasks, and it asks you a question when it is unsure rather than spending twenty minutes guessing. The second time you ask for something, it is not starting from zero.

Where do you check what you have left?

In your Manus dashboard. Their plans documentation states that the dashboard provides usage tracking and gives estimates before tasks begin, which is the closest thing to a budget check the product currently offers.

As for topping up, the documented routes are straightforward: free users can upgrade, paid subscribers can move to a higher tier, add-on credits can be purchased at any time during a subscription, and event participation grants event credits. We are not quoting plan prices here because they change, so read manus.im/pricing for the current figures.

Sources

• Manus Help Center, What are the rules for credits consumption and how can I obtain them
• Manus, What are credits
• Manus Help Center, Understanding credit consumption in the Manus desktop app
• Manus Help Center, How to optimize my credit usage
• Manus documentation, Plans and Pricing
• No Code MBA, Manus AI pricing analysis, updated June 2026
• Plus AI, Manus AI slide generator review

The short version: credits buy agent minutes, not messages. Plan the task where it is free, run it once with a clear brief, and check your balance before and after so you are budgeting with your own numbers instead of someone else's estimates.