Apple Notes Markdown Import and Export on iPhone: What Actually Converts

Apple Notes now has a direct bridge to Markdown on iPhone, but it is easy to misunderstand what that bridge does. Import turns a Markdown file into a Notes note. Export turns a Notes note into a Markdown file that can live outside Apple’s database. Those are useful capabilities, but they do not make Notes a Markdown editor or guarantee that every Notes-specific object can make a perfect round trip.

That distinction matters in iOS 27 because most “Markdown import/export not working” problems are really one of three things: the control is being looked for in the wrong place, the user expects import and export to be mirror images, or the converted file is being treated as a backup before its contents have been checked.

Import and export begin from different places

Apple’s current iPhone guide puts Markdown import in the Notes app’s folder-level menu. Open Notes, go to the Folders view, tap the More button, choose Import to Notes, select a Markdown file, then choose where the imported note should go. That is a file-to-note operation.

Export begins inside an individual note. Open the note, tap Share, choose Export as Markdown, then choose where to save or send the resulting file. Apple notes that you may need to tap Show More to reveal Export as Markdown in the share sheet. If you are staring at the Folders menu looking for an export command, or inside a note looking for the import command, the feature can appear to be missing even though nothing is broken.

The current Apple instructions are available in its Notes import guide and iOS 27 export guide.

A successful conversion is not the same as a lossless round trip

Markdown is a plain-text markup format. Notes is a richer note system. A Notes document can contain formatting and objects whose behavior is defined by Notes rather than by a universal Markdown rule. Apple documents the import and export commands, but it does not promise that every possible Notes object will survive Notes → Markdown → Notes with identical structure and behavior.

That changes the safest workflow. If the note matters, keep the original note until you have opened the exported .md file in another app and checked the content you care about. Likewise, after importing a Markdown file, inspect the resulting note before deleting or replacing the source file.

This is especially important for notes that do more than hold ordinary text. Headings, paragraphs and simple lists have straightforward text representations. A note that depends on richer Notes behavior deserves a deliberate verification pass rather than an assumption that “export completed” means “everything is preserved.”

Use a small conversion sample to learn the boundary

If you are moving a large archive, do not discover conversion behavior on the entire archive. Make a representative sample containing the kinds of content you actually use: a heading, nested or checked items if relevant, links, emphasis, and any richer objects that matter to your workflow. Export that note as Markdown, open the file outside Notes, and compare it with the original.

For an import migration, do the reverse with a copy of one representative Markdown file. Import it, inspect the note, and confirm that the structure is useful before processing more files.

This is not busywork. It answers a question no generic compatibility list can answer reliably: whether the specific constructs in your notes survive the conversion in a form you are willing to keep.

The destination file is separate from the note you exported

Exporting a note as Markdown creates a file for another destination; it does not turn the live Notes item into a Markdown-backed document. If you later edit the note in Notes, do not assume the previously exported file updates with it. If you edit the exported file elsewhere, do not assume the original note changes either.

That separation is useful. It lets you move a note into a code repository, text editor, documentation system or ordinary file archive without abandoning the Notes copy immediately. It also means you need a deliberate source-of-truth decision if you plan to keep editing in both places.

For one-time migration, export, verify, then choose which copy becomes authoritative. For ongoing interoperability, decide whether Notes or the external Markdown file is the master and repeat the conversion intentionally when needed. Treating both as automatically synchronized invites silent divergence.

If Export as Markdown is missing, diagnose the surface before the phone

Open a normal note and use its Share button. Then look through the available actions and use Show More if necessary. Do not search only in the folder-level More menu; that is where Apple places import, not the per-note Markdown export.

If the action is still absent, check Settings → General → Software Update. A device on an older system can have a different Notes feature set from the current iOS 27 documentation. Our iPhone software-update guide explains the current update path and safe update checks.

A normal restart is reasonable if the Notes interface itself is behaving abnormally after an update. It is not a reason to erase the iPhone, sign out of the Apple Account, or reset network settings. Those broad actions do not logically repair a missing item in a local Notes share sheet. If the phone is genuinely unresponsive rather than merely missing a menu action, use the correct procedure in our iPhone restart and force-restart guide.

If Import to Notes is missing, return to the Folders view

Import is easy to miss for the opposite reason. It is not a command inside the note editor. Return to the main Folders view in Notes, open the More menu, and look for Import to Notes. Select the Markdown file through the file picker and choose the destination Apple provides.

Confirm that the source is actually a Markdown file rather than a document that merely contains Markdown-looking text. A web page, rich-text document or proprietary editor file does not become a Markdown file just because it contains headings with hash characters.

If one known-good .md file imports and another does not, that is stronger evidence about the source file than about the Notes app. Keep the failing original intact while you investigate instead of repeatedly rewriting it in place.

Conversion quality should be judged by meaning, not appearance alone

A Markdown file is meant to encode structure in text. The useful post-export check is therefore not “does this look pixel-for-pixel like Notes?” but “did the information and hierarchy I need survive?” Open the file in a plain-text editor as well as, if useful, a Markdown renderer. That lets you see both the actual markup and its rendered interpretation.

For migration, check headings, list nesting, links and any syntax your destination system relies on. For archival use, confirm that the exported file contains enough context to remain understandable without Notes. For publishing or developer workflows, run the file through the actual destination tool rather than assuming every Markdown parser handles every extension identically.

The same rule applies after import: judge the resulting note by whether it preserves the meaning and structure you need. If a specialized Markdown construct is essential, keep the original file until you have verified the imported result.

Markdown export is portability, not a Notes backup system

The strongest reason to use Markdown export is portability. The resulting text file is easy to store, search with ordinary tools, version in many developer workflows, and open without depending on the Notes interface. That is different from a full Notes backup.

A backup is expected to preserve the information needed to restore the original system state. Apple’s Markdown export documentation describes an export format, not a promise that every Notes-specific behavior or object can be reconstructed from the file. If your goal is disaster recovery for an important Notes library, do not replace your broader device or account backup strategy with a folder of unverified Markdown exports.

The safest migration has a reversible middle

For a few notes, the workflow can stay simple: export or import, inspect the result, and keep the original until you are satisfied. For a larger migration, add one discipline: make the conversion reversible while you are validating it.

Keep source Markdown files when importing. Keep original Notes items when exporting. Test representative content before scaling up. Open the converted result in the tool that will actually use it. Only after that should you decide whether old copies can be archived or removed.

That approach avoids the two worst Markdown migration failures: discovering too late that a feature did not translate the way you expected, and ending up with two independently edited copies without knowing which one is current. Apple Notes now makes the file conversion straightforward; preserving meaning still depends on checking the boundary between a rich note and a plain-text format.