> For the complete documentation index, see [llms.txt](https://help.sdocs.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.sdocs.com/sdocs/template-architecture/template-settings/header-and-footer-tabs.md).

# Header And Footer Tabs

Use this section when you need content that repeats at the top or bottom of a generated document.

The **Header** and **Footer** tabs control content outside the main template body. Use them for letterhead, page numbers, disclaimers, branding, and other repeated elements.

In PDF templates, you can define one header or footer for the first page and another for the remaining pages. S-Docs places the document body between those regions during generation and repeats each section based on your settings.

{% hint style="info" %}
These settings belong to the parent PDF template. Component templates do not include Header or Footer tabs.
{% endhint %}

### How it works

* Add first-page content when page 1 needs a unique layout.
* Add remaining-page content when later pages should differ.
* Enable the first-page option for all pages when you want one consistent header or footer throughout the document.

### Common uses

* Show letterhead only on page 1.
* Repeat page numbers or legal text on every page.
* Keep branding outside the main body content.

### Related guides

* [Generating different headers on different pages in PDF templates](/sdocs/maintenance-and-troubleshooting/additional-troubleshooting/generating-different-headers-on-different-pages-in-pdf-templates.md)
* [Adding Headers & Footers from Components in PDF Templates](/sdocs/advanced-template-logic/build-reusable-templates/component-template-how-to-article/adding-headers-footers-from-components-in-pdf-templates.md)


---

# 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://help.sdocs.com/sdocs/template-architecture/template-settings/header-and-footer-tabs.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.