> For the complete documentation index, see [llms.txt](https://docs.deepwriter.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.deepwriter.com/tips-tricks-and-hacks/using-your-files.md).
# Using your files
DeepWriter can find data on its own—but you can also provide up to 20 files, each with a max size of 100 MB.
{% hint style="info" %}
**Pro tip:** Your prompt can include tips for DeepWriter to guide it on where to find the sources you prefer. For example you can suggest a particular web repository or author for it to focus its research on.
{% endhint %}
**Example Usage:**
For highly specialized or proprietary research, giving DeepWriter your key documents—like internal reports or datasets—helps it create more accurate, detailed, and relevant content than a general model could.
{% hint style="info" %}
**Important:** DeepWriter can’t process image- only PDFs. Make sure your PDF contains selectable text so the tool can analyze it.
{% endhint %}
To upload your own files, please click on the file upload icon in the lower right of the prompt window:
{% hint style="info" %}
**Important**: DeepWriter will not log in to external sites, and you should never provide credentials or passwords. Third-party authentication is not supported (yet), but it's on the roadmap.
{% endhint %}
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.
Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:
```
GET https://docs.deepwriter.com/tips-tricks-and-hacks/using-your-files.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
