> 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/tips-miscellaneous/export-ole-objects-to-pdf.md).

# Can I export OLE objects to PDF?

Starting with version 4.08, SWING PDF Converter supports OLE objects as binary attachments.

This means that embedded OLE object will be attached as file attachment to PDF document with the correct file extension.

{% hint style="info" %}
**Note:** Please contact us at <support@swingsoftware.com> if your OLE object is not recognised as correct file type attachment.
{% endhint %}

Earlier Swing PDF Converter versions:

OLE objects and objects gathered from a file will be exported to the PDF document and displayed just as they are seen in the Notes documents when opened for Print Preview.&#x20;

Note however that some OLE objects or controls cause issues in Notes, such as Notes crashing etc.\
However, if you can view these objects properly in Print Preview and in Read mode then they will also be converted to PDF properly, since PDF Converter basically renders a Read mode representation of Notes documents to PDF format.


---

# 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/tips-miscellaneous/export-ole-objects-to-pdf.md?ask=<question>&goal=<user_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.