> 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/writing-and-editing/generating-and-inserting-tables/pasting-tables-into-your-project.md).

# Pasting tables into your project

You can copy and paste tables from webpages, word processors and spreadsheets into Overleaf.

## Pasting tables into your Overleaf project

**Visual Editor** can’t fully preserve the form and style of every table pasted into your project, but you can still save time and effort by pasting a wide range of tables created in other applications.

**Visual Editor** tries to preserve and preview the following table elements:

* horizontally merged cells (spanning multiple columns)
* borders applied to cells
* formatting of text within table cells
* table captions and headings

**Visual Editor** also lets you [modify the pasted table](https://docs.overleaf.com/writing-and-editing/generating-and-inserting-tables.md#how-to-edit-or-customize-an-inserted-table), such as editing cell contents or adding rows and columns. You can also switch to **Code Editor** to make changes, including setting $$\LaTeX$$ parameters that control the table’s [position within the typeset document](https://docs.overleaf.com/writing-and-editing/inserting-images.md#positioning).


---

# 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/writing-and-editing/generating-and-inserting-tables/pasting-tables-into-your-project.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.
