Uploading Reference Documents to Your Project

Knowledge files separate a good Project from a great one. Upload once and Claude can pull from them in any conversation inside that Project.

What Knowledge Files Are

Any document uploaded to a Project so Claude can reference it. Once there, Claude reads it as background context — like a reference binder on a shared desk that any conversation can pull from.

You don't have to mention the file in your prompt. If you ask a question the file can answer, Claude draws on it automatically. You can also ask directly: "Based on the proposal template I uploaded, what section is missing here?"

File Types That Work Well

PDF — contracts, specs, reports, proposals
Word (.doc, .docx) — templates, SOPs, letters
Excel/CSV (.xlsx, .csv) — price lists, schedules, registers
Plain text/Markdown (.txt, .md) — notes, guides, lists
PowerPoint (.pptx) — presentations (text content, not slide design)

Photos and images of documents get attached in the chat itself, not uploaded as knowledge files. Scanned PDFs with real text work fine.

Practical Limits

Per file: roughly 30 MB. Most business docs are well under this.
Per Project: you can upload dozens, but the real limit is what Claude can hold in mind. 40 documents synthesize worse than 5 focused ones.
Best practice: keep knowledge lean and purposeful. If a 200-page doc has 10 pages that matter, trim it first.

What to Upload

Good candidates:

Stay the same (or mostly the same) over time
Come up frequently across many conversations
Give Claude context it couldn't figure out on its own

Strong choices:

Your standard proposal or contract template
Rate card or price list
Brand voice guide / style guide
Scope exclusion list
Employee handbook sections you often quote
3–5 examples of past work done well

What NOT to Upload

Changes frequently. Monthly rates will be stale within a month. Paste the current version into chat instead.
Large and mostly irrelevant. A 500-page code book for 2 relevant sections dilutes Claude's focus. Extract.
Sensitive personal data. See Lesson 14 for what's appropriate.

Example 1: Proposal Template + Rate Card

An estimator at Empower uploads two files to his "Estimating" Project:

The standard proposal template (Word doc, 4 pages)
The current labor rate sheet (Excel, rates by role and tier)

When he pastes a scope: "Draft a proposal using our template and price this scope from our rate sheet." Claude produces a first draft. He adjusts numbers and project-specific details. What used to take 3 hours on a simple bid takes 45 minutes.

Example 2: Voice Guide + Past Emails

A marketing coordinator uploads three files to her "Communications" Project:

A 2-page brand voice guide
Three "best-in-class" past customer emails
A one-page FAQ

Claude now writes emails that sound like Empower instead of generic corporate. She edits for specific facts, rarely for tone.

How to Upload

Open the Project.
Find "Project Knowledge" / "Files" or the upload icon near Project settings.
Click Add files or drag and drop.
Upload. Files are active immediately.

To remove: click the file in the list → delete. Removal affects future conversations only. Past conversations stay unchanged.

Start with 2–3 files. It's tempting to upload everything. Don't. Start with the 2–3 documents that come up most often, use the Project for a couple of weeks, then add more based on what Claude keeps not knowing. Lean beats cluttered every time.

For live data and connected systems. If information lives in a live system — your CRM, accounting, project management — uploading a file is the wrong approach. That's what connectors are for. See Lesson 17.

Try This Now (5 min)

Pick your most-used Project. Upload the single most-referenced document from your current job (a template, a rate card, a style guide). Start a chat and ask Claude to do something that would normally require pasting that document. Notice what it does without being asked.

What Comes Next

Role-specific templates you can copy and adapt in 15 minutes. Continue to Lesson 09.