Upload PDFs, images, and documents to a Rocket.new project once, then reference the shared files from any Solve or Build task inside it.
Upload your reference files to a project once and they become persistent context for every task inside it. Company overview, financial model, brand guidelines, research data. Whatever your work depends on, it is available from the first message in every task.
Project files vs task files: Files uploaded directly inside a task are scoped to that conversation only. Files uploaded at the project level are persistent and available to every task in the project automatically, without being re-uploaded or re-explained.
Upload anything that provides lasting context for your work on this initiative. The best project files are things you’d otherwise paste or re-explain in every task.
File type
Examples
Company context
Company deck, one-pager, mission/strategy doc
Financial data
P&L, financial model, cap table (.xlsx, .csv)
Research
Market reports, competitor teardowns, user interviews (.pdf)
Brand assets
Brand guidelines, logo usage, design system
Product specs
PRD, feature specs, user stories (.pdf, .md)
Reference data
Pricing data, industry benchmarks, customer data exports
You don’t need to upload everything upfront. Start with the files you’d reach for most often, and add more as the project evolves.
Projects support up to 5 context sources at a time. This limit counts across all source types: uploaded files, Google Drive links, and Notion pages combined. If you need to add a new source, remove an existing one first.
Every task in the project can draw on the shared files automatically. You do not need to re-upload or re-reference them. For the most precise results, mention the file by name in your prompt: “Using the brand guidelines PDF, build a landing page that matches our visual identity.”
As your project grows, keeping files organized helps both you and Rocket find what’s needed.
Use descriptive file names
Name files clearly: brand-guidelines-v2.pdf is better than document.pdf. Descriptive names help Rocket match files to task context and make it easier for collaborators to find what they need.
Remove outdated files
If a file has been superseded, remove the old version to avoid confusion. Rocket may reference outdated files if they’re still present in the project.
Upload early in the project lifecycle
Add foundational files such as brand guides, product specs, and research data when you first create the project. This ensures every task from the start has access to the right context.
Keep files focused
Upload files that are relevant to the project’s scope. A project about “Q3 Product Launch” only needs the product brief and brand assets, not the full employee handbook.
Open the Context tab in the project’s right panel.
2
Hover over the file
Hover over the file you want to remove.
3
Click the X button
Click the X button that appears on the file.
Deleting a shared file removes it from the project permanently. Tasks that previously referenced the file won’t lose their existing outputs, but future tasks won’t have access to that file’s content.
