The short version of everything people ask. No signup, no fine print.
Copy the response with the AI's copy button (this preserves the Markdown formatting), paste it into the converter at llm2doc.app, and click DOCX. Headings, lists, tables, code blocks, and equations arrive as real Word formatting — not flattened text. It's free, with no signup, and the same three steps work for ChatGPT, Claude, Gemini, Grok, DeepSeek, and Perplexity.
Step-by-step guide: ChatGPT to Word →Partly. ChatGPT's code tool can generate a .docx download, but it isn't available in every mode, the download links expire with the session, and complex tables or equations often don't survive. Copying the Markdown and converting it is the reliable path to a clean, editable document.
ChatGPT export not working? Five fixes →That message comes from ChatGPT's own export, which has a size ceiling. Skip it: copy the replies you need with the copy button under each one (long threads are best copied reply by reply), paste them into the converter, and click DOCX or PDF. There is no size limit on the paste — documents of tens of thousands of words convert in a few seconds — and the PDF is built entirely in your browser.
ChatGPT to PDF, any length →Not from the markers alone: a footnote needs something to say, so a [1] only becomes one when a numbered Sources or References list at the end names that number. Add one — a line per source, "1. Title — https://…" — and the markers turn into footnotes on the next export. Links written inline, like (reuters.com) after a sentence, become footnotes on their own without a list.
Yes — that is research mode. Paste an answer from Perplexity, Deep Research, or ChatGPT's web search and the converter notices the [1] markers, the Sources list, or the parenthesized source links and offers to turn them into footnotes; the same switch, Citations as footnotes, lives in Document setup. Word gets native footnotes at the foot of each page, PDF and HTML get a footnotes section, sources that nothing cites stay in a list at the end, and the text in the editor is left exactly as you pasted it.
The ChatGPT to Word guide →Yes — the sliders button above the preview opens Document setup: A4 or Letter, narrow, normal, or wide margins, a sans or serif body at 10, 11, or 12 pt, page numbers, a contents list built from your headings, and a cover page with title, author, and date. Word gets all of it, including a real contents field (Word offers to update fields when the file opens — say yes and the page numbers fill in; or switch the contents numbers to "On F9" in the panel and Word asks nothing); PDF gets the page size, margins, fonts, cover, contents, and numbers. You can also choose your own Word template (.docx) so its styles, page setup, and headers shape every Word export. Choices are remembered on your device.
Yes. Paste a chatgpt.com/share or gemini.google.com/share link into the editor — nothing else, just the link — and the whole conversation imports: the title as a heading, your prompts as quoted blocks, every answer verbatim with its tables, code, and equations. Then export to Word, PDF, or anything else. Our server reads the public page once and keeps nothing. Claude share pages can't be read by a server yet, so for those copy the conversation and paste it.
ChatGPT share link to Word or PDF →Those markers are Markdown, the format the copy button puts on the clipboard, and Word pastes them literally. Paste the reply into the converter first, then use Copy ▾ → Copy formatted above the preview: the clipboard now holds real headings, bold, lists, tables, and code, and Word, Outlook, or Google Docs paste it as formatting. Copy plain text does the opposite — it strips every marker for places that take only plain text.
Guide: paste ChatGPT into Word with formatting →Yes. Paste the answer, pick Excel in the More formats picker — or hover any table in the preview and click its Excel chip — and download an .xlsx with one sheet per table (pipe tables and HTML tables alike), named after the heading above it. Header rows are bold and numeric cells are stored as numbers, so SUM and sorting work at once. The workbook is built in your browser; nothing uploads.
Markdown table to Excel converter →Not in core Markdown — but nearly every modern renderer adds it as an extension: $…$ for inline math and $$…$$ for display math, written in standard LaTeX. GitHub, Obsidian, Jupyter, and this converter all support it; DOCX export turns equations into native, editable Office Math.
LaTeX in Markdown: cheat sheet & live editor →Yes. The Upload button next to the editor opens .md, .markdown, and .txt files, and converts Word (.docx), .odt, .rtf, and .html files to Markdown — equations as LaTeX, images inlined — so a Word document can be re-exported to PDF, Google Docs, or Excel, or copied into an AI prompt. Dropping a file on the editor does the same; the Markdown-to-Word page has a drop zone too. For many Markdown files at once, the batch converter takes up to 20 and returns one ZIP.
Markdown to Word: upload a file →Yes. Paste formatted text into the editor — a selection from Word, Google Docs, an email, or a web page — and it lands as Markdown: headings, bold and italic, lists, tables, links, and code, converted in your browser as you paste. Paste plain text (Ctrl or Cmd + Shift + V) if you want it untouched.
Yes — the workspace doubles as a Markdown viewer. Drop a .md file on the Markdown Viewer page (or switch the converter to Preview-only and Focus mode) and read it rendered full-window: GitHub-style tables, highlighted code, LaTeX math, Mermaid diagrams, and a Contents navigator. Everything renders in your browser; nothing uploads. Exporting stays one click away, but it's entirely optional.
Open the Markdown viewer →Yes — the converter is one: Markdown on the left, the exact rendered page on the right, updating as you type. The editor has a formatting toolbar (bold, italic, code, links, headings, lists, quotes, tables) with ⌘/Ctrl+B, I, K shortcuts, and the toolbar is context-aware — it disables inside code fences and math blocks where formatting would corrupt the content.
Markdown preview & online editor →Yes — the Share button in the preview compresses the whole document into the link itself (gzip, in the URL fragment), so nothing is stored on any server and the link never expires. The recipient opens a full-window rendered view, no account needed, one click from their own Word or PDF copy. Long documents can exceed practical URL length — the button warns you if so.
Yes. Inline (`$E = mc^2$`) and block (`$$ ... $$`) both render via KaTeX. DOCX exports translate equations to native Office Math (OMML), so they stay fully editable in Word. PDF and HTML render the equations as-is.
That was a real bug — html2canvas mis-positioned KaTeX's fraction bars. It's now fixed: the PDF exporter renders math via the browser's native SVG <foreignObject> path, which lays fractions out correctly.
Free, with no account, no quota, no watermarks, and no trial clock. The PDF, HTML, and Markdown exports are generated entirely in your browser, so serving them costs nothing; the DOCX export takes a brief detour through our Pandoc service to produce native Word equations, and that cost is small enough to absorb. There is no premium tier holding features back: every format, the batch converter, the viewer, share links, and the formatting toolbar are all included. If a paid tier ever appears it would add new capabilities (like cloud sync) rather than paywalling anything that is free today.
Mostly local, with one honest exception: PDF, HTML, Markdown export, and the live preview all run entirely in your browser. DOCX export POSTs the markdown text to our /api/convert-to-docx route so Pandoc can produce a higher-fidelity Word file — the markdown lives in /tmp on the server for the duration of the conversion (a second or two), then the temp files are deleted and the binary is streamed back. We don't log document content, store it, or send it anywhere else. If you'd rather skip the server roundtrip entirely, the converter falls back to a fully-local DOCX path on any failure.
GitHub-Flavored Markdown: headings, bold/italic, lists (nested, with custom start numbers), tables (with alignment), code blocks (with syntax highlighting via highlight.js), inline code, blockquotes, links, images, horizontal rules, strikethrough, task lists, and LaTeX math.
Yes. Code blocks export with monospace fonts and highlighting preserved — 100+ languages auto-detected by highlight.js. Specifying the language (```python) gives the most reliable output.
Markdown images keep their src URLs in HTML/Markdown exports. For DOCX and PDF, cross-origin images are fetched and embedded inline — they render in the document only if the source serves with permissive CORS (most CDNs do; some private hosts don't).
Yes — the batch converter at /batch accepts up to 20 Markdown files at once via drag-and-drop, converts three in parallel while the rest queue, and bundles every result into a single ZIP download. Each file is converted with exactly the same pipeline as the single-document flow, so tables, code highlighting, and LaTeX equations survive in every document, and one failed file doesn't stop the rest — errors are reported per file. It works with DOCX, PDF, HTML, and Markdown output, which makes it practical for migrating a folder of AI-exported notes or a documentation set in one pass.
DOCX, PDF, HTML, and Markdown from the main bar — plus Excel (every table as its own sheet), Open in Google Docs (copies the formatted content and opens a new Doc to paste into), EPUB, PowerPoint slides (split on H2 headings), and copy-for-Notion in the More formats picker. The Copy ▾ menu above the preview copies the whole document as formatted rich text or as plain text.
Yes. The current markdown is saved to localStorage (debounced) and restored on next visit. Documents you exported also appear as cards under the converter — Recent conversions — and one click loads any of them back. Clearing browser storage wipes both.
No — the interface uses a single paper-light theme by design, and exports have always rendered light regardless, so what you see is exactly what prints.
There's no hard cap, but DOCX and PDF generation is CPU-bound on the client. Documents under ~50,000 words export in a few seconds; larger ones may take longer or stress lower-end devices. The browser tab handles all the work.
There are two DOCX paths. The default sends your markdown to /api/convert-to-docx (server-side Pandoc) for highest fidelity — better tables, cleaner equations, nicer typography. If that route is unreachable or fails, the converter falls back to a fully-local DOCX path using the `docx` npm package. Both are good; Pandoc just wins on edge cases.
Modern Chrome, Edge, Firefox, and Safari. The exporter uses html2canvas, jsPDF, the `docx` package, and KaTeX — all of which require ES2020+ and standard Canvas/SVG support.
ChatGPT occasionally outputs inline math as `( x = 1 )` and block math as `[ x = 1 ]` instead of `$x = 1$` / `$$x = 1$$`. Our markdown preprocessor (lib/utils/markdown-preprocessor.ts) detects the pattern (parens/brackets containing backslashes, carets, or underscores — telltale LaTeX) and rewrites them automatically. If something still won't render, search-and-replace those delimiters by hand.
Highlight.js auto-detects 100+ languages, with explicit hints (```python, ```typescript, ```rust) producing the most reliable output. The same GitHub-Light theme renders in the live preview, HTML export, and PDF export. DOCX exports preserve the language hint as a label and use a monospace font with a gray background.
Yes — Recent conversions, right under the converter, keeps your last 10 exports in localStorage: one card per document with its title, the formats it went out as, and when. Click a card to load the document back into the editor; hover and × to forget one, or Clear for all. Stored entirely on your device; nothing about it syncs anywhere.
Three things, all aimed at making LLM-emitted text render correctly: (1) normalizes ChatGPT's parenthesis-wrapped LaTeX to standard `$...$` / `$$...$$`, (2) preserves dollar-sign delimiters that are already correct, and (3) leaves non-LaTeX content untouched. It's intentionally conservative — if a parenthesized expression doesn't look like LaTeX (no backslash, caret, or underscore), it's treated as ordinary prose.
No rate limits on PDF/HTML/MD (those run entirely in your browser; the limit is your CPU). The /api/convert-to-docx Pandoc route is shared infrastructure — under normal use it's instant, but a sustained high-volume batch could hit transient limits. The fully-local DOCX fallback always works regardless.