Claude Projects Tutorial: Stop Your AI From Forgetting Everything

Enhanced Human·March 15, 2026

You spend an hour teaching Claude about your project. It writes a perfect analysis.

Next week, you start a new chat. Claude acts like you've never met.

Everything you built together? Gone. You're starting from scratch. Again.

This week, Anthropic made the fix free for everyone: Claude Projects.

It's the difference between hiring a consultant who forgets you exist between meetings and hiring someone who actually remembers your business.

Here's how to set it up and why it changes everything.

What Claude Projects Actually Does

Think of Projects as giving Claude a persistent brain.

Without Projects, every conversation is isolated. You can't reference previous chats. Context resets constantly. You explain the same background information over and over.

With Projects, Claude remembers:

Your documents and reference materials
Your previous conversations in that project
The context you've built over time
Your preferences and patterns

It's the closest thing to having AI that actually knows your work.

What Are Artifacts? (And Why You'll Use Them Constantly)

Artifacts are Claude's workspace for creating things.

When you ask Claude to write code, create a document, or design something, it appears in a dedicated panel instead of buried in chat.

You can edit it directly. Iterate on it. Export it. Copy it. Use it.

It solves the "AI outputs disappear into chat history" problem.

Instead of scrolling through a conversation to find that perfect prompt or code snippet, it's right there in your workspace.

Artifacts work inside Projects, so everything you create stays organized and accessible.

Step-by-Step Setup (5 Minutes)

Here's how to create your first Project.

Step 1: Go to claude.ai and log in (free account works).

Step 2: Click "Projects" in the left sidebar.

Step 3: Click "New Project" in the top right.

Step 4: Name your project. Be specific - "Q2 Planning" not "Work Stuff."

Step 5: Add a description. This is important. Claude reads this at the start of every conversation in the project.

Example: "This project is for planning Q2 2026 marketing campaigns. Focus on organic social, email sequences, and partnership outreach. Target audience is non-technical founders building AI products."

That description becomes Claude's persistent context. Every chat in this project starts with that knowledge.

Step 6: Upload relevant documents (optional but powerful). PDFs, text files, spreadsheets, whatever Claude needs to understand your work.

You can add up to 10 documents. Claude can reference them in every conversation.

Step 7: Start chatting. Every conversation in this project builds on the last one.

How to Structure Projects for Maximum Value

Most people create one giant project for everything. That's a mistake.

Think of Projects like different workspaces, not one massive brain dump.

Good project structure:

"Client: Acme Corp" (all context for one client)
"Blog Content Pipeline" (content strategy, drafts, SEO research)
"Product Launch: WidgetPro" (launch plan, messaging, go-to-market)
"Weekly Reports" (templates, data sources, recurring deliverables)

Bad project structure:

"Work" (too broad, context gets mixed)
"Random Ideas" (no focus, hard to build on)
"Everything" (defeats the purpose entirely)

Specific projects mean Claude has the right context every time.

Document Upload Best Practices

Not all documents are equally useful for Claude.

What works great:

Strategy docs and briefs
Data exports (CSVs, spreadsheets)
Style guides and brand voice docs
Previous work examples
Research reports and analysis
Meeting notes and decisions

What doesn't help much:

Huge PDFs with no clear structure
Image-heavy presentations (Claude can't see images well)
Documents with tons of irrelevant information
Anything you wouldn't want Claude to reference constantly

Pro tip: Create a "Project Brief" document specifically for Claude. Include background, goals, constraints, and preferences. Upload that first.

Claude will reference it in every conversation without you having to repeat yourself.

Using Artifacts for Real Work

Here's where Projects get powerful.

Let's say you're building a presentation. In a regular chat, you'd ask Claude for an outline. Copy it. Paste it somewhere. Ask for revisions. Copy again. Lose track of versions.

With Artifacts, here's what happens:

You: "Create a 10-slide presentation outline for our Q2 product launch. Focus on market opportunity, product differentiation, and go-to-market strategy."

Claude generates the outline in an Artifact. You see it in a dedicated panel next to the chat.

You: "Slide 3 is too technical. Make it more customer-focused."

Claude updates the Artifact in place. You see the changes immediately.

You: "Add speaker notes for each slide."

Updated again. Same Artifact. No copying and pasting.

When you're done, click "Copy" or "Download." Your presentation outline is ready to drop into Google Slides or PowerPoint.

You can come back tomorrow, reference "the presentation we built yesterday," and Claude knows exactly what you're talking about.

Real Example: Project Planning Workflow

Here's how I use Projects for recurring work.

Project name: "Weekly Status Reports"

Documents uploaded:

Team roster with roles
Project status template
Last 4 weeks of completed reports
Company OKRs for Q2

Custom instructions: "Generate weekly status reports every Friday. Focus on progress against OKRs, blockers, and next week's priorities. Keep it under 500 words. Use bullet points for readability."

Now every Friday, I open this project and say "Generate this week's status report."

Claude knows:

The template format
The team structure
What we've been working on (from previous reports)
The OKRs we're tracking

It generates a report that's 90% done. I tweak a few details. Ship it.

No re-explaining. No "here's the format again." No copying templates from old chats.

Projects turn one-time prompts into reusable workflows.

Claude Projects vs ChatGPT Projects (Side-by-Side)

Both tools added Projects recently. Here's how they compare.

| Feature | Claude Projects | ChatGPT Projects |

|---------|----------------|------------------|

| Free tier | Yes (as of March 2026) | Custom GPTs free, Projects paid only |

| Document uploads | 10 documents per project | 10+ files per project |

| Context window | 200K tokens (~150K words) | 128K tokens (~96K words) |

| Artifacts workspace | Yes, built-in | No (separate Canvas feature) |

| Conversation memory | All chats in project share context | All chats in project share context |

| Custom instructions | Project description field | Custom instructions section |

| Export options | Copy, download individual artifacts | Copy from chat or Canvas |

| Search across projects | Yes | Yes |

| Collaboration | Individual only | Individual only (Team plans can share) |

When to use Claude Projects:

You need longer context (complex projects, lots of background)
You want Artifacts for iterative editing
You prefer Claude's reasoning style
Free tier is a requirement

When to use ChatGPT Projects:

You're already in the ChatGPT ecosystem
You need web browsing during research (Claude doesn't browse)
You want DALL-E image generation integrated
You have a Team plan and need collaboration

Honest take: for document-heavy work and long-term context, Claude wins. For research and multi-modal work (images, browsing, voice), ChatGPT wins.

Use both. They're good at different things.

Integration with Existing Work Tools

Projects don't replace your tools. They connect to them.

Here's how to build Projects into your workflow.

Notion users:

Export Notion pages as Markdown
Upload to Claude Project as reference docs
Generate new content in Artifacts
Copy back to Notion

Google Docs users:

Download Docs as PDFs or text files
Upload to Project for context
Use Artifacts to generate drafts
Paste into Google Docs for final editing

Slack users:

Copy important Slack threads into a text file
Upload to Project for context awareness
Generate responses or summaries
Post back to Slack

Email users:

Forward key email threads to yourself
Copy into a doc, upload to Project
Use Claude to draft replies in Artifacts
Copy back to email

The workflow is simple: get context into Claude, use Claude to generate or analyze, export back to your tools.

Projects make this repeatable instead of one-off.

Privacy Considerations

Before you upload your company's entire strategy deck, understand what Anthropic sees.

What Anthropic does:

Stores your uploaded documents on their servers
Uses conversations to improve Claude (unless you opt out)
Applies their standard privacy policy to Projects

What you should know:

Don't upload confidential client data unless your company policy allows it
Free tier users should assume conversations may be used for training
Paid users (Pro, Team) can opt out of training data usage
Projects are private to your account (not shared publicly)

Best practice:

Use Projects for general work that isn't confidential
Anonymize sensitive data before uploading (replace client names, redact financials)
Check your company's AI usage policy before uploading proprietary docs

If you're working with truly sensitive information, use API access instead of the web interface. You get more control over data handling.

When Free Tier Is Enough vs When to Upgrade

Claude Projects just went free. Here's what you get and when you'll hit limits.

Free tier includes:

Projects feature (unlimited projects)
Artifacts workspace
Document uploads (up to 10 per project)
Claude 3.5 Sonnet (the good model)
Usage limits: resets daily, enough for moderate use

You'll need Pro ($20/month) if:

You hit rate limits regularly (heavy daily use)
You need priority access during peak times
You want 5x higher usage limits
You're using Claude for business-critical work

You'll need Team ($30/user/month) if:

You need to share Projects with colleagues
You want centralized billing
You need admin controls and usage analytics
You're using Claude across a team

For most individuals, free tier is plenty. Start there. Upgrade when you hit limits.

Common Mistakes (And How to Fix Them)

Here's what trips people up when they start using Projects.

Mistake 1: Creating too few projects (everything in one place)

Fix: Split by context. Different clients, different projects. Different work streams, different projects.

Mistake 2: Uploading everything (massive documents with irrelevant info)

Fix: Curate what you upload. Create summary docs instead of dumping raw data.

Mistake 3: Not writing clear project descriptions

Fix: Spend 2 minutes writing a good description. Claude reads this at the start of every chat. Make it count.

Mistake 4: Forgetting Projects exist (still using regular chats for repeat work)

Fix: Bookmark your key Projects. Make them your default starting point.

Mistake 5: Not using Artifacts (leaving everything buried in chat)

Fix: Ask Claude to generate things in Artifacts explicitly. "Create a document artifact with..." or "Generate code in an artifact for..."

Mistake 6: Treating Projects like file storage (upload and forget)

Fix: Projects are for active work, not archives. Keep them focused on current tasks.

Quick Wins to Try This Week

Here are 3 Projects you can set up in 10 minutes that will save you hours.

Project 1: "Email Drafts"

Description: "Help me write professional emails. Match my tone: direct but friendly. Keep emails under 150 words."
Documents: Upload 3-5 of your best emails as examples
Use case: "Draft a follow-up email to [person] about [topic]"

Project 2: "Meeting Prep"

Description: "Generate meeting agendas, talking points, and follow-up summaries."
Documents: Upload your meeting notes template
Use case: Paste meeting notes, ask for "action items summary"

Project 3: "Content Repurposing"

Description: "Turn long-form content into social posts, email sequences, and summaries."
Documents: Upload brand voice guide
Use case: Paste a blog post, get 5 LinkedIn posts in Artifacts

Each of these turns a 15-minute task into a 2-minute task.

Over a month, that's hours saved.

The Bottom Line

You've been using AI like a magic 8-ball. Ask a question, get an answer, shake it again.

Projects turn AI into a coworker who actually remembers what you're working on.

Your context persists. Your documents stay accessible. Your work builds on itself instead of resetting every time.

And as of this week, it's free.

Set up your first Project today. Upload the docs Claude needs to understand your work. Start a conversation.

Next week, when you come back, Claude will remember.

And you'll never want to go back to one-off chats again.

All articles