THE FILE FIELD GUIDE
.onepkg

OneNote notebook package

Documents

ONEPKG packages OneNote notebook data for compatible OneNote workflows, rather than universal viewing. Uploading it does not restore a notebook. Check the destination, duplicate names, restored pages and attachments, and current web restrictions.

Main use
Transferring packaged OneNote notebook data
Data type
Binary data / document
All sections, questions and sources

Content reviewed: · Editor:Kai

Example: a practical checking sequence

Example: restore a ONEPKG backup to a new notebook name and location while preserving the package. Verify sections, pages and attachments before deleting anything. For collaboration, use supported OneNote sharing and check access and sync; unpacking alone does not reconnect the original notebook.

Opening steps

Choose your environment or purpose to see its steps.

Unpack in Windows OneNote

Check desktop compatibility and free space.

  1. Save locally and retain an untouched copy.
  2. Open ONEPKG in compatible Windows OneNote and choose the notebook name and destination.
  3. Compare restored sections, pages and attachments with the original inventory.
Transfer to another platform

Unpacking and cloud sharing are separate operations.

  1. Verify the unpacked notebook in Windows OneNote.
  2. Use the app’s supported move or sharing workflow to an appropriate storage location.
  3. Check permissions and sync on the receiving platform and open required pages.

Menu labels and support vary by app, OS and version. Preserve the original before making changes.

Troubleshooting by symptom

  • Browser opening fails: ONEPKG is not a web-viewing document; use supported unpacking and sharing.
  • Old web-import instructions no longer work because that import workflow is deprecated.
  • Duplicate notebook names: distinguish paths and names before deleting any existing notebook.
  • Insufficient space: allow room for both package and unpacked data.
  • Missing pages: ask the sender about export scope and sync completion.

Separate viewing PDF from editable notebooks

  1. Unpack using supported OneNote.
  2. Export PDF for viewing or use notebook sharing for continued editing.
  3. Verify pages, attachments and permissions with the recipient.

Renaming is not conversion; PDF does not preserve notebook structure or sync and may require separate attachments.

A package is not live synchronization

A package is a point-in-time transfer. Later edits to the original do not automatically update the received package.

Record creation date and scope; use shared notebooks for collaboration.

Personal versus organizational accounts

Microsoft’s web export applies to notebooks on personal OneDrive, not identically to work/school OneDrive or SharePoint.

Use OneNote’s supported sharing or migration method rather than merely copying unpacked folders into a sync location.

Source for these steps:Microsoft · Export and import OneNote notebooks / Microsoft · OneNote platform data protection and recovery

Related-format differences

Related-format differences
Format / purposeUse and preserved information
ONEPKGPackaged notebook transfer.
ONESection data.
PDFViewing output, not a replacement for an editable notebook.

Handling and security

Do not automatically execute restored attachments; notebook backups can contain sensitive information, so check storage and sharing permissions.

Questions and answers

Can I restore it directly on the web?

The old import is deprecated; use supported Windows and sharing workflows.

Will it sync with the original automatically?

Unpacking alone does not establish sync with the original shared notebook.

Is it the same as ONE?

ONE is section data; ONEPKG is a package.

Can I delete the package after unpacking?

Keep it until contents are verified and backed up.

Does web export support work accounts?

Conditions differ from personal OneDrive; check current Microsoft documentation and policy.

Format facts: name, steward and MIME type
Formal name
OneNote Package
Steward / specification
Microsoft
MIME type
Check the producer or implementation; do not assume a single universal MIME value.

Primary and official sources