All posts

Share a Markdown File as a Web Page

Share a Markdown file as a web page instead of pasting it into an email. ShareMyPage turns any .md file into a clean page with a link, from the browser or straight from your AI, and keeps your source.

July 9, 2026 · 4 min read

If you want to share a Markdown file as a web page, the usual move is to paste it into an email or a doc and hope. It almost never survives. The formatting dies in the email, the doc tool needs ten minutes of repair, and sending the raw .md file makes the other person find an app that opens it.

This matters more now than it used to. Ask an AI for meeting notes, a project plan, a research summary or a README, and what you get back is Markdown. The writing took thirty seconds. The sharing is where it falls apart.

I built ShareMyPage, and Markdown is a first-class format in it. So take my recommendation knowing it is my product, and read the part about when to use something else.

Drop a .md file on the homepage or your dashboard and the page is live in seconds. Headings, lists, blockquotes, tables and code blocks come out as a designed page. Tables, task lists and strikethrough work, code gets syntax highlighting, and every heading gets an anchor you can link to.

This is for you if:

  • your AI already wrote the words and they need to reach people who were not in the chat
  • the reader is not technical and should not have to know what a repository is
  • you want comments on the document itself, next to the sentence they are about

The rest works like any page. You choose who can open it, from just you up to public, or add a password. Your team can comment on any sentence they select. Replace the content and the link stays the same.

Your Markdown source stays yours

I keep the original Markdown next to the rendered page. You, or your AI, can download it back at any time and keep editing. The page is a view of the file, and the file is still the source of truth.

If the file starts with front matter, its title and description become the page's title and meta description. Without it, the first # heading becomes the title.

Publishing from your AI is the shortest path

If you have the ShareMyPage MCP connected, your agent can publish Markdown straight from the conversation with create_page. There is a dedicated markdown field, and big documents can go through an upload URL instead of squeezing through the chat.

"Turn these notes into a Markdown summary and publish it as a page my team can comment on."

The agent calls create_page, you get back a live link, and the source stays attached for the next edit.

This path did not always work, and I'd rather you hear it from me. Markdown upload worked on the website for weeks. Then I watched an AI agent use the MCP to publish a Markdown document, and the result was a wall of raw text: literal pound signs, visible table pipes. The conversion only existed on the web upload path. The MCP, where Markdown is most likely to show up, stored it verbatim and called it a success.

I fixed it the same day with the explicit markdown field, plus detection for content that is clearly Markdown, so agents that never update their integration still get the right result. A few hours later another session tried Markdown that quoted HTML tags inside code fences and found an edge case in that detection, and I fixed that too. Rendering is now the same pipeline whether the file comes from the browser or the MCP. How I watch agents use the MCP and turn what I see into fixes is its own post.

Images are the real limit

A single Markdown upload has no folder of assets beside it. So an image has to be a full http(s) URL or a data:image URI. A relative path like ./chart.png is dropped.

If your document leans on local images, either host them somewhere first or write the page as HTML, where you can drop the file together with its images.

Use something else when

  • the output is interactive, like a calculator, a chart you can click or a prototype. That is HTML's job, and ShareMyPage hosts that too.
  • you want your own design. Markdown gets my typography and you never touch CSS, which is the point until it isn't.
  • the document lives in a repository and everyone reading it is a developer. Leave it there.

How to do it

From the browser:

  1. Go to sharemypage.app and drop your .md file on the uploader.
  2. Without an account, the page stays up for 3 days and anyone with the link can open it. With a free account, it stays, and a new page starts out visible to just you.
  3. Send the link, or open the page settings to invite specific people, set a password, or make it public.

From your AI, ask it to publish the document with the MCP connected, as above.

The short version

  • Words from an AI: Markdown in, page out.
  • Anything interactive: HTML.
  • Local images: host them first, or switch to HTML.

One tip: sign up before you share anything you'll need next week. The no-account link is fine for a quick look, and it is gone after 3 days.

Publish your own page in about a minute.
Drop in HTML or Markdown from any AI, decide who can open it, and share one link. Free plan, no credit card.