Why Apple Notes’ Native Markdown Export Corrupts Large Libraries

macOS 26 Tahoe and iOS 26 gave Apple Notes something it never had before: a real, built-in way to export notes as Markdown, including selecting several notes at once and exporting them in one action. It is a genuinely useful feature, and we covered what it does well and where it falls short back in August. What that earlier piece did not cover, because it was not yet clear how serious it was, is a separate, more damaging problem: a bulk export of a large library can come back corrupted.

This is not a guess or a rumor picked up secondhand. It is documented in specific, dated posts on a public forum, with exact quotes describing exactly what went wrong. This guide walks through precisely what is confirmed, what is only a single report, and how to protect a large Apple Notes library if you need to export it before Apple fixes anything.

Where This Bug Is Documented

The clearest account sits in a MacRumors Forums thread titled “iPadOS 26 data corruption when exporting notes,” opened October 7, 2025. The original poster describes running a bulk Markdown export of a large notes library and getting corrupted output back, not a crash, not an error message, just files that silently came out wrong.

We could not find a matching report on Reddit, Apple’s Developer Forums, or in mainstream tech coverage of the Markdown export feature. That does not mean it is rare, plenty of real bugs go unreported by most of the people who hit them, but it does mean this is currently a thinly corroborated issue rather than a widely confirmed one. What makes it worth taking seriously anyway is how specific and consistent the reports are, and that a second, independent report turned up months later describing the same symptom on a different device and a newer macOS version. That pattern is covered below.

The Exact Symptoms, Quoted

Reading the thread closely, three distinct problems show up, and it is worth separating them because they call for slightly different caution.

• Duplicated lines. An exported Markdown file contains the same lines repeated multiple times, more than doubling what should be a short note.
• Blank files. Some notes export as a file with no content in it at all, despite the original note being intact in the Notes app.
• A different set of files each time. A follow-up reply in the same thread notes: “each time an export is done a different set of random files are corrupted,” meaning re-running the export does not reliably reproduce, or fix, the same failures.

The same thread flags a fourth issue worth knowing about even though it is a separate mechanism from the corruption bug: notes are overwritten in the export folder if two of them share an identical title. The thread states this bluntly, in capitals, as a standalone warning. It is not random or intermittent like the corruption bug; it is a predictable consequence of how the export writes files by name, so it is easy to avoid once you know about it.

How Many Notes Does It Take?

The original poster gave a specific number: “This happens when exporting over 100 notes on iPadOS 26.0.1.” That is a real, directly quoted figure, and it is the reason 100 notes shows up as a rough line in the title of this guide. But it is worth being precise about what that number actually is: it is one person’s own reproduction point on one device and one iPadOS version, not a threshold Apple has confirmed or that a broad sample of users has independently measured.

Treat it as a useful warning sign rather than a hard rule. If your library is smaller than 100 notes, that is not a guarantee you are safe; if it is larger, that is not a guarantee you will hit the bug. The one piece of advice that holds regardless of the exact number is the practical one covered further down: export in batches, and check what comes out.

Is It Still Happening in 2026?

Based on the public record, yes. A reply posted January 7, 2026, from a different user on a different device, describes the same core symptom on a newer OS version:

That is three months after the original October 2025 report, on macOS rather than iPadOS, and on the 26.2 point release rather than 26.0.1. It is still a single additional corroborating report rather than a mass of them, but it is meaningful specifically because it is independent: a different person, a different platform, and a later OS build, describing the same failure mode. We found no Apple Feedback Assistant reference number, support article, or changelog entry addressing this issue in either report or anywhere else. Until Apple says otherwise, the safest assumption is that it is unresolved.

Why This Probably Happens

Apple has not explained a cause, so anything here is informed reasoning rather than a confirmed mechanism. The pattern reported, different random files failing on each run of the same export, is more consistent with a timing or resource issue in how the export writes many files in quick succession than with a problem in any single note’s content. A bulk export of a large library means reading and writing a lot of files back to back in a short window, and that is exactly the kind of operation where a race condition or a buffer that is not fully flushed before the next file starts tends to show up as intermittent, file-specific corruption rather than a clean crash. This is a plausible explanation, not a diagnosis Apple has confirmed.

Originals Are Safe, Exports Are Not

The real risk is a quieter one: you run a bulk export to make a backup, the export looks like it finished normally with no error message, and you assume it worked. If you do not open the files to check, a corrupted or blank export can sit there for months looking like a valid backup until the day you actually need it, which is the worst possible moment to discover it is not.

How to Export a Large Library Without Losing Anything

1. Export in batches well under 100 notes at a time, rather than selecting your whole library and exporting it in one action. Smaller batches are also easier to spot-check.
2. Check for duplicate note titles before you export. Rename any notes that share an identical title first, since the same thread documents that duplicate titles cause one exported file to silently overwrite another, independent of the corruption bug.
3. Open several exported files after each batch. Compare the line count and content against the original note in Notes. This is the only reliable way to catch a blank file or duplicated lines before you rely on the export.
4. Do not delete or overwrite your last known-good export until the new batch has been checked, so a bad run never becomes the only copy you have.
5. Consider a tool that does not use Apple’s native export pipeline if you need to export a large library regularly. Apple Notes Exporter Pro reads your notes directly and writes each file through its own export code rather than calling File > Export as Markdown, so this specific, documented bug in Apple’s pipeline does not apply to it.

Native Export vs a Dedicated Exporter

Not using Apple’s native export pipeline is not proof any tool, including ours, is free of every possible bug. It does mean this specific, documented issue does not apply, since it is tied to how the native feature itself writes files during a bulk export.

Already Exported a Large Library? Check It Now

If you have already run a large bulk Markdown export on iPadOS 26.0.1 or later, or on macOS Tahoe, it is worth a few minutes to check rather than assume it worked. Open a random sample of the exported files, ideally at least a dozen spread across the batch, and compare each one against the original note in Notes. Look specifically for a file that is empty when the note is not, or a file where a paragraph appears to repeat itself. If you find either, the fix is straightforward: re-export just the affected notes in a smaller batch and check those results too. Because your original notes are untouched, there is nothing to recover, only the export to redo.

Sources

Frequently Asked Questions

The Bottom Line

This bug is real, documented in specific, dated, directly quoted reports, and still unaddressed by Apple as far as any public record shows. It is also, so far, thinly corroborated rather than a mass-reported epidemic, which is exactly why it is easy to miss: an export that finishes without an error message looks successful whether or not the files inside it are actually intact. If you are exporting a large Apple Notes library, export in batches, check what comes out, and keep your previous export until the new one passes that check. That habit costs a few minutes and protects you regardless of whether this specific bug is ever officially fixed.

Keep reading: see what else macOS 26’s native Markdown export gets right and wrong beyond this bug, learn how to automatically back up Apple Notes on Mac so a bad export is never your only copy, or browse every Apple Notes export and backup guide.