Before the first check: copy the file. Put a copy somewhere separate and do everything from here on to the copy. Repair attempts on a damaged file can turn a partly recoverable situation into an unrecoverable one, and that is not reversible. Note the copy's size and, if you want to be thorough, its checksum — certutil -hashfile <file> SHA256 on Windows, shasum -a 256 <file> on Mac.

Check 1 — did the file arrive complete?

The most common cause of this message is not corruption inside the file. It is a transfer that stopped early.

Look at the file size and ask whether it is plausible. A section holding a year of notes that shows as 4 KB did not survive the journey. Zero bytes is conclusive. Compare against the source if you still have it — the email attachment, the cloud folder, the backup drive — and fetch it again.

Common ways files get truncated: an interrupted download, a cloud-sync client that is still fetching an online-only file, an email system that clipped a large attachment, or a copy from a failing drive that returned an error someone clicked past.

Check 2 — is Windows blocking the file?

Files that arrive from the internet or from another machine are marked by Windows, and some applications refuse to open them until the mark is cleared. Right-click the file, choose Properties, and if you see an Unblock checkbox at the bottom of the General tab, tick it and apply.

Thirty seconds, and it accounts for a surprising share of “this file must be broken” reports.

Check 3 — is the extension telling the truth?

OneNote decides how to read a file partly from its extension, and extensions get changed by well-meaning people, by email systems, and by unzipping tools. Turn on file extensions in File Explorer (View › File name extensions) and check you have what you think:

  • .one — a section. This is where notes live.
  • .onetoc2 — a table of contents. Contains no page text at all. If you are trying to open one of these expecting notes, this message is the honest answer and no tool will change it.
  • .onepkg — a packaged notebook.

Our reference on the OneNote file formats goes through each in detail if you are not sure what you have.

Check 4 — is it a .onepkg the current OneNote won't import?

The word package in the message is a clue. A .onepkg bundles a whole notebook into one file, and the current Microsoft 365 OneNote does not create or import them.

The way through is to unbundle it. A .onepkg is built on the Microsoft Cabinet (CAB) archive format, so archive tools that understand CAB — 7-Zip on Windows, The Unarchiver on macOS — can generally list and extract its contents, which turn out to be the .one section files you actually wanted. Deal with those individually afterwards.

If a CAB tool also refuses the file, that is a stronger signal of real damage than OneNote's message was, because you have now had two independent readers decline it.

Check 5 — are you using a OneNote that can do this at all?

Only the OneNote desktop app for Windows works with notebooks and section files stored on a local drive. The web version and OneNote for Mac are built around notebooks in OneDrive or SharePoint. If you have been trying this in a browser, that alone can produce a refusal that looks like corruption.

The desktop app for Windows is available as a free standalone download and does not require an Office subscription. Once installed, right-click the .one and choose Open with › OneNote; it appears under Opened Sections, from where you can copy it into a real notebook. Mac users have their own path, covered in opening a local .one file on a Mac.

Check 6 — is there a healthier copy elsewhere?

Before spending effort on a damaged file, spend ten minutes looking for an undamaged one. In rough order of likely success:

  • The OneNote backup folder. Default on current Windows installs: C:\Users\<account>\AppData\Local\Microsoft\OneNote\16.0\Backup\, with a subfolder per notebook and ordinary .one files inside. Older installs use 15.0, 14.0 or 12.0. AppData is hidden by default.
  • OneDrive or SharePoint version history. If the section ever synced, an earlier version may be intact and one right-click away.
  • The Notebook Recycle Bin. Deleted pages and sections are retained there; Microsoft's documentation puts the window at 60 days.
  • Any machine that once opened the notebook. Old laptops and disk images are full of forgotten copies.

Where are my OneNote files stored? lists every path worth sweeping, on Windows and Mac.

What “corrupt” actually means for a .one file

This is the part most pages on this topic skip, and it is the part that decides whether it is worth continuing.

A .one is not a single flat document. It is a revision store: a structured container holding objects and successive revisions of them, so that OneNote can sync incrementally rather than rewriting the whole file on every edit. That design has a genuinely useful consequence when things go wrong — damage to one region of the file does not necessarily destroy the rest. Whole pages, and often older revisions of pages, frequently remain intact and readable inside a file that OneNote as a whole refuses to open.

So a blanket refusal from OneNote is a statement about OneNote's tolerance, not a verdict on the contents. A reader that walks the structure and reports what it can and cannot decode will often get real pages out of a file the app declined.

What that same design does not do is conjure back data that was never written or has been physically overwritten. If the file is 0 bytes, or the drive it came from is failing, the honest answer is that no parser can help and the next step is disk-level recovery or a different copy.

If you are technical: read it directly

Microsoft published the OneNote format specifications, and open-source projects such as onenote2xml, pyOneNote and one-extract read .one files and emit XML or JSON. Running one over a stubborn file is free and tells you quickly whether there is readable content in there. Expect structured output rather than a tidy notebook, and expect coverage to vary between projects and file versions.

If you are not: a focused local tool

OneNote Rescue does the same job in a few clicks, with the output already arranged for reading rather than left as raw XML. It is a small desktop app for Windows and Mac: it reads your own section file on your own computer, walks the structure, and recovers the page titles and note text it can read into plain text, a readable per-page HTML notebook and a JSON report that states what was found and what was catalogued but not extracted.

The two behaviours that matter most for a file you are worried about:

  • It is read-only, and structurally so. Your source is copied to a temporary location and only the copy is read. Nothing is written next to the original; its bytes and timestamp are untouched. A recovery tool should be able to demonstrate it left your file alone, not merely say so.
  • It reports rather than pretends. Where content cannot be recovered, the report says so. There is no hollow declaration of success over an empty result — if a file gives up nothing, you are told that plainly.

Honest scope. OneNote Rescue recovers page titles and note text. From a OneDrive-format section it also writes the embedded images out as real files next to the notebook — along with any other embedded file whose type it recognises by its file signature — each with its SHA-256 recorded in the report. From a classic desktop revision store, embedded files are noted in the report but not extracted in this pass. Ink and handwriting strokes are noted, not converted to text, and any object it cannot identify is listed as present and not extracted rather than guessed into a file. Rich formatting and the exact page hierarchy are simplified into readable text. Nothing is ever decrypted or bypassed: password-protection markers are flagged in the classic revision store, and are not detected in the OneDrive-format container in this pass. And it cannot recover data that is not in the file — a truncated or overwritten section is beyond any parser.

Supported operating systems: Windows 10 and 11 (64-bit), and macOS 10.15 or later. One purchase covers both, so you can recover the files where they already are — no copying them to another machine first.

The order to work in

  1. Copy the file. Work on the copy.
  2. Check the size — is it plausible, or was the transfer cut short?
  3. Unblock it in Properties if Windows has marked it.
  4. Confirm the extension is really .one and not .onetoc2.
  5. If it is .onepkg, extract it with a CAB-capable archive tool.
  6. Try it in the free OneNote desktop app for Windows via Open with.
  7. Look for a healthier copy: backup folder, version history, Recycle Bin, old machines.
  8. Only then reach for a parser or a recovery tool to read what remains.

Most people who arrive at this message finish somewhere around step three or step seven, and never need step eight. That is the outcome we would prefer for you too.