What Does “PDF inclusion: invalid other resource” Mean in pdfLaTeX?

The warning PDF inclusion: invalid other resource which is no dict: ignored is usually about a PDF file that your document includes, not an error in the surrounding LaTeX syntax. pdfTeX encountered a resource entry in that PDF whose value was not a dictionary of the kind it expected, so it skipped that entry.

The document may still compile and produce a PDF. Whether anything looks wrong depends on whether the skipped resource was needed by the included page. Here’s how to locate the file and decide what to do.

What “other resource” refers to

A PDF page can refer to resources such as fonts, images, color spaces, patterns, or graphics states. These are listed in the page’s resource dictionary. When pdfTeX includes a PDF page, it reads and copies the resources needed to render that page.

This warning indicates that pdfTeX found an entry it treated as a resource category, but its value was not a dictionary. It ignored that entry rather than stopping compilation. The wording does not, on its own, tell you which resource was affected or whether the page’s visible content depends on it.

The problem is generally in an included PDF’s structure or in how that PDF was produced. It is not usually fixed by changing ordinary LaTeX text, margins, or fonts in the main document.

Find the PDF that triggers the warning

Look in the compiler output or .log file for the warning’s surrounding lines. They may include the name of the PDF being read. If not, check the files included around the point where the warning appears. Common commands that include PDFs are:

\includegraphics{figure.pdf}

and, when using the pdfpages package:

\includepdf[pages=1]{appendix.pdf}

To isolate the problem, temporarily comment out PDF inclusions and compile again. If the warning disappears, restore the inclusions one at a time until it returns. This is especially useful in a large document with many figures.

Decide whether you need to fix it

Inspect the final compiled PDF at the page containing the included file. Check for missing text or images, incorrect colors, or other visible changes. If the page looks right, the skipped resource may not be used by the content you included. You can often leave the warning alone, but keep an eye on the output if the source PDF changes.

If something is missing or rendered incorrectly, repair the specific source PDF rather than trying random changes to the LaTeX document. Keep the original file so you can compare results and recover if a conversion changes the appearance.

Regenerate or rewrite the included PDF

If you control the source document, export it to PDF again using its original application, preferably with an up-to-date exporter. If another application created the PDF, try exporting it again or saving a fresh copy through a reputable PDF editor.

You can also try rewriting the file with Ghostscript. For example:

gs -dBATCH -dNOPAUSE -sDEVICE=pdfwrite \\
  -dPDFSETTINGS=/prepress \\
  -sOutputFile=repaired.pdf original.pdf

On Windows, the command-line program may be named gswin64c instead of gs. Check the rewritten file before replacing the original: rewriting can alter fonts, transparency, colors, or other details. If you do not have the source PDF, converting the affected page to an image and including that image is a fallback, but it sacrifices selectable text and vector quality.

A PDF checker such as qpdf --check original.pdf can report structural problems. A clean check does not guarantee that every PDF reader will interpret every resource identically, so also test the file by compiling and inspecting the result.

Worked example: testing a replacement

Suppose this figure causes the warning:

\documentclass{article}
\usepackage{graphicx}

\begin{document}
\includegraphics[width=0.7\linewidth]{figure.pdf}
\end{document}

First confirm that figure.pdf is the file being read when the warning appears. Then create repaired.pdf by exporting the figure again or rewriting it with a PDF tool. Change the inclusion temporarily to:

\includegraphics[width=0.7\linewidth]{repaired.pdf}

Compile again. If the warning disappears and the figure still looks correct, use the repaired copy. If it remains, verify that the replacement really is the file being included and check whether another PDF inclusion triggers the same message.

Common mistakes

• Treating every warning as a failed build. pdfTeX may finish successfully; the important question is whether the output is complete and correct.
• Assuming the main .tex file is malformed. The message usually concerns the structure of an included PDF.
• Changing the output PDF version as a first fix. Settings that control the version of the PDF your document produces do not necessarily repair the resource entries in an input PDF.
• Overwriting the only copy. Keep the original when trying a repair or conversion, and compare the new output visually.
• Ignoring a visible difference. A successful compile does not prove that the included page rendered exactly as intended.