Add files to chat
Use this guide to attach a file to a chat message so Atlas can analyze its content in that conversation.
What this page covers
Attach files to a chat and check supported types, size and count limits, processing states, and removal behavior.
When to attach a file
Attach a file when the chat conversation needs temporary context that does not need to be a permanent part of the project. Good cases include:
- Asking Atlas to analyze a document before deciding whether to import it
- Comparing an attachment with a source already in the project
- Extracting key points from a file quickly without full source processing
If the material should become searchable, citable project evidence, import it as a source instead.
Steps
- Open the chat where you want to ask the question.
- Select the attachment option in the chat input.
- Choose the file you want to attach.
- Write a message that tells Atlas what to do with the file.
- Review the answer.
- If the content matters beyond this conversation, save the findings in a note or import the file as a source.
Good questions to ask with an attachment
- What does this document say about [topic]?
- Extract the key points from this file.
- Compare this attachment with @[source name] on [topic].
- Does this attachment contradict anything in my project?
Troubleshooting
| Problem | What to check |
|---|---|
| File is rejected | Check the file type, file size, and your plan limits |
| Answer does not use the file | Restate what the file contains and what you need Atlas to do with it |
| You need the result in future chats | Save a note or import the file as a proper project source |
Check attachment formats and states
Attachments are files added to a specific chat or note context. They are useful for quick analysis, visual context, or one-off material that does not need the full source pipeline.
Attachments are different from sources. A source becomes part of the project library and can support search, citations, summaries, and maps. An attachment helps the current workflow.
Where attachments appear
| Surface | Attachment role |
|---|---|
| Chat | Add files or images that should inform the current answer. |
| Notes | Preserve screenshots, figures, diagrams, or visual evidence next to written notes. |
| Source workflows | Prefer source import when the material should become reusable project evidence. |
Use attachments for
- screenshots you want to ask about once
- figures or images that clarify a note
- small supporting files for a single question
- drafts or snippets that are not part of the permanent research corpus.
Use sources instead for
- PDFs you will cite later
- articles, papers, websites, or videos that should be searchable
- material that should appear in project-wide retrieval
- evidence that should support knowledge maps or summaries.
Attachment boundaries
An attachment can help Atlas interpret the immediate context, but it should not be treated as a fully indexed source unless the product explicitly imports it as one.
For durable research evidence, import the material as a source first, then ask questions against that project context.
Decision table
| Attachment use | Best for |
|---|---|
| Chat attachment | Temporary analysis in one conversation. |
| Note image | Visual context attached to written interpretation. |
| Source import | Searchable, citable, reusable project evidence. |
| Unsupported file | Convert to a supported source or attach only for limited context. |