A Document That Lives in Its Link — No Account, No Storage, No Upload

What is actually new here

The new part is not Markdown, and it is not link sharing. It is the removal of the middleman. A normal shared document has two things: the content and a place that holds it. Link Doc collapses them into one. The content travels inside the address itself, so there is no backend to trust, no signup form, no "your files are stored in our cloud" policy to read, and no account that can be locked, breached, or deleted.

In practice this changes the feel of sharing a short document completely. You do not invite anyone, grant anyone permission, or wait for anyone to accept. You paste a link into a chat, an email, or a message, and the recipient clicks it and reads. They do not need an account either. They do not even need to know the tool exists — the link opens straight to the rendered document.

It also changes who holds the document. Nobody does, except the people holding the link. The page itself says it plainly: the part after # never leaves your browser as a server request, and there is no account and no way to recover a document once its link is lost. That is not a bug in this design. It is the design.

How to use it

Open /text/link-doc/ and start typing in the editor. The supported Markdown covers the everyday set: headings, bullet and numbered lists, blockquotes, horizontal rules, code blocks, inline code, bold and italic text, and links. Links are restricted to http:, https:, and mailto: addresses, and they open with rel="noopener" in a new tab — anything else is rendered as plain text rather than a clickable link.

Every edit is written into the address bar automatically. You do not press save, and there is no save button to forget. When the document reads the way you want it, copy the link from the address bar and send it. That is the entire workflow: write, copy, send.

The recipient gets a read of the document as you sent it. If they edit their copy, they are editing their own version — their changes go into their own link, not back into yours. Think of sharing as sending a copy, not granting access to a shared original. If you revise the document, send the new link; the old link still shows the old version.

One practical note: very long documents make very long links. The tool warns as a link approaches roughly 1,800–2,000 characters, not because the browser cannot handle more, but because chat apps wrap or truncate long links and a truncated link is a broken document. Keep Link Doc documents short — a page or two of Markdown, not a novel.

Markdown preview: Edit, Split, Preview

Link Doc already renders Markdown as you type — preview is not a missing feature, it is one of the three modes at the top of the page. Split is the default: editor on the left, rendered preview on the right, updating live on every keystroke, so you see headings, lists, quotes, and code blocks exactly as the recipient will. Preview hides the editor and shows only the rendered document, which is the view to check before you copy the link. Edit shows only the source, for longer writing stretches.

Two preview details matter. First, the renderer escapes all source text before rendering, so what you type cannot inject scripts into the preview; images are not supported at all — only their alt text is shown — and links are limited to http:, https:, and mailto:. Second, a recipient who opens your link sees the same Split view by default and can switch to Preview themselves; preview is a way of looking at the document, not a separate file. If you need the source, the Download button saves it as a .md file; if you need to share, copy the link.

What it is good for

Link Doc fits the documents that are short, self-contained, and meant to be read as-is:

• A quick brief or explainer. Meeting notes, a how-to, a decision summary, a reading list. Write it, send the link, done.
• A checklist or agenda. A packing list, a release checklist, a workshop agenda — things people open once, scan, and act on.
• A draft you want eyes on, fast. A blog outline, a product note, a proposal sketch. The recipient does not need to install anything or create an account to read it.
• Anything you would otherwise paste as a giant block of text into chat. A link is cleaner, renders with headings and lists, and survives copy-paste far better than raw Markdown in a message box.

In all of these, the advantage is speed and zero friction: no accounts on either side, no storage to manage, no permissions to configure.

What it is not good for

The same design rules out a whole category of uses, and reaching for Link Doc there will frustrate you:

• Collaborative editing. There is no shared original to co-edit. Two people editing at once produce two separate links, and there is no merge.
• Access control. Anyone with the link can read the document. There is no password, no expiry, no revoking access, and no view log. If you need any of those, use a tool built for them.
• Long-term archiving. If the link is lost, the document is gone. There is no account to sign back into and no recovery flow. Anything you want to keep for years should also live somewhere durable — your own notes, a file, a version-controlled document.
• Sensitive information. Passwords, private keys, personal data, internal company details, anything you would not paste into a chat message — do not put it in a Link Doc. The link itself is the content, so forwarding, screenshotting, or pasting the link anywhere shares the whole document. Treat every Link Doc link as public to whoever receives it.

The privacy boundary, stated plainly

Link Doc's privacy story is unusually simple, which is a strength — but only if you understand it. The content is not uploaded to or stored on a server, and the fragment after # is not sent to the server when the page loads. At the same time, the content is not encrypted, protected, or access-controlled in any way. Whoever holds the link holds the document, in full, forever, with no way for you to take it back.

So the rule is short: use Link Doc for documents you are happy for the recipient to keep, forward, and quote. Do not use it for anything you would regret seeing forwarded. That single rule, applied consistently, keeps the tool's greatest convenience from becoming its greatest mistake.

The bottom line

Link Doc is a small idea executed cleanly: a document that is its own link. No account, no storage, no upload, no permissions to manage — and, by the same token, no collaboration, no access control, and no recovery. For short, shareable, low-sensitivity documents, that trade is a clear win: write it, copy the link, send it, and the recipient is reading in one click. For everything else, pick a tool whose trade-offs match the job — and keep Link Doc for the quick shares it was built for.