> For the complete documentation index, see [llms.txt](https://docs.swingsoftware.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.swingsoftware.com/pdf-converter-for-notes/how-to/how-to-add-header-and-footer-to-a-pdf-document.md).
# How to add header and footer to a PDF document
Swing PDF Converter supports Lotus Notes form\* header and footer data as well as custom header and footer.
Header and footer can be enabled in Swing PDF Converter - PDF settings, under "Header/Footer" tab.
{% hint style="info" %}
\*Please note that Swing PDF Converter does not support document title tag (\&W) in form header / footer settings. A workaround for this limitation would be to use Lotus Formula to recreate document title.
{% endhint %}
There are two header/footer options available from this page:
### 1. "**Use header/footer defined on source document form**"
When this option is enabled, Swing PDF Converter looks for document form defined header and footer data and exports it to pdf document.
### 2. "**Define custom header/footer**"
When this option is enabled, Swing PDF Converter transfers data from "Header" and "Footer" fields in settings document to PDF document.
From PDF Converter version 3.13. it is possible to write Lotus formula to header/footer.
Formula must be nested in "" tags. Syntax:
`...Lotus Formula...`
For example:
`Today is @Today.`
`Time is @Now.`
{% hint style="info" %}
Swing formula tags should be written in the same paragraph style (size, color, style..). \
You can combine text colors for header/footer, only Swing tag style must be uniform.
{% endhint %}
[Please read this article for header and footer management from LotusScript API.](https://sites.google.com/a/swingsoftware.com/lc/pdf-converter/for-developers/lotusscript-code-samples/add-custom-header-footer-to-pdf-document)
---
# 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.swingsoftware.com/pdf-converter-for-notes/how-to/how-to-add-header-and-footer-to-a-pdf-document.md?ask=&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.