Marked Share: Practical Tips and Common Mistakes When Handing Off Markdown
Reviewed by the FreeOnline.fyi team · Updated 2026-09-14
What actually happens when you paste
You paste Markdown on the left, and roughly 150 milliseconds after you stop typing, the right pane shows the rendered result — sanitized, in your browser, with nothing uploaded. We built Marked Share around exactly one job: you have a README, release note, or set of meeting notes in plain text, and you need to hand it to someone who does not read asterisks.
Because the conversion runs locally, the outputs are self-contained. The share link does not point at a stored document — the document is encoded into the URL fragment, the part after the #. Browsers never send fragments to servers, so the text is not transmitted until you actually send the link to a person.
That design has one honest consequence: link length grows with your document. The source box caps at 20,000 characters, and past 8,000 characters the share-link option switches off, leaving the HTML snippet and the .html download as your paths out.
The share link is the document, not a pointer
When a share link works, it is the fastest hand-off there is: no account, no upload, no expiry to manage. The flip side of no storage is no revocation. You cannot delete a link once it is out, because there is nothing on a server to delete. Treat a share link like the text itself — if you would not paste the words into the chat, do not paste the link either.
Length is where people get caught. Encoding typically adds roughly 30–50% on top of your Markdown, so in our testing a 5,000-character note lands somewhere around 6,500–7,000 characters of URL. Chat clients fold long links, some mail clients wrap them, and a truncated fragment decodes to a broken or partial document.
Our rule of thumb: use link sharing for short notes, then paste the link into the real destination app — not into your own notes app — before you send it. Between roughly 2,000 and 8,000 characters of source, rich text usually serves you better anyway, because it pastes as visible content instead of a URL someone has to trust.
Choosing an exit: rich text, snippet, file, or plain text
Rich text puts formatted content straight on your clipboard, which is what you want for Gmail, Google Docs, Notion, or Confluence. The destination has the final say, though: Docs keeps headings and lists but often drops custom fonts and colors, and some ticketing systems flatten everything into plain paragraphs. Glance at the paste before you hit send.
The HTML snippet is for fields that accept markup — a CMS body, an email template, a static page. It is also one of only two outputs affected by the include-styling toggle. If a CMS strips your tags, that is the CMS's sanitizer, not ours; the CommonMark specification describes what the source should parse to, but no spec can promise what a third-party editor keeps.
Download .html is the format for anything long: one self-contained file with inline styling that opens offline, survives forwarding, and remains available above the 8,000-character cut-off for links. Plain text is the escape hatch for editors that mangle formatting entirely. And if the document is a résumé, a Markdown hand-off is rarely the right final format — a dedicated Resume Builder Top Rated will give you a finished document rather than a URL.
Titles, styling, and the table of contents
The title field defaults to "Untitled note" and accepts up to 120 characters. It feeds the browser tab and the share header, and it is the difference between a link that looks deliberate and one that looks like a stray paste. Spend the two seconds.
The include-styling toggle governs the HTML snippet and the share view only. It does nothing to plain text, and rich text carries formatting regardless of where the toggle sits. If you are pasting into a system with its own house style, turning styling off gives the destination a clean slate.
The table of contents auto-numbers h2 and h3 headings, and hides itself when the document has fewer than two headings. The surprise we see most often is a document built entirely from h1 and h4: no TOC appears, and that is correct behaviour rather than a bug. If you want a contents block, promote your sections to h2.
The mistakes we see most
Raw HTML in your Markdown is stripped — script tags, iframes, and inline event attributes such as onclick do not survive, which is the same class of defence described in the OWASP XSS Prevention Cheat Sheet. Trying to smuggle a widget through the source will not work. A related gotcha: Markdown inside a raw HTML block is not parsed, so text wrapped in a div stays literal.
Tables fail for two predictable reasons. Without a blank line before the table, the header row can fold into the paragraph above, and without the |---|---| separator row there is no table at all — just a line of pipes. Both are easy to spot in the live preview if you actually look at it.
Line breaks trip up chat-style notes: a single newline does not create a break, so you need two trailing spaces or a blank line between paragraphs. In code blocks, if your snippet contains three backticks, fence it with four — otherwise the block ends early and the rest of your document renders as code.
A 30-second hand-off checklist
Write or paste the source and watch the character counter — 8,000 is the practical link ceiling, 20,000 is the hard cap. Fill in the title. Then pick the format from the destination rather than from habit: rich text for docs and email, HTML for CMS fields, the .html file for long documents, plain text for hostile editors.
Before copying, open the collapsible raw output and check the exact string being generated. Five seconds there catches encoding oddities and stray characters, and it is the difference between trusting the tool and hoping. After pasting, read the result once in the destination itself.
Finally, remember what the tool does not do: it stores nothing. Close the tab and the source is gone, and no one — including us — can recover a share link for you. Keep your own copy of the Markdown. Marked Share is one of the browser-based utilities on FreeOnline.fyi, and like the rest it runs without an account, but for anything that matters — a spec, a contract, a client-facing note — verify the rendered output in the place your reader will actually see it.