> ## Knowledge Base Index
> Fetch the complete knowledge base index at: https://authorea.crisp.help/sitemap.xml
> Use this file to discover available pages before exploring further.
> Pure-Markdown content can be obtained by appending a '.md' suffix to the content URLs listed in the sitemap (without the trailing slash).

# How to prevent wide or long tables from overflowing in the exported PDF

## Basic tables
If your table is too wide and/or long and it does not easily fit on a Letter/A4 page, we suggest you customize the table look. Every table can be customized in its look: the number of rows and columns you want to export, as well as the font size. Just *click on the table* to see what options are available.

![Table Options](https://storage.crisp.chat/users/helpdesk/website/d38f777e-0276-4c52-8a15-b5855ac4903c/ee5f8f57-53f4-46b2-9f0f-575dd6e29d4e.png)
## LaTeX tables
Is your table written in LaTeX? If so, keep reading for suggestions on how to fix horizontal and vertical flow.

### Horizontal Overflow (Wide Tables)
A standard table in LaTeX is typically realized via the *{tabular}* environment. However, if the content is too wide to fit a single line of a printed page, the resulting PDF eventually looks broken as the content gets clipped at the edge of the page. You can see an example in *Table 1* from this Authorea-generated PDF export.

![](https://storage.crisp.chat/users/helpdesk/website/d38f777e-0276-4c52-8a15-b5855ac4903c/b0996023-959e-4200-b06c-0ff3745b91ed.png)
To counteract this, one may use the more advanced *{tabulary}* package, a detailed introduction to which can be found [here.](https://en.wikibooks.org/wiki/LaTeX/Tables#The_tabulary_package) The main difference in effect is that tabulary will re-wrap all column content so that it will fit the page, even if some content has to be pushed down some rows. The syntax is also slightly different (capital letters for the L,C,R column format letters), but it is mostly a drop-in replacement.

### Vertical Overflow (Long Tables)
Similarly to wide tables, a long table done with *{tabular}* will be clipped at the bottom end of the page, losing any content that couldn't fit. To avoid that one can use the *{longtable}* environment instead, which gracefully continues on the following page with any remaining content. There are advanced customization options available for the appearance of a longtable, which can be studied in more detail [here.](http://www.ctex.org/documents/packages/table/longtable.pdf)

![](https://storage.crisp.chat/users/helpdesk/website/d38f777e-0276-4c52-8a15-b5855ac4903c/c8eb13d5-4e2e-4c74-b468-9ce430a284ab.png)

​