Skip to content
Extraction tools

Turn a web page into plain text or Markdown

Paste a link. A server in the EU fetches the page, strips navigation, cookie notices and footers, and hands back the main content as text or Markdown with an estimated token count, so you know what it costs before it goes into a prompt.

Enter the URL of an article, a documentation page or a product page, then pick text or Markdown.

Observations, not verdicts. What you enter is processed for this result and written to a usage journal described in the privacy policy; nothing else is stored.

Website to text, without the browser

This is the fastest tool on the site because it does the least. The server requests the URL the way a plain HTTP client would, parses the HTML, decides which part of the document is the content and which part is furniture, and serialises the content as text or Markdown. No browser is launched and no script on the page runs, which is why a result comes back in well under a second for most pages and why some pages come back nearly empty.

Link to text: what gets kept

The content heuristic scores blocks of the document by text density, link density and position, the approach readability-style extractors have used for fifteen years. Headings, paragraphs, lists, block quotes, tables and code blocks inside the winning region are kept. The Markdown mode preserves their structure with ATX headings, GFM tables and fenced code; the text mode flattens them to paragraphs separated by blank lines. Menus, cookie notices, share bars, related-article rails and footers are dropped. Images are replaced by their alt text where one exists, and by nothing where it does not.

Page to text converter: the token estimate

The number beside the output is characters divided by four and is labelled an estimate on purpose. Tokenisers differ by model, and German text with long compound nouns tokenises worse than English. The estimate is there to catch the difference between a 2,000-token article and a 40,000-token forum thread before either reaches a context window, not to bill against.

What this tool cannot see

A page that renders its content with JavaScript after load, a page behind a login, a page that sends a consent wall instead of the article until a choice is made: all of these return a skeleton, because the server saw what a client without JavaScript sees. The result says so when the extracted content is suspiciously short relative to the HTML, and offers to open the same URL in the agent view, which loads it in a real browser, answers the cookie banner and reads the page the way an agent would. That path costs a browser session and takes a few seconds; this one costs nothing but a fetch.

It also does not transcribe. A link to a video, a podcast or a PDF returns the text that surrounds the media on the page, which is usually a title and a description. The media itself is not downloaded.

Nothing is kept

The fetched HTML and the extracted text exist for the duration of one request. A usage journal records that a fetch happened, when, and how large the response was, as the privacy policy describes; the URL you entered and the text that came back are not written anywhere.

Three steps from URL to text

  1. Paste the URL

    Any public http or https address. Redirects are followed; the final URL is shown with the result so you know which page was actually read.

  2. Pick text or Markdown

    Markdown keeps headings, lists, tables and links and is what you want for a prompt or a knowledge base. Text is for search indexes, diffing and anything that should not carry formatting.

  3. Copy, download, or open in the agent view

    The result can be copied or saved. If it is thin because the page needs JavaScript, the agent view button loads the same URL in a real EU browser and shows what an agent reads there.

Where the output usually goes

Into a prompt


Markdown with the boilerplate removed is the cheapest faithful representation of an article for a model. The token estimate tells you whether it fits before you paste.

Into a retrieval index


Plain text with headings kept as lines chunks cleanly. Navigation and footers, which would otherwise be retrieved for every query, are already gone.

Into a diff


Fetch the same URL twice, a week apart, and compare the text. Changes in the content show; changes in the theme, the menu or the ads do not.

Into a scheduled workflow


When the page needs a login or a browser, the same extraction runs inside a Browserberg session on a schedule, with the result posted to your endpoint.

Questions about extracting text from a website

How do I extract text from a website without copying and pasting?

Paste the URL above. The server fetches the page and returns the main content as text or Markdown, with the menus, cookie notice and footer already removed.

Does it work on pages that load content with JavaScript?

Not on its own: the server reads the HTML as sent, without running scripts. When the result looks thin, the tool offers to open the same URL in the agent view, which uses a real browser.

Can it convert a video link to text?

No. It returns the text on the page around the video, typically a title and a description. It does not download or transcribe audio or video.

How accurate is the token count?

It is characters divided by four and labelled an estimate. Real counts depend on the model's tokeniser and on the language; German usually needs more tokens per word than English.

Is the URL or the extracted text stored?

No. Both exist for one request. A usage journal keeps the time and the size of the fetch, nothing else.

What about pages behind a login?

The server has no account, so it sees the login page. For your own portals, a Browserberg session with a vaulted credential can log in and run the same extraction as a workflow step.

When the page needs a browser or a login

Five browser hours, no card. Run the same extraction inside a session that can sign in, answer the banner and wait for the script.