Apple Notes to Substack: Why Your Formatting Keeps Breaking

You drafted your newsletter in Apple Notes. It looks good. Clean headers, a few bullet points, some bold text, a couple of links. You select all, copy, and paste into Substack.

And now it looks wrong. The headers turned into bold text. Your nested list is flat. The links might or might not have survived. The image you pasted in? Gone entirely.

This is not a one-time glitch. It happens every single time. Millions of people draft in Apple Notes because it is fast, syncs across every Apple device, and is always one swipe away. But Apple Notes was never designed to produce content for publishing platforms. The formatting that looks fine on your phone falls apart the moment it leaves the app.

What Breaks When You Paste

The damage is consistent. Here is what happens to your Apple Notes formatting when you paste into Substack:

Headers become bold text. Apple Notes does not use standard HTML heading tags. It uses a proprietary "Title" and "Heading" style that renders as oversized bold text on paste. Substack sees bold, not a heading. Your table of contents breaks. Your post hierarchy disappears.
Nested lists flatten. You had a three-level outline with sub-points under each main point. Substack receives a single flat list. The indentation is gone. Your carefully structured argument reads like a random collection of bullet points.
Images do not transfer. Apple Notes stores images as embedded attachments in its own database format. The clipboard does not carry them. You paste and the images simply vanish. You have to re-insert every image manually into Substack.
Checklists become plain text. Apple Notes checklists are a custom element. Substack has no idea what to do with them. You get dashes or nothing at all.
Links are inconsistent. Sometimes hyperlinks survive the paste. Sometimes they do not. It depends on how you created the link in Apple Notes, which version of macOS or iOS you are on, and possibly the phase of the moon. There is no reliable behavior.

The pattern is clear. Anything beyond plain text and basic bold/italic is a gamble. And even bold/italic can behave differently depending on whether you paste from macOS or iOS.

Why This Happens

Apple Notes stores your content in a proprietary format backed by a local database (or iCloud sync). It is not HTML. It is not markdown. It is not rich text in any standard sense. Apple designed it for quick capture and personal note-taking, not for interoperability with external editors.

When you copy from Apple Notes, macOS puts several representations on the clipboard: plain text, attributed string data, and sometimes a partial HTML conversion. But that HTML conversion is lossy. Apple's heading styles do not map to <h2> or <h3> tags. Nested list depth is often collapsed. Image attachments are excluded entirely because the clipboard cannot carry binary blobs to arbitrary applications.

Substack, on the other end, expects clean HTML or rich text with standard semantic markup. It needs proper heading tags to build your post hierarchy. It needs standard list nesting to render indentation. It needs image URLs, not embedded attachments. The gap between what Apple Notes puts on the clipboard and what Substack expects is enormous.

This is not a bug in Apple Notes or in Substack. Both tools work fine within their own context. The problem is the translation layer between them. It does not exist in any meaningful way. You are copy-pasting across two formats that were never designed to talk to each other.

The Workarounds (and Why They All Fall Short)

1. Reformat Everything Manually in Substack

This is what most people do. Paste the text, then spend fifteen to twenty minutes re-applying headers, fixing lists, re-inserting images, and re-adding links. For a 1,500-word newsletter, the reformatting takes longer than the writing.

It works, technically. But it is tedious, error-prone, and it defeats the purpose of drafting in Apple Notes in the first place. You wanted speed and convenience. Instead you got a formatting chore at the end of every publish cycle.

2. Use Apple Notes Only for Quick Captures

Some writers keep Apple Notes for jotting down ideas, quotes, and rough outlines. Then they move to a "real" editor for the actual draft. This avoids the paste problem because you never try to move a finished post out of Apple Notes.

The downside is obvious. You now have two writing environments. Your ideas live in one place, your drafts in another. You lose the continuity of working in a single tool. And you still need to pick an editor that exports cleanly to Substack.

3. Draft in Markdown from the Start

Markdown solves the format translation problem because it is plain text with lightweight syntax. A ## is always a second-level heading. A - is always a bullet point. Any tool that reads markdown will interpret your formatting correctly.

The issue: Substack does not support raw markdown either. You still need a conversion step to turn markdown into HTML that Substack accepts. And Apple Notes does not support markdown at all, so you would need to switch to a different app entirely.

4. Paste into Google Docs First

Some writers paste from Apple Notes into Google Docs as an intermediate step, clean up the formatting there, then paste from Google Docs into Substack. Google Docs handles the Apple Notes clipboard slightly better and produces cleaner HTML on copy.

This is a three-step copy-paste chain. Apple Notes to Google Docs to Substack. Each step can introduce its own formatting quirks. It is fragile, slow, and one more tool in an already crowded workflow.

The Real Problem: You Are Writing in the Wrong Tool

All of these workarounds treat the symptom. The symptom is broken formatting on paste. The underlying problem is that Apple Notes was built for personal note-taking and Substack was built for newsletter publishing. They occupy different worlds with different format assumptions. No amount of clipboard gymnastics will bridge that gap cleanly.

If you publish a newsletter regularly, you need a writing tool that understands publishing. That means a tool that stores your content in a format compatible with Substack, Ghost, WordPress, and other platforms. That means markdown or clean HTML under the hood, not a proprietary database format.

The best writing apps for Substack share a few traits: they give you a visual editor so you do not have to memorize syntax, they store content in a portable format, and they export clean output that publishing platforms accept on the first paste.

What a Publishing-Ready Editor Looks Like

The fix is not to abandon Apple Notes. It is a great capture tool. The fix is to stop using it as your primary drafting environment for content you plan to publish.

A publishing-ready editor does three things that Apple Notes cannot:

Stores content in markdown. Your formatting is never trapped in a proprietary format. Headers are headers. Lists are lists. The underlying text is portable and convertible to any output format.
Shows you rich text while you write. You do not need to stare at raw markdown syntax. A good WYSIWYG markdown editor renders your headers, bold text, lists, and links in real time. It looks and feels like Apple Notes, but the underlying format is clean.
Exports clean HTML. When you are ready to publish, you export. The output is semantic HTML that Substack, Ghost, and WordPress render correctly. No reformatting. No manual cleanup. No intermediate steps.

Athens is a markdown WYSIWYG editor built for exactly this workflow. You write in a visual editor that feels familiar. AI editing is built directly into the document, so you can select a paragraph and ask it to tighten, restructure, or simplify without leaving your draft. When you are done, you export clean HTML and paste it into Substack. The formatting works on the first try.

No three-step copy-paste chain. No reformatting. No lost images (export your images separately and upload them to Substack, or use Substack's image tools directly). Your headers are headers. Your lists have the right nesting. Your links work.

Here is the workflow that eliminates the Apple Notes-to-Substack formatting problem:

Capture ideas in Apple Notes. Keep using it for what it is good at. Quick thoughts, links, quotes, rough outlines. It syncs everywhere and it is fast.
Draft in a markdown editor. When you sit down to write the actual newsletter, move to a tool that stores content in markdown. Type or paste your notes in and start structuring.
Edit with AI. Use built-in AI to tighten sentences, cut filler, and improve clarity. Review inline diffs so you see exactly what changed and keep your voice intact.
Export and publish. Export as HTML. Paste into Substack. Hit publish. Total formatting cleanup time: zero.

This workflow keeps Apple Notes in the picture. It just stops pretending that Apple Notes is a publishing tool. The drafting and editing happen in a tool designed for it. The publishing platform receives clean input. Nobody spends twenty minutes re-bolding headers.

Stop Reformatting. Start Publishing.

The Apple Notes-to-Substack formatting problem is not going to fix itself. Apple has no incentive to make its clipboard output compatible with Substack. Substack has no incentive to parse Apple's proprietary format. The gap between these two tools is structural, not incidental.

You can keep fighting the clipboard. Or you can write in a tool that was built for publishing. The ideas start in Apple Notes. The finished newsletter starts in a real editor.

Try Athens and see what your Substack workflow looks like without the formatting cleanup step. For more on building an efficient newsletter process, read our guide on how to write a newsletter with AI.