What Is an .ONE File?

Microsoft OneNote Section (.one)

Overview

A .one file is a Microsoft OneNote section: a binary container holding pages of freeform notes, including rich text, ink strokes, embedded images, audio and video recordings, file attachments, and tables. In OneNote's model a notebook is a folder, and each section within it is a separate .one file.

The format is unusual among Office formats in being binary rather than a ZIP of XML parts. It was designed around continuous incremental saving and multi-user synchronisation, which pushed it toward a revision-store structure rather than a document snapshot.

Technical Specifications

Format Details

• MIME Type: application/onenote
• File Extensions: .one (section), .onetoc2 (notebook table of contents), .onepkg (packaged notebook)
• Category: Document
• Structure: binary revision store
• Specification: MS-ONE and MS-ONESTORE, published by Microsoft under its Open Specifications programme
• Introduced: OneNote 2003

File Signatures

OneNote files begin with a 16-byte GUID identifying the store type:

Section (.one):      E4 52 5C 7B 8C D8 A7 4D  AE B1 53 78 D0 29 96 D3
TOC (.onetoc2):      A1 2F FF 43 D9 EF 76 4C  9E E2 10 EA 57 22 76 5F

These GUIDs are the reliable way to identify OneNote content, since the extensions are not widely recognised by generic tooling.

File Structure

OneNote uses a revision store: rather than rewriting the document on each save, it appends new object revisions and updates pointers. The layout is roughly:

.one file
├── Header (1024 bytes)
│     ├── File type GUID
│     ├── File format version
│     └── References to the root file node list
├── File node lists
│     ├── Object space manifests   (one per page group)
│     ├── Revision manifests       (the version history)
│     └── Object declarations and references
├── Object data
│     ├── Property sets            (typed key/value structures)
│     ├── Rich text runs
│     ├── Ink data
│     └── Embedded file blobs
└── Free chunk list                (space reclaimed from old revisions)

Content is modelled as objects carrying property sets, with properties identified by numeric IDs defined in MS-ONE. A page is an object referencing outline objects, which reference paragraph and run objects, and so on.

This design is what enables OneNote's near-continuous autosave and its ability to merge concurrent edits from several devices: two clients can append independent revisions and reconcile them later.

History and Development

OneNote shipped in 2003 as part of Office, aimed at tablet PCs and pen input. The original .one format was revised for OneNote 2007 and again for 2010, when the store gained better support for co-authoring and shared notebooks.

Microsoft published the MS-ONE and MS-ONESTORE specifications as part of the Open Specifications programme following interoperability commitments, which is why third-party readers exist at all. They remain difficult to implement fully: the revision store, property model, and ink encoding are each substantial.

More recently, OneNote's centre of gravity moved to OneDrive and SharePoint synchronisation, where the .one files are stored in the cloud and cached locally. The OneNote for Windows 10 app used a different local store entirely, though Microsoft consolidated back onto the desktop app.

Common Use Cases

• Personal and academic note-taking: lecture notes, research, and handwritten annotations.
• Meeting notes: shared team notebooks with linked audio recordings.
• Project documentation: freeform collections of text, screenshots, and attachments.
• Handwritten and ink content: tablet and stylus input preserved as vector strokes rather than images.
• Clipped web content: pages captured via the OneNote Web Clipper.

How to Open a ONE File

Microsoft applications

• OneNote (desktop): the native application on Windows and macOS. Open the file directly, or use File → Open Notebook.
• OneNote for the web: opens notebooks stored in OneDrive or SharePoint at onenote.com.
• OneNote mobile: iOS and Android apps, working against synced notebooks.

A caveat worth knowing: OneNote expects a notebook structure. A lone .one file separated from its .onetoc2 may open as a standalone section, but relationships to other sections will be missing.

Third-party and open-source options

• libone / libmson: libraries used by document converters to read the revision store.
• LibreOffice: limited import support via those libraries in some builds; expect imperfect fidelity.
• OneNote MCP and export tools: various community scripts export pages to Markdown or HTML through the OneNote API rather than by parsing the file.

Exporting to portable formats

From OneNote itself, File → Export offers:

• PDF: the most faithful fixed-layout export.
• Word (.docx): editable, though freeform positioning is flattened.
• OneNote package (.onepkg): a full notebook bundle for moving between machines.
• Single-file section (.one): the section on its own.

For bulk extraction, the Microsoft Graph API exposes OneNote notebooks, sections, and pages as HTML, which is generally more reliable than parsing the binary format.

Advantages

• Freeform canvas: content can be placed anywhere on a page, unlike linear word processors.
• Rich media: ink, audio, video, and arbitrary file attachments in one document.
• Continuous save and sync: the revision store is built for incremental, multi-device editing.
• Searchable ink and images: OneNote indexes handwriting and performs OCR on pictures.
• Documented: Microsoft publishes the format specification.

Limitations

• Effectively single-vendor: full-fidelity reading and writing is practical only in OneNote.
• Complex binary structure: far harder to parse than the ZIP-and-XML Office formats.
• Poor version control: a binary revision store does not diff or merge in Git.
• Fragile outside its notebook: sections separated from their .onetoc2 lose context.
• Export fidelity varies: freeform layout does not translate cleanly to linear formats.

Related Formats

• DOCX: the ZIP-and-XML Word format, far easier to process programmatically.
• PDF: the usual export target for sharing notes.
• MARKDOWN: the plain-text alternative for notes that need to live in version control.
• CHM: another Microsoft binary document container.