Claude Projects is one of Anthropic's more useful features for anyone who uses Claude regularly — persistent file context, project-specific instructions, organized conversation history. When it works, it's genuinely better than starting fresh every conversation.
When it doesn't work, it's confusing in ways that aren't obvious from the error messages (which are often minimal or absent). Most Projects issues fall into a few specific categories. Here's how to diagnose and fix each one.
Understanding How Projects Works Technically
Before the fixes, it helps to know what's actually happening. Projects doesn't create a persistent AI "memory" in a deep sense. What it does:
- Stores uploaded files in Anthropic's infrastructure
- Loads those files into the context window at the start of each conversation
- Includes your project instructions as a system prompt prepended to each conversation
So "context not persisting" means something specific: the files and instructions are technically loaded, but if there's too much content to fit in the context window, some gets truncated. Or your conversation history has grown long enough to push the instructions toward the edges of effective attention.
This is why Projects issues often feel like the AI is "forgetting" things — technically it's not forgetting, it's working with a full context window where your oldest instructions are getting less weight.
Problem 1: File Upload Limits and Silent Failures
What you see: You try to upload a file to a Project and either get an error, the spinner spins indefinitely, or the file appears to upload but isn't visible in subsequent conversations.
Upload limits:
- Single file max: 10MB
- Accepted formats: PDF, TXT, DOCX, CSV, code files, and more — but not images in Projects (images only work in the regular conversation interface)
- Total project storage: varies by plan tier
Silent failure is the tricky one. If your upload spinner never resolves and you navigate away, the file wasn't saved. Claude won't tell you this in the conversation — it'll just proceed without the file.
Fixes:
- Watch the upload confirmation. Wait for the file to show a checkmark or appear in the file list before closing the upload dialog.
- Check file size. Anything approaching or over 10MB needs to be trimmed or split. For PDFs, remove images or reduce to text-only before uploading.
- Try a different browser. Firefox has had more upload reliability issues with Projects than Chrome. Chrome is recommended.
- Clear browser cache and retry. Stale session data sometimes interferes with upload handling.
Problem 2: Context Not Persisting Between Sessions
This is the most common complaint about Projects — "I uploaded everything, set up my instructions, and then in a new conversation Claude has no idea what I told it."
First, confirm what "not persisting" actually means in your case:
Are your files still listed in the project? Click into the Project and check the Files section. If they're listed, they're being loaded. The issue is likely context window crowding (see below), not missing files.
Did you start a new conversation or look at the same conversation? Each new conversation in a project starts fresh — loading your files and instructions from scratch. Long conversations from previous sessions don't carry forward. That's by design. If you need continuity from a previous conversation, you have to summarize it manually or start the new conversation with context.
Context window crowding. If you have a lot of uploaded files, Claude loads them in order at the start of each conversation. Files that collectively exceed the available context window get truncated — Claude sees the beginning of each file but not the end. For a project with 5 large documents, the last documents in the loading order may be barely visible to the model.
Fix: Prioritize what's in your project files. Remove files that aren't essential. For large reference documents, create condensed versions (key excerpts, summaries) rather than uploading the full document. Claude doesn't need to read the entire document every time — just the parts relevant to your work.
Problem 3: Project Instructions Being Ignored
You wrote careful instructions for how Claude should behave in this project. Half the time it follows them. The other half it seems to ignore them completely.
The consistency problem is real. Project instructions are not a hard constraint enforced by a separate system — they're part of the context that Claude considers. This means:
- Long, complex instruction sets are harder to follow consistently than short, clear ones
- Instructions that conflict with a user's explicit message ("actually, write it formally even though I said casual") get overridden by the explicit message
- Very long conversations push the instruction text further from the model's primary attention
Fixes:
Trim your instructions. If your project instructions are 2,000+ words, cut them to the essentials. Claude follows short, specific instructions more reliably than long, elaborate ones.
Frame critical instructions as constraints, not preferences. "Always respond in bullet points" is clearer than "I prefer responses in bullet points." Constraint language works better.
Don't contradict your own instructions. If your project instructions say "always be concise" and then you message "give me a comprehensive analysis," the instruction will likely lose to your explicit request. Decide which takes precedence.
Start a fresh conversation. If a specific conversation has accumulated a lot of back-and-forth that seems to be overriding your instructions, start a new conversation within the same project. Fresh conversations load your instructions at full weight.
Problem 4: Sync Failures — Changes Not Saving
You edit your project instructions, close the panel, and later they've reverted. Or you upload a new file version and the old version is still what Claude references.
The autosave assumption. Projects has autosave, but it's not instantaneous. If you edit instructions and immediately start a new conversation, the old instructions might still be cached for that conversation.
Fixes:
- After editing project instructions, wait 5-10 seconds before starting a new conversation
- For file updates: delete the old file version first, then upload the new one — don't rely on re-uploading to overwrite
- If instructions keep reverting, check if you're logged into multiple devices/tabs. Simultaneous edits from multiple sessions can cause version conflicts
Problem 5: Projects Not Available on Your Account
If you can't find the Projects feature in Claude at all, or see a prompt to upgrade when you try to access it:
Projects requires Claude Pro ($20/month) or a Team plan. It's not available on the free tier. There's no workaround — this is a paid feature.
If you're on Pro and still can't access Projects, try:
- Sign out and sign back in
- Clear browser cache
- Try a different browser
In rare cases, a billing issue (failed payment, subscription lapse) can silently downgrade your account access while leaving you logged in.
Problem 6: Claude Not Using Uploaded Files
You uploaded documents to the project but Claude clearly isn't referencing them when it should be.
Explicit reference helps. Claude doesn't automatically "apply" everything in uploaded files to every response. For uploaded reference documents, you often need to explicitly tell Claude to use them: "Based on the product spec document in this project, explain..." or "Referring to the uploaded style guide..."
File format matters. PDFs with complex layouts, heavy formatting, or lots of images don't parse as cleanly as plain text or simple DOCX files. If you're uploading a formatted PDF and Claude seems to miss details, try exporting to plain text first.
For general Claude issues unrelated to the Projects feature — slowness, response quality, connection errors — the Claude AI not working guide covers platform-level status. Projects-specific errors are almost always one of the issues above, and most have clear fixes once you understand how the feature actually works under the hood.
