# Insert a line break or page break
## Line break
Line breaks are inserted by using the [special code](https://help.clause9.com/clauses/special-codes) `%%`. The text after `%%` will start on a new line. This command will not insert a new paragraph. However, by inserting multiple line breaks a new paragraph can be created.
## Page break
There are two ways you can implement a page break. The first way is to use a setting which will be applied and saved at the document level and the second way is tied to a clause and will therefore be applied to all documents that clause appears in.
### Page break to be applied in one document only
Select the clause that you want to appear on a new page and navigate to *Advanced* *> Layout.*
Multiple layout options for the selected clause will appear.
By way of a reminder: it may seem like some of the options under *Advanced* and under *Styling* are overlapping. However, there is a difference between those two settings: changes made under the *Styling* tab will be applied to the **whole document.** Under the *Advanced* tab, any changes will be applied to the **currently selected clause**. A walkthrough of the *Advanced* tab can be found [here](https://help.clause9.com/assemble-document-operations-panel/advanced-pane).
Under *General*, tick the box that says . In the document, a blue dotted line will appear in place of the page break. The page break will be inserted right before the clause you selected.
### Page break to be applied to all instances of a clause
If all instances of a clause should be accompanied by a page break, there are three ways of doing this:
* apply custom styling
* use the special code `% page break before %`
* use the special function @page-break
### **Custom styling**
Edit the clause that should have a page break inserted **before** it. Go to in the menu on the right, click on *Custom styling* at the right, navigate to *Title* and then click on the green *+ Custom styling* button.
Scroll down to *Text flow settings of each paragraph* and enable *Page break before* by clicking the slider and then click the checkbox to enable it.
You could also insert a page break before **every single paragraph** of a clause by enabling the same setting outlined above under “non-title parts” of the custom styling settings.
### **Special code**
If you insert the [special code](https://help.clause9.com/clauses/special-codes) `% page break before %` before any paragraph, ClauseBase will insert a page break before that paragraph. That also means that inserting this special code before the text in the clause’s *content title*, means the page break will be inserted before the clause, including its title.
Using this special code will thus give you some flexibility in choosing where the page break should be inserted – whether before the title or before any other paragraph of that clause.
### Special function
The special function [@page-break](https://help.clause9.com/special-functions/special-items-1#page-break) will insert a page break at the location the special function is 'invoked'. This is therefore the most flexible option, enabling you to choose the exact location in a clause or document for the page break to be inserted.
{% hint style="warning" %}
Note that the special function @page-break can not be used in a table. If @page-break is included in a table, Clause9 will simply ignore it and output the table without a page break.
{% endhint %}
. In the document, a blue dotted line will appear in place of the page break. The page break will be inserted right before the clause you selected.
### Page break to be applied to all instances of a clause
If all instances of a clause should be accompanied by a page break, there are three ways of doing this:
* apply custom styling
* use the special code `% page break before %`
* use the special function @page-break
### **Custom styling**
Edit the clause that should have a page break inserted **before** it. Go to in the menu on the right, click on *Custom styling* at the right, navigate to *Title* and then click on the green *+ Custom styling* button.
