> For the complete documentation index, see [llms.txt](https://docs.overleaf.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.overleaf.com/templates/submitting-to-publishers.md).

# Submitting to publishers

{% hint style="info" %}
If you're looking for information on how to submit your project to the [Overleaf template gallery](https://www.overleaf.com/latex/templates), you can find that in [Submitting to the Overleaf template gallery](/templates/submitting-to-the-overleaf-template-gallery.md).
{% endhint %}

Overleaf works with a range of partners to streamline your publishing workflow by providing the ability to send/submit your paper (project) to those partners—using features accessible from within your Overleaf project. Those submission processes are designed to meet the requirements specified by each partner, so the actual submission workflow will show some variation according to the publisher, journal, repository or service you are submitting to.

## How to submit to a publisher

### Publisher submission links

Some publishers have opted for a full Overleaf integration which enables Overleaf to export the project (article) files and send them to the publisher's manuscript submission system—meaning you don't need to download anything.

For these partnering publishers or journals, use of their official LaTeX template, accessible from the Gallery, will create a *submission link* within the menu of your project, helping to further streamline the publishing workflow.

<figure><img src="https://3502988919-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FVetOkhFZmAC8QCQK0Pi7%2Fuploads%2FVuxDfIe5qzH5rh3kydCz%2FScreenshot%202026-02-10%20at%2010.46.21%E2%80%AFAM.png?alt=media&amp;token=940b4ea4-713a-4da0-a757-b383c778f2b8" alt="An example of an official submission link from a publisher, next to the Share and Layout buttons" width="328"><figcaption><p>An example of an official template's submission button</p></figcaption></figure>

### The Submit menu option

Other publishers have chosen a less-complete integration which requires you to download the project files and upload them to the publisher's manuscript submission system.

If your project is not an official template, but the publisher you want to submit to has partnered with Overleaf, you can find the **Submit** menu option located in the File menu or in the project name drop-down menu:

{% columns %}
{% column %}

{% endcolumn %}

{% column %}

{% endcolumn %}
{% endcolumns %}

From there, you will see a modal to search for any academic journals, online repositories, author services, or conference proceedings that accept submissions from Overleaf.

## Submit modal

Each publisher has their own set of actions for downloading files and submitting manuscripts. Please follow your publisher's instructions for successful submission.

<figure><img src="https://3502988919-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FVetOkhFZmAC8QCQK0Pi7%2Fuploads%2FEyMNzjWCj1T3Oo3tNw8b%2FScreenshot%202026-02-10%20at%202.04.32%E2%80%AFPM.png?alt=media&amp;token=5a486e51-2de3-4980-89d6-b49f0713080b" alt="" width="563"><figcaption></figcaption></figure>


---

# 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.overleaf.com/templates/submitting-to-publishers.md?ask=<question>&goal=<user_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.
