> For the complete documentation index, see [llms.txt](https://overleaf-pro.ayaka.space/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://overleaf-pro.ayaka.space/latex/tex-latex-primitives/08-pdfinclusionerrorlevel.md).

# \pdfinclusionerrorlevel

`\pdfinclusionerrorlevel[=]` *integer*

This command is used to control the behavior of the TEX engine when a PDF file is included that has a newer version than the one specified by [`\pdfminorversion`](/latex/tex-latex-primitives/09-pdfminorversion.md).

* “`[=]`” means that the equals sign is optional.

**Usage examples**

* `\pdfinclusionerrorlevel=-1` (or anything $$<0$$): gives no diagnostic information.
* `\pdfinclusionerrorlevel=0` (default): causes the TEX engine to issue a warning.
* `\pdfinclusionerrorlevel=1`: causes the TEX engine to raise an error.

#### \pdfinclusionerrorlevel: Background information

Since it was first published in the 1990s, the [PDF file format](https://en.wikipedia.org/wiki/PDF) has undergone numerous revisions and enhancements which periodically result in the publication of a new version of the formal PDF specification. Consequently, any PDF file, including those produced by TEX engines, will conform to a particular version of the PDF specification—such as PDF version 1.4, 1.5 etc. Every PDF file contains data that identifies which version of the PDF specification the file conforms to—so that any application that wishes to “consume” a PDF file (e.g., importing, processing etc) knows which set of PDF features are likely to be present within that file.

If your TEX document imports a graphic in PDF format, for example via `\includegraphics`, that graphic file might conform to a PDF specification that is newer (later) that the one supported by the TeX engine’s own output PDF file. Clearly, this has the potential to cause a “clash” between the PDF version generated by a TEX engine and the PDF version used by one of the imported graphics. By way of an example, the typeset document produced by a TEX engine might conform to, say, PDF version 1.4 but an imported graphic conforms to, say, PDF 1.5. If that imported graphic is simply embedded without further action then, clearly, the PDF output file produced by TEX no longer conforms to PDF 1.4 because it now contains graphical content based on the PDF 1.5 specification. The `\pdfinclusionerrorlevel` command helps to manage this.


---

# 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://overleaf-pro.ayaka.space/latex/tex-latex-primitives/08-pdfinclusionerrorlevel.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.