> For the complete documentation index, see [llms.txt](https://docs.apryse.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.apryse.com/cli/pdf2xps/troubleshoot.md). # Common solutions when troubleshooting PDF2XPS Learn why white spaces appear between pictures in XPS files and how to avoid aliasing artifacts. Discover solutions for rasterization, font rendering inconsistencies, and more with PDF2XPS conversion. ### **Why is a white space separating neighboring pictures?** In some cases, XPS viewers that support anti-aliased rendering produce line/space artifacts at neighboring picture elements (e.g. for image tiles or polygons sharing common edges). These artifacts are not a byproduct of PDF2XPS conversion, but are produced due to anti-aliased rendering in the XPS viewer. The same issue applies to the input PDF document however the current PDF viewers are typically better at handling this type of issues. The aliasing artifacts should not be visible during printing or high-resolution output. ### **Why are some pages rasterized?** Occasionally, there will be PDF elements that have no equivalent in XPS. In these cases PDF2XPS will by default render the necessary elements at 92 dpi or at the resolution given by the '---dpi' parameter. In other select cases, to generate the exact appearance of the original PDF document, an entire page may need to be rendered. In these cases rendering can be disabled using the '--norender' option. Disabling rendering will preserve resolution independent properties of input PDF documents (including fonts, paths, and shadings) as well as text selection and extraction capability in XPS processing software. ### **Why are some fonts in PDF not rendered consistently?** PDF format, unlike XPS, does not require mandatory font embedding. As a result PDF consumers, such as PDF2XPS and your favorite PDF viewer, need to find substitute fonts for missing fonts on the client system. Unfortunately, this means that there is no guarantee that file will render accurately on different systems or even in different PDF viewers. Default font substitution can be overridden using [PDF SDK](https://apryse.com/products/core-sdk/pdf) which offers additional options that are not available in the PDF2XPS Command-Line Utility. To avoid font substitution errors, simply make sure to create PDF documents with all fonts embedded. --- # 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.apryse.com/cli/pdf2xps/troubleshoot.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.