> For the complete documentation index, see [llms.txt](https://overleaf-pro.ayaka.space/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://overleaf-pro.ayaka.space/latex/knowledge-base/086-if-my-latex-project-is-split-into-multiple-tex-files-can-i-edit-them-all-on-overleaf.md).

# If my LaTeX project is split into multiple tex files, can I edit them all on Overleaf?

For larger projects, it is often preferable not to insert all the code in one main file, but rather to split the contents into multiple files (e.g. chapters of a thesis). The overall project then consists of one main tex file and many sub-files.

These sub-files can be included in such a project on Overleaf by uploading them as attachments (via the files --> upload menu in the editor), and referenced in the usual way via `\input` or `\include`.

You can then edit these sub-files directly on Overleaf simply by clicking on them

To see a short video demonstrating this, see our blog post on [writing your thesis with Overleaf](https://www.overleaf.com/blog/30).

![Overleaf files edit screenshot](/files/sOchs7chiJITszR1HSVR)


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://overleaf-pro.ayaka.space/latex/knowledge-base/086-if-my-latex-project-is-split-into-multiple-tex-files-can-i-edit-them-all-on-overleaf.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.