You've seen Claude Code go by — Anthropic's development assistant that works right inside your terminal — and you're asking the only question that matters before you start: how much is this going to cost me every month? The answer fits in one sentence: anywhere from $0 to several hundred dollars, depending on the billing mode you pick and how you use it. There are two modes, a fixed-price monthly subscription and an API billed per token consumed, and they're aimed at completely different people. A beginner coding two hours in the evening and a studio running agents all day long don't pay the same amount, and they don't pay the same way.
So let's put the numbers on the table: the sample bills for each kind of usage, and the concrete settings that bring the total down without hurting the quality of what you get back. By the end you'll know which mode to pick and what budget to expect.
What You're Actually Paying For When You Use Claude Code
You never pay for the Claude Code software itself: it's free to install. What you pay for is access to the AI model doing the work behind it.
This is the part everyone misses at the start. Claude Code is a command-line program you install on your computer in about a minute. Installing it costs nothing. But every time it reads a file, thinks, or writes code, it sends a request to Anthropic's servers — and that request is what gets billed.
Billing happens in tokens. A token is a chunk of a word: roughly 4 characters, or about 750 words per 1,000 tokens. You're charged for input tokens (everything Claude reads: your request, your files, the conversation history) and output tokens (everything it writes: the code, the explanations). Output always costs more than input, usually about 5 times more.
Worth remembering: a 300-line code file is roughly 4,000 tokens. If Claude Code reads ten files to understand your project before answering, it has already burned through 40,000 input tokens before writing a single line. That's exactly where bills get out of hand — and it's also exactly where you can cut them in half.
There are three ways to pay for that access. Here they are, in the order I'd suggest considering them when you're starting out.
Method 1: Learn First, Burn Tokens Later
The cheapest way to use Claude Code is to learn how to drive it before you turn on the billing tap.
This isn't feel-good advice. A beginner poking around the tool easily burns three to five times more tokens than someone who's been trained — and gets worse results. They fire off the same request five times, let the conversation history balloon over hours, let Claude re-read the entire project for every question, and pick the most expensive model to rename a variable. Over a month, the gap between the two adds up to tens of dollars.
The Claude Code in the terminal program from Skilzy is built around exactly that: installation, the commands that matter, structuring a project, keeping consumption under control. You get to the billing question already knowing which plan to take and how not to waste it.
Skilzy is a French AI learning platform covering more than 15 programs (images, video, music, automation with n8n, prompt writing, AI-assisted development). It includes an AI Lab where you use the real tools with credits included, which saves you from stacking up three or four subscriptions during your learning phase. Two state-recognized, publicly fundable certifications round it out (RS7439 in AI content marketing, RS6792 in AI and sales).
Be clear on one thing: training doesn't replace your access to Claude. You'll still need a Claude subscription or an API key to run Claude Code on your machine. What you save is the month or two of waste that almost everyone pays for while learning on the fly.
Method 2: The Monthly Claude Pro or Max Subscription
The subscription is the right call in more than 80% of cases: fixed price, no end-of-month surprises, and Claude Code included.
Anthropic offers several consumer plans, and Claude Code is available on the paid ones. Here are the ballpark public prices, in dollars, billed monthly.
| Plan | Ballpark price | Who it's for |
|---|---|---|
| Free | $0 | Chatting with Claude on the web, no Claude Code |
| Pro | around $20 per month | Regular but reasonable use, a few hours a week |
| Max (first tier) | around $100 per month | Heavy daily use, several long sessions a day |
| Max (higher tier) | around $200 per month | Very long sessions, several agents running in parallel |
These amounts are in dollars and they change. Always check Anthropic's official pricing page before committing — it's the only source that counts.
How it works is simple: you pay a flat rate and get a generous but capped amount of usage, which resets every few hours. If you hit the limit, you wait for the next window or move up a tier. No unexpected charges ever land on your card.
The smart move: start with Pro. It's more than enough to learn, build a website, automate scripts, and work on a personal project in the evenings and on weekends. You only move up to Max the day you regularly hit the ceiling — and when that day comes, you'll know it without a doubt, because Claude Code tells you.
For teams, Anthropic offers per-user plans with centralized billing and access management. The price per seat is higher than individual Pro, but the admin side is worth it as soon as you have three or four developers.
Method 3: The API, Billed Per Token
The API charges you exactly what you consume, no more and no less: brutally cheap for light use, dangerously elastic for heavy use.
There's no flat rate here. You create an API key, top up a balance, and every request draws that balance down. Prices are quoted per million tokens and depend on the model. Here are the ballpark figures for the three tiers:
| Model tier | Input (per million tokens) | Output (per million tokens) |
|---|---|---|
| Fast, lightweight model | around $1 | around $5 |
| Balanced model | around $3 | around $15 |
| Most powerful model | around $15 | around $75 |
Let's translate that into real usage. A serious work session on a balanced model — say 50,000 tokens read and 10,000 tokens written — costs about $0.15 of input plus $0.15 of output, so roughly $0.30. Thirty sessions like that in a month and you're at about $9. At that point, the API is clearly cheaper than a Pro subscription.
Now picture a developer running the most powerful model on a big project all day long, with full code reviews. That same day can cost $20 to $40. Over twenty working days, the bill blows way past Max. That's the whole problem with the API: it protects you from nothing.
Two official mechanisms bring the total down. Prompt caching stores the stable part of your context: writing to the cache costs a bit more, but re-reads are billed at a fraction of the normal price, which pays off enormously when Claude Code is re-reading the same files all day. Batch processing, for non-urgent requests, applies a discount on the order of 50%. The details of both, along with cost tracking, are covered in the official Claude Code docs on costs.
If you go with the API, do one thing before anything else: set a monthly spending cap in your Anthropic console and turn on email alerts. That's two minutes of setup that saves you from a very bad surprise.
Three Sample Bills, by Profile
For the vast majority of people starting out, a realistic budget lands around $20 a month, not more.
| Profile | Actual usage | Recommended mode | Monthly budget |
|---|---|---|---|
| Curious, 2 to 3 hrs a week | Small scripts, personal site, learning | API with a cap, or Pro | $5 to $20 |
| Regular developer, 2 hrs a day | One serious project, fixes, tests | Pro | around $20 |
| Full-time developer | All day, large codebase | Max, first tier | around $100 |
| Team of 3 to 5 people | Daily production work | Team plans | $60 to $150 per person |
Compare those amounts to what they replace. Twenty dollars a month is the price of lunch. If Claude Code saves you two hours a week, the math is settled, whatever your hourly rate is.
One last useful note: pricing is in US dollars. If you're billed in another currency, your bank will apply the day's exchange rate and sometimes a foreign transaction fee. Expect a few percent of difference between the listed price and the amount charged.
Six Settings That Bring the Bill Down
What costs money isn't Claude Code — it's the useless context you keep making it re-read.
Here's what produces a measurable effect, in order of impact:
- Clear the history between tasks. The
/clearcommand resets the conversation. Without it, every new message sends the whole accumulated history back as input, and you pay repeatedly for the same information. - Write a
CLAUDE.mdfile at the root of your project. It describes your architecture, your conventions, and your commands once and for all. Claude stops blindly exploring your repo to guess how it's organized. This is the setting with the best effort-to-savings ratio, covered in detail in our guide to the CLAUDE.md file. - Match the model to the task. Renaming variables or reformatting a file doesn't need the most expensive model. Save that one for architecture and hard debugging, and switch to a fast model for the mechanical stuff.
- Watch your spend live. The
/costcommand shows what the current session has cost. Check it a few days in a row and you'll immediately spot your expensive habits. It's one of the Claude Code commands worth knowing. - Be specific in your requests. “Fix the authentication bug in
auth/login.js, line 42” costs ten times less than “there's a bug somewhere, find it,” because Claude doesn't have to comb through the entire project. - Approve the plan before any writing happens. Asking for a plan first, correcting it, then launching execution avoids having to rewrite an entire feature that went off in the wrong direction. What you're saving is output — the expensive part.
Applied together on the same project, these six points routinely bring a $40-a-month habit down to around $15. Nothing heroic: just less waste.
So, Subscription or API?
If you're starting out, get the Pro subscription. Fixed price, zero surprises, and you focus on your code instead of your meter. Move to the API the day you realize your usage is either very light and occasional (it'll cost you a few dollars) or, at the other extreme, truly industrial, with caching and batching to optimize. And if you're still on the fence, install Claude Code, follow a structured training program, and watch your actual consumption for two weeks before choosing. The numbers from your own /cost beat any estimate out there, including the ones in this article.
The prices quoted here are public ballpark figures as of the publication date. Confirm them on Anthropic's official page before committing to anything.
