EEditSnappy

AI Rewrite Stripped My Formatting — How to Keep It

You highlighted a nicely formatted paragraph — bold key terms, a couple of links, a bulleted list — asked the AI to tighten it, and got back a single grey wall of plain text. Now you’re re-bolding, re-linking, and rebuilding bullets by hand. You spent more time fixing the formatting than the rewrite saved.

This is one of the most common reasons people abandon inline AI editors, and it comes from a design shortcut almost all of them take.

Why it happens: the round-trip throws structure away

Your text isn’t just characters. In a document, an email, or a markdown editor, it carries structure: which words are bold, which are links, where the bullets and headings are, where the line breaks fall. That structure is stored alongside the text as rich-text formatting (or as markdown syntax).

When an inline AI tool grabs your selection, it usually takes the simplest possible path: it reads the selection as a raw plain-text string. Everything that isn’t a literal character — the bold, the links, the list structure — is discarded at the moment of reading, before the AI ever sees it.

From there it’s hopeless. The AI receives Our Q3 results beat target by 12 percent see the report instead of a bulleted, bolded, linked version. It rewrites the plain text, returns plain text, and the tool pastes plain text back. The formatting was gone before the model touched it.

There’s a second, subtler version: the tool does read rich text, but when it writes the result back via a clipboard paste, it pastes as plain text (or the host app interprets the paste as plain). Same flat result, different step.

Why “just re-format it afterward” isn’t a fix

It feels minor on one paragraph. But the whole promise of inline editing is speed — select, press, done. If every rewrite costs you 30–90 seconds of re-bolding and re-linking, the tool has a negative time budget. For people doing this dozens of times a day, formatting loss isn’t an annoyance; it’s a dealbreaker.

How to actually keep your formatting

1. Work in markdown where you can

In markdown-native apps (Obsidian, many note tools, anything where bold is literally **bold**), the formatting is plain text — **, [](), -. A tool that reads and writes raw text can preserve markdown by accident, as long as it’s told to leave markdown syntax intact and not “clean it up.” If your tool supports a “preserve markdown” instruction or a structure-safe mode, turn it on. (See Structure-safe edits in the inline-workflow silo for more on protecting syntax.)

2. Prefer tools that capture rich text, not just a string

The real solution is architectural: the tool must read your selection with its formatting, send the AI a representation that carries structure (rich text or markdown), and reconstruct the formatting when it writes the result back. This is harder to build, which is exactly why most tools skip it — but it’s the only way bold, links, and bullets survive a rewrite in a rich-text editor like Word, Google Docs, or Gmail.

3. Test before you trust it on real work

Run a quick check on a throwaway paragraph with bold, a link, and a bullet list. If it comes back flat, the tool reads plain text — and no setting will fully fix that. Better to know before you flatten a client document.

4. Use the diff/undo safety net

Even with a good tool, occasionally check the result. A tool that shows you the change before it commits (and lets you undo instantly) means a formatting surprise is never permanent.

How EditSnappy fixes this at the root

EditSnappy is built to preserve your formatting on replace, not flatten it. Bold, links, bullets, line breaks and markdown survive the rewrite — so there’s no re-formatting tax after every edit. It captures the structure of your selection, keeps it through the AI round-trip, and reconstructs it when the new text lands.

And because EditSnappy shows the change as a diff before it commits — Tab to accept, Esc to keep your original — you’d catch any formatting surprise before it ever touched your document, with one-key undo as a backstop.

See how EditSnappy works and try it free on your own formatted text.

Part of the Why Inline AI Editors Fail troubleshooting hub · EditSnappy home.