The short version: Anthropic's terms currently give you ownership of what Claude Code produces, and commercial use is permitted across plan tiers. The longer version — which terms apply to your plan, and a couple of real caveats worth knowing before you ship generated code — is what actually matters once you're using this for client or commercial work.
| Plan | Terms that apply |
|---|---|
| Free, Pro, Max | Consumer Terms of Service |
| Team, Enterprise, Claude API | Commercial Terms |
This split is confirmed directly in Claude Code's own legal and compliance documentation — it's not a guess or a third-party summary. If you're not sure which applies to your account, that's worth checking before you assume either set of terms.
Under Anthropic's current terms, code Claude Code writes for you is yours to use — including commercially, including in client and proprietary work. This is the part most people asking about "licensing" actually want to know, and the answer is straightforward: it's permitted.
Ownership under Anthropic's terms and copyright protection under the law aren't the same question. Portions that are purely AI-generated, with no meaningful human modification, may have limited or no independent copyright protection in some jurisdictions. If you're relying on copyright specifically — not just Anthropic's terms — to protect a piece of code, that's a reason to actually review and meaningfully edit it, not just accept it unchanged.
Common patterns and idioms aren't copyrightable on their own — Claude Code producing a standard debounce function or a typical form-validation pattern isn't a licensing issue. But if a substantial, recognizable chunk of a specific open-source project shows up in the output, that project's original license still applies to that chunk. An AI tool generating it doesn't strip the license it came attached to — the same due diligence you'd apply to copy-pasting code from a repo still applies here.
The freelancer and agency workflow guides cover the practical side of keeping client projects clean — CLAUDE.md scoping, review habits, and what to standardize across projects.
Read Claude Code for Freelance Developers →Anthropic's terms currently permit commercial use of Claude's output across plan tiers, and Claude Code follows the same rules. Which specific terms apply depends on your plan — Commercial Terms for Team, Enterprise, and API users, Consumer Terms for Free, Pro, and Max — so check whichever applies to your account before relying on this for client work.
Not necessarily. Portions that are purely AI-generated with no human modification may have limited or no independent copyright protection in some jurisdictions, which matters if you're relying on copyright specifically to protect that code — a real reason to review and meaningfully edit generated code you intend to protect that way, not just accept it as-is.
Common patterns and idioms aren't copyrightable on their own, but if a substantial, recognizable portion of a specific open-source project shows up, that project's original license still applies to that portion — the fact that an AI tool produced it doesn't erase the license it came attached to.
No. This is a plain-language summary to orient you, not a substitute for reading Anthropic's actual current terms or talking to a lawyer for anything with real commercial or legal stakes.