What a copied DeepSeek answer contains
- DeepThink (R1) answers can copy with the whole <think>…</think> reasoning block ahead of the answer.
- Maths and units as LaTeX — \( \), $…$, \frac{}{} — which word processors show literally.
- Markdown with ### headings, long numbered lists with bold lead-ins, pipe tables and fenced code.
- Occasional full-width Chinese punctuation (,、:) in English answers.
- Dense paragraphs with em dashes and colons chaining clauses.
What is different about DeepSeek's output
DeepSeek's thinking models reason before they answer, and that reasoning leaks into the clipboard more often than people expect. The official app keeps it in a collapsible panel and leaves it out of the copy button's output, but a drag-select from above the answer takes it, the API returns it inside <think> and </think> tags, and so do local models through Ollama or LM Studio and most third-party chat clients. The result is an answer with several paragraphs of first-person deliberation in front of it — and, in analytical answers, draft tables that look like the real one.
Underneath that, DeepSeek's markdown has its own habits: ### headings even at the top level, long numbered lists with a bold lead-in on each item, pipe tables for anything comparative, fenced code with language tags, LaTeX for any maths — \( x^2 \), $\frac{a}{b}$ — and the occasional full-width Chinese comma or colon in an English sentence. Its paragraphs are dense, chaining clauses with em dashes and colons.
Removing the formatting, or converting it
The editor above removes. With Remove citations on, which it is by default on this page, the <think> block is removed on paste. The markdown goes with it: headings become plain lines, links become readable text with the address, hidden characters are stripped, and bold and bullets can be kept as Unicode characters that plain-text boxes cannot strip. That is the tool for posts, proposals, plain email, CRM notes and forms. The preferences add the rest — replace the em dashes, straighten the quotes, strip italics, code and tables — and the full-width punctuation is visible in the output for a quick manual fix.
The destination pages convert. DeepSeek to Word and DeepSeek to Google Docs drop the reasoning and turn the markdown into real headings and lists, with notes on getting the LaTeX rendered in each. DeepSeek to Excel and DeepSeek to Google Sheets ignore the reasoning block — and the draft tables inside it — and type the numbers in the answer's tables. For Gmail, Outlook, Slack, Notion and the chat apps, the platform formatters linked above read the same markdown; the reasoning block is removed on paste there too.
LaTeX, and the prompt that avoids it
No page on this site converts LaTeX, because a wrong rendering is worse than the source. Word renders LaTeX natively through Insert → Equation in LaTeX mode; Docs accepts a subset in its equation editor and the rest through an add-on; spreadsheets keep it as text. The reliable fix is upstream: ask DeepSeek for "plain-text maths, no LaTeX" and it writes x², a/b and × from the start. Likewise, "no reasoning" keeps the <think> block out of the answer where the client supports a non-thinking mode, and "final table as CSV, numbers only" produces a table that pastes as columns anywhere.
The tell, and what to do about it
A cleaned DeepSeek answer reads as a dense, numbered, bolded briefing, which is its own kind of generated-text tell: every item a bold phrase and a colon, every paragraph the same weight, a dash in each one. The tools here fix the punctuation and the markup in one paste — the em dash remover covers the dash question — and the structure you loosen by editing: unbold the lead-ins that are not headings, merge the list items that are one point, cut the restatement at the end. Formatting makes the text look typed; editing makes it read written.