Claude Projects, Explained: Folders, Limits & Setup

A tidy desk workspace with a MacBook and neatly stacked notebooks

I use Claude every single day, and for a long time my chat history was a disaster — hundreds of unrelated conversations in one endless scroll. Claude has no native folders for individual chats, but it does have Projects, and once I understood what they actually do (and don’t do), they became my main organizing primitive.

Here is everything I learned about Claude Projects: how to set them up, what the real limits are, and when they stop being enough.

What a Claude Project actually is

A Project is an isolated workspace inside claude.ai. Think of it less like a folder and more like a mini-environment: it has its own set of chats, its own uploaded knowledge files, and its own persistent instructions that apply to every conversation inside it.

That last part is the most underrated feature. You can write a system prompt once — “You are helping me with a SaaS product for indie developers; always respond in British English; assume I know TypeScript” — and every chat in that project inherits it automatically. No more pasting context at the top of each new conversation.

Projects are available on every plan. Free accounts get five of them. Pro, Max, Team, and Enterprise accounts get unlimited.

How to create and populate a project

Finding the new project button confused me the first time. On claude.ai, look in the left sidebar — there is a “Projects” section above your recent chats. Click “New Project,” give it a name, and you are in.

From inside the project you can:

  • Upload knowledge files individually (up to 30 MB each). Claude can reference these in any chat within that project — design docs, reference PDFs, a style guide, whatever context you want always available.
  • Set project instructions in the “Instructions” field. This is your persistent system prompt.
  • Add existing chats by going to your Chats history page, checking the boxes next to conversations you want to move, and bulk-moving them into the project. I used this to migrate a month of scattered client work chats into one place in about two minutes.

You can also star a project to pin it at the top of the sidebar, or archive old ones to clear the clutter.

The real limits you will hit

This is where I want to be honest, because the marketing around Projects makes them sound more powerful than they are for heavy users.

No nesting. There are no sub-projects. Every project sits at the same flat level. If you work across five clients and three internal tools, you end up with eight projects all in one list. That is fine at eight — it gets messy at twenty-five.

One chat, one project. A conversation belongs to exactly one project. You cannot tag it into multiple places or keep a shared research thread visible across different project contexts.

Project sprawl is real. Because nesting is impossible, the only way to add granularity is more projects — and past a dozen, “where does this conversation live?” becomes its own problem.

Individual chats still can’t be pinned. You can star a project, but not a specific chat inside one. A conversation you return to every morning drifts down the list as new chats appear. Sidebar search on paid plans helps, but it searches within one project at a time — no cross-project queries.

No local folder import. The claude.ai web app cannot ingest a raw directory from your computer. You add files individually or zip them. (Local filesystem access belongs to Claude Code and Claude Desktop with MCP connectors — not the web chat.)

When Projects are enough

If your Claude usage clusters naturally into a handful of clearly distinct contexts — one for work, one for side projects, one for personal research — Projects work beautifully. The persistent instructions alone are worth it, and the knowledge file uploads are genuinely powerful for giving Claude stable context across many sessions.

I have a “NorthLab” project with the full product spec, pricing copy, and support tone guide uploaded. Every support draft I write there already knows the product. That workflow would be painful without Projects.

When you need more than Projects

The gaps — no pinning individual chats, no nesting, no cross-project tagging — are what pushed me to build something on top of claude.ai rather than waiting for Anthropic to ship it.

If you want to go deeper on the organizational options available today, I wrote a full breakdown of how to add folders to Claude covering every approach. And if your specific need is grouping existing chats into folder collections, the post on how to make a folder of chats in Claude walks through that workflow.

For chat-level pinning, real subfolders, and bulk export, I built NorthLab Folders — a browser extension that adds a folder sidebar directly inside claude.ai (and ChatGPT). You get subfolders one level deep, the ability to pin any individual chat, date stamps, and bulk ZIP export of entire folders as Markdown. It runs local-first: nothing leaves your browser.

NorthLab Folders is free for up to 3 folders on Chrome, Edge, Brave, Arc, and Safari on macOS.

Frequently asked questions

How do I create a folder in Claude? Claude has no native folder system for individual chats. The closest substitute is Projects — go to the sidebar on claude.ai, click “New Project,” give it a name, and start adding chats. Free accounts get up to 5 projects; paid plans are unlimited.

Where do I find my Claude projects? Your projects live in the left sidebar on claude.ai under a “Projects” section, above your recent chats. Click any project name to open its workspace and see its chats, uploaded knowledge files, and instructions.

Is there a limit to how many Claude projects I can have? Free plan users are capped at 5 projects. Pro, Max, Team, and Enterprise plans all get unlimited projects. There is no limit on the number of chats inside a project on any plan.

Can I nest folders inside a Claude project? No. Claude Projects have no sub-project or nesting support. Every project sits at the same level — you cannot create a project inside another project, which is the main reason project sprawl becomes a problem as your Claude usage grows.