Supported OneNote Content and Known Limitations
Aspose.Note for .NET can create, read, edit, save, and convert Microsoft OneNote documents. OneNote files can contain content produced by different OneNote versions and applications, so support depends on the content type and the file format features used by a document.
This page summarizes the main OneNote content areas that are supported by Aspose.Note for .NET, and the known areas that have limited or no support.
Support Status
| Status | Meaning |
|---|---|
| Supported | The content type is represented in the Aspose.Note object model or supported by the documented loading, saving, and conversion APIs. |
| Limited | The content type can be processed in common scenarios, but some OneNote-specific data, layout, rendering, or round-trip behavior may not be preserved. |
| Not supported | The content type or file format feature is not currently supported. |
Supported Content
| Content area | Status | Details |
|---|---|---|
| Document structure and pages | Supported | Documents, pages, page titles, outlines, outline elements, and outline groups are available through the Aspose.Note document object model. |
| Rich text and text styles | Supported | Text content and common text formatting can be read, edited, created, and saved. |
| Tables | Supported | Tables, rows, and cells can be accessed and processed programmatically. |
| Bulleted and numbered lists | Supported | List content and list properties can be read and created. Some exact layout rendering cases are listed under known limitations. |
| Embedded images | Supported | Images stored inside the OneNote document can be read, inserted, saved, and exported. |
| Attached files | Supported | Files attached to a OneNote document can be retrieved and added. Export layout limitations are listed below. |
| Hyperlinks | Supported | Hyperlinks can be added to text and images. |
| Tags and Outlook tasks | Supported | Basic note tags and Outlook task information can be accessed, added, and rendered. Advanced task metadata and layout limitations are listed below. |
| Loading, saving, and conversion | Supported | Aspose.Note for .NET supports creating and loading OneNote documents, saving documents, and converting documents to formats such as PDF, images, HTML, and Word. |
| File format detection | Supported | The API can determine the OneNote file format so applications can handle format-specific behavior explicitly. |
Known Limitations
| Content area | Status | Details |
|---|---|---|
| OneNote 2007 file format | Not supported | Documents stored in the old OneNote 2007 format are not currently supported. |
| Old or nonstandard OneNote variants | Not supported | Some older or nonstandard .one files can be rejected as an unsupported file type or unsupported file format version. |
| Drawings, ink, and free-hand annotations | Limited | Preserving or saving drawing and ink objects is not currently supported. Documents that contain this content should be tested before round-tripping through Aspose.Note. |
| Mathematical formulas and equations | Limited | Formula support is limited. Formulas may not be preserved or rendered with the same visual fidelity as in Microsoft OneNote. |
| Encrypted OneNote Online documents | Not supported | Encrypted documents in the OneNote Online format are not currently supported. |
| OneNote Online Package Store metadata | Limited | Saving some OneNote Online documents can lose Package Store-specific metadata. This can matter for documents that must continue syncing through OneDrive or SharePoint after modification. |
Images stored outside the .one file | Limited | Embedded images are supported. Images referenced from an external onefiles folder can have limited support. |
| Rule lines | Limited | Page rule lines may not be preserved when saving a document. |
| Page background images during export | Limited | Page background images can have limited support during export. |
| Advanced tags, tasks, and list layout | Limited | Basic tags, Outlook tasks, and lists are supported, but advanced task metadata and exact tag or numbered-list positioning can differ from Microsoft OneNote. |
| Attached-file visual layout during export | Limited | Attached files are supported, but the visual size and position of attached-file placeholders can differ during PDF or image export. |
Recommendations
When your workflow requires full visual fidelity or document round-tripping, test representative OneNote files before using them in production. Keep the original documents when preserving all OneNote-specific metadata is critical.
For documents stored in OneDrive, SharePoint, or another sync-sensitive environment, verify the saved document in the target environment before replacing the original file.
If a document contains unsupported content, contact support and provide a sample file that demonstrates the issue.