URL to Markdown Converter

Your URLs. Ready to work.

Public sources, ready for your notes and AI.

Choose one supported file to get started.

Conversion details & limits

URL to Markdown Converter for One Public Page.

Paste a public HTTPS page or a supported document or video link. This webpage to Markdown (URL to MD) workflow produces a portable Markdown (.md) file. Fetch, review the estimate, then confirm.

Public links only. Some sites restrict access, and remote images are not downloaded. Failed conversions spend no Credits.

01 / How it works

From a public link to useful Markdown.

01

Authorize

Paste a link and click Fetch. Each source uses its own reading method; no site login is needed for public content.

02

Validate

Review the extracted word count, or audio duration for YouTube, and the Credit ceiling before you start the conversion.

03

Review

The bundle contains sanitized Markdown, metadata, a source map, quality evidence, and a verifiable manifest.

02 / What you get

The same explicit contract in API, CLI, and MCP.

REST API
POST /v1/url-estimates
{"url":"https://example.com/report",
 "accept_remote_fetch":true}
CLI
markovo url-convert https://example.com/report \
  --out runs/report --max-credits 1 \
  --accept-remote-fetch
MCP
markovo_convert_url({
  "url": "https://example.com/report",
  "max_credits": 1,
  "accept_remote_fetch": true
})
03 / Source details

Review output from the URL to Markdown Converter.

Public webpages use a bounded static fetch. Supported provider links use their own reading methods: Google Docs exports the document, GitHub and Hacker News expose structured content, Notion exposes public blocks, and YouTube supplies audio for transcription. Each Fetch handles one link.

PUBLIC

Use a page anyone can access

Public webpage targets must resolve to public network addresses and allow fetching under their current robots rules. Source adapters have additional access and size limits, described on each provider page. Private login credentials and customer headers are never forwarded.

STATIC

Read the available webpage content

For general webpage links, client-side dashboards, personalized pages, infinite scrolling, and text that only appears after interaction may be absent. The webpage reader does not execute active scripts or recursively import remote images and linked pages.

REVIEW

Check attribution and update timing

Confirm headings, links, lists, code, and tables against the public page. Keep the source URL and fetch metadata with the Markdown when freshness, citation, licensing, or later changes matter.

04 / Connect your tools

Use imported Markdown as a dated public-page snapshot.

A successful fetch records what the bounded route could read at that time; it does not promise that the page will remain unchanged or that every dynamic element was present. Before publishing, check the canonical source, author, date, headings, links, code blocks, tables, legal notices, and attribution. For RAG, retain the source URL and fetch metadata so results can be refreshed or traced. Respect copyright, site terms, and robots policy. If access requires an account, cookie, payment, private network, or bypass, do not use this route. Paste only a public page you are authorized to fetch.

For sources that change — changelogs, pricing pages, live documentation — re-fetch before relying on an older snapshot; each conversion is tied to a dated entry in your account history, so staleness is checkable.

05 / Ways to use your Markdown

Refresh changing sources.

Recheck important sources before relying on an older snapshot of a public page.

URL to Markdown: what converts cleanly, what needs review.

The page is fetched, boilerplate is stripped, and the article body is converted to clean Markdown. The honest limits are paywalls, login walls and app-shell pages.

includedPublic HTTPS sources

Public pages convert with dedicated reading methods for supported sources — you get the page body as Markdown.

reviewPaywalled & login pages

Content behind authentication is not converted — login-only sources report what could be fetched, nothing fabricated.

includedLinks

In-page links stay links — check important links and headings against the source page before reusing.

reviewApp-shell / JS-heavy pages

Pages that render content only after heavy client-side JS may capture less than a browser shows — compare on app-shell sites.

reviewPaginated & infinite-scroll pages

One Fetch handles one link. Multi-page articles only include what the fetched page exposes, and content loaded by scrolling may be absent — a snapshot is the page’s static body, not a full-site crawl.

reviewMedia & remote images

Remote images and linked assets are not downloaded — the Markdown keeps references the page exposed, not a media archive. Pages that are mostly galleries, video, or canvas produce thin output.

Format references: CommonMark · MDN HTML docs. GitHub/YouTube/Notion/HN URLs have dedicated converters with source-aware extraction.

URL to MD questions

What is a URL to MD converter?

URL to MD reads a public HTTPS source and produces a Markdown (.md) snapshot. Supported sources have dedicated reading methods; login-only or unavailable content is not converted.

Does the URL converter run JavaScript?

No. It uses a bounded static fetch — pages that only render content after client-side JavaScript, login, or interaction can come back thin or empty. Dedicated adapters for GitHub, Notion, Hacker News, Google Docs, and YouTube read through each source’s own structured access instead.

Can I fetch a paywalled or login-only page I have access to?

No. The fetcher never forwards your cookies, credentials, or customer headers. If access requires an account, payment, private network, or any bypass, use the file-upload converters with an export you own instead.

Is a converted snapshot a citable archive?

It is a dated record of what the bounded fetch could read at that moment — not a guarantee the page stays unchanged. Keep the source URL and fetch metadata in the bundle when citation or freshness matters.