> For the complete documentation index, see [llms.txt](https://docs.reportandrun.com/manual/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.reportandrun.com/manual/faq/c160/c164/q536.md). # My reports aren’t generating or displaying correctly in PDF format – how do I fix it? If your reports fail to save, print, or show text and images properly (e.g. characters missing, images distorted), try: * **(iOS only)** Changing the PDF to version 2: PDF screen > settings > other > PDF version > 2 * Updating the drivers on your computer and printer * Printing from Adobe Acrobat with the option "print as image" selected. [See this article](https://helpx.adobe.com/acrobat/kb/quick-fix-print-pdf-image.html) * Printing the document from a different device (Windows, Android, iOS) If you are unable to resolve the issue, we will try reproducing it on one of our development devices. Please [contact us](/manual/faq/c169/q575.md) with the following information for troubleshooting: * A sample of the document * Relevant screenshots of the issue * The type of device that you are using to print the document * A copy of the report, or a test report, with the error ([as a .jrep file](/manual/report-and-run/data/export-jrep.md), if possible) ## Related * [FAQ: What should I do if the app fails to convert files or export reports to PDF and shows errors?](/manual/faq/c160/c164/q538.md) * [FAQ: How do I fix issues with pending uploads, duplicates, or reports that aren’t saving or syncing between devices?](/manual/faq/c160/c163/q528.md) * [FAQ: Why are there blank spaces between photos and text in my report?](/manual/faq/c160/c164/q535.md) * [FAQ: How do I contact support?](/manual/faq/c169/q575.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 by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://docs.reportandrun.com/manual/faq/c160/c164/q536.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.